Question Getting BSOD "DRIVER_POWER_STATE_FAILURE ntoskrnl.exe" ?

[DingoDangoDongo]

Randomly getting this blue screen. There is no specific thing that I am doing to trigger this issue and I think it's a hardware issue. Not sure how to read a mini dump to see what the issue is.
- I already reinstalled my OS but it seems to still be happening.
- Used mem test to test out my ram and got 0 issues

Minidumps

Current Parts:

PCPartPicker Part List

CPU: AMD Ryzen 7 7800X3D 4.2 GHz 8-Core Processor
CPU Cooler: NZXT Kraken Elite 360 RGB 78.02 CFM Liquid CPU Cooler
Motherboard: ASRock B650E Taichi Lite EATX AM5 Motherboard
Memory: G.Skill Trident Z5 RGB 64 GB (2 x 32 GB) DDR5-6000 CL30 Memory
Storage: Samsung 960 Pro 512 GB M.2-2280 PCIe 3.0 X4 NVME Solid State Drive
Storage: Samsung 980 Pro 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
Storage: Western Digital Black SN850X w/Heatsink 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
Storage: Seagate ST2000DX001 2 TB 3.5" 7200 RPM Hybrid Internal Hard Drive
Video Card: MSI VENTUS 3X OC GeForce RTX 4080 SUPER 16 GB Video Card
Power Supply: MSI A1000G PCIE5 1000 W 80+ Gold Certified Fully Modular ATX Power Supply

 

[ubuysa]

The BSODs are happening because a device is failing to complete a power transition (idle to running) in a reasonable time. In all three dumps it's the same device; your WD Blue hard drive.

One workaround for this is to change your active power plan so that the "Turn of hard disk after" value is 0. This stops hard drives from powering down so that this problem shouldn't happen.

However, this may be a sign of a failing hard drive, so download CrystalDiskInfo, use that to display the SMART data for that drive and post a screenshot of that.

 

[DingoDangoDongo]

The BSODs are happening because a device is failing to complete a power transition (idle to running) in a reasonable time. In all three dumps it's the same device; your WD Blue hard drive.

One workaround for this is to change your active power plan so that the "Turn of hard disk after" value is 0. This stops hard drives from powering down so that this problem shouldn't happen.

However, this may be a sign of a failing hard drive, so download CrystalDiskInfo, use that to display the SMART data for that drive and post a screenshot of that.

I think I below is the right information:

 

[ubuysa]

It's tricky interpreting SMART data but it looks to me as though the drive is OK but not quite perfect. You have had some errors; the Reported Uncorrectable Errors is not 100 as we would like it. Also, the Airflow Temperature is not 100 either. That might suggest that the drive has been getting hot? Does it have a heatsink and is it properly attached to the drive?

When an SSD fails it fails catastrophically and it's most unlikely that you'll ever be able to recover data from it. Keep a regular backup of all user data on that drive. Save this screenshot somewhere and look at the SMART data once a month, if you see the Reported Uncorrectable Errors number decreasing each month then I would look to replace the drive.

 

[DingoDangoDongo]

It's tricky interpreting SMART data but it looks to me as though the drive is OK but not quite perfect. You have had some errors; the Reported Uncorrectable Errors is not 100 as we would like it. Also, the Airflow Temperature is not 100 either. That might suggest that the drive has been getting hot? Does it have a heatsink and is it properly attached to the drive?

When an SSD fails it fails catastrophically and it's most unlikely that you'll ever be able to recover data from it. Keep a regular backup of all user data on that drive. Save this screenshot somewhere and look at the SMART data once a month, if you see the Reported Uncorrectable Errors number decreasing each month then I would look to replace the drive.

So the drive is a mechanical drive so no heat sink. The issue that I have noticed is that the drive will sometimes disconnect and reconnect popping open windows explorer.

I have taken the drive out and will see what happens while this drive isn't connected.

Thanks

 

[ubuysa]

Ah, that sounds like a failing drive then. If it were mine I'd replace it now.