F5F Stay Refreshed Software Operating Systems Driver Power State Failure

Driver Power State Failure

Driver Power State Failure

I
ImiSiS
Member
Find
75
06-12-2026, 03:11 PM
#1
Hi everyone, I have this BSOD error on my computer after it goes to sleep and then I try to turn it back on. Please help me with this problem. Here is the info you need: A Zip File of MiniDump here in a link: https://www.dropbox.com/scl/fi/e06p...7-...cn2fs&dl=0 SysInfo says it is running on Microsoft Windows 11 Pro Version 10.0.22621 Build 22621. The computer comes from LENOVO, and the model number is 20TK0046US. It runs on a x64-based PC with an Intel Core i9-10885H CPU that has 2400 MHz speed and 8 cores.

The BIOS version is LENOVO N2VET38W from 1/10/2022. There are some security settings turned on, like Secure Boot and Hyper-V features. The total memory is 16 GB (but only about 15.7 GB is actually used). The page file has a lot of space available. Interestingly, the system detected a hypervisor, which means it thinks there might be virtualization software running in the background. These features prevent some things from showing up on this error report because they are needed to run Hyper-V properly.
Reply
Reply
I
ImiSiS
06-12-2026, 03:11 PM #1

Hi everyone, I have this BSOD error on my computer after it goes to sleep and then I try to turn it back on. Please help me with this problem. Here is the info you need: A Zip File of MiniDump here in a link: https://www.dropbox.com/scl/fi/e06p...7-...cn2fs&dl=0 SysInfo says it is running on Microsoft Windows 11 Pro Version 10.0.22621 Build 22621. The computer comes from LENOVO, and the model number is 20TK0046US. It runs on a x64-based PC with an Intel Core i9-10885H CPU that has 2400 MHz speed and 8 cores.

The BIOS version is LENOVO N2VET38W from 1/10/2022. There are some security settings turned on, like Secure Boot and Hyper-V features. The total memory is 16 GB (but only about 15.7 GB is actually used). The page file has a lot of space available. Interestingly, the system detected a hypervisor, which means it thinks there might be virtualization software running in the background. These features prevent some things from showing up on this error report because they are needed to run Hyper-V properly.

Reply
Reply
D
DjReindeer5
Member
Find
123
06-20-2026, 08:48 AM
#2
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... Code: 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... Code: 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.. Code: 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.
Reply
Reply
D
DjReindeer5
06-20-2026, 08:48 AM #2

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... Code: 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... Code: 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.. Code: 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.

Reply
Reply