Drive_Power_state_failure BSOD


  1. jewklw
    Posts : 2
    Windows premium home 7 x64
       New #1

    Drive_Power_state_failure BSOD


    My computer is shutting down almost daily due to Drive_power_state_failure

    I used the HP products to check all hardware and software, made sure all drivers are up to date.

    Computer was purchased new 3/30/2010.
    OS Windows 7 Premium Home edition x64
    OEM

    No changes made. Nothing installed to computer.

    I followed the instructions to download the attached files bsod.rar.

    I look forward to your recommendations. Thank you so much.
      My Computer
    Quote Quote

  3. ePeen
    Posts : 306
    Windows 7 Ultimate x64
       New #2

    Hello, welcome to SevenForums!

    All are 9F bugchecks, power state failures as you've said. Multiple dumps show usbaapl64.sys as the culprit (
    Apple iPod/iPhone Mobile USB device driver). You can update that driver here.

    Code:
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800777aa10, fffff80000ba2748, fffffa80072a44c0}

Probably caused by : pci.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: fffffa800777aa10, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa80072a44c0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000d4a000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  PresentationFo

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00ba26f8 fffff800`03533cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0777aa10 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`034d15fc : fffff800`00ba2830 fffff800`00ba2830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00ba27a0 fffff800`034d1496 : fffffa80`0d9628b0 fffffa80`0d9628b0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00ba2810 fffff800`034d137e : 00000126`eccdb76c fffff800`00ba2e88 00000000`007be5e0 fffff800`0363fe88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`034d1167 : fffffa80`0aaa2cc2 00000000`007be5e0 00000000`00000000 00000000`000000e0 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`034c8765 : 00000000`00000000 fffffa80`0d014b60 00000000`00000000 fffff880`016eca00 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`034c857c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`08a77be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_athrx_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_athrx_IMAGE_pci.sys

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800c274990, fffff80000ba2748, fffffa800dc92210}

*** WARNING: Unable to verify timestamp for usbaapl64.sys
*** ERROR: Module load completed but symbols could not be loaded for usbaapl64.sys
Probably caused by : usbaapl64.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: fffffa800c274990, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa800dc92210, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa800bf02950

IMAGE_NAME:  usbaapl64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4db9b137

MODULE_NAME: usbaapl64

FAULTING_MODULE: fffff88006f95000 usbaapl64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  wmpnetwk.exe

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00ba26f8 fffff800`034f2cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0c274990 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`034905fc : fffff800`00ba2830 fffff800`00ba2830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00ba27a0 fffff800`03490496 : fffff800`0362ff00 00000000`00139c69 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00ba2810 fffff800`0349037e : 0000002e`ae8476d1 fffff800`00ba2e88 00000000`00139c69 fffff800`035fdfa8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`03490167 : fffff800`035faec1 fffffa80`00139c69 00000000`00000000 00000000`00000069 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`03487765 : 00000000`00000000 fffffa80`0b08ab60 00000000`00000000 fffff880`03afa588 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`0348757c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0a5e2770 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_usbaapl64.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_usbaapl64.sys

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8006a18680, fffff800047e5510}

Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )

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: fffffa8006a18680, The thread currently holding on to the Pnp lock.
Arg4: fffff800047e5510

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


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8006a18680

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003286f32 to fffff800032844da

STACK_TEXT:  
fffff880`031b6710 fffff800`03286f32 : fffffa80`06a18680 fffffa80`06a18680 00000000`00000000 00000000`00000009 : nt!KiSwapContext+0x7a
fffff880`031b6850 fffff800`0328644a : 00000000`00000010 00000000`00000082 fffff880`00000000 00000000`00000082 : nt!KiCommitThreadWait+0x1d2
fffff880`031b68e0 fffff800`034ec214 : fffff8a0`00000003 fffff880`031b6bf8 00000000`00000001 fffffa80`00000000 : nt!KeWaitForMultipleObjects+0x272
fffff880`031b6ba0 fffff800`034ec9ea : fffff8a0`01c7f5f0 fffffa80`0c0c0e90 fffff8a0`01c7f4e0 fffffa80`0c0c0e90 : nt!PnpNotifyUserMode+0x158
fffff880`031b6c20 fffff800`034ebada : 00000000`00000000 fffffa80`0c0c0e90 fffff8a0`0d5c4590 00000000`00000001 : nt!PnpProcessCustomDeviceEvent+0x1a
fffff880`031b6c50 fffff800`0328c001 : fffff800`034eb998 fffff8a0`01c7f4e0 fffff800`034222b8 fffff800`034316a0 : nt!PnpDeviceEventWorker+0x142
fffff880`031b6cb0 fffff800`0351cfee : 00000000`00000000 fffffa80`06a18680 00000000`00000080 fffffa80`06a01890 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`032735e6 : fffff880`02fd5180 fffffa80`06a18680 fffff880`02fdffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b58a0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa8006a18680 ; kb

FOLLOWUP_IP: 
nt!KiSwapContext+7a
fffff800`032844da 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiSwapContext+7a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a

BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a

Followup: MachineOwner
      My Computer
    Quote Quote

  4. jewklw
    Posts : 2
    Windows premium home 7 x64
    Thread Starter
       New #3

    Thank you. I have an iphone connected but do not have service for it, have used it as an mp3. Don't know if I can update the driver if I don't have phone service. I will disconnect it for now. Strangely, in itunes I am told that the iphone is up to date with the current updates.
    Last edited by jewklw; 26 Feb 2012 at 16:18. Reason: addition
      My Computer
    Quote Quote

  6. ePeen
    Posts : 306
    Windows 7 Ultimate x64
       New #4

    Keep me updated :)
      My Computer
    Quote Quote

 

  Related Discussions
Hi, and thanks in advance for reading this. EVERY TIME I shutdown my computer it stays in the shutdown screen for about 5-10 minutes before going into BSOD (STOP: 0x0000009F). Built this PC myself about 9 months ago (first build, not very experienced), but this issue is recent (no hardware change)....
Hi. My computer has been crashing very often recently with the BSOD saying, "Driver_Power_State_Failure." It is a refurbished computer form Windows XP, running Windows 7 with an Intel Prentium D processor. I have tried to fix it but nothing I have tried worked. If anyone knows how to fix this,...
BSOD randomly while surfing listed as Driver_Power_State_Failure. I'm a newb who just registered but have attached the zipped SF file for your perusal if you so choose. Not even sure how to open the .dmp file to further explore the issue. Thanks for whatever help you can provide. Aaron
Blue screen Drive_Power_State_Failure
in BSOD Help and Support

Hi. So i have a pretty brand new computer and about 4 months in I get a crash with Drive_Power_State_Failure. I know crashes happen but i'm trying to keep this computer as clean as a whistle. So ideas would be nice. And I know this is not very specific, so most of you will ask for more detail, but...
Our Sites
Site Links
About 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 09:57.
Find Us