MeatMan Feb 17, 2016 @ 3:24pm
Blue Screen with "bugcode_usb_driver" PLEASE HELP
Hi, I was hoping someone could help me or give me advice about my problem. My computer was working fine until I installed a new CPU cooler yesterday to get rid of my very loud, older one. I was able to get new cooler in with some time and it all seemed to be working fine. I then tried to play a game and each time I play a game I get a blue screen after about 3 or 4 minutes. I do not know what to do about it anymore.

I have tried updating my drivers, changing the setting in game (I have a powerful PC), and other stuff I do not remember it was a long night last night. I then decided that a system restore would get rid of the problem if it was a software issue. I did a complete default restore and installed a game (RUST), played it, and the same thing happened.

Thanks for reading this hopefully someone can help me! I just have no idea how to fix this. I am guessing it may be a hardware problem now if I restored and it still happens. Thanks so much.

Here is the WhoCrashed analysis of my problem:

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 2/18/2016 12:35:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021716-17625-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x127D4)
Bugcheck code: 0xFE (0x5, 0xFFFFE000F03F91A0, 0x10024397, 0xFFFFE000EFE8B2D8)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Thu 2/18/2016 12:35:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x127D4)
Bugcheck code: 0xFE (0x5, 0xFFFFE000F03F91A0, 0x10024397, 0xFFFFE000EFE8B2D8)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion

--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
< >
Showing 1-15 of 34 comments
Revelene Feb 17, 2016 @ 3:29pm 
Sounds like you are having an issue with the USB 2.0 port that you have the new cooler connected to. Try another port.
MeatMan Feb 17, 2016 @ 3:30pm 
That would make sense, but the cooler is just plugged into the motherboard for power to the fan. It isnt plugged into any USB port.

Thanks for the respose
Last edited by MeatMan; Feb 17, 2016 @ 3:30pm
Revelene Feb 17, 2016 @ 3:34pm 
Originally posted by SauerPatchKids:
That would make sense, but the cooler is just plugged into the motherboard for power to the fan. It isnt plugged into any USB port.

Hmm.

You didn't change anything else in the system, other than the cooler? And it worked fine before the cooler swap?

If so, it could just be a coincidence or something was changed or messed with during the swap.
MeatMan Feb 17, 2016 @ 3:38pm 
Yeah nothing changed during the swap out other than the cooler. The only variable is that when taking out the cooler the CPU got stuck to the old cooler and came right out with the cooler. So I had to get some alcohol and sort of pull it off the bottom of that old cooler. Then I cleaned off the old thermal paste, put the CPU back in, and installed the new cooler.
MeatMan Feb 17, 2016 @ 3:41pm 
I can think of three possible things, but they dont really make sense with the errors...

1. The PSU isnt giving enough power to the system
OR
2. The new cooler isnt keeping it cool enough, but I started playing RUST and before it crashed I was watcing the temp of my CPU and it never went above 60C. So, not sure about this
OR
3. I ♥♥♥♥♥♥ up my CPU when it got pulled out and it is malfunction now.

But like right now I'm on my PC and it is fast and responsive so I dont know
Revelene Feb 17, 2016 @ 3:44pm 
Originally posted by SauerPatchKids:
Yeah nothing changed during the swap out other than the cooler. The only variable is that when taking out the cooler the CPU got stuck to the old cooler and came right out with the cooler. So I had to get some alcohol and sort of pull it off the bottom of that old cooler. Then I cleaned off the old thermal paste, put the CPU back in, and installed the new cooler.

The CPU should not have came out with the cooler... the only way I can see this happening is with an AMD cpu... and you must have unlocked it when pulling the cooler off.

Either way, this shouldn't matter as the only thing that could have really been damaged would be the CPU.. and you would be able to tell if it was.

You say you tried reinstalling drivers, how did you go about that process? You got them from your motherboard manufacturer's support webpage, yes?
MeatMan Feb 17, 2016 @ 3:56pm 
Yup I have all AMD stuff. and I know it shoudnt have came out I was scared ♥♥♥♥♥♥♥♥ when it did. the latch was not undone so it should have stayed in, but my roommate just pulled straight up and it came out. All the pins were in order and everything looked okay so I think the CPU is fine.

Yes so I installed MSI (my motherboard and graphics card maker), Updater 6 to do it and there really wasnt anything to update expect for some audio drivers. I double checked with my manufacturers website and the application had the numbers right so I thought everything was up to date. So I did those audio drivers and it didn't help, I tried this before the restore. Mind you I completely restored my computer and I have not updated since I restored.
Revelene Feb 17, 2016 @ 4:04pm 
Originally posted by SauerPatchKids:
Yup I have all AMD stuff. and I know it shoudnt have came out I was scared ♥♥♥♥♥♥♥♥ when it did. the latch was not undone so it should have stayed in, but my roommate just pulled straight up and it came out. All the pins were in order and everything looked okay so I think the CPU is fine.

Yes so I installed MSI (my motherboard and graphics card maker), Updater 6 to do it and there really wasnt anything to update expect for some audio drivers. I double checked with my manufacturers website and the application had the numbers right so I thought everything was up to date. So I did those audio drivers and it didn't help, I tried this before the restore. Mind you I completely restored my computer and I have not updated since I restored.

Hopefully the CPU and motherboard were not damaged.

Have you tried a dedicated CPU stress test?
MeatMan Feb 17, 2016 @ 4:11pm 
We can only hope it isnt damaged haha.
No I have not tried that a stress test. How do I do that?
Revelene Feb 17, 2016 @ 4:33pm 
Originally posted by SauerPatchKids:
We can only hope it isnt damaged haha.
No I have not tried that a stress test. How do I do that?

I mainly use AIDA64.

The reason why I would like you to try it is because it can help take CPU damage out of the equation. It'll run the CPU at max load, using a contant stream of complex calculations.

Also, did you wiggle the CPU when you put it back into the slot? Hopefully it wasn't loose, though if it passes a stress test you should be golden.
MeatMan Feb 17, 2016 @ 4:34pm 
I did it was solidly in there from what i remember when i put it back in. I will try this test and tell you how it goes.
Revelene Feb 17, 2016 @ 4:42pm 
Originally posted by SauerPatchKids:
I did it was solidly in there from what i remember when i put it back in. I will try this test and tell you how it goes.

AIDA64 is a paid program, but they have a free trial.

The stress test is located under Tools > System Stability Check. It is a continuous test, so it does not end. It tests full system stability under full load, so check what you want to test and press start.

Once you know that it is at least stable (aka not damaged), then just run FPU to get the CPU to push some heat and test that new cooler.

Do you overclock? These stress tests and system stability tests are key for overclocking as well.
MeatMan Feb 17, 2016 @ 4:42pm 
I dont think the CPU being damaged is the problem, I am five minutes into the stress test for it and everything is fine and its only at 55C degrees.
MeatMan Feb 17, 2016 @ 4:44pm 
No i dont overclock, I am stressing the FPU right now its at 62 degrees
MeatMan Feb 17, 2016 @ 4:49pm 
Ill be back in a few hours, but so far everything has been just fine. Ill tell you when Im back. If you think of anything for me to try post it here.

Thanks so much.
< >
Showing 1-15 of 34 comments
Per page: 1530 50

Date Posted: Feb 17, 2016 @ 3:24pm
Posts: 34