How to fix the error "A driver has failed to complete a power IRP within a specific time" that causes windows to freeze

Question

I've updated windows to the current 21H1 build, uninstalled my NVIDIA devices and drivers and reinstalled them again as a result of an issue with my nvlddmkm.sys file. This is the first time I've seen this error since. My laptop is hooked up to an MSI USB-C docking station with dual monitors.

Below is the minidump file data from Windbg:

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: ffff8c8b7bbe7600, Physical Device Object of the stack
Arg3: ffffc98e36c7f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff8c8b81e8d060, The blocked IRP

Debugging Details:

---

Implicit thread is now ffff8c8b`792ac400
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvmii.inf_amd64_ae100378cf58e795\nvlddmkm.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3109

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 4294

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

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

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

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: ffff8c8b7bbe7600

BUGCHECK_P3: ffffc98e36c7f750

BUGCHECK_P4: ffff8c8b81e8d060

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: ffff8c8b792ac400

ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffc98e36c16e80 fffff8025b20c970 : ffffa00100000000 0000000000000000 0000000000000000 ffffc98e36c170d0 : nt!KiSwapContext+0x76
ffffc98e36c16fc0 fffff8025b20be9f : 0000000000000003 0000000000000000 ffffc98e36c17180 0000000000000000 : nt!KiSwapThread+0x500
ffffc98e36c17070 fffff8025b20b743 : fffff80200000000 0000000000000000 0000000000000000 ffff8c8b792ac540 : nt!KiCommitThreadWait+0x14f
ffffc98e36c17110 fffff80278baab14 : ffff8c8b86fc7f60 0000000000000000 ffffa001fcd9c000 0000000000000000 : nt!KeWaitForSingleObject+0x233
ffffc98e36c17200 fffff80278c4d63c : ffff8c8b82044000 ffffc98e36c17309 ffff8c8b82044000 0000000000000001 : nvlddmkm+0xa8ab14
ffffc98e36c17260 fffff80278b628f0 : 0000000000000001 ffff8c8b82044000 ffff8c8b82044000 0000000000000000 : nvlddmkm+0xb2d63c
ffffc98e36c17290 fffff80278b6bdd1 : 0000000000000000 0000000000000001 0000000000000000 ffff8c8b82044000 : nvlddmkm+0xa428f0
ffffc98e36c17370 fffff80278e60e5a : 0000000000000004 0000000000000004 ffff8c8b82022000 0000000000000001 : nvlddmkm+0xa4bdd1
ffffc98e36c173f0 fffff80278e6068b : 0000000000000001 ffff8c8b82022000 0000000000000000 0000000000000000 : nvlddmkm+0xd40e5a
ffffc98e36c174c0 fffff80278e8bb06 : ffff8c8b82022000 ffffc98e36c175b9 0000000000000001 0000000000000007 : nvlddmkm+0xd4068b
ffffc98e36c17510 fffff80274064b6e : fffff80278e8b9dc 0000000000000001 0000000000000000 00000000ffffffff : nvlddmkm+0xd6bb06
ffffc98e36c17620 fffff802740640bf : 0000000000000000 ffffc98e36c176e1 0000000000000000 ffff8c8b82627670 : dxgkrnl!DpiDxgkDdiSetPowerState+0x5a
ffffc98e36c17680 fffff80274064fee : 0000000000000000 ffff8c8b81e8d060 0000000000000001 0000000000000001 : dxgkrnl!DpiFdoSetAdapterPowerState+0x15f
ffffc98e36c17740 fffff80274064441 : ffff8c8b822e7700 ffff8c8b822e7790 ffff8c8b7bbeba90 ffff8c8b81e8d250 : dxgkrnl!DpiFdoHandleDevicePower+0x2ee
ffffc98e36c177e0 fffff80274065991 : ffff8c8b81e8d060 ffff8c8b826cd180 ffff8c8b826cd030 e94bd39e4794807b : dxgkrnl!DpiFdoDispatchPower+0x21
ffffc98e36c17810 fffff80278ea4248 : ffff8c8b86fb2000 ffffc98e36c179d9 ffff8c8b86fb2000 ffff8c8b81e8d250 : dxgkrnl!DpiDispatchPower+0xe1
ffffc98e36c17930 fffff80278ea3350 : ffff8c8b826cd030 ffff8c8b82022000 ffff8c8b826cd030 ffff8c8b00000000 : nvlddmkm+0xd84248
ffffc98e36c17a40 fffff8025b39ce99 : ffff8c8b792ac400 ffffc98e36c17af0 ffff8c8b81e8d060 ffff8c8b00000000 : nvlddmkm+0xd83350
ffffc98e36c17a70 fffff8025b2f53b5 : 0000000000000000 fffff8025b39ccc0 0000000000000000 0000000000000197 : nt!PopIrpWorker+0x1d9
ffffc98e36c17b10 fffff8025b3fe348 : ffffa001f8d00180 ffff8c8b792ac400 fffff8025b2f5360 8948c43348003515 : nt!PspSystemThreadStartup+0x55
ffffc98e36c17b60 0000000000000000 : ffffc98e36c18000 ffffc98e36c11000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

STACK_COMMAND: .thread 0xffff8c8b792ac400 ; kb

SYMBOL_NAME: nvlddmkm+a8ab14

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

BUCKET_ID_FUNC_OFFSET: a8ab14

FAILURE_BUCKET_ID: 0x9F_3_DXG_POWER_IRP_TIMEOUT_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {8cc60268-7d19-e594-85e0-3d3e4d0907af}

Answer 1

I have the same issue...only difference is that I have not updated to 21H1 yet which means there seems to be a common denominator in the updates that come before that specific update.

Not really helpful

I also updated my video drivers recently and I am working on rolling back to see where I can find a fix. It could also be the built in Intel video chip not playing well (I updated both) with the NVIDIA card.

I ONLY have this problem (so far) when alt-tabbing out of a game which will shut down my NVIDIA GPU (since Firefox/desktop is using the onboard Intel video chip) which of course causes my NVIDIA card to shut down (this can be seen from the temp displayed according to HWiNFO going from it's current temp to 0).

Surprisingly setting the GPU to "prefer performance" and/or setting the global preference to use my NVIDIA card in the NVIDIA control panel (essentially forcing it to always be "on") did not seem to prevent this.

Will update if I find a solution...you do the same if you can.

Logs Below:

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: ffff8e8839dd1630, Physical Device Object of the stack
Arg3: fffff8024ca6e750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff8e883f0a5a20, The blocked IRP

Debugging Details:

---

Implicit thread is now ffff8e88`38cf0040

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.Sec
Value: 3

