Windows 7 USB Bug Code

[solidbarton]

Hey guys,

After scouring the internet for several days, I have come to the point of asking for help. I've been getting a USB Bug Code BSOD and have tried several different remedies and suggestions to no avail. Attached is my grab it files Link Removed. Any suggestions/comments/recommadations would be greatly appreciated! Sorry about the hastiness of the post, I'm on my way into work, but will be able to check and update periodically. Thanks again!

 

[solidbarton]

So here is what has been happening. Starting about a month ago, I've been getting the USB bug code bsod, at first during games of league of legends but recently hs been happening in windows 7 desktop.

I've tried reinstalling the USB bus host, the USB controllers, and even bought a cheap PCI to USB expansion caed which crashed too, and is the most recent mini dump in my attachment (the other two are from my mobo USB slots).

I don't know what to do at this point. Please advise!

 

[Saltgrass]

The dump file seems to be point at USBOHCI.sys, which is the USB Open Hub Controller Interface.

I am not the expert here, so use my info if you can... guesses are just guesses.

You have many USB devices on your system, like xBox and Android. There may be a situation where the USB power is being overloaded. If you have an external, powered hub, it might not be relevant.

Have you tried disconnecting all devices you are not currently using to see if it helps?

In the bios, you might check some of the settings for the USB devices. If you were to see something like EHCI hand off or some other setting, you might try changing one at time for testing.

You might also open an Administrative command prompt and type SFC /scannow to check your system files. Let us know if it finishes without non-repairable items.

 

[solidbarton]

The dump file seems to be point at USBOHCI.sys, which is the USB Open Hub Controller Interface.

I am not the expert here, so use my info if you can... guesses are just guesses.

You have many USB devices on your system, like xBox and Android. There may be a situation where the USB power is being overloaded. If you have an external, powered hub, it might not be relevant.

Have you tried disconnecting all devices you are not currently using to see if it helps?

In the bios, you might check some of the settings for the USB devices. If you were to see something like EHCI hand off or some other setting, you might try changing one at time for testing.

You might also open an Administrative command prompt and type SFC /scannow to check your system files. Let us know if it finishes without non-repairable items.

Thanks for the reply. As for the connected devices, when the crashes occur recently, I've had everything removed but my USB mouse, keyboard, and headset. I don't have a ps/2 mouse or keyboard so I need those plugged in.

For that sfc scan now command, i did run that before I posted and it did come up with something so I restarted and I thought it may have fixed it, but alas it still bsod.

 

[BIGBEARJEDI]

hi solidbarton: I was just looking over your BSOD issues and your system specs, and I noticed something that may help you. Besides the possible USB overloading problem, I noticed that your C: drive is over 3/4 full, and in fact is about 77% full. When any version of Windows gets to about 85% full on the boot drive you can begin to experience performance problems including freezing, halting, slower disk access time means longer program app load times, and of course the dreaded BSODs. Technically, you are not in the "Red" zone of 85% or higher, but I would certainly be aware that you are only 8% away from the "Red" zone on disk usage on your boot drive. In the old days of Windows98/Win2k we used to worry when we got above 75%-80%. Where you are at now. I see you have other much larger drives/partitions, you might consider rebuilding your system to utilize some of that extra space to give Windows some "breathing" room. In commercial environments we tried to keep at least 25% free space on all user's boot drives just to prevent these types of problems from occurring. If you download a couple of 3 hour movie files in MPEG4 onto that boot drive, you could easily be in the "Red Zone", and begin experiencing random crashes if you don't immediately move those files off onto one of your other drives. Just sayin.

I'm not seeing too many Win7 boot drives setup for less than 100GB total, which you have in a desktop, let alone a laptop where you might not have a choice on your boot drive size; you might want to remedy this if your BSODs continue.

Best of luck.

BIGBEARJEDI

 

[usasma]

Please do what Saltgrass and BIGBEARJEDI have suggested before trying my fixes/suggestions.

Here's what I got from the reports:

SP1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates (may take repeated visits)
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates. May take repeated visits, but keep it up until you get several "Windows is updated" results.
If you're having difficulties with installing a Service Pack, please use the SURTool from this link: What is the System Update Readiness Tool?
Also, check out this troubleshooting link from Microsoft: Troubleshoot problems installing Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2

I have had limited success in installing updates/Service Packs when using a "clean boot". I suspect that I'm just bypassing the problem - and that it can come back to bite me in the butt later on.

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956
27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.

