F5F Stay Refreshed Software Operating Systems [BSOD] DRIVER_POWER_STATE_FAILURE ntoskrnl.exe

[BSOD] DRIVER_POWER_STATE_FAILURE ntoskrnl.exe

[BSOD] DRIVER_POWER_STATE_FAILURE ntoskrnl.exe

K
Klyner
Member
Find
184
03-12-2026, 04:47 AM
#1
Hi everyone, can someone help me find the cause of this bsod problem on a new PC? CPU: Intel Core i7-7800X3D GPU: Gigabyte 4090 Gaming OC PSU: NZXT 1200 Gold Mobo: Asrock B650E Taichi RAM: G.Skill Trident Z5 Usually I get the bsod right after I start using OBS (not while streaming, but a short time after stopping). I have OBS version 29 and all drivers are updated. For video encoding I use NVENC. The temps are okay and I only limited the SoC voltage since X3D chips are very sensitive to heat, plus some RAM tuning from BuildZoid. Here are my three mini dumps in .dmp format, saved as minidumps.zip at drive.google.com. As for now I have no more ideas on what's wrong.
Reply
Reply
K
Klyner
03-12-2026, 04:47 AM #1

Hi everyone, can someone help me find the cause of this bsod problem on a new PC? CPU: Intel Core i7-7800X3D GPU: Gigabyte 4090 Gaming OC PSU: NZXT 1200 Gold Mobo: Asrock B650E Taichi RAM: G.Skill Trident Z5 Usually I get the bsod right after I start using OBS (not while streaming, but a short time after stopping). I have OBS version 29 and all drivers are updated. For video encoding I use NVENC. The temps are okay and I only limited the SoC voltage since X3D chips are very sensitive to heat, plus some RAM tuning from BuildZoid. Here are my three mini dumps in .dmp format, saved as minidumps.zip at drive.google.com. As for now I have no more ideas on what's wrong.

Reply
Reply
N
noodledoodle4
Junior Member
Find
6
03-12-2026, 11:32 AM
#2
The DRIVER_POWER_STATE_FAILURE error happens when a driver holds onto (blocks) an IRP for too long. The cause is either a problem with the driver itself or a problem with the device it controls. Two out of three dumps you sent are DRIVER_POWER_STATE_FAILURE, and they are exactly the same. The triage check helps point us to useful places in the memory... Code: DRIVER_POWER_STATE_FAILURE (9f) A driver failed to finish its power IRP within a set time limit. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffff800bb7f8e050, Physical Device Object of the stack Arg3: fffff8003dfd4198, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack...
Reply
Reply
N
noodledoodle4
03-12-2026, 11:32 AM #2

The DRIVER_POWER_STATE_FAILURE error happens when a driver holds onto (blocks) an IRP for too long. The cause is either a problem with the driver itself or a problem with the device it controls. Two out of three dumps you sent are DRIVER_POWER_STATE_FAILURE, and they are exactly the same. The triage check helps point us to useful places in the memory... Code: DRIVER_POWER_STATE_FAILURE (9f) A driver failed to finish its power IRP within a set time limit. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffff800bb7f8e050, Physical Device Object of the stack Arg3: fffff8003dfd4198, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack...

Reply
Reply
A
ashton555
Member
Find
57
03-14-2026, 05:44 AM
#3
First, I'll change your RAM back to its normal spot and check how things go from then on.
Reply
Reply
A
ashton555
03-14-2026, 05:44 AM #3

First, I'll change your RAM back to its normal spot and check how things go from then on.

