BSOD Driver Power State Failure

Toggle sidebar Toggle sidebar
M

MattB101

Reputable
Apr 18, 2014
2
0
4,510
Hello,
I'm running windows 8.1 and for a while now I've been periodically getting a BSOD shorty after startup. The screen always shows the error Driver_Power_State_Failure.

I've tried to analyse my minidump files using whocrashed and windbg and I think there seems to be some issue with ATAIP.SYS however I'm not really an expert at this sort of thing and I only know what I've read on the internet about using these tools.

So I'd appreciate some help if possible.
This is the contents of my crashdump file here -

Many Thanks
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe00001a34610, Physical Device Object of the stack
Arg3: fffff8009c25a980, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe0000481ec60, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffe00000fbe460

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5215f8b7

MODULE_NAME: atapi

FAULTING_MODULE: fffff80000720000 atapi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

TAG_NOT_DEFINED_c000000f: FFFFF8009C261FB0

STACK_TEXT:
fffff800`9c25a948 fffff800`9aa811a6 : 00000000`0000009f 00000000`00000003 ffffe000`01a34610 fffff800`9c25a980 : nt!KeBugCheckEx
fffff800`9c25a950 fffff800`9aa810c6 : ffffe000`04b025d0 fffff800`00723358 ffffe000`0024e520 fffff800`9ab78180 : nt!PopIrpWatchdogBugcheck+0xde
fffff800`9c25a9b0 fffff800`9a937f64 : ffffe000`04b02608 00000000`00000282 fffff800`9c25aa79 00000000`00000000 : nt!PopIrpWatchdog+0x32
fffff800`9c25aa00 fffff800`9a938478 : 00000000`00000000 ffffe000`02985480 fffff800`9ab78180 fffff800`9ab7b620 : nt!KiProcessExpiredTimerList+0x1d8
fffff800`9c25aae0 fffff800`9a994478 : fffff800`9ab78180 00000000`00da7a64 fffff800`0016380d 00000000`00163825 : nt!KiExpireTimerTable+0x218
fffff800`9c25ab80 fffff800`9a8e4abc : ffffe000`02985240 00000000`00000001 fffff800`9c25ad50 fffff800`9a8dffbc : nt!KiTimerExpiration+0x148
fffff800`9c25ac30 fffff800`9a9db7ea : fffff800`9ab78180 fffff800`9ab78180 00000000`001a3fe0 fffff800`9abd0a80 : nt!KiRetireDpcList+0x19c
fffff800`9c25ada0 00000000`00000000 : fffff800`9c25b000 fffff800`9c255000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys

BUCKET_ID: 0x9F_3_IMAGE_atapi.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe00001a34610, Physical Device Object of the stack
Arg3: fffff8009c25a980, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe0000481ec60, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffe00000fbe460

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5215f8b7

MODULE_NAME: atapi

FAULTING_MODULE: fffff80000720000 atapi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

TAG_NOT_DEFINED_c000000f: FFFFF8009C261FB0

STACK_TEXT:
fffff800`9c25a948 fffff800`9aa811a6 : 00000000`0000009f 00000000`00000003 ffffe000`01a34610 fffff800`9c25a980 : nt!KeBugCheckEx
fffff800`9c25a950 fffff800`9aa810c6 : ffffe000`04b025d0 fffff800`00723358 ffffe000`0024e520 fffff800`9ab78180 : nt!PopIrpWatchdogBugcheck+0xde
fffff800`9c25a9b0 fffff800`9a937f64 : ffffe000`04b02608 00000000`00000282 fffff800`9c25aa79 00000000`00000000 : nt!PopIrpWatchdog+0x32
fffff800`9c25aa00 fffff800`9a938478 : 00000000`00000000 ffffe000`02985480 fffff800`9ab78180 fffff800`9ab7b620 : nt!KiProcessExpiredTimerList+0x1d8
fffff800`9c25aae0 fffff800`9a994478 : fffff800`9ab78180 00000000`00da7a64 fffff800`0016380d 00000000`00163825 : nt!KiExpireTimerTable+0x218
fffff800`9c25ab80 fffff800`9a8e4abc : ffffe000`02985240 00000000`00000001 fffff800`9c25ad50 fffff800`9a8dffbc : nt!KiTimerExpiration+0x148
fffff800`9c25ac30 fffff800`9a9db7ea : fffff800`9ab78180 fffff800`9ab78180 00000000`001a3fe0 fffff800`9abd0a80 : nt!KiRetireDpcList+0x19c
fffff800`9c25ada0 00000000`00000000 : fffff800`9c25b000 fffff800`9c255000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys

BUCKET_ID: 0x9F_3_IMAGE_atapi.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe00001a34610, Physical Device Object of the stack
Arg3: fffff8009c25a980, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe0000481ec60, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffe00000fbe460

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5215f8b7

MODULE_NAME: atapi

FAULTING_MODULE: fffff80000720000 atapi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

TAG_NOT_DEFINED_c000000f: FFFFF8009C261FB0