Key  : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-NAR4F2T

Key  : Analysis.DebugData
Value: CreateObject

Key  : Analysis.DebugModel
Value: CreateObject

Key  : Analysis.Elapsed.Sec
Value: 17

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

Key  : Analysis.System
Value: CreateObject

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffff8e8839dd1630

BUGCHECK_P3: fffff8024ca6e750

BUGCHECK_P4: ffff8e883f0a5a20

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: ffff8e8838cf0040

ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd7081041e6a0 fffff80262a14c34 : 000000000000000a ffffd7081041e7d0 0000000000000000 0000000000000000 : nt!KeStallExecutionProcessor+0x10c
ffffd7081041e720 fffff80262e67d2a : ffff8e884059a000 00000000ffffffff 0000000000000000 0000000000000000 : nvlddmkm+0x84c34
ffffd7081041e750 fffff80262e5a3c0 : 0000000000000003 0000000000000000 ffffd70800610590 ffff8e884059a000 : nvlddmkm+0x4d7d2a
ffffd7081041e780 fffff80262e4f984 : 0000000000000000 0000000000000000 00000000c1d00002 ffff8e884059a000 : nvlddmkm+0x4ca3c0
ffffd7081041e810 fffff80262e60c52 : ffff8e8800000014 ffff8e884059a000 ffff8e8840596010 ffff8e883d991820 : nvlddmkm+0x4bf984
ffffd7081041e880 fffff80262a38bec : ffff8e8800000004 ffff8e883f0e3e10 ffff8e8800000025 ffff8e8840590000 : nvlddmkm+0x4d0c52
ffffd7081041e8f0 fffff80262be7635 : ffff8e884057c000 fffff80200000000 ffff8e884057c000 ffff8e883d2bd000 : nvlddmkm+0xa8bec
ffffd7081041e9f0 fffff80262be74c9 : ffff8e884057c000 0000000000000000 ffff8e883d2bd000 ffff8e8840648c30 : nvlddmkm+0x257635
ffffd7081041ea30 fffff80262be4bb2 : ffff8e884057c000 0000000000000000 ffff8e884059a000 ffffd70800000000 : nvlddmkm+0x2574c9
ffffd7081041ea60 fffff80262ba0433 : 0000000000000000 fffff8026333c120 ffff8e88406d2018 ffffd7081041ec40 : nvlddmkm+0x254bb2
ffffd7081041eae0 fffff80262a9d782 : 0000000000000004 ffffd70800000001 ffffd7081041ebf0 fffff802631f7e60 : nvlddmkm+0x210433
ffffd7081041eb40 fffff80262aa55d6 : 0000000000000000 0000000000000013 ffff8e8800000001 ffff8e883f0308c8 : nvlddmkm+0x10d782
ffffd7081041ebc0 fffff80262aa5825 : ffff8e88509c88c8 00000000ff030000 00000000c1d00002 00000000c1d00002 : nvlddmkm+0x1155d6
ffffd7081041edc0 fffff80262aa58d3 : ffffd7081041ee60 0000000000000000 0000000000000000 0000002000000000 : nvlddmkm+0x115825
ffffd7081041ee20 fffff80262a115a4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nvlddmkm+0x1158d3
ffffd7081041f0c0 fffff80262a1150f : ffffd7081041f200 0000000000000014 0000000000000000 0000000000000000 : nvlddmkm+0x815a4
ffffd7081041f170 fffff80263185d39 : ffffd7081041f260 0000000000000014 0000000000000000 ffffd7081041f301 : nvlddmkm+0x8150f
ffffd7081041f1b0 fffff80263185f97 : fffff80263185ccd 000000002080270d ffff8e883d444138 fffff80262a0bfed : nvlddmkm+0x7f5d39
ffffd7081041f240 fffff802629a430b : 0000000000000000 000000002080270d ffffd7081041f3b0 ca274b9740b73df5 : nvlddmkm+0x7f5f97
ffffd7081041f2a0 fffff8026319c468 : ffff8e883d0b4000 ffffd7081041f389 0000000000000001 0000000000000001 : nvlddmkm+0x1430b
ffffd7081041f300 fffff802636cd8c7 : 0000000000000004 0000000000000000 0000000000000000 ffff8e883d444000 : nvlddmkm+0x80c468
ffffd7081041f3f0 fffff802636cd61b : 0000000000000000 ffff8e883d444000 0000000000000000 0000000000000000 : nvlddmkm+0xd3d8c7
ffffd7081041f4c0 fffff802636f8a8a : ffff8e883d444000 ffffd7081041f5b9 0000000000000004 0000000000000007 : nvlddmkm+0xd3d61b
ffffd7081041f510 fffff8025e5b4b6e : fffff802636f8960 0000000000000004 0000000000000000 00000000ffffffff : nvlddmkm+0xd68a8a
ffffd7081041f620 fffff8025e5b42ae : 0000000000000000 ffffd7081041f6e1 0000000000000000 ffff8e883d2c4050 : dxgkrnl!DpiDxgkDdiSetPowerState+0x5a
ffffd7081041f680 fffff8025e5b4e34 : 0000000000000000 ffff8e883f0a5a20 0000000000000004 0000000000000004 : dxgkrnl!DpiFdoSetAdapterPowerState+0x34e
ffffd7081041f740 fffff8025e5b4441 : ffffd7081041f801 0000000000000004 ffff8e8839dc1bd0 ffff8e883f0a5c10 : dxgkrnl!DpiFdoHandleDevicePower+0x134
ffffd7081041f7e0 fffff8025e5b5991 : ffff8e883f0a5a20 ffff8e883d2c3180 ffff8e883d2c3030 ffff8e883d2c3030 : dxgkrnl!DpiFdoDispatchPower+0x21
ffffd7081041f810 fffff802637111cc : ffff8e883d0b4000 ffffd7081041f9d9 ffff8e883d0b4000 ffff8e883f0a5c10 : dxgkrnl!DpiDispatchPower+0xe1
ffffd7081041f930 fffff802637102d4 : ffff8e883d2c3030 0000000000000000 ffff8e883d2c3030 ffff8e883f0a5a20 : nvlddmkm+0xd811cc
ffffd7081041fa40 fffff80245d9ce99 : ffff8e8838cf0040 ffffd7081041faf0 ffff8e883f0a5a20 ffff8e8800000000 : nvlddmkm+0xd802d4
ffffd7081041fa70 fffff80245cf53b5 : 0000000000000000 fffff80245d9ccc0 0000000000000000 00000000000000f9 : nt!PopIrpWorker+0x1d9
ffffd7081041fb10 fffff80245dfe348 : ffffdd01bcdc7180 ffff8e8838cf0040 fffff80245cf5360 d0ec8148ffffff30 : nt!PspSystemThreadStartup+0x55
ffffd7081041fb60 0000000000000000 : ffffd70810420000 ffffd70810419000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