Reply
Reply
S
Shen_456
Junior Member
Find
49
03-22-2026, 01:08 PM
#4
The DRIVER_POWER_STATE_FAILURE bugcheck happens when a driver holds on to (blocks) an IRP (Interrupt Request Packet) for too long. The cause is either a problem with the driver or a problem with the device it controls. Two of the three dumps you uploaded are DRIVER_POWER_STATE_FAILURE and they are identical. The dump triage gives us pointers to useful data areas... 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: ffff800bb7f8e050, Physical Device Object of the stack Arg3: fffff8003dfd4198, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffff800bbc1759c0, The blocked IRP Argument 4 is the address of the blocked (held) IRP, displaying that gives... Code: 0: kd> !irp ffff800bbc1759c0 Irp is active with 8 stacks 4 is current (= 0xffff800bbc175b68) 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 ffff800bb7f8e050 00000000 00000000-00000000 pending \Driver\storahci Args: 00000000 00000001 00000001 00000000 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff800bbc04ada0 00000000 fffff80044f68510-ffff800bbc155730 Success Error Cancel pending \Driver\EhStorClass CLASSPNP!ClasspPowerUpCompletion Args: 00000000 00000001 00000001 00000000 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff800bbc1551f0 00000000 fffff80043e3ec60-00000000 Success Error Cancel pending \Driver\disk partmgr!PmPowerCompletion Args: 00000000 00000001 00000001 00000000 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff800bbbf888d0 00000000 fffff8003f7a6b30-ffff800bbc175228 Success Error Cancel pending \Driver\partmgr nt!PopRequestCompletion Args: 00000000 00000001 00000001 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffff800bbc175228 Args: 00000000 00000000 00000000 00000000 The driver blocking (holding) the IRP is the bottom one; partmgr.sys. This is the Windows partition manager driver and because it's a Windows driver it's not at fault. This does however indicate that the problem was storage driver related and that because of some problem with a storage drive the partmgr.sys driver couldn't complete. But which drive? Argument 2 is the clue here, it cotains the address of the device object for the storage device having a problem. Displaying this device object gives... Code: 0: kd> !devobj ffff800bb7f8e050 Device object (ffff800bb7f8e050) is for: Cannot read info offset from nt!ObpInfoMaskToOffset \Driver\storahci DriverObject ffff800bb7e7ad40 Current Irp 00000000 RefCount 0 Type 00000007 Flags 00001050 SecurityDescriptor ffffc8877f75c5e0 DevExt ffff800bb7f8e1a0 DevObjExt ffff800bb7f8f3a0 DevNode ffff800bb7fa9c20 ExtensionFlags (0000000000) Characteristics (0x00000180) FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN AttachedDevice (Upper) ffff800bbc04ada0 \Driver\EhStorClass Device queue is not busy Notice that the output here contains the address of the device node, that's the actual device at fault. Displaying that device node gives... Code: 0: kd> !devnode ffff800bb7fa9c20 DevNode 0xffff800bb7fa9c20 for PDO 0xffff800bb7f8e050 Parent 0xffff800bb7f35a60 Sibling 0000000000 Child 0xffff800bbbff68a0 InstancePath is "SCSI\Disk&Ven_&Prod_CT500MX500SSD1\7&2a9b7bbb&0&010000" ServiceName is "disk" State = DeviceNodeStarted (0x30a) Previous State = DeviceNodeEnumerateCompletion (0x30f) StateHistory[15] = DeviceNodeEnumerateCompletion (0x30f) StateHistory[14] = DeviceNodeEnumeratePending (0x30e) StateHistory[13] = DeviceNodeStarted (0x30a) StateHistory[12] = DeviceNodeEnumerateCompletion (0x30f) StateHistory[11] = DeviceNodeEnumeratePending (0x30e) StateHistory[10] = DeviceNodeStarted (0x30a) StateHistory[09] = DeviceNodeEnumerateCompletion (0x30f) StateHistory[08] = DeviceNodeEnumeratePending (0x30e) StateHistory[07] = DeviceNodeStarted (0x30a) StateHistory[06] = DeviceNodeStartPostWork (0x309) StateHistory[05] = DeviceNodeStartCompletion (0x308) StateHistory[04] = DeviceNodeStartPending (0x307) StateHistory[03] = DeviceNodeResourcesAssigned (0x306) StateHistory[02] = DeviceNodeDriversAdded (0x305) StateHistory[01] = DeviceNodeInitialized (0x304) StateHistory[00] = DeviceNodeUninitialized (0x301) StateHistory[19] = Unknown State (0x0) StateHistory[18] = Unknown State (0x0) StateHistory[17] = Unknown State (0x0) StateHistory[16] = Unknown State (0x0) Flags (0x24000130) DNF_ENUMERATED, DNF_IDS_QUERIED, DNF_NO_RESOURCE_REQUIRED, DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS CapabilityFlags (0x00002180) SilentInstall, RawDeviceOK, WakeFromD3 The SCSI\Disk&Ven_&Prod_CT500MX500SSD1\7&2a9b7bbb&0&010000 identifies the device, its a Crucial MX500 500GB 2.5" SATA SSD (from the product code CT500MX500SSD1). It would appear that there may be a problem with this device, so I would backup all data on it as soon as possible (when SSDs fail the data is gone forever). I would download and run the Crucial Storage Executive software from here, and run the drive self test from there. Also see whether there are firmware or other updates for the drive. If it were mine I would replace the drive, once an SSD becomes untrusted it's time to replace it.
Reply
Reply
S
Shen_456
03-22-2026, 01:08 PM #4

