Windows 7 - BSOD Driver power state failure 9f

787Bill · 01-27-2012

I just recently got a new laptop and have gotten BSOD twice now with DRIVER_POWER_STATE_FAILURE
I wasn't on the computer at the time of the errors, the first time it was on over night downloading, the second time i think it just had some folders open and google chrome.It is on Windows 7 Home Premium 64bit OEM, I've only had it for about 2 weeks.
HP Pavilion dv6-6b10tx Notebook (DV66B10TX(A3E16PA)) | Techbuy Australia
I couldn't run perfmon /report it said
An error occured while attempting to generate the report.

Access Denied.

Hope you can help!

writhziden · 01-27-2012

Code:


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


Loading Dump File [K:\BSODDmpFiles\787Bill\Windows_NT6_BSOD_jcgriff2\012712-21496-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`041733c0?
Symbol search path is: SRV*c:\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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5c000 PsLoadedModuleList = 0xfffff800`02ea1670
Debug session time: Fri Jan 27 01:38:38.811 2012 (GMT-7)
System Uptime: 0 days 8:57:27.857
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80086d9060, fffff800041733d8, fffffa800b86abd0}

Probably caused by : WUDFRd.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: fffffa80086d9060, Physical Device Object of the stack
Arg3: fffff800041733d8, Functional Device Object of the stack
Arg4: fffffa800b86abd0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800b86abd0

DEVICE_OBJECT: fffffa800a0a8a40

DRIVER_OBJECT: fffffa800a099a70

IMAGE_NAME:  WUDFRd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a654

MODULE_NAME: WUDFRd

FAULTING_MODULE: fffff8800bc00000 WUDFRd

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d46cd2 to fffff80002cd8c40

STACK_TEXT:  
fffff800`04173388 fffff800`02d46cd2 : 00000000`0000009f 00000000`00000003 fffffa80`086d9060 fffff800`041733d8 : nt!KeBugCheckEx
fffff800`04173390 fffff800`02ce45fc : fffff800`041734c0 fffff800`041734c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`04173430 fffff800`02ce4496 : fffffa80`0b5a6c68 fffffa80`0b5a6c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`041734a0 fffff800`02ce437e : 0000004b`153891ee fffff800`04173b18 00000000`001f8ad5 fffff800`02e52d28 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04173af0 fffff800`02ce4167 : 00000010`183e6fc2 00000010`001f8ad5 00000010`183e6fc7 00000000`000000d5 : nt!KiTimerExpiration+0x1be
fffff800`04173b90 fffff800`02cd096a : fffff800`02e4ee80 fffff800`02e5ccc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04173c40 00000000`00000000 : fffff800`04174000 fffff800`0416e000 fffff800`04173c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_WUDFRd.sys

BUCKET_ID:  X64_0x9F_IMAGE_WUDFRd.sys

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

Loading Dump File [K:\BSODDmpFiles\787Bill\Windows_NT6_BSOD_jcgriff2\012012-37596-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c16000 PsLoadedModuleList = 0xfffff800`02e5b670
Debug session time: Thu Jan 19 15:43:03.589 2012 (GMT-7)
System Uptime: 0 days 22:48:30.524
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, 0, fffff80000b9c3d0}

Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: 0000000000000000, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c3d0

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


DRVPOWERSTATE_SUBCODE:  4

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d1eca6 to fffff80002c92c40

STACK_TEXT:  
fffff800`00b9c398 fffff800`02d1eca6 : 00000000`0000009f 00000000`00000004 00000000`00000258 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c3a0 fffff800`02ed02fc : 00000000`00000000 fffff800`00000000 00000000`00000200 fffff800`02c98fda : nt!PnpBugcheckPowerTimeout+0x76
fffff800`00b9c400 fffff800`02c9e5fc : 00000000`00000000 00000000`00000000 00000004`40661200 00000000`00000010 : nt!PopBuildDeviceNotifyListWatchdog+0x1c
fffff800`00b9c430 fffff800`02c9e496 : fffffa80`08920c68 fffffa80`08920c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02c9e37e : 000000bf`2dafb281 fffff800`00b9cb18 00000000`00505065 fffff800`02e0bf28 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02c9e167 : 00000028`fb083ac4 00000028`00505065 00000028`fb083a50 00000000`00000065 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02c8a96a : fffff800`02e08e80 fffff800`02e16cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PnpBugcheckPowerTimeout+76
fffff800`02d1eca6 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PnpBugcheckPowerTimeout+76

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x9F_nt!PnpBugcheckPowerTimeout+76

BUCKET_ID:  X64_0x9F_nt!PnpBugcheckPowerTimeout+76

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

These were caused by a device driver. Unfortunately, the crash reports do not yield any information as to which device driver cased them and blame system files. To rule out system file corruption or hard disk errors, start with the following steps.

If you are overclocking anything, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations.

787Bill · 02-02-2012

I ran a disk check and it seems to be fine and no system files had to be replaced or fixed. So I've just done a system restore back to when i first got it, there haven't been any problems so far but I will post back if there are.
Thank you!

writhziden · 02-02-2012

You're welcome. Restoring to the factory image is a good troubleshooting step if you are unable to find what is causing the crashes. Good work!

Once it stays stable for a few weeks, this thread can be marked as solved.

poseiden79 · 02-03-2012

Hey guys, I have a similar error right now. Not in front of my pc, so I will update later with a crash dump file. But my stop codes I get rightmost are: stop: 9f (0x000000000000003, fffffa8006cd7, fffff800044b8748, fffffa800875c4f0).

Any initial ideas would be great. this seems to be happening right now when I'm inside of windowthis seems to be happening right now when I'm inside of windows in the computers just sitting therewhile the computer is just sitting there.

writhziden · 02-03-2012

poseiden79, please start your own thread following the Blue Screen of Death (BSOD) Posting Instructions to get assistance. While your crash code may be the same, the causes likely is not, and you should get your own analysis done to determine what is causing your crashes.

787Bill · 02-08-2012

I've just had Driver power state failure again, and then while checking for a solution for that I got another BSOD(c9) related to dtsoftbus01.sys it must be daemontools related
Uploading the .zip failed on the website so I had to upload to rapidshare sorry
https://rapidshare.com/files/1846259...D_jcgriff2.zip
Should I just take my laptop back to the shop and replace it under warranty? or is it my fault? :/

writhziden · 02-09-2012

Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.

Also, try updating all drivers for network adapters. Check the laptop's support site for your model. Disable Verifier. Post back when finished with these two steps whether the system is stable.

If you continue to have problems after the above two steps, AVG is known to cause crashes on some systems. Remove AVG using the AVG Remover and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall.

How is the system currently running after the above steps? Did you have to take it in under warranty?

787Bill · 03-02-2012

Well i removed daemon tools and replaced avg with avast antivirus, updated my network drivers, disabled driver verifier. But it still seems to be acting up, so im going to try restoring to factory default and if that doesnt work then back to the shop it goes haha

writhziden · 03-02-2012

Alright, let us know how things go after restoring to the factory system image.

Windows 7 - BSOD Driver power state failure 9f

BSOD Driver power state failure 9f problems?