Windows 10: BSOD DRIVER_POWER_STATE_FAILURE (9f) HELP

Hi guys,


I very recently bought an asus zenbook UX461UA , windows 10 64 bit installed.


the problem that i have is big...When my computer is charging sometimes the screen freezes for good and never gets back to normal , ocasionaly a BSOD is thrown . It seems like the laptop is overheating every time BSOD comes, also most of the time the BSOD comes without freeze before. Again 90 % of the time this is happening when my battery is charging. It started 1 month after i bought it....Just after a windows update. Anyway I re-installed windows > didnt fix the issue. Called Microsoft ...they had me update every single bit of drivers , I even updated the Bios and yet...the issue is still here. I used all Windows diagbostics tools and nothing....issue is still here kinda desperate I rly need help. This is my minidump :


Kernel base = 0xfffff800`16c19000 PsLoadedModuleList = 0xfffff800`16fc7150
Debug session time: Wed Jan 23 20:33:44.700 2019 (UTC - 5:00)
System Uptime: 1 days 8:31:39.661
*******************************************************************************
* *
* 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: ffff9485b52b9060, Physical Device Object of the stack
Arg3: fffffc0dca83f7d0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffff9485ba9f9d30, 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: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e00d0f2

MODULE_NAME: pci

FAULTING_MODULE: fffff80317000000 pci

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffffc0d`ca****10 fffff****5a 00000000`001daee1 00000000`00000019 : nt!KiProcessExpiredTimerList+0x159
fffffc0d`ca83f950 fffff800`16dc67da : ffffffff`00000000 ffffba80`ab510180 00000000`00000000 ffffba80`ab520200 : nt!KiRetireDpcList+0x4c7
fffffc0d`ca83fb60 00000000`00000000 : fffffc0d`ca840000 fffffc0d`ca839000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_Netwtw06_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_Netwtw06_IMAGE_pci.sys

:)

 

BSOD - DRIVER_POWER_STATE_FAILURE (9f)

Got the BSOD each time I shutdown / restart.

This system is not a branded computer, the motherboard is ASUS ROG MAXIMUS VIII HERO ALPHA (https://www.asus.com/Motherboards/ROG-MAXIMUS-VIII-HERO-ALPHA/specifications/)

msinfo32 report: https://1drv.ms/t/s!AhFRgfjjMEqohLNkB73osuV5lmTE9g

driverview report: https://1drv.ms/t/s!AhFRgfjjMEqohLNjJNdZ-c_ZkqsihA

memory.dmp file: https://db.tt/d0QcYPVE

minidump: https://1drv.ms/f/s!AhFRgfjjMEqohLNlUE5mdQTjLv7Ehg

The results of bugcheck is also attached

Microsoft (R) Windows Debugger Version 10.0.10586.567 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Zixiao\Desktop\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Symbol Path validation summary **************

Response Time (ms) Location

Deferred srv*https://msdl.microsoft.com/download/symbols

Symbol search path is: srv*https://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 14393 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 14393.0.amd64fre.rs1_release.160715-1616

Machine Name:

Kernel base = 0xfffff803`5a287000 PsLoadedModuleList = 0xfffff803`5a58c060

Debug session time: Thu Jul 28 15:07:13.525 2016 (UTC - 7:00)

System Uptime: 0 days 2:12:24.140

Loading Kernel Symbols

...............................................................

................................................................

..................................................

Loading User Symbols

Loading unloaded module list

................

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffff908d14106b90, ffffc200d97f48e0, ffff908d12bc7010}

*** ERROR: Module load completed but symbols could not be loaded for UsbHub3.sys

Probably caused by : UsbHub3.sys

Followup: MachineOwner

---------

6: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DRIVER_POWER_STATE_FAILURE (9f)

A driver has failed to complete a power IRP within a specific time.

Arguments:

Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time

Arg2: ffff908d14106b90, Physical Device Object of the stack

Arg3: ffffc200d97f48e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

Arg4: ffff908d12bc7010, The blocked IRP

Debugging Details:

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 14393.0.amd64fre.rs1_release.160715-1616

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1701

BIOS_DATE: 03/25/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: MAXIMUS VIII HERO ALPHA

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 1

BUGCHECK_P1: 3

BUGCHECK_P2: ffff908d14106b90

BUGCHECK_P3: ffffc200d97f48e0

BUGCHECK_P4: ffff908d12bc7010

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5789998e

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff80f616e0000 UsbHub3

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-ZIXIAO

ANALYSIS_SESSION_TIME: 07-28-2016 15:38:01.0372

ANALYSIS_VERSION: 10.0.10586.567 x86fre

STACK_TEXT:

ffffc200`d97f48a8 fffff803`5a4811ff : 00000000`0000009f 00000000`00000003 ffff908d`14106b90 ffffc200`d97f48e0 : nt!KeBugCheckEx

ffffc200`d97f48b0 fffff803`5a481112 : ffff908d`0cb146e0 00000000`00049fdc 00000000`00000001 ffffc200`d97c9180 : nt!PopIrpWatchdogBugcheck+0xeb

ffffc200`d97f4910 fffff803`5a2be260 : ffff908d`0cb14718 00000000`003bb94e 00000000`00140001 00000000`00000000 : nt!PopIrpWatchdog+0x22

ffffc200`d97f4960 fffff803`5a3d401a : 00000000`00000000 ffffc200`d97c9180 ffffc200`d97d5cc0 ffff908d`12a77080 : nt!KiRetireDpcList+0x440

ffffc200`d97f4be0 00000000`00000000 : ffffc200`d97f5000 ffffc200`d97ee000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 81a7ba75a791115b4f55c8910c64a260d525502e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: dfbcb3f9a415e4b8c955f15c39a77a130e810657

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 10.0.14393.0

FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ACPI_IMAGE_UsbHub3.sys

BUCKET_ID: 0x9F_3_POWER_DOWN_ACPI_IMAGE_UsbHub3.sys

PRIMARY_PROBLEM_CLASS: 0x9F_3_POWER_DOWN_ACPI_IMAGE_UsbHub3.sys

TARGET_TIME: 2016-07-28T22:07:13.000Z

OSBUILD: 14393

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-07-15 19:16:17

BUILDDATESTAMP_STR: 160715-1616

BUILDLAB_STR: rs1_release

BUILDOSVER_STR: 10.0.14393.0.amd64fre.rs1_release.160715-1616

ANALYSIS_SESSION_ELAPSED_TIME: 4ec

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_acpi_image_usbhub3.sys

FAILURE_ID_HASH: {6e40eb19-6eeb-40bd-279f-7a4937ea67c1}

Followup: MachineOwner

---------

 

DRIVER_POWER_STATE_FAILURE (9f) usbccgp.sys

Hi and thank you for your answer!

I spend the whole night, learning how to read dmp - files.

usbccgp.sys (I also have found a BSOD with UsbHub3.sys) is the one who crashed, but why?

I found this very useful article:

Bug Check 0x9F DRIVER_POWER_STATE_FAILURE - Windows drivers

Sample 1:

• WinDbg -> File -> Open Crash Dump -> c:\windows\minidump\xxx.dmp
• BugCheck 9F, {3, ffff9002b91f86c0, ffffa7018acff960, ffff9002bcd4e9f0}
• UsbHub3.sys

3: kd> !devstack ffff9002b91f86c0

!DevObj !DrvObj !DevExt ObjectName

ffff9002b91f0e20 *** WARNING: Unable to verify timestamp for Wdf01000.sys

*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys

\Driver\USBHUB3 ffff9002b91ed310 InfoMask field not found for _OBJECT_HEADER at ffff9002b91f0df0
ffff9002b9218a00 \Driver\ACPI ffff9002b4de38b0 InfoMask field not found for _OBJECT_HEADER at ffff9002b92189d0
> ffff9002b91f86c0 \Driver\USBHUB3 ffff9002b91ef310 Cannot read info offset from nt!ObpInfoMaskToOffset
!DevNode ffff9002b91c4d30 :

DeviceInst is "USB\VID_174C&PID_3074\5&1cc0e58a&0&21"

ServiceName is "USBHUB3"

Google tells me that this may be my onboard USB Hub (Asmedia) of my Asus X99 Mainboard.

It could also be an internal USB Hub of some of my devices.

Im not sure but I think they are connected at the intel usb ports.

The Asus Sabertooth X99 has an additional Asmedia USB3.1 controller, but as far as I know without a hub...

Sampe 2:

• BugCheck 9F, {3, ffffd58f2a7e28d0, ffffac800ddff960, ffffd58f2d8e1580}
• usbccgp.sys

1: kd> !devstack ffffd58f2a7e28d0

!DevObj !DrvObj !DevExt ObjectName

ffffd58f2ad4de20 Unable to load image \SystemRoot\System32\drivers\ocusbvid111.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ocusbvid111.sys

*** ERROR: Module load completed but symbols could not be loaded for ocusbvid111.sys

*** WARNING: Unable to verify timestamp for Wdf01000.sys

*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys

\Driver\OCUSBVID ffffd58f2ad4ae10 InfoMask field not found for _OBJECT_HEADER at ffffd58f2ad4ddf0
> ffffd58f2a7e28d0 \Driver\usbccgp ffffd58f2a7e2a20 Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffd58f2a891260 :

DeviceInst is "USB\VID_2833&PID_0211&MI_00\7&2017bc24&0&0000"

ServiceName is "OCUSBVID"

This is from the Oculus Rift...

With also have an internal USB Hub and is connected to one of the Intel USB ports with internal Hub.

Im not sure if I have done it right, but I try to use the Asmedia USB3.1 ports for Oculus Rift the next days. I also will deactivate all power saving features on the device... Maybe this woraround helps, until all drivers are fixed.

Please correct me, if I have undestand something wrong!

BR!

Mathias

 

DRIVER_POWER_STATE_FAILURE (9f) usbccgp.sys

Hi,

Since I have updated Windows to Build 1607, I have random BSOD all the time while working on the PC.

• I dont use standby.
• No Hardware changes since stable 1511
• I have tryed to flip usb devices and disconnect them one by one
• I can not find any pattern, it happens randomly
• With and without secureboot
• Fresh install without secureboot and with original newest whql drivers from all my hardware devices

Im figured out that usbccgp.sys is involved. So Im sure a usb device driver is the problem, but how I can find out witch one? I to stupid to understand the dmp´s completely...

Minidumps:

https://cloud.humpeler.at/index.php/s/nddZU1ZngxwHzor

Can anyone give me a hint, with driver caused this BSOD´s?

Please :-/

Best regards, and thank you so much!!!

Mathias

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)

Online Crash Dump Analysis Service

See OSR Online - The Home Page for Windows Driver Developers for more information

Windows 8 Kernel Version 14393 MP (6 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 14393.0.amd64fre.rs1_release.160715-1616

Machine Name:

Kernel base = 0xfffff800`a4a17000 PsLoadedModuleList = 0xfffff800`a4d1c060

Debug session time: Wed Aug 10 13:47:15.926 2016 (UTC - 4:00)

System Uptime: 0 days 0:02:27.681

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

* *

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

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

Arg4: ffffd58f2d8e1580, The blocked IRP

Debugging Details:

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

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

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffd58f2ad54e60

IMAGE_NAME: usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 57899bb3

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff80919300000 usbccgp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:

ffffac80`0ddff928 fffff800`a4c111ff : 00000000`0000009f 00000000`00000003 ffffd58f`2a7e28d0 ffffac80`0ddff960 : nt!KeBugCheckEx

ffffac80`0ddff930 fffff800`a4c11112 : ffffd58f`2bf5cdc0 00000000`00000001 00000000`00000003 ffffd58f`2bf5ce38 : nt!PopIrpWatchdogBugcheck+0xeb

ffffac80`0ddff990 fffff800`a4a4e260 : ffffd58f`2bf5cdf8 ffffd58f`2bf5cdf8 ffffac80`0ddffae0 00000000`00000002 : nt!PopIrpWatchdog+0x22

ffffac80`0ddff9e0 fffff800`a4b6401a : ffffffff`00000000 ffffac80`0e107180 ffffac80`0e113c40 ffffd58f`2a887040 : nt!KiRetireDpcList+0x440

ffffac80`0ddffc60 00000000`00000000 : ffffac80`0de00000 ffffac80`0ddfa000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_usbccgp.sys

BUCKET_ID: X64_0x9F_3_IMAGE_usbccgp.sys

Followup: MachineOwner