The DRIVER_POWER_STATE_FAILURE bugcheck happens when a driver holds on to (blocks) an IRP (Interrupt Request Packet) for too long. The cause is either a problem with the driver or a problem with the device it controls. Two of the three dumps you uploaded are DRIVER_POWER_STATE_FAILURE and they are identical. The dump triage gives us pointers to useful data areas... 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: ffff800bb7f8e050, Physical Device Object of the stack Arg3: fffff8003dfd4198, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffff800bbc1759c0, The blocked IRP Argument 4 is the address of the blocked (held) IRP, displaying that gives... Code: 0: kd> !irp ffff800bbc1759c0 Irp is active with 8 stacks 4 is current (= 0xffff800bbc175b68) 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 ffff800bb7f8e050 00000000 00000000-00000000 pending \Driver\storahci Args: 00000000 00000001 00000001 00000000 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff800bbc04ada0 00000000 fffff80044f68510-ffff800bbc155730 Success Error Cancel pending \Driver\EhStorClass CLASSPNP!ClasspPowerUpCompletion Args: 00000000 00000001 00000001 00000000 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff800bbc1551f0 00000000 fffff80043e3ec60-00000000 Success Error Cancel pending \Driver\disk partmgr!PmPowerCompletion Args: 00000000 00000001 00000001 00000000 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff800bbbf888d0 00000000 fffff8003f7a6b30-ffff800bbc175228 Success Error Cancel pending \Driver\partmgr nt!PopRequestCompletion Args: 00000000 00000001 00000001 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffff800bbc175228 Args: 00000000 00000000 00000000 00000000 The driver blocking (holding) the IRP is the bottom one; partmgr.sys. This is the Windows partition manager driver and because it's a Windows driver it's not at fault. This does however indicate that the problem was storage driver related and that because of some problem with a storage drive the partmgr.sys driver couldn't complete. But which drive? Argument 2 is the clue here, it cotains the address of the device object for the storage device having a problem. Displaying this device object gives... Code: 0: kd> !devobj ffff800bb7f8e050 Device object (ffff800bb7f8e050) is for: Cannot read info offset from nt!ObpInfoMaskToOffset \Driver\storahci DriverObject ffff800bb7e7ad40 Current Irp 00000000 RefCount 0 Type 00000007 Flags 00001050 SecurityDescriptor ffffc8877f75c5e0 DevExt ffff800bb7f8e1a0 DevObjExt ffff800bb7f8f3a0 DevNode ffff800bb7fa9c20 ExtensionFlags (0000000000) Characteristics (0x00000180) FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN AttachedDevice (Upper) ffff800bbc04ada0 \Driver\EhStorClass Device queue is not busy Notice that the output here contains the address of the device node, that's the actual device at fault. Displaying that device node gives... Code: 0: kd> !devnode ffff800bb7fa9c20 DevNode 0xffff800bb7fa9c20 for PDO 0xffff800bb7f8e050 Parent 0xffff800bb7f35a60 Sibling 0000000000 Child 0xffff800bbbff68a0 InstancePath is "SCSI\Disk&Ven_&Prod_CT500MX500SSD1\7&2a9b7bbb&0&010000" ServiceName is "disk" State = DeviceNodeStarted (0x30a) Previous State = DeviceNodeEnumerateCompletion (0x30f) StateHistory[15] = DeviceNodeEnumerateCompletion (0x30f) StateHistory[14] = DeviceNodeEnumeratePending (0x30e) StateHistory[13] = DeviceNodeStarted (0x30a) StateHistory[12] = DeviceNodeEnumerateCompletion (0x30f) StateHistory[11] = DeviceNodeEnumeratePending (0x30e) StateHistory[10] = DeviceNodeStarted (0x30a) StateHistory[09] = DeviceNodeEnumerateCompletion (0x30f) StateHistory[08] = DeviceNodeEnumeratePending (0x30e) StateHistory[07] = DeviceNodeStarted (0x30a) StateHistory[06] = DeviceNodeStartPostWork (0x309) StateHistory[05] = DeviceNodeStartCompletion (0x308) StateHistory[04] = DeviceNodeStartPending (0x307) StateHistory[03] = DeviceNodeResourcesAssigned (0x306) StateHistory[02] = DeviceNodeDriversAdded (0x305) StateHistory[01] = DeviceNodeInitialized (0x304) StateHistory[00] = DeviceNodeUninitialized (0x301) StateHistory[19] = Unknown State (0x0) StateHistory[18] = Unknown State (0x0) StateHistory[17] = Unknown State (0x0) StateHistory[16] = Unknown State (0x0) Flags (0x24000130) DNF_ENUMERATED, DNF_IDS_QUERIED, DNF_NO_RESOURCE_REQUIRED, DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS CapabilityFlags (0x00002180) SilentInstall, RawDeviceOK, WakeFromD3 The SCSI\Disk&Ven_&Prod_CT500MX500SSD1\7&2a9b7bbb&0&010000 identifies the device, its a Crucial MX500 500GB 2.5" SATA SSD (from the product code CT500MX500SSD1). It would appear that there may be a problem with this device, so I would backup all data on it as soon as possible (when SSDs fail the data is gone forever). I would download and run the Crucial Storage Executive software from here, and run the drive self test from there. Also see whether there are firmware or other updates for the drive. If it were mine I would replace the drive, once an SSD becomes untrusted it's time to replace it.

