npusb.sys BSOD during hardware install
Posted: Fri Feb 03, 2006 11:58 pm
serial number: 44141
Ok, I know there's nothing wrong with this TIR4 (bought to replace the TIR1 gathering dust down the back of my desk where it fell after I gave up struggling with its unreliable tracking
because I've tested it on this PC and can immediately see things have improved a lot since the TIR1.
However this PC is for general dull stuff, not the important things in life. On my games box everything goes fine until I plug in the TIR, it gets detected as a TIR4, and the driver installation begins.
I get as far as "install the hardware automatically", then the "this hasn't passed Windows Logo testing" window, hit "continue anyway", a dialogue box pops up very briefly with a progress bar which goes very quickly to the end, then up pops the extremely rare XP BSOD refering to npusb.sys at the bottom of the screen (it doesn't last long enough to read much more).
The PC reboots OK but I've now tried several combinations of de-installing, re-installing, registry fixing (using NPRegFix), and sacrificing small goats.
However I've had no luck, plenty of BSODs, and now I've run out of goats and the neighbour's cat is looking nervous, so I thought I'd just post here before I head for bed... or is it work? Mmm, time flies when you're having fun!
Obviously there's something wrong with my games PC, and I'm not expecting a fix short of "reinstall windows" and try again. However I've only recently (2 months ago) reinstalled everything onto a new HD and it seemed to be working very happily until this morning.
That means nothing with PCs though, I appreciate that.
Anyway, if anyone has any suggestions, let me know. However I'm pretty much resigned to it being another of those mysterious PC illnesses which make tech support such an enjoyable occupation and leads to increased sales in XBoxes.
Andrew McP
PS FWIW my motherboard is a DFI Ultra Infinity NF2 chipset, and I'm using the onboard USB. Processor (Barton mobile XP2500) & RAM are running at very stable default values for video editing at the moment... no thrashing for maximum frame rates.
[ February 04, 2006, 07:00 AM: Message edited by: Andrew McP ]
Ok, I know there's nothing wrong with this TIR4 (bought to replace the TIR1 gathering dust down the back of my desk where it fell after I gave up struggling with its unreliable tracking

However this PC is for general dull stuff, not the important things in life. On my games box everything goes fine until I plug in the TIR, it gets detected as a TIR4, and the driver installation begins.
I get as far as "install the hardware automatically", then the "this hasn't passed Windows Logo testing" window, hit "continue anyway", a dialogue box pops up very briefly with a progress bar which goes very quickly to the end, then up pops the extremely rare XP BSOD refering to npusb.sys at the bottom of the screen (it doesn't last long enough to read much more).
The PC reboots OK but I've now tried several combinations of de-installing, re-installing, registry fixing (using NPRegFix), and sacrificing small goats.
However I've had no luck, plenty of BSODs, and now I've run out of goats and the neighbour's cat is looking nervous, so I thought I'd just post here before I head for bed... or is it work? Mmm, time flies when you're having fun!

Obviously there's something wrong with my games PC, and I'm not expecting a fix short of "reinstall windows" and try again. However I've only recently (2 months ago) reinstalled everything onto a new HD and it seemed to be working very happily until this morning.
That means nothing with PCs though, I appreciate that.
Anyway, if anyone has any suggestions, let me know. However I'm pretty much resigned to it being another of those mysterious PC illnesses which make tech support such an enjoyable occupation and leads to increased sales in XBoxes.
Andrew McP
PS FWIW my motherboard is a DFI Ultra Infinity NF2 chipset, and I'm using the onboard USB. Processor (Barton mobile XP2500) & RAM are running at very stable default values for video editing at the moment... no thrashing for maximum frame rates.
[ February 04, 2006, 07:00 AM: Message edited by: Andrew McP ]