Unsolved

2 Posts

1109

August 7th, 2022 08:00

DRIVER_POWER_STATE_FAILURE by WIN11

Hello, in the last month I have been experiencing the DRIVER_POWER_STATE_FAILURE error when using both Photoshop and Lightroom. I thought this error was related to the Win 11 upgrade, so I did a clean install of Win 11 from the original distribution and installed the drivers using Dell's SupportAssist. But the problem, unfortunately, did not disappear (
I updated all the drivers to the latest and rolled back to the previous ones - neither one nor the other action gave any result.
Help me please!!!
I am attaching the dumps:

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


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


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Users\nost1\Documents\Sym_WinDBG*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Users\nost1\Documents\Sym_WinDBG*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff801`40412000 PsLoadedModuleList = 0xfffff801`4103b730
Debug session time: Sun Aug  7 15:02:39.413 2022 (UTC + 4:00)
System Uptime: 1 days 5:37:44.904
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
...........................
For analysis of this file, run !analyze -v
7: 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: ffffe20fee3ad390, Physical Device Object of the stack
Arg3: fffffd0f8bc97b40, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe20ff844b4e0, The blocked IRP

Debugging Details:
------------------

Implicit thread is now ffffe20f`e8927040
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3421

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 10496

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  080722-13640-01.dmp

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe20fee3ad390

BUGCHECK_P3: fffffd0f8bc97b40

BUGCHECK_P4: ffffe20ff844b4e0

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffffe20fe8927040

ADDITIONAL_DEBUG_TEXT:  DXG Power IRP timeout.

IRP_ADDRESS: ffffe20ff844b4e0

DEVICE_OBJECT: ffffe20fee3ad390

DRIVER_OBJECT: ffffe20fee393cb0

IMAGE_NAME:  pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff80141ca0000 pci

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  PhoneExperienceHost.exe

DPC_STACK_BASE:  FFFFFD0F8BC97FB0

STACK_TEXT:  
fffffd0f`8bc1f370 fffff801`40692c17     : fffff801`3fa77180 fffff801`3fa77180 00000000`00000000 00000000`00000003 : nt!KiSwapContext+0x76
fffffd0f`8bc1f4b0 fffff801`40694ac9     : ffffe20f`00000000 fffff801`00000008 fffffd0f`8bc1f690 fffff801`00000000 : nt!KiSwapThread+0x3a7
fffffd0f`8bc1f590 fffff801`4068e9e4     : 00000000`00000000 ffffe20f`00000000 fffffd0f`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x159
fffffd0f`8bc1f630 fffff80c`c887ef3b     : fffffd0f`8bc1f758 ffffe20f`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x234
fffffd0f`8bc1f720 fffff80c`c887e6a1     : ffffe20f`f766b030 00000000`00050200 fffffd0f`8bc1f7e8 00000000`00000018 : dxgkrnl!DpiFdoHandleDevicePower+0x21b
fffffd0f`8bc1f7c0 fffff80c`c8880011     : ffffe20f`f844b4e0 ffffe20f`f766b180 ffffe20f`f766b030 00000000`00000000 : dxgkrnl!DpiFdoDispatchPower+0x21
fffffd0f`8bc1f7f0 fffff80c`daa3d602     : ffffe20f`fa66f000 00000000`00000001 ffffe20f`fa66f000 ffffe20f`f7fc2000 : dxgkrnl!DpiDispatchPower+0xe1
fffffd0f`8bc1f910 ffffe20f`fa66f000     : 00000000`00000001 ffffe20f`fa66f000 ffffe20f`f7fc2000 ffffe20f`00000004 : nvlddmkm+0xead602
fffffd0f`8bc1f918 00000000`00000001     : ffffe20f`fa66f000 ffffe20f`f7fc2000 ffffe20f`00000004 00000000`00000000 : 0xffffe20f`fa66f000
fffffd0f`8bc1f920 ffffe20f`fa66f000     : ffffe20f`f7fc2000 ffffe20f`00000004 00000000`00000000 00000000`00000001 : 0x1
fffffd0f`8bc1f928 ffffe20f`f7fc2000     : ffffe20f`00000004 00000000`00000000 00000000`00000001 00000000`000000ff : 0xffffe20f`fa66f000
fffffd0f`8bc1f930 ffffe20f`00000004     : 00000000`00000000 00000000`00000001 00000000`000000ff ffffe20f`f7fc2000 : 0xffffe20f`f7fc2000
fffffd0f`8bc1f938 00000000`00000000     : 00000000`00000001 00000000`000000ff ffffe20f`f7fc2000 00000000`00000000 : 0xffffe20f`00000004