Reply
Reply
P
pooh_bear6
Member
Find
192
03-25-2026, 09:27 PM
#5
OMG! You're a magician! How can I get those millions of likes for such an in-depth look? Honestly, I don't know how you do that with all those deep details or dumps. But after hours of searching every single place without finding anything, thank you very much. It's an old SSD, so maybe it just needs to be tossed anyway. I'll listen and back up the data before exchanging it (just in case). UPD: I guess it's broken because I can't even read the firmware or update it via their tools. The error message won't fix itself, so I think we're done with it. Thanks for not being critical! (Pun was meant to be cute XD.)
Reply
Reply
P
pooh_bear6
03-25-2026, 09:27 PM #5

OMG! You're a magician! How can I get those millions of likes for such an in-depth look? Honestly, I don't know how you do that with all those deep details or dumps. But after hours of searching every single place without finding anything, thank you very much. It's an old SSD, so maybe it just needs to be tossed anyway. I'll listen and back up the data before exchanging it (just in case). UPD: I guess it's broken because I can't even read the firmware or update it via their tools. The error message won't fix itself, so I think we're done with it. Thanks for not being critical! (Pun was meant to be cute XD.)

Reply
Reply
C
Callysqually
Member
Find
57
03-26-2026, 08:00 AM
#6
@AshySamurai ! This thread saved my day. I've been struggling with the same problem for a long time that was really hard to fix. Learned a ton from this post. The reason I'm replying is because I have the exact same error and following @ubuysa's guide (using WinDbg) found out it's coming from my CRUCIAL MX500 2TB 2.5" SATA SSD. Small world! Did you ever get this working? Were you able to return it under warranty? My drive is only 6 months old. I'm on the latest firmware, so I'm wondering if a new drive will help, or are these Crucial drives just doomed forever?
Reply
Reply
C
Callysqually
03-26-2026, 08:00 AM #6

@AshySamurai ! This thread saved my day. I've been struggling with the same problem for a long time that was really hard to fix. Learned a ton from this post. The reason I'm replying is because I have the exact same error and following @ubuysa's guide (using WinDbg) found out it's coming from my CRUCIAL MX500 2TB 2.5" SATA SSD. Small world! Did you ever get this working? Were you able to return it under warranty? My drive is only 6 months old. I'm on the latest firmware, so I'm wondering if a new drive will help, or are these Crucial drives just doomed forever?

Reply
Reply