Question BSOD DRIVER_POWER_STATE_FAILURE

[JacquesFR]

Hi Everyone,
I get a BSOD error on my system after the system goes to sleep and then I resume use. I would appreciate any help on offer. Here is the info I have: (and thank you in advance!)

Zip File of MiniDump: https://www.dropbox.com/scl/fi/e06p...7-01.zip?rlkey=1vghpmrhe7itfwwy97yccn2fs&dl=0

SysInfo:
OS Name Microsoft Windows 11 Pro

Version 10.0.22621 Build 22621

OS Manufacturer Microsoft Corporation

System Manufacturer LENOVO

System Model 20TK0046US

System Type x64-based PC

System SKU LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3

Processor: Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz, 2400 Mhz, 8 Core(s), 16 Logical Processor(s)

BIOS Version/Date LENOVO N2VET38W (1.23 ), 2/10/2022

SMBIOS Version 3.2

Embedded Controller Version 1.11

BIOS Mode UEFI

BaseBoard Manufacturer LENOVO

BaseBoard Product 20TK0046US

BaseBoard Version SDK0T08861 WIN

Platform Role Mobile

Secure Boot State On

PCR7 Configuration Elevation Required to View

Windows Directory C:\WINDOWS

System Directory C:\WINDOWS\system32

Boot Device \Device\HarddiskVolume1

Locale United States

Hardware Abstraction Layer Version = "10.0.22621.1413"

Installed Physical Memory (RAM) 16.0 GB

Total Physical Memory 15.7 GB

Available Physical Memory 8.10 GB

Total Virtual Memory 16.7 GB

Available Virtual Memory 5.39 GB

Page File Space 1.00 GB

Page File C:\pagefile.sys

Kernel DMA Protection On

Virtualization-based security Running

Virtualization-based security Required Security Properties

Virtualization-based security Available Security Properties Base Virtualization Support, Secure Boot, DMA Protection, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization

Virtualization-based security Services Configured Hypervisor enforced Code Integrity, Secure Launch, SMM Firmware Measurement

Virtualization-based security Services Running Hypervisor enforced Code Integrity, Secure Launch, SMM Firmware Measurement

Windows Defender Application Control policy Enforced

Windows Defender Application Control user mode policy Off

Device Encryption Support Elevation Required to View

A hypervisor has been detected. Features required for Hyper-V will not be displayed.

 

[ubuysa]

It's always risky making a diagnosis based on one dump, if you have other recent dumps please upload those as well. That said, the one dump you did upload is pretty clear.

The bugcheck code is a DRIVER_POWER_STATE_FAILURE, which means that a device failed to complete a power transition with a specified time. Since you're talking about waking from sleep, this will be the power transition from the low power Modern Standby state to the high power active and running state.

When the dump is created certain useful information is included and we can see that in the initial dump 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: ffffca8dc53fbd90, Physical Device Object of the stack
Arg3: ffffe004468a76f8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffca8dc33183d0, The blocked IRP

The 'blocked IRP' address ins argument 4 is the address of the interrupt request packet that was managing this power transition. If we display that we can see what was holding things up...

5: kd> !irp ffffca8dc33183d0
Irp is active with 10 stacks 8 is current (= 0xffffca8dc3318698)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     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
 [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_WAIT_WAKE(0)]
            0  0 ffffca8dc53fbd90 00000000 fffff8024049b4d0-ffffca8dc55751a0 
           \Driver\IntcOED    portcls!PowerIrpCompletionRoutine
            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  1 ffffca8dc5575050 00000000 00000000-00000000    pending
          Unable to load image RTKVHD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
 \Driver\IntcAzAudAddService
            Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffca8dc52ded90 00000000 fffff80220ab56b0-ffffca8dc5563208 Success Error Cancel pending
           \Driver\ksthunk    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffca8dc5563208 

            Args: 00000000 00000000 00000000 00000000

There are three drivers at the bottom there. The ksthunk.sys driver at the bottom is a Microsoft streaming driver, so that's not at fault. The other two drivers however are Intel drivers (note in 'Int' prefix to their names). There is also a reference to a Realtek driver there (RTKVHD64.sys). The Realtek driver is fairly recent but the IntecOED.sys driver is quite old..

5: kd> lmDvmIntcOED
Browse full module list
start             end                 module name
fffff802`1fb90000 fffff802`1fcd1000   IntcOED  T (no symbols)        
    Loaded symbol image file: IntcOED.sys
    Image path: IntcOED.sys
    Image name: IntcOED.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Oct 17 12:07:49 2022 (634D1B65)
    CheckSum:         00151659
    ImageSize:        00141000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would initially suggest downloading the Intel Driver Support Assistant tool and use that to look for updated Intel driver.

Note that the IntcOED.sys driver is the Intel Smart Sound Technology driver and the RTKVHD64.sys driver is the Realtek High Definition Audio Codec driver, so we're looking at a sound issue here and the most likely cause of the bugcheck is the Intel driver.