Windows 10: DRIVER_POWER_STATE_FAILURE 9f

Hello I been dealing with this problem for a couple of months now and need guidance on how to remedy this. I hope to hear from you soon and thank you in advance.



Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\minidump\121220-90125-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 48 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff802`48e00000 PsLoadedModuleList = 0xfffff802`49248190Debug session time: Sat Dec 12 16:17:22.485 2020 UTC - 8:00System Uptime: 0 days 22:42:06.940Loading Kernel Symbols.................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff802`48fc23a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd403`a6b17880=000000000000009f18: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_POWER_STATE_FAILURE 9fA 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 timeArg2: ffff9a8a818a3060, Physical Device Object of the stackArg3: ffffd403a6b178b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stackArg4: ffff9e8549a579f0, The blocked IRPDebugging Details:------------------DBGHELP: Timeout to store: C:\ProgramData\Dbg\sym*https://msdl.microsoft.com/download/symbols*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5765 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-D0UHAM0 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 46624 Key : Analysis.Memory.CommitPeak.Mb Value: 82 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 9fBUGCHECK_P1: 3BUGCHECK_P2: ffff9a8a818a3060BUGCHECK_P3: ffffd403a6b178b0BUGCHECK_P4: ffff9e8549a579f0DRVPOWERSTATE_SUBCODE: 3IMAGE_NAME: usbccgp.sysMODULE_NAME: usbccgpFAULTING_MODULE: fffff802584f0000 usbccgpBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffffd403`a6b17878 fffff802`490ee817 : 00000000`0000009f 00000000`00000003 ffff9a8a`818a3060 ffffd403`a6b178b0 : nt!KeBugCheckExffffd403`a6b17880 fffff802`490ee721 : ffff9e85`4a6d6490 00000000`00000001 ffffda80`cd518100 ffffda80`cd518180 : nt!PopIrpWatchdogBugcheck+0xefffffd403`a6b178f0 fffff802`48e512d9 : ffff9e85`4a6d64c8 000000be`490d6147 00000001`00000002 ffff9a8a`81812050 : nt!PopIrpWatchdog+0x31ffffd403`a6b17940 fffff802`48e50039 : 00000000`00000016 00000000`00989680 00000000`002f9243 00000000`0000005b : nt!KiProcessExpiredTimerList+0x169ffffd403`a6b17a30 fffff802`48fc5ece : ffffffff`00000000 ffffda80`cd518180 ffffda80`cd529c40 ffff9a8a`876b7580 : nt!KiRetireDpcList+0x4e9ffffd403`a6b17c60 00000000`00000000 : ffffd403`a6b18000 ffffd403`a6b12000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7eIMAGE_VERSION: 10.0.18362.693STACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: 0x9F_3_dgmbx2_IMAGE_usbccgp.sysOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {f2749d30-8ff2-77c9-b6c9-67911e8954bb}Followup: MachineOwner---------

:)

 

BSOD DRIVER_POWER_STATE_FAILURE (9f) HELP

A. Analysis Results

File Name: 012419-10859-01.dmp

DRIVER_POWER_STATE_FAILURE (9f)

IMAGE_NAME: nwifi.sys

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

B. Third Party Drivers

VBoxNetLwf.sys - Virtual Box

Driver Date - 8-Nov-2018

C. Recommendations

1. Create a system restore point so that if something wrong happens you can revert.

Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

2. Update your Virtual box to latest. Your driver date is 8-Nov-18 and see if you get a driver later than this. If Virtual box is not required, get it uninstalled.

 

Blue Screen of Death - DRIVER_POWER_STATE_FAILURE (9f)

My computer started crashing with DRIVER_POWER_STATE_FAILURE (9f).

I analyzed the dump files but cannot resolve which driver is resulting in this error. I also used google but not many errors of this type seem to occur and I was not able to find any with this specific driver.

I hoped someone could clear this up for me.

Here is the dump file:

 

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:

https://msdn.microsoft.com/en-us/li...329(v=vs.85).aspx?f=255&MSPPError=-2147217396

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