This device is disabled. Is this deliberate? If so, why?

PCI Input Device PCI\VEN_1102&DEV_7003&SUBSYS_00401102&REV_04\4&35E69562&0&31A4 This device is disabled.

It is most likely a Creative Game Port device (?associated with your Creative Sound Card?)

The WER section of MSINFO32 shows several BSOD's that blame USB (as you already know)

MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's in some Windows systems. Please un-install it immediately!

If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

Although you have physically removed the USB devices, this doesn't prevent the drivers from loading - and it's the drivers that are usually the problem when you have a BSOD. The wireless XBox controller driver (xusb21.sys) is a known cause of BSOD's on Windows systems - and there are no updated drivers available for it. Please:
- Physically remove the XBox controller from the system
- Un-install the software for the wireless XBox controller
- monitor for further BSOD's

Finally, we're starting to see more BSOD's in systems with older Creative drivers. While not a pattern yet, it's advisable to update the Creative cards to drivers that were released after Win7 SP1 was released. If these drivers aren't available, test by removing the Creative card and un-installing the software/drivers for the card.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

emupia2k.sys Mon Apr 9 09:08:10 2007 (461A3ABA)
Creative E-mu Plug-in Architecture Driver
Link Removed

ctsfm2k.sys Mon Apr 9 09:08:11 2007 (461A3ABB)
Creative SoundFont Management Device Driver
Link Removed

ctoss2k.sys Mon Apr 9 09:08:14 2007 (461A3ABE)
Creative OS Services Driver
Link Removed

ha10kx2k.sys Mon Apr 9 09:08:15 2007 (461A3ABF)
Creative Hardware Abstract Layer Driver
Link Removed

hap16v2k.sys Mon Apr 9 09:08:17 2007 (461A3AC1)
Creative Audio card drivers
Link Removed

ctaud2k.sys Mon Apr 9 09:08:29 2007 (461A3ACD)
Creative Audio Driver (WDM)
Link Removed

ctprxy2k.sys Mon Apr 9 09:08:30 2007 (461A3ACE)
Creative Audio Driver (WDM)
Link Removed

COMMONFX.DLL Mon Apr 9 09:08:38 2007 (461A3AD6)
Creative Common FX Plug-in
Link Removed

CTAUDFX.DLL Mon Apr 9 09:08:39 2007 (461A3AD7)
Creative Audio Driver (WDM)
Link Removed

CTSBLFX.DLL Mon Apr 9 09:08:42 2007 (461A3ADA)
Creative SB FX Plug-in
Link Removed

Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Fri Mar 22 11:13:21.290 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032213-10873-01.dmp]
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
[B][COLOR=RED]Missing Windows 7 Service Pack 1[/COLOR][/B]
Built by: [B]7600[/B].17207.amd64fre.win7_gdr.130104-1435
System Uptime:[B]0 days 0:07:37.648[/B]
*** ERROR: Module load completed but symbols could not be loaded for usbuhci.sys
Probably caused by :[B]usbuhci.sys ( usbuhci+60f7 )[/B]
BugCheck [B]D1, {c006cba5f0, 2, 1, fffff880043410f7}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 000000c006cba5f0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880043410f7, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_usbuhci+60f7[/B]
  BIOS Version                  F12
  BIOS Release Date             03/22/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-MA770T-UD3P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Mar 20 22:22:34.718 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032013-9937-01.dmp]
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
[B][COLOR=RED]Missing Windows 7 Service Pack 1[/COLOR][/B]
Built by: [B]7600[/B].17207.amd64fre.win7_gdr.130104-1435
System Uptime:[B]0 days 1:31:16.076[/B]
*** WARNING: Unable to verify timestamp for usbohci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
Probably caused by :[B]usbohci.sys ( usbohci+1ed9 )[/B]
BugCheck [B]FE, {5, fffffa800800f1a0, 10024398, fffffa80075baf68}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
    using a physical memory address that was not allocated by
    the USBport driver.
