Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
D
darkman007e
1 Rookie
•
5 Posts
0
8289
July 17th, 2022 21:00
XPS 9570 DRIVER_POWER_STATE_FAILURE BSoD
Since late June 27, I've been having random BSoD with the error DRIVER_POWER_STATE_FAILURE.
I used WinDLG to try to find the root cause.
Here is what I have from my latest BSoD.
Spoiler
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`12400000 PsLoadedModuleList = 0xfffff801`1302a2b0
Debug session time: Mon Jul 18 00:07:53.949 2022 (UTC - 4:00)
System Uptime: 1 days 1:09:05.612
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...............................................
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff801`127f7dd0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe687`51e5f720=000000000000009f
4: 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: ffffd602ceb20060, Physical Device Object of the stack
Arg3: ffffe68751e5f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd602fb833a40, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffd602`cc48e040
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvdm.inf_amd64_d622d16ed9c37077\nvlddmkm.sys, Win32 error 0n2
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4874
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 5755
Key : Analysis.Init.CPU.mSec
Value: 3218
Key : Analysis.Init.Elapsed.mSec
Value: 4326
Key : Analysis.Memory.CommitPeak.Mb
Value: 104
Key : Bugcheck.Code.DumpHeader
Value: 0x9f
Key : Bugcheck.Code.KiBugCheckData
Value: 0x9f
Key : Bugcheck.Code.Register
Value: 0x9f
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
FILE_IN_CAB: MEMORY.DMP
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffd602ceb20060
BUGCHECK_P3: ffffe68751e5f750
BUGCHECK_P4: ffffd602fb833a40
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffffd602cc48e040
ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.
IRP_ADDRESS: ffffd602fb833a40
DEVICE_OBJECT: ffffd602ceb20060
DRIVER_OBJECT: ffffd602ceaa9270
IMAGE_NAME: pci.sys
MODULE_NAME: pci
FAULTING_MODULE: fffff801170b0000 pci
BLACKBOXACPI: 1 (!blackboxacpi)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffffe687`51e1f3c0 fffff801`126550b0 : ffffc580`fce80180 fffff801`ffffffff 00000000`00000001 fffff801`170301ca : nt!KiSwapContext+0x76
ffffe687`51e1f500 fffff801`126545df : 00000000`00000001 fffff801`00000000 ffffe687`51e1f6c0 ffffd602`00000000 : nt!KiSwapThread+0x500
ffffe687`51e1f5b0 fffff801`12653e83 : 00000000`00000000 fffff801`00000000 00000000`00000000 ffffd602`cc48e180 : nt!KiCommitThreadWait+0x14f
ffffe687`51e1f650 fffff801`244019c6 : ffffe687`51e1f778 ffffd602`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x233
ffffe687`51e1f740 fffff801`24400ee1 : ffffe687`51e1f800 ffffd602`ef877700 ffffd602`ceaedde0 ffffd602`fb833c30 : dxgkrnl!DpiFdoHandleDevicePower+0x226
ffffe687`51e1f7e0 fffff801`24402431 : ffffd602`fb833a40 ffffd602`e748c180 ffffd602`e748c030 ffffe687`51e1f900 : dxgkrnl!DpiFdoDispatchPower+0x21
ffffe687`51e1f810 fffff801`2b48eb8c : ffffd602`fb2d9000 ffffd602`ea5bf000 ffffd602`fb2d9000 ffffd602`fb833c30 : dxgkrnl!DpiDispatchPower+0xe1
ffffe687`51e1f930 fffff801`2b48dc90 : ffffd602`e748c030 ffffd602`ea5bf000 ffffd602`e748c030 ffffd602`00000000 : nvlddmkm!nvDumpConfig+0x4c86fc
ffffe687`51e1fa40 fffff801`1279d629 : ffffd602`cc48e040 ffffe687`51e1faf0 ffffd602`fb833a40 ffffd602`00000000 : nvlddmkm!nvDumpConfig+0x4c7800
ffffe687`51e1fa70 fffff801`126eea75 : 00000000`00000000 fffff801`1279d450 00000000`00000000 00000000`00000138 : nt!PopIrpWorker+0x1d9
ffffe687`51e1fb10 fffff801`127ff428 : ffffc580`fd101180 ffffd602`cc48e040 fffff801`126eea20 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffe687`51e1fb60 00000000`00000000 : ffffe687`51e20000 ffffe687`51e19000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
IMAGE_VERSION: 10.0.19041.1741
STACK_COMMAND: .process /r /p 0xffffd602cc4c5080; .thread 0xffffd602cc48e040 ; kb
FAILURE_BUCKET_ID: 0x9F_3_DXG_POWER_IRP_TIMEOUT_IMAGE_pci.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {52f87b6b-6f6d-7c24-f421-639ee8689be5}
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff801`12400000 PsLoadedModuleList = 0xfffff801`1302a2b0 Debug session time: Mon Jul 18 00:07:53.949 2022 (UTC - 4:00) System Uptime: 1 days 1:09:05.612 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................................................ ........... Loading User Symbols Loading unloaded module list ............................................... For analysis of this file, run !analyze -vnt!KeBugCheckEx: fffff801`127f7dd0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe687`51e5f720=000000000000009f 4: 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: ffffd602ceb20060, Physical Device Object of the stack Arg3: ffffe68751e5f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffd602fb833a40, The blocked IRP Debugging Details: ------------------ Implicit thread is now ffffd602`cc48e040 Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvdm.inf_amd64_d622d16ed9c37077\nvlddmkm.sys, Win32 error 0n2 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4874 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 5755 Key : Analysis.Init.CPU.mSec Value: 3218 Key : Analysis.Init.Elapsed.mSec Value: 4326 Key : Analysis.Memory.CommitPeak.Mb Value: 104 Key : Bugcheck.Code.DumpHeader Value: 0x9f Key : Bugcheck.Code.KiBugCheckData Value: 0x9f Key : Bugcheck.Code.Register Value: 0x9f 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 FILE_IN_CAB: MEMORY.DMP TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b BUGCHECK_CODE: 9f BUGCHECK_P1: 3 BUGCHECK_P2: ffffd602ceb20060 BUGCHECK_P3: ffffe68751e5f750 BUGCHECK_P4: ffffd602fb833a40 DRVPOWERSTATE_SUBCODE: 3 FAULTING_THREAD: ffffd602cc48e040 ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout. IRP_ADDRESS: ffffd602fb833a40 DEVICE_OBJECT: ffffd602ceb20060 DRIVER_OBJECT: ffffd602ceaa9270 IMAGE_NAME: pci.sys MODULE_NAME: pci FAULTING_MODULE: fffff801170b0000 pci BLACKBOXACPI: 1 (!blackboxacpi) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: ffffe687`51e1f3c0 fffff801`126550b0 : ffffc580`fce80180 fffff801`ffffffff 00000000`00000001 fffff801`170301ca : nt!KiSwapContext+0x76 ffffe687`51e1f500 fffff801`126545df : 00000000`00000001 fffff801`00000000 ffffe687`51e1f6c0 ffffd602`00000000 : nt!KiSwapThread+0x500 ffffe687`51e1f5b0 fffff801`12653e83 : 00000000`00000000 fffff801`00000000 00000000`00000000 ffffd602`cc48e180 : nt!KiCommitThreadWait+0x14f ffffe687`51e1f650 fffff801`244019c6 : ffffe687`51e1f778 ffffd602`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x233 ffffe687`51e1f740 fffff801`24400ee1 : ffffe687`51e1f800 ffffd602`ef877700 ffffd602`ceaedde0 ffffd602`fb833c30 : dxgkrnl!DpiFdoHandleDevicePower+0x226 ffffe687`51e1f7e0 fffff801`24402431 : ffffd602`fb833a40 ffffd602`e748c180 ffffd602`e748c030 ffffe687`51e1f900 : dxgkrnl!DpiFdoDispatchPower+0x21 ffffe687`51e1f810 fffff801`2b48eb8c : ffffd602`fb2d9000 ffffd602`ea5bf000 ffffd602`fb2d9000 ffffd602`fb833c30 : dxgkrnl!DpiDispatchPower+0xe1 ffffe687`51e1f930 fffff801`2b48dc90 : ffffd602`e748c030 ffffd602`ea5bf000 ffffd602`e748c030 ffffd602`00000000 : nvlddmkm!nvDumpConfig+0x4c86fc ffffe687`51e1fa40 fffff801`1279d629 : ffffd602`cc48e040 ffffe687`51e1faf0 ffffd602`fb833a40 ffffd602`00000000 : nvlddmkm!nvDumpConfig+0x4c7800 ffffe687`51e1fa70 fffff801`126eea75 : 00000000`00000000 fffff801`1279d450 00000000`00000000 00000000`00000138 : nt!PopIrpWorker+0x1d9 ffffe687`51e1fb10 fffff801`127ff428 : ffffc580`fd101180 ffffd602`cc48e040 fffff801`126eea20 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffffe687`51e1fb60 00000000`00000000 : ffffe687`51e20000 ffffe687`51e19000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 IMAGE_VERSION: 10.0.19041.1741 STACK_COMMAND: .process /r /p 0xffffd602cc4c5080; .thread 0xffffd602cc48e040 ; kb FAILURE_BUCKET_ID: 0x9F_3_DXG_POWER_IRP_TIMEOUT_IMAGE_pci.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {52f87b6b-6f6d-7c24-f421-639ee8689be5} Followup: MachineOwner ---------
This line indicates the issues is caused by the Nvidia GPU.
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvdm.inf_amd64_d622d16ed9c37077\nvlddmkm.sys
I've performed all of this already :
-Disabled all sleep features in Windows
-Install latest Nvidia drivers
-Install Nvidia studio drivers (BSoD still happens but a bit less frequently)
-Install the Bios update (1.25.0)
-Install latest DisplayLink drivers (I use mostly an old USB 3.0 dock)
-Uninstall both Intel and Nvidia drivers
-Reinstall the latest Dell Intel and Nvidia drivers (this has initally help where I had 5 days with no BSoD as opposed to a BSoD every 1-2 days).
My only option left at this point is to reinstall Windows 10. The other weird thing is that sometime it happens when I'm using my PC but most BSoD happens when the PC hasn't been used for a while.
I have just disabled the Nvidia GPU in the device manager. We'll see in a few days what happens.