STACK_COMMAND: .thread 0xffff8e8838cf0040 ; kb

SYMBOL_NAME: nvlddmkm+84c34

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

BUCKET_ID_FUNC_OFFSET: 84c34

FAILURE_BUCKET_ID: 0x9F_3_DXG_POWER_IRP_TIMEOUT_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {8cc60268-7d19-e594-85e0-3d3e4d0907af}

Followup: MachineOwner

---

0: kd> !blackboxbsd
Version: 176
Product type: 1

Auto advanced boot: FALSE
Advanced boot menu timeout: 30
Last boot succeeded: TRUE
Last boot shutdown: FALSE
Sleep in progrees: FALSE

Power button timestamp: 0
System running: TRUE
Connected standby in progress: FALSE
User shutdown in progress: FALSE
System shutdown in progress: FALSE
Sleep in progress: 0
Connected standby scenario instance id: 0
Connected standby entry reason: 0
Connected standby exit reason: 0
System sleep transitions to on: 0
Last reference time: 0x1d75b8ad3abff0b
Last reference time checksum: 0x4c8399eb
Last update boot id: 183

Boot attempt count: 2
Last boot checkpoint: TRUE
Checksum: 0x7f
Last boot id: 183
Last successful shutdown boot id: 173
Last reported abnormal shutdown boot id: 182

