POWER_STATE_FAILURE BSOD Possibly Due To Graphics Driver?

Hello,

My computer, at random times BSOD's on me and the error report has points back to a driver causing a power state failure. I tried going through all of my devices and updating the driver's but the crash is persistent. My graphics card is an ATI Mobility Radeon HD 5730. Something interesting to note is that after I tried updating the driver, the ATI CCC "Catalyst Control Center" would not open.

My machine is about a year old and I am still running Windows 7 Home Premium OEM.

All the required information is attached.

Thank you for your help.

ninemas said:

Hello,

My computer, at random times BSOD's on me and the error report has points back to a driver causing a power state failure. I tried going through all of my devices and updating the driver's but the crash is persistent. My graphics card is an ATI Mobility Radeon HD 5730. Something interesting to note is that after I tried updating the driver, the ATI CCC "Catalyst Control Center" would not open.

My machine is about a year old and I am still running Windows 7 Home Premium OEM.

All the required information is attached.

Thank you for your help.

This one was blamed on your USBHUB.SYS

Read this tutorial USB Driver - General Fix for Problems

Code:

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


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

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`03254650
Debug session time: Fri May 27 14:57:26.230 2011 (GMT-4)
System Uptime: 0 days 4:13:23.276
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006d4c440, fffff80000b9c518, fffffa800558b680}

Probably caused by : usbhub.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006d4c440, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800558b680, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800558b680

DEVICE_OBJECT: fffffa8006d4c440

DRIVER_OBJECT: fffffa8006e64550

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c15

MODULE_NAME: usbhub

FAULTING_MODULE: fffff880060d8000 usbhub

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800030fb9c2 to fffff8000308ed00

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`030fb9c2 : 00000000`0000009f 00000000`00000003 fffffa80`06d4c440 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`0309a652 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`0309a4f6 : fffffa80`086d5168 fffffa80`086d5168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0309a3de : 00000023`65dbf30f fffff800`00b9cc58 00000000`000edee2 fffff800`03205ec8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0309a1c7 : 00000005`fa1e6cc4 00000005`000edee2 00000005`fa1e6cb2 00000000`000000e2 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03086a2a : fffff800`03201e80 fffff800`0320fcc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_usbhub.sys

BUCKET_ID:  X64_0x9F_IMAGE_usbhub.sys

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

I followed through with the tut. I'll keep you posted if another crash occurs.
Thanks for the help!

My screen went white followed by black ripples of color going through it. I downloaded a program called WhoCrashed and here are the reports:


crash dump file: C:\Windows\Minidump\052811-15412-01.dmp
uptime: 01:35:53
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8007B2B060, 0xFFFFF80000B9C518, 0xFFFFFA8009202B80)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

crash dump file: C:\Windows\memory.dmp
uptime: 01:35:53
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8007B2B060, 0xFFFFF80000B9C518, 0xFFFFFA8009202B80)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Ive attached another zip containing all of the info that is needed.

Thanks.

ninemas said:

My screen went white followed by black ripples of color going through it. I downloaded a program called WhoCrashed and here are the reports:


crash dump file: C:\Windows\Minidump\052811-15412-01.dmp
uptime: 01:35:53
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8007B2B060, 0xFFFFF80000B9C518, 0xFFFFFA8009202B80)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

crash dump file: C:\Windows\memory.dmp
uptime: 01:35:53
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8007B2B060, 0xFFFFF80000B9C518, 0xFFFFFA8009202B80)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Ive attached another zip containing all of the info that is needed.

Thanks.

This one (olny one uploaded) caused by USBHUB.SYS. I would run a sytem file check to verify and repair it.

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.


AND read her USB Driver - General Fix for Problems

Code:

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


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

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03002000 PsLoadedModuleList = 0xfffff800`03247650
Debug session time: Sat May 28 20:27:19.692 2011 (GMT-4)
System Uptime: 0 days 1:35:53.738
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007b2b060, fffff80000b9c518, fffffa8009202b80}

Probably caused by : usbhub.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007b2b060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8009202b80, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8009202b80

DEVICE_OBJECT: fffffa8007b2b060

DRIVER_OBJECT: fffffa80053a1920

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c15

MODULE_NAME: usbhub

FAULTING_MODULE: fffff88004310000 usbhub

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800030ee9c2 to fffff80003081d00

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`030ee9c2 : 00000000`0000009f 00000000`00000003 fffffa80`07b2b060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`0308d652 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`0308d4f6 : fffff800`03229f00 00000000`0005a0bb 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0308d3de : 0000000d`657ed10a fffff800`00b9cc58 00000000`0005a0bb fffff800`031f89e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0308d1c7 : 00000002`431bcdc1 00000002`0005a0bb 00000002`431bcd7c 00000000`000000bb : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03079a2a : fffff800`031f4e80 fffff800`03202cc0 00000000`00000002 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_usbhub.sys

BUCKET_ID:  X64_0x9F_IMAGE_usbhub.sys

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

The System Scan returned the result:

"Windows Resource Protection did not find any integrity violations."

I already did the USB General Fix tutorial once and everything seemed to go smoothly. I'll do it again, but I have a feeling that may not be the fix I need :/

ninemas said:

The System Scan returned the result:

"Windows Resource Protection did not find any integrity violations."

I already did the USB General Fix tutorial once and everything seemed to go smoothly. I'll do it again, but I have a feeling that may not be the fix I need :/

How many external USB drivers are connected?

When you say "external USB drivers" connected, are you referring to how many are installed or how many physical USB devices are connected?

When I followed through with the step in the tut that said to uninstall every USB driver, I uninstalled everything underneath the tree called "Universal Serial Bus Controllers". Are you implying I must uninstall other drivers beside only those specifically underneath this tree in the Device Manager?

How do I know a driver is definitively one relating to USB? May they be scattered about in the tree of my drivers in the Device Manager?

ninemas said:

When you say "external USB drivers" connected, are you referring to how many are installed or how many physical USB devices are connected?

When I followed through with the step in the tut that said to uninstall every USB driver, I uninstalled everything underneath the tree called "Universal Serial Bus Controllers". Are you implying I must uninstall other drivers beside only those specifically underneath this tree in the Device Manager?

How do I know a driver is definitively one relating to USB? May they be scattered about in the tree of my drivers in the Device Manager?

I am interested in un powered external devices.

Here are two screencaps of my devices as viewed in the Device Manager.