Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD with "usbhub.sys" and "driver power state failure"

10 May 2010   #1
Kraut55

WIN 7
 
 
BSOD with "usbhub.sys" and "driver power state failure"

I have been getting the BSOD since a few weeks and found out by trial and error that a USB-hub is causing the problem. Whenever I disconnect the hub before I shut off the computer I do not get the blue screen.
Yesterday I also got a BSOD that mentioned driver power state failure. After I had de-installed Ubuntu 10.04 (I wanted to see what people are talking about but did not really like it) that problem did not show up again, although I do not know if that is just coincidence.

I have enclosed the dump files as per your instructions and hope that somebody will be able to help me.
Thank you.


My System SpecsSystem Spec
.
10 May 2010   #2
Jonathan_King

Windows 7 Professional x64
 
 

Welcome!

It does look as if your USB drivers are causing the issue.


BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed Apr 28 03:41:32.255 2010 (GMT-4)
System Uptime: 0 days 0:31:47.502
BugCheck 1000007E, {c0000005, 9482319c, ad39bb40, ad39b720}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+428c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon May 10 03:46:15.009 2010 (GMT-4)
System Uptime: 0 days 0:00:15.272
BugCheck 124, {0, 8752f544, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon May 10 05:22:31.146 2010 (GMT-4)
System Uptime: 0 days 0:02:23.393
BugCheck 1000007E, {c0000005, 9444b19c, adb53b40, adb53720}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+428c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun May  9 16:04:28.103 2010 (GMT-4)
System Uptime: 0 days 0:14:08.365
BugCheck 9F, {4, 258, 863e9798, 83943b24}
Probably caused by : WUDFRd.sys ( WUDFRd!RdDevice::MarkForDelete+15 )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun May  9 16:35:12.200 2010 (GMT-4)
System Uptime: 0 days 0:13:06.447
BugCheck 9F, {4, 258, 86403020, 8396ab24}
Probably caused by : WUDFRd.sys ( WUDFRd!RdDevice::MarkForDelete+15 )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat May  8 08:41:03.887 2010 (GMT-4)
System Uptime: 0 days 4:47:33.010
BugCheck 1000007E, {c0000005, 9467919c, b3f10b40, b3f10720}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+428c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat May  1 18:44:19.351 2010 (GMT-4)
System Uptime: 0 days 14:50:58.598
BugCheck 1000007E, {c0000005, 9443619c, adf69b40, adf69720}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+428c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu Apr 29 04:59:54.140 2010 (GMT-4)
System Uptime: 0 days 1:25:46.402
BugCheck 1000007E, {c0000005, 9467f19c, ad7d9b40, ad7d9720}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+428c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Apr 27 18:42:43.646 2010 (GMT-4)
System Uptime: 0 days 4:02:53.908
BugCheck 7E, {c0000005, 9442a19c, afaf7b40, afaf7720}
Probably caused by : ntkrpamp.exe ( nt!PoIdle+538 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
  
  
I suggest updating your USB drivers via Device Manager.
My System SpecsSystem Spec
10 May 2010   #3
Kraut55

WIN 7
 
 

I checked all the USB controllers below and Windows confirmed that for all the best drivers were already installed.



As I received the BSOD again I have included the latest dumps, just in case.
My System SpecsSystem Spec
.

10 May 2010   #4
Jonathan_King

Windows 7 Professional x64
 
 

The latest drivers may be installed, but perhaps they are corrupted. Uninstall them and reboot; the new ones should be automatically installed.
My System SpecsSystem Spec
10 May 2010   #5
Kraut55

WIN 7
 
 

Did that.
No more exclamation marks, everything reinstalled but no change.
My System SpecsSystem Spec
10 May 2010   #6
Jonathan_King

Windows 7 Professional x64
 
 

This one is a 124 hardware error. See this article on what it is and how to fix it: https://www.sevenforums.com/crash-loc...-what-try.html

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_Seven Forums.zip\Seven Forums\Minidumps\051010-32994-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x8384a000 PsLoadedModuleList = 0x83992810
Debug session time: Mon May 10 03:46:15.009 2010 (GMT-4)
System Uptime: 0 days 0:00:15.272
Loading Kernel Symbols
......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 8752f544, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 BSOD with "usbhub.sys" and "driver power state failure"




Thread Tools




Similar help and support threads
Thread Forum
BSOD - ntoskrnl.exe "driver power state failure" at shutdown
I'm getting a BSOD pretty much every time I shutdown the PC. Has only just started happening in the last couple of weeks. DRIVER_POWER_STATE_FAILURE caused by driver: ntoskrnl.exe I've attached the SFDiagnostic here - thanks.
BSOD Help and Support
BSOD after sleep or hibernation - "Driver Power State Failure"
Hello, I left my computer on and open this morning before I left for class. When I returned, I had a BSOD, which specified "Driver Power State Failure" (I did not copy down any numbers, as I probably should have). I did a forced shut down (held the power button) and then restarted it, where it...
BSOD Help and Support
Frequent BSOD "Driver Power State Failure," No pattern that I see
My Alienware M17x suffers daily, random BSODs, I think most are Driver Power State Failures. These persist when I re-install my NVIDIA drivers (I even tried using Driver Fusion to get a clean install), but they do seem more frequent with the recent beta drivers. Maybe it's my Intel display...
BSOD Help and Support
BSOD "Driver power state failure" caused by: ntoskrnl.exe
Hi Folks, I really hope you can help me, I followed the instructions to create the attachement. What I know so far is that this machine has BSOD'd several times...The last 2 times a ultilty called BlueScreenViewer.exe says it's due to "Driver power state failure" caused by: ntoskrnl.exe ...
BSOD Help and Support
BSOD when going sleep mode "DRIVER POWER STATE FAILURE"
Hi, i keep having this issue. Anyone knows how to solve? My minidump is https://skydrive.live.com/#cid=392FCBBA17F5ACA1&id=392FCBBA17F5ACA1%21187
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 08:10.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App