question

CasperThorrez-9389 avatar image
0 Votes"
CasperThorrez-9389 asked CasperThorrez-9389 edited

my pc has been bleu screening and now I looked at the dump file and I found this and dont understand it pls help

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


Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\042621-14390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`4a000000 PsLoadedModuleList = 0xfffff801`4ac2a3d0
Debug session time: Sun Apr 25 21:16:05.677 2021 (UTC + 2:00)
System Uptime: 0 days 3:11:16.433
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`4a3f5e40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`4f66e720=000000000000009f
0: 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: ffffd58b06c716f0, Physical Device Object of the stack
Arg3: fffff8014f66e750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd58b08d49010, The blocked IRP

Debugging Details:



Implicit thread is now ffffd58b`12d08540
WARNING: Unable to verify timestamp for CMUSBDAC.sys
WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

 Key  : Analysis.CPU.mSec
 Value: 5233

 Key  : Analysis.DebugAnalysisManager
 Value: Create

 Key  : Analysis.Elapsed.mSec
 Value: 70303

 Key  : Analysis.Init.CPU.mSec
 Value: 593

 Key  : Analysis.Init.Elapsed.mSec
 Value: 70006

 Key  : Analysis.Memory.CommitPeak.Mb
 Value: 100

 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.1


BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffd58b06c716f0

BUGCHECK_P3: fffff8014f66e750

BUGCHECK_P4: ffffd58b08d49010

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: ffffd58b12d08540

IMAGE_NAME: USBXHCI.SYS

MODULE_NAME: USBXHCI

FAULTING_MODULE: fffff80167f20000 USBXHCI

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa081`9c543f70 fffff801`4a265850 : ffffc080`62180180 00000000`ffffffff ffffa081`00000000 00000000`00000000 : nt!KiSwapContext+0x76
ffffa081`9c5440b0 fffff801`4a264d7f : 40008001`00000008 fffff801`0000000b ffffa081`9c544270 ffffd58b`00000000 : nt!KiSwapThread+0x500
ffffa081`9c544160 fffff801`4a264623 : 00000000`0000001f fffff801`00000000 ffff8000`00000000 ffffd58b`12d08680 : nt!KiCommitThreadWait+0x14f
ffffa081`9c544200 fffff801`6409fbf3 : ffffa081`9c544398 ffffd58b`00000000 fffff801`640ced00 00002a74`f7924f00 : nt!KeWaitForSingleObject+0x233
ffffa081`9c5442f0 fffff801`64087e7f : 00002a74`f7924f98 ffffa081`9c5443c9 ffffd58b`086db350 ffffffff`dc3cba00 : UsbHub3!HUBMISC_WaitForSignal+0xff
ffffa081`9c544360 fffff801`4deba977 : ffffd58b`1a3caaa0 ffffd58b`1a3caaa0 ffffd58b`1a3caaa0 ffffd58b`0162ed00 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0xf7f
ffffa081`9c544430 fffff801`4a252f55 : fffff801`6666b008 ffffd58b`083d8e10 00000000`00000000 ffffd58b`1a3caaa0 : Wdf01000!FxDevice::DispatchWithLock+0x267 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
ffffa081`9c544490 fffff801`4e03b58d : ffffd58b`083d8e10 ffffd58b`1a3caaa0 00000000`00000040 00000000`00000000 : nt!IofCallDriver+0x55
ffffa081`9c5444d0 fffff801`4e0310d6 : ffffd58a`f6305be0 00000000`00000007 ffffd58b`1a3caf60 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0xad
ffffa081`9c544510 fffff801`4a252f55 : 00000000`00000007 ffffd58b`1a3caaa0 00000000`0000000c ffffd58b`0175a8f8 : ACPI!ACPIDispatchIrp+0xc6
ffffa081`9c544590 fffff801`66656656 : 00000000`00000200 00000000`00000000 00000000`00000508 00000000`000000c0 : nt!IofCallDriver+0x55
ffffa081`9c5445d0 fffff801`66651a25 : ffffd58b`06c71848 ffffd58b`0175a8f8 00000000`00000028 fffff801`4a9b1094 : usbccgp!UsbcForwardIrp+0x36
ffffa081`9c544620 fffff801`666512a6 : ffffd58b`1a3caaa0 ffffd58b`06c71840 ffffd58b`06c71848 fffff801`00000000 : usbccgp!DispatchPdoInternalDeviceControl+0x235
ffffa081`9c544690 fffff801`4a252f55 : ffffd58b`06c716f0 ffffa081`00000001 00000000`00000000 ffffa081`00000000 : usbccgp!USBC_Dispatch+0x296
ffffa081`9c544760 fffff801`67ae4077 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc080`6230e000 : nt!IofCallDriver+0x55
ffffa081`9c5447a0 00000000`00000000 : 00000000`00000000 00000000`00000000 ffffc080`6230e000 00000000`00000000 : CMUSBDAC+0x374077


STACK_COMMAND: .thread 0xffffd58b12d08540 ; kb

IMAGE_VERSION: 10.0.19041.867

SYMBOL_NAME: USBXHCI!Isoch_EvtDmaCallback <PERF> (USBXHCI+0x0)+0

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_UsbHub3_USBXHCI!Isoch_EvtDmaCallback_PERF_(USBXHCI+0x0)

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7bc5ac66-4808-00bc-ea12-43f8a9f12b88}

Followup: MachineOwner



windows-10-general
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

CarlFan-MSFT avatar image
1 Vote"
CarlFan-MSFT answered CasperThorrez-9389 edited

Hi,
According to the information, it refers to the error DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Wdf01000 .sys is a device frame driver. These BSOD errors are due to damaged drivers installed on your computer.

There are some of the most common reasons for this error. One of them is the USB problem port.
In the STACK_TEXT: some information displayed:
UsbHub.sys and CMUSBDAC.sys.
So please reinstall or update the motherboard chipset and usb driver from the manufacturer's official website.
Also C-Media USB Device Audio Class Driver.
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

thx I wil try this but it sounds like it wil work

0 Votes 0 ·

@CarlFan-MSFT I did everthing you said accept for the c media I did not find a download for windows 10
I did do the driver updates but still my pc blue screens some times if you pls would help me

0 Votes 0 ·