Windows 10: DRIVER_POWER_STATE_FAILURE 9f usbccgp.sys crashing on browser use

Hello,


I'm new to this debugging, and I checked some other posts but the commands that I find don't seem to work, so I'm not sure what I can do....


My system crashes at random, the screen just goes black and you can still hear the tasks are running but they freeze up later.


Could anyone give me a clue where the issue is?


Thank you very much!





[COLOR=rgba30, 30, 30, 1]1: 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: ffffde0f57dad060, Physical Device Object of the stackArg3: ffff9e0b1522f810, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stackArg4: ffffde0f596be920, The blocked IRPDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5436 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 5464 Key : Analysis.Init.CPU.mSec Value: 328 Key : Analysis.Init.Elapsed.mSec Value: 10925 Key : Analysis.Memory.CommitPeak.Mb Value: 83 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1BUGCHECK_CODE: 9fBUGCHECK_P1: 3BUGCHECK_P2: ffffde0f57dad060BUGCHECK_P3: ffff9e0b1522f810BUGCHECK_P4: ffffde0f596be920DRVPOWERSTATE_SUBCODE: 3DRIVER_OBJECT: [/COLOR][COLOR=rgba0, 0, 255, 1]ffffde0f57f77660[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: usbccgp.sysMODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]usbccgp[/COLOR][COLOR=rgba30, 30, 30, 1]FAULTING_MODULE: fffff807344a0000 [/COLOR][COLOR=rgba0, 0, 255, 1]usbccgp[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXPNP: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxpnp[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1PROCESS_NAME: SystemSTACK_TEXT: ffff9e0b`1522f7d8 fffff807`2015f487 : 00000000`0000009f 00000000`00000003 ffffde0f`57dad060 ffff9e0b`1522f810 : nt!KeBugCheckExffff9e0b`1522f7e0 fffff807`2015f3a1 : ffffde0f`596c11e8 00000000`00000000 ffffde0f`655291f0 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0xdfffff9e0b`1522f850 fffff807`1fe44f12 : ffffde0f`596c1220 ffffa081`0efe2180 ffffa081`0efe2180 ffffde0f`00000002 : nt!PopIrpWatchdog+0x31ffff9e0b`1522f8a0 fffff807`1fe06eed : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`0060e489 : nt!KiProcessExpiredTimerList+0x172ffff9e0b`1522f990 fffff807`1fff95ee : 00000000`00000000 ffffa081`0efe2180 ffffa081`0efed340 ffffde0f`5f585080 : nt!KiRetireDpcList+0x5ddffff9e0b`1522fc20 00000000`00000000 : ffff9e0b`15230000 ffff9e0b`15229000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9eSTACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: 0x9F_3_IMAGE_usbccgp.sysOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {2240478d-2a07-44ce-f277-d13120a9d2d6}Followup: MachineOwner[/COLOR]

:)

 

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

 

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

 

How do I fix DRIVER_POWER_STATE_FAILURE (9f)?

Hello I am using a Desktop and I am having problems when I turn on the PC, a minute or two after startup is finished my computer crashes and gives me the DRIVER_POWER_STATE_FAILURE message.

I updated my mobo manufacturer's drivers, changed the power controls, turned off sleep mode, turned off fast-startup, checked for newer versions of network adapter and display adapter driver on device manager, and I reset my PC. Today I launched my PC and after
a few minutes I think, I got another crash.

Also I don't know how to read the analysis below but it says FAULTING_MODULE: fffff80370800000 UsbHub3, is this anything significant in why the crashes are happening?

This doesn't happen every time I boot my computer but it happens almost frequently, and I was wondering how I can fix this problem? Thank you for any help in advance.

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

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

Arg4: ffffb40de24b0200, The blocked IRP

Debugging Details:

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec

Value: 2

Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-4R31QKK

Key : Analysis.DebugData

Value: CreateObject

Key : Analysis.DebugModel

Value: CreateObject

Key : Analysis.Elapsed.Sec

Value: 17

Key : Analysis.Memory.CommitPeak.Mb

Value: 72

Key : Analysis.System

Value: CreateObject

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffb40de1ed8dd0

BUGCHECK_P3: ffffd7868ecb5850

BUGCHECK_P4: ffffb40de24b0200

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffb40ddbb28e30

IMAGE_NAME: UsbHub3.sys

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff80370800000 UsbHub3

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:

ffffd786`8ecb5818 fffff803`69b6de47 : 00000000`0000009f 00000000`00000003 ffffb40d`e1ed8dd0 ffffd786`8ecb5850 : nt!KeBugCheckEx

ffffd786`8ecb5820 fffff803`69b6dd61 : ffffb40d`dfd618b8 00000000`00000000 ffffb40d`e8397500 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0xdf

ffffd786`8ecb5890 fffff803`698368f2 : ffffb40d`dfd618f0 ffffd881`5e76f180 ffffd881`5e76f180 ffffd881`00000002 : nt!PopIrpWatchdog+0x31

ffffd786`8ecb58e0 fffff803`69839d8d : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`002df970 : nt!KiProcessExpiredTimerList+0x172

ffffd786`8ecb59d0 fffff803`699e1aae : ffffffff`00000000 ffffd881`5e76f180 ffffd881`5e77a340 ffffb40d`e4eea540 : nt!KiRetireDpcList+0x5dd

ffffd786`8ecb5c60 00000000`00000000 : ffffd786`8ecb6000 ffffd786`8ecb0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

IMAGE_VERSION: 10.0.19041.264

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_IMAGE_UsbHub3.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {58bbe6fe-0b43-accc-1beb-340d4227ae9c}

Followup: MachineOwner

---------