windows 10 Driver_Power_State_Failure

[Guest Keith__]

For a long time I have been struggling with BSODs caused by Driver_Power_State_Failure.

 

It happens randomly, but most of the time it seems to be related to hibernation. After an hour or so hibernated, it crashes.

 

 

I have disconnected all usb devices except for a simple keyboard and the mouse.

The hardware is an Asus Rampage 5 motherboard, with latest update on drivers and bios.

 

I have manually gone through the usb devices in the device manager to make sure the drivers are updated there.

 

 

Here is the complete crash dump: http://www.filedropper.com/071417-14375-01

 

 

And an analysis of the dump from osronline.com:

 

Primary Analysis

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)

Online Crash Dump Analysis Service

See http://www.osronline.com for more information

Windows 8 Kernel Version 15063 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 15063.0.amd64fre.rs2_release.170317-1834

Machine Name:

Kernel base = 0xfffff800`8227e000 PsLoadedModuleList = 0xfffff800`825ca5e0

Debug session time: Thu Jul 13 23:22:39.340 2017 (UTC - 4:00)

System Uptime: 0 days 2:02:38.743

*******************************************************************************

* *

* 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: ffff88811a581730, Physical Device Object of the stack

Arg3: ffff9e80fa6be8f0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack

Arg4: ffff88811a6f4820, The blocked IRP

 

Debugging Details:

------------------

 

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

 

DRVPOWERSTATE_SUBCODE: 3

 

IMAGE_NAME: UsbHub3.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 20eb4039

 

MODULE_NAME: UsbHub3

 

FAULTING_MODULE: fffff80a3db70000 UsbHub3

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

 

BUGCHECK_STR: 0x9F

 

PROCESS_NAME: System

 

CURRENT_IRQL: 2

 

STACK_TEXT:

ffff9e80`fa6be8b8 fffff800`824a1e97 : 00000000`0000009f 00000000`00000003 ffff8881`1a581730 ffff9e80`fa6be8f0 : nt!KeBugCheckEx

ffff9e80`fa6be8c0 fffff800`824a1da2 : ffff8881`1a6ef900 00000000`00000002 ffff9e80`fa691180 00000000`00000001 : nt!PopIrpWatchdogBugcheck+0xeb

ffff9e80`fa6be920 fffff800`822ef898 : ffff8881`1a6ef938 ffff8881`1a6ef978 00000000`00000002 00000000`00000002 : nt!PopIrpWatchdog+0x22

ffff9e80`fa6be970 fffff800`822f0707 : ffff9e80`fa691180 00000000`00da7a64 00000000`00044889 00000000`000448a1 : nt!KiProcessExpiredTimerList+0x248

ffff9e80`fa6bea60 fffff800`823ed56a : ffffffff`00000000 ffff9e80`fa691180 00000000`00000000 ffff9e80`fa69de80 : nt!KiRetireDpcList+0x367

ffff9e80`fa6bec60 00000000`00000000 : ffff9e80`fa6bf000 ffff9e80`fa6b9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

 

 

STACK_COMMAND: kb

 

FOLLOWUP_NAME: MachineOwner

 

FAILURE_BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_UsbHub3.sys

 

BUCKET_ID: OLD_IMAGE_UsbHub3.sys

 

Followup: MachineOwner

---------

 

Continue reading...