Arg2: fffffa800800f1a0, Device extension pointer of the host controller
Arg3: 0000000010024398, PCI Vendor,Product id for the controller
Arg4: fffffa80075baf68, Pointer to Endpoint data structure
BUGCHECK_STR:  0xFE
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xFE_INVALID_PHYSICAL_ADDR_usbohci+1ed9[/B]
  BIOS Version                  F12
  BIOS Release Date             03/22/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-MA770T-UD3P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar 18 20:42:14.430 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031813-11559-01.dmp]
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
[B][COLOR=RED]Missing Windows 7 Service Pack 1[/COLOR][/B]
Built by: [B]7600[/B].17207.amd64fre.win7_gdr.130104-1435
System Uptime:[B]0 days 3:19:05.788[/B]
*** WARNING: Unable to verify timestamp for usbohci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
Probably caused by :[B]usbohci.sys ( usbohci+1ed9 )[/B]
BugCheck [B]FE, {5, fffffa8007d941a0, 10024398, fffffa800abe7258}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
    using a physical memory address that was not allocated by
    the USBport driver.
Arg2: fffffa8007d941a0, Device extension pointer of the host controller
Arg3: 0000000010024398, PCI Vendor,Product id for the controller
Arg4: fffffa800abe7258, Pointer to Endpoint data structure
BUGCHECK_STR:  0xFE
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xFE_INVALID_PHYSICAL_ADDR_usbohci+1ed9[/B]
  BIOS Version                  F12
  BIOS Release Date             03/22/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-MA770T-UD3P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Fri Mar 22 11:13:21.290 2013 (UTC - 4:00)**************************
[COLOR=RED][B]emupia2k.sys                Mon Apr  9 09:08:10 2007 (461A3ABA)[/B][/COLOR]
[COLOR=RED][B]ctsfm2k.sys                 Mon Apr  9 09:08:11 2007 (461A3ABB)[/B][/COLOR]
[COLOR=RED][B]ctoss2k.sys                 Mon Apr  9 09:08:14 2007 (461A3ABE)[/B][/COLOR]
[COLOR=RED][B]ha10kx2k.sys                Mon Apr  9 09:08:15 2007 (461A3ABF)[/B][/COLOR]
[COLOR=RED][B]hap16v2k.sys                Mon Apr  9 09:08:17 2007 (461A3AC1)[/B][/COLOR]
[COLOR=RED][B]ctaud2k.sys                 Mon Apr  9 09:08:29 2007 (461A3ACD)[/B][/COLOR]
[COLOR=RED][B]ctprxy2k.sys                Mon Apr  9 09:08:30 2007 (461A3ACE)[/B][/COLOR]
[COLOR=RED][B]COMMONFX.DLL                Mon Apr  9 09:08:38 2007 (461A3AD6)[/B][/COLOR]
[COLOR=RED][B]CTAUDFX.DLL                 Mon Apr  9 09:08:39 2007 (461A3AD7)[/B][/COLOR]
[COLOR=RED][B]CTSBLFX.DLL                 Mon Apr  9 09:08:42 2007 (461A3ADA)[/B][/COLOR]
[COLOR=RED][B]Rt64win7.sys                Thu Feb 26 04:04:13 2009 (49A65B0D)[/B][/COLOR]
[COLOR=RED][B]xusb21.sys                  Wed Apr  8 10:28:44 2009 (49DCB49C)[/B][/COLOR]
vpcnfltr.sys                Tue Sep 22 21:32:30 2009 (4AB97AAE)
vpchbus.sys                 Tue Sep 22 21:32:32 2009 (4AB97AB0)
vpcvmm.sys                  Tue Sep 22 21:32:38 2009 (4AB97AB6)
vpcusb.sys                  Tue Sep 22 21:32:39 2009 (4AB97AB7)
LGVirHid.sys                Mon Nov 23 20:36:48 2009 (4B0B38B0)
LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
ElbyCDIO.sys                Thu Dec 16 17:58:13 2010 (4D0A9985)
VClone.sys                  Sat Jan 15 11:21:04 2011 (4D31C970)
[COLOR=RED][B]RTCore64.sys                Tue Sep  6 08:24:50 2011 (4E661112)[/B][/COLOR]
PLTGC.sys                   Wed Mar 28 04:09:30 2012 (4F72C73A)
LGSHidFilt.Sys              Wed Aug 22 18:27:24 2012 (50355CCC)
MpFilter.sys                Wed Oct 31 18:43:06 2012 (5091A97A)
nvhda64v.sys                Wed Dec 19 00:41:41 2012 (50D15395)
HWiNFO64A.SYS               Sat Jan 26 07:28:11 2013 (5103CBDB)
nvlddmkm.sys                Thu Mar 14 03:29:32 2013 (51417C5C)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[solidbarton]

Oh man, thank you guys for all of these recommendations! Looks like I have a lot of work ahead of me, and will keep updating this thread as I learn more! Thanks again!