STACK_TEXT:
fffff800`9c25a948 fffff800`9aa811a6 : 00000000`0000009f 00000000`00000003 ffffe000`01a34610 fffff800`9c25a980 : nt!KeBugCheckEx
fffff800`9c25a950 fffff800`9aa810c6 : ffffe000`04b025d0 fffff800`00723358 ffffe000`0024e520 fffff800`9ab78180 : nt!PopIrpWatchdogBugcheck+0xde
fffff800`9c25a9b0 fffff800`9a937f64 : ffffe000`04b02608 00000000`00000282 fffff800`9c25aa79 00000000`00000000 : nt!PopIrpWatchdog+0x32
fffff800`9c25aa00 fffff800`9a938478 : 00000000`00000000 ffffe000`02985480 fffff800`9ab78180 fffff800`9ab7b620 : nt!KiProcessExpiredTimerList+0x1d8
fffff800`9c25aae0 fffff800`9a994478 : fffff800`9ab78180 00000000`00da7a64 fffff800`0016380d 00000000`00163825 : nt!KiExpireTimerTable+0x218
fffff800`9c25ab80 fffff800`9a8e4abc : ffffe000`02985240 00000000`00000001 fffff800`9c25ad50 fffff800`9a8dffbc : nt!KiTimerExpiration+0x148
fffff800`9c25ac30 fffff800`9a9db7ea : fffff800`9ab78180 fffff800`9ab78180 00000000`001a3fe0 fffff800`9abd0a80 : nt!KiRetireDpcList+0x19c
fffff800`9c25ada0 00000000`00000000 : fffff800`9c25b000 fffff800`9c255000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys

BUCKET_ID: 0x9F_3_IMAGE_atapi.sys

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

0: kd> lmvm atapi
start end module name
fffff800`00720000 fffff800`0072a000 atapi T (no symbols)
Loaded symbol image file: atapi.sys
Image path: \SystemRoot\System32\drivers\atapi.sys
Image name: atapi.sys
Timestamp: Thu Aug 22 12:40:39 2013 (5215F8B7)
CheckSum: 0000E383
ImageSize: 0000A000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
 
Sort by date Sort by votes
G

Grapid

Reputable
Apr 18, 2014
10
0
4,510
Could you please post your specs? As this could be a power supply problem, but what looks interesting is the line that says

fffff800`9ab78180 : nt!PopIrpWatchdogBugcheck+0xde
fffff800`9c25a9b0 fffff800`9a937f64 : ffffe000`04b02608 00000000`00000282 fffff800`9c25aa79

that's a reference to Fast Boot, disable fast boot (just google how to if you don't know) and then see if the error still occurs
 
Upvote 0 Downvote
M

MattB101

Reputable
Apr 18, 2014
2
0
4,510


Thanks for the info, I've disbaled fast boot now and I'll see how it goes. The problem is periodic so I'll just have to wait and see.

In the meantime here's my specs. If there's anything else that you need then just let me know

Windows 8.1 Professional (x64) (build 9600)
Install Language: English (United Kingdom)
System Locale: English (United Kingdom)
Installed: 17/10/2013 20:25:11
Boot Mode: BIOS (Secure Boot not supported)

3.40 gigahertz AMD Phenom II X4 965
512 kilobyte primary memory cache
2048 kilobyte secondary memory cache
6144 kilobyte tertiary memory cache
64-bit ready
Multi-core (4 total)
Not hyper-threaded

Board: ASUSTeK Computer INC. M4A79XTD EVO Rev X.0X
Serial Number: MT709CK01801599
Bus Clock: 200 megahertz
BIOS: American Megatrends Inc. 0704 11/25/2009

16384 Megabytes Usable Installed Memory

Slot 'DIMM0' has 4096 MB (serial number SerNum00)
Slot 'DIMM1' has 4096 MB (serial number SerNum01)
Slot 'DIMM2' has 4096 MB (serial number SerNum02)
Slot 'DIMM3' has 4096 MB (serial number SerNum03

Generic- Compact Flash USB Device [Hard drive] -- drive 4
Generic- MS/MS-Pro USB Device [Hard drive] -- drive 7
Generic- SD/MMC USB Device [Hard drive] -- drive 6
Generic- SM/xD-Picture USB Device [Hard drive] -- drive 5
SAMSUNG HD103SJ [Hard drive] (1000.20 GB) -- drive 3, s/n S246J9DB200076, rev 1AJ10001, SMART Status: Healthy
SAMSUNG HD103SJ [Hard drive] (1000.20 GB) -- drive 2, s/n S246J9DB200075, rev 1AJ10001, SMART Status: Healthy
SAMSUNG HD502HI [Hard drive] (500.11 GB) -- drive 1, s/n S1VZJ9DSC11665, rev 1AG01118, SMART Status: Healthy
SAMSUNG HD502HJ [Hard drive] (500.11 GB) -- drive 0, s/n S20BJ9DSC30765, rev 1AJ100E4, SMART Status: Healthy
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom