Log in

View Full Version : Blue Screen 'bugcode_usb_driver'


Maverick
April 22nd, 2012, 03:23 PM
Sometimes on my laptop running windows 7 I get a blue screen error with 'bugcode_usb_driver'

It never really happens while I'm using it but I notice if I leave the computer idle for a good while and come back it will have the blue screen. For the most part it never happens but its frequent enough. Any ideas on what I can do to fix it? Its a fairly new laptop.

Rayquaza
April 22nd, 2012, 03:53 PM
I was looking at this thread from the Microsoft Website;
http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/bugcodeusbdriver-blue-screen-of-death/13172ae7-44d6-4790-9b07-c7080908eb38

It seems that it was either due to a faulty driver or an update. Have you tried reinstalling, updating or removing some of the drivers of your display devices? Have a look in the Device Manager.

Also, have you plugged in incompatible hardware for your computer?
[http://social.technet.microsoft.com/Forums/en/w7itproperf/thread/d69d6866-a157-416a-b5b9-5245f1889560]
According to this website, that could be the case aswell.

DerBear
April 22nd, 2012, 05:30 PM
Well we had something similar to happen on one of our desktops a few weeks ago.

We found it was primarily to do with updates. One of our updates for our drivers never installed properly and it was causing a blue screen and we had to shut it down.

I can only suggest you re-install your device.

This probably wasn't helpful because this area is not in anyway my expertise.

FojeJC
April 22nd, 2012, 06:06 PM
Arrrrggggghhhhh!?! Not the blue screen of DEATH!!!

But seriously, obviously a driver update or failure problem, I suggest using dps (Driverpack Solution), it updates or gives you any driver you need, and its not a scam. If this doesn't fix it then using the power options make your laptop sleep after a 2 minutes of being idle.

TheMatrix
April 22nd, 2012, 11:30 PM
(It's what you get for using Windoze :P)

I think that the cause is a badly written driver expecting a signal from a (currently idle) keyboard(or mouse), but that never comes. So, it times out, and there is no proper error handler for that, so you get BSoD(which makes for an excellent xscreensaver in the Linux world, btw :P).
What I suggest you do: try finding a driver update -- not necessarily the official ones if you notice those don't work. Often times there may be a generic driver available that may or may not work with your hardware. If it's open source, then that's even better, and should work unless you have some really rare hardware.

If it's not that, then try disconnecting any non-vital peripherals(printers are also big culprits). If that works, you know the problem lies in the driver of a peripheral. You will probably need to spend a weekend trying to figure out which peripherals are causing issues, conflict, etc. Have fun with that, but don't forget to brew lots of coffee -- you will need it.