O
OG SAZOPAEZ
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 AMD64
Copyright (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) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (48 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`48e00000 PsLoadedModuleList = 0xfffff802`49248190
Debug session time: Sat Dec 12 16:17:22.485 2020 (UTC - 8:00)
System Uptime: 0 days 22:42:06.940
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`48fc23a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd403`a6b17880=000000000000009f
18: 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: ffff9a8a818a3060, Physical Device Object of the stack
Arg3: ffffd403a6b178b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff9e8549a579f0, The blocked IRP
Debugging Details:
------------------
DBGHELP: Timeout to store: C:\ProgramData\Dbg\sym*Symbol information
*** WARNING: Unable to verify checksum for win32k.sys
KEY_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.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffff9a8a818a3060
BUGCHECK_P3: ffffd403a6b178b0
BUGCHECK_P4: ffff9e8549a579f0
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbccgp.sys
MODULE_NAME: usbccgp
FAULTING_MODULE: fffff802584f0000 usbccgp
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffd403`a6b17878 fffff802`490ee817 : 00000000`0000009f 00000000`00000003 ffff9a8a`818a3060 ffffd403`a6b178b0 : nt!KeBugCheckEx
ffffd403`a6b17880 fffff802`490ee721 : ffff9e85`4a6d6490 00000000`00000001 ffffda80`cd518100 ffffda80`cd518180 : nt!PopIrpWatchdogBugcheck+0xef
ffffd403`a6b178f0 fffff802`48e512d9 : ffff9e85`4a6d64c8 000000be`490d6147 00000001`00000002 ffff9a8a`81812050 : nt!PopIrpWatchdog+0x31
ffffd403`a6b17940 fffff802`48e50039 : 00000000`00000016 00000000`00989680 00000000`002f9243 00000000`0000005b : nt!KiProcessExpiredTimerList+0x169
ffffd403`a6b17a30 fffff802`48fc5ece : ffffffff`00000000 ffffda80`cd518180 ffffda80`cd529c40 ffff9a8a`876b7580 : nt!KiRetireDpcList+0x4e9
ffffd403`a6b17c60 00000000`00000000 : ffffd403`a6b18000 ffffd403`a6b12000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e
IMAGE_VERSION: 10.0.18362.693
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_dgmbx2_IMAGE_usbccgp.sys
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f2749d30-8ff2-77c9-b6c9-67911e8954bb}
Followup: MachineOwner
---------
Continue reading...
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (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) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (48 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`48e00000 PsLoadedModuleList = 0xfffff802`49248190
Debug session time: Sat Dec 12 16:17:22.485 2020 (UTC - 8:00)
System Uptime: 0 days 22:42:06.940
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`48fc23a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd403`a6b17880=000000000000009f
18: 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: ffff9a8a818a3060, Physical Device Object of the stack
Arg3: ffffd403a6b178b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff9e8549a579f0, The blocked IRP
Debugging Details:
------------------
DBGHELP: Timeout to store: C:\ProgramData\Dbg\sym*Symbol information
*** WARNING: Unable to verify checksum for win32k.sys
KEY_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.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffff9a8a818a3060
BUGCHECK_P3: ffffd403a6b178b0
BUGCHECK_P4: ffff9e8549a579f0
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbccgp.sys
MODULE_NAME: usbccgp
FAULTING_MODULE: fffff802584f0000 usbccgp
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffd403`a6b17878 fffff802`490ee817 : 00000000`0000009f 00000000`00000003 ffff9a8a`818a3060 ffffd403`a6b178b0 : nt!KeBugCheckEx
ffffd403`a6b17880 fffff802`490ee721 : ffff9e85`4a6d6490 00000000`00000001 ffffda80`cd518100 ffffda80`cd518180 : nt!PopIrpWatchdogBugcheck+0xef
ffffd403`a6b178f0 fffff802`48e512d9 : ffff9e85`4a6d64c8 000000be`490d6147 00000001`00000002 ffff9a8a`81812050 : nt!PopIrpWatchdog+0x31
ffffd403`a6b17940 fffff802`48e50039 : 00000000`00000016 00000000`00989680 00000000`002f9243 00000000`0000005b : nt!KiProcessExpiredTimerList+0x169
ffffd403`a6b17a30 fffff802`48fc5ece : ffffffff`00000000 ffffda80`cd518180 ffffda80`cd529c40 ffff9a8a`876b7580 : nt!KiRetireDpcList+0x4e9
ffffd403`a6b17c60 00000000`00000000 : ffffd403`a6b18000 ffffd403`a6b12000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e
IMAGE_VERSION: 10.0.18362.693
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_dgmbx2_IMAGE_usbccgp.sys
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f2749d30-8ff2-77c9-b6c9-67911e8954bb}
Followup: MachineOwner
---------
Continue reading...