Getting BUGCODE_USB_DRIVER BSOD's

[gerdgoebel]

I have a Lenovi T61 with a clean install of W7 Pro 32 with all latest patches. Connected to the T61 is a Lenovo USB DVD ROM, a LaCie 1.5TB USB drive and a Belkin KVM switch. Those 3 devices were connected when I installed W7.

Several times a week i get a BSOD with the following information:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: fe
BCP1: 00000008
BCP2: 00000006
BCP3: 00000005
BCP4: 8B1F3D88
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\030910-115362-01.dmp
C:\Windows\Temp\WER-120869-0.sysdata.xml

After this seems to be USB related I went into the device manager and deleted all the USB devices i could find, then let W7 recreate those again, what it did. All the USB devices work correctly.

One of the suggestions in the Alert Manager was to switch off the power settings for USB devices. I did that but got another BSOD this morning.

I zipped the 2 files created.

I checked the forum, found numerous similar BSOD's but none of them was what the problem seems to be on my system.

I hope that somebody can help me identifying what the problem is and how to resolve it.

 

[Jonathan_King]

I haven't even looked at the dmps, but I can guess what's in them.

Try downloading the latest chipset and USB drivers from here: Lenovo Support & downloads - Drivers and software - ThinkPad T61, T61p

 

[gerdgoebel]

I have all of those

I should have mentioned it, i run Lenovo system update 4 regularly. I have all the latest W7 drivers that system update detected.
I also check this web-site for new drivers as well as sometimes there are new drivers that don't show up in system update.
This is the Lenovo link for the T61 that include the W7 drivers
http://www-307.ibm.com/pc/support/site.wss/product.do?template=/product.do?template=%2Fproductpage%2Flandingpages%2FproductPageLandingPage.vm&sitestyle=lenovo&brandind=10&familyind=370153&machineind=370168&modelind=0&partnumberind=0&subcategoryind=0&doctypeind=9&doccategoryind=0&operatingsystemind=466746&validate=true

 

[zigzag3143]

I have a Lenovi T61 with a clean install of W7 Pro 32 with all latest patches. Connected to the T61 is a Lenovo USB DVD ROM, a LaCie 1.5TB USB drive and a Belkin KVM switch. Those 3 devices were connected when I installed W7.

Several times a week i get a BSOD with the following information:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: fe
BCP1: 00000008
BCP2: 00000006
BCP3: 00000005
BCP4: 8B1F3D88
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\030910-115362-01.dmp
C:\Windows\Temp\WER-120869-0.sysdata.xml

After this seems to be USB related I went into the device manager and deleted all the USB devices i could find, then let W7 recreate those again, what it did. All the USB devices work correctly.

One of the suggestions in the Alert Manager was to switch off the power settings for USB devices. I did that but got another BSOD this morning.

I zipped the 2 files created.

I checked the forum, found numerous similar BSOD's but none of them was what the problem seems to be on my system.

I hope that somebody can help me identifying what the problem is and how to resolve it.

This crash was caused by your USBHUB.sys I would uninstall the current one and dl and install a fresh copy.

I would also run a system file check
(type cmd in search>right click and run as admiin>sfc /scannow)

Good luck and let us know if you need help

Also your version is rather odd. where did you get it? It doesnt use any of the same symbols as the other versions

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\030910-115362-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82c39000 PsLoadedModuleList = 0x82d81810
Debug session time: Tue Mar  9 10:43:18.025 2010 (GMT-5)
System Uptime: 0 days 14:46:40.323
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
.............
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 00000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 00000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: 8b1f3d88, TimeoutContext - PortData

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: usbhub

FAULTING_MODULE: 82c39000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc8a6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82910aed to 82d15e10

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8d927ca4 82910aed 000000fe 00000008 00000006 nt+0xdce10
8d927cc0 828f9e2b 9c560028 00000005 8b1f3d88 usbhub!UsbhTrapFatalTimeout_x9f+0x28
8d927cec 82e597b5 9c560028 8b1f3d88 857bed48 usbhub!UsbhHubProcessChangeWorker+0xa2
8d927d00 82ca702b 9c5687e0 00000000 857bed48 nt+0x2207b5
8d927d50 82e4766d 00000001 a610303d 00000000 nt+0x6e02b
8d927d90 82cf91d9 82ca6f1e 00000001 00000000 nt+0x20e66d
00000000 00000000 00000000 00000000 00000000 nt+0xc01d9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbhub!UsbhTrapFatalTimeout_x9f+28
82910aed cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  usbhub!UsbhTrapFatalTimeout_x9f+28

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  usbhub.sys

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------

 

[gerdgoebel]

Usbhub.sys

My USBHUB.SYS is version 6.1.7600.16385. I found a newer version 6.1.7600.20521 on the MS support site and have requested that hotfix. Once I get it how to i install it? you mentioned to uninstall it and re-install a fresh copy. I normally do a right click on device manager to select/update a driver, but where is this driver being used?

I also don't know what you mean with "version is rather odd". Are you referring to the W7 version? I loaded W7 from an upgrade DVD that i purchased from MS. After the install i used windows update to download all critical patches.

sfc /scannow did not find any errors.

 

[Brainer]

Remove these devices before installing

One other suggestion thing I'll add in. I know this may not apply now, and I'm not trying to be
rude/sarcastic etc.

However, make sure to disconnect all those devices before installing Windows. IIRC, it's actually
in the Win 7 Installation readme file.

I've found things work much better when I do.


Brainer

I have a Lenovi T61 with a clean install of W7 Pro 32 with all latest patches. Connected to the T61 is a Lenovo USB DVD ROM, a LaCie 1.5TB USB drive and a Belkin KVM switch. Those 3 devices were connected when I installed W7.

Several times a week i get a BSOD with the following information:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: fe
BCP1: 00000008
BCP2: 00000006
BCP3: 00000005
BCP4: 8B1F3D88
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\030910-115362-01.dmp
C:\Windows\Temp\WER-120869-0.sysdata.xml

After this seems to be USB related I went into the device manager and deleted all the USB devices i could find, then let W7 recreate those again, what it did. All the USB devices work correctly.

One of the suggestions in the Alert Manager was to switch off the power settings for USB devices. I did that but got another BSOD this morning.

I zipped the 2 files created.

I checked the forum, found numerous similar BSOD's but none of them was what the problem seems to be on my system.

I hope that somebody can help me identifying what the problem is and how to resolve it.

 

[gerdgoebel]

Got the hotfix from MS

I got the hotfix (KB974476) from MS and have installed it. The USBHUB.SYS driver is not at version 6.1.7600.20521.
Let's see if this resolves the problem.

zigzag3143, could you tell me what "odd version" you are referring to?

 

[gerdgoebel]

Getting hopeful: no BSOD yet.

 

[Jonathan_King]

Great, thanks for keeping us posted.

 

[gerdgoebel]

well, i was too optimistic. I got another BSOD, but the last code is different this time.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: fe
BCP1: 00000008
BCP2: 00000006
BCP3: 00000005
BCP4: 9C5C93B0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\031110-115752-01.dmp
C:\Windows\Temp\WER-119683-0.sysdata.xml

 

[gerdgoebel]

I finally called MS tech support to find out what the problem is. According to the tech the ntkrnlpa.exe
did not have a valid timestamp. According to him this caused the BSOD and that those symbols could not be loaded.
The file has been corrected but let see if this resolves the issue.