Error info boot id: 0
Error info repeat count: 0
Error info other error count: 0
Error info code: 0
Error info other error count: 0

Power button last press time: 0
Power button cumulative press count: 0
Power button last press boot id: 0
Power button last power watchdog stage: 0
Power button watchdog armed: FALSE
Power button shutdown in progress: FALSE
Power button last release time: 0
Power button cumulative release count: 0
Power button last release boot id: 0
Power button error count: 0
Power button current connected standby phase: 0
Power button transition latest checkpoint id: 0
Power button transition latest checkpoint type: 0
Power button transition latest checkpoint sequence number: 0
0: kd> !blackboxntfs

NTFS Blackbox Data

0 Slow I/O Timeout Records Found
0 Oplock Break Timeout Records Found
0: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 132675366031160594
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : SW{96E080C7-143C-11D1-B40F-00A0C9223196}{3C0D501A-140B-11D1-B40F-00A0C9223196}
VetoString :

Answer 2

Hi friends,

Have you guys found the solution or fix for this issue? I am facing the same exact issue on my HP Omen 15. The debugger is showing the same error details which Jeff shared. I am facing this when my laptop is in lock state (Winkey+L). After approx 2 mins, the display goes off along with keyboard freeze and system reboot.

Answer 3

Having this same issue with a Dell Mobile Precision connected to a dock with dual monitors (DisplayPort) on 21H1. Once the monitors go dark, only 1 (or sometimes none) re-awake. Previously using latest Nvidia drivers for laptop per Dell's website now using Nvidia reference drivers. Any updates?

Answer 4

I still don't have any clue what is causing the issue? My laptop specifications are HP Omen i7 10th Gen, 32 GB RAM, NVIDIA RTX 3070 8 GB.
Just for a work around and not to lose my work during restart, I increased the time for 'Turn off display after' and 'Console lock display off timeout' to 6 hours.
I hope someone will find the root cause of this but I am sure there is some link with 21H1 update with NVIDIA drivers.

Cheers.

Answer 5

Having the same issue here too, Surface Laptop 3 (intel) on 21H1, looks like it wasn't happening pre-update to 21H1.