IMAGE_VERSION:  10.0.22000.832

STACK_COMMAND:  .process /r /p 0xffffe20fe890d040; .thread 0xffffe20fe8927040 ; kb

FAILURE_BUCKET_ID:  0x9F_VRF_3_DXG_POWER_IRP_TIMEOUT_IMAGE_pci.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f5a42204-e1d8-eb03-a0cb-2d153e492dea}

Followup:     MachineOwner
---------

7: kd> !irp fffffd0f8bc97b40
IRP signature does not match, probably not an IRP.  Use any flag to force.
7: kd> !irp ffffe20ff844b4e0
Irp is active with 6 stacks 4 is current (= 0xffffe20ff844b688)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe20fee3ad390 00000000 fffff80cc86b48b0-fffffd0f8bc1f758 Success Error Cancel pending
	       \Driver\pci	dxgkrnl!DpiFdoPowerCompletionRoutine
			Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe20ff766b030 00000000 fffff801407b23b0-ffffe20ffa94a8a8 Success Error Cancel pending
	       \Driver\nvlddmkm	nt!PopRequestCompletion
			Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe20ffa94a8a8    

			Args: 00000000 00000000 00000000 00000000

Irp Extension present at 0xffffe20ff844b760:
7: kd> !drvobj \Driver\nvlddmkm
fffff80141036e90: Unable to get value of ObpRootDirectoryObject
Driver object \Driver\nvlddmkm not found
7: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff80c`d9b90000 fffff80c`dc638000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvdmsig.inf_amd64_49dd3278a0522d90\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Jul 21 07:04:31 2022 (62D8C23F)
    CheckSum:         029BD8AE
    ImageSize:        02AA8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

 

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


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


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Users\nost1\Documents\Sym_WinDBG*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Users\nost1\Documents\Sym_WinDBG*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff804`1d40a000 PsLoadedModuleList = 0xfffff804`1e033730
Debug session time: Sun Aug  7 18:20:11.054 2022 (UTC + 4:00)
System Uptime: 0 days 2:09:21.148
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
2: 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: ffff8608a4230370, Physical Device Object of the stack
Arg3: fffff58c3743f6d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff8608a41daa60, The blocked IRP

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2437

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7095

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  080722-14281-01.dmp

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffff8608a4230370

BUGCHECK_P3: fffff58c3743f6d0

BUGCHECK_P4: ffff8608a41daa60

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff8041ee30000 pci

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff58c`3743f698 fffff804`1d9ccd47     : 00000000`0000009f 00000000`00000003 ffff8608`a4230370 fffff58c`3743f6d0 : nt!KeBugCheckEx
fffff58c`3743f6a0 fffff804`1d9ccc61     : ffff8608`a41da2e0 00000000`00000080 fffff58c`3743f9f8 fffff58c`3743f9f0 : nt!PopIrpWatchdogBugcheck+0xdf
fffff58c`3743f710 fffff804`1d6b2324     : 00000000`00000000 00000000`00000001 fffff58c`00000000 00000000`00000002 : nt!PopIrpWatchdog+0x31
fffff58c`3743f760 fffff804`1d6b0914     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`1cc11288 : nt!KiProcessExpiredTimerList+0x204
fffff58c`3743f890 fffff804`1d825c6e     : 00000000`00000000 ffff9600`70200180 ffff9600`7020c340 ffff8608`c72ea080 : nt!KiRetireDpcList+0x714
fffff58c`3743fb40 00000000`00000000     : fffff58c`37440000 fffff58c`37439000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


IMAGE_VERSION:  10.0.22000.832

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x9F_VRF_3_AML!_SB.PCI0.PEG0.PG00._ON_ACPI_IMAGE_pci.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {44ab3790-951d-40ef-027e-1aadc709d77a}

Followup:     MachineOwner
---------

2: kd> !irp ffff8608a41daa60
Irp is active with 6 stacks 4 is current (= 0xffff8608a41dac08)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff8608a4284d60 00000000 fffff8041ee47ae0-ffff8608a41d0a20 Success Error Cancel pending
	       \Driver\ACPI	pci!PciBusPowerUpCompletion
			Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff8608a41d08d0 00000000 fffff8041d7aa3b0-ffff8608a41da2e0 Success Error Cancel pending
	       \Driver\pci	nt!PopRequestCompletion
			Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffff8608a41da2e0    

			Args: 00000000 00000000 00000000 00000000

Irp Extension present at 0xffff8608a41dace0:

 

No Responses!

0 events found

No Events found!

Top