Another BSOD occurrence reported – driver system power failure possibly linked to ntoskrnl.exe
Another BSOD occurrence reported – driver system power failure possibly linked to ntoskrnl.exe
I've been attempting to identify and resolve this issue on my own for a long time, but even checking other similar posts hasn't clarified the problem. So I'm sharing it here myself.
Occasionally, every few hours while using my computer, I experience a BSOD with the stop code Driver_Power_System_Failure. I've confirmed all drivers are up to date, and tools like BlueScreenViewer suggest ntoskrnl.exe might be the cause, though it doesn't provide much detail.
Here are the dumps:
https://drive.google.com/drive/folders/1...drive_link
And my PC specifications:
CPU: Ryzen 7950x
GPU: RTX 3070
Storage: WD Blue SN550 500GB (boot drive, I suspect it's the problem)
WD Black SN750 1TB (game drive)
Samsung 990 Pro 2TB (footage drive)
OS: Windows 11, upgraded from 10 (not a fresh install, which could also be the cause)
Ram: 64GB (32x2) of G.Skill TridentZ RGB
I'm really stuck, as this only began a few days ago. If anyone can examine the dumps and tell me what's wrong, I'd appreciate it! Thanks!
Whilst waiting for someone to comment on the dumps, can I suggest you follow through on your instinct: back up your data, unplug the HDDs do a fresh install to the SSD, reconnect the HDDs and see how you go.
nice, so completely reinstall windows just to see if you don't get the driver... a little excessive.
BSV always blames ntoskrnl as it was what crashed, its not the cause though... just the victim
It is going to be a driver, we just have to figure out which.
report
- mostly for me
File: 122223-16031-01.dmp (Dec 23 2023 - 07:32:46)
BugCheck: [
DRIVER_POWER_STATE_FAILURE (9F)
]
Probably caused by: memory_corruption (Process:
System
)
Uptime: 0 Day(s), 19 Hour(s), 02 Min(s), and 01 Sec(s)
File: 122123-18156-01.dmp (Dec 22 2023 - 05:33:13)
BugCheck: [
DRIVER_POWER_STATE_FAILURE (9F)
]
Probably caused by: memory_corruption (Process:
System
)
Uptime: 2 Day(s), 8 Hour(s), 16 Min(s), and 55 Sec(s)
File: 122123-16437-01.dmp (Dec 22 2023 - 08:58:58)
BugCheck: [
DRIVER_POWER_STATE_FAILURE (9F)
]
Probably caused by: memory_corruption (Process:
System
)
Uptime: 0 Day(s), 3 Hour(s), 24 Min(s), and 27 Sec(s)
File: 122123-16000-01.dmp (Dec 22 2023 - 12:24:51)
BugCheck: [
DRIVER_POWER_STATE_FAILURE (9F)
]
Probably caused by: memory_corruption (Process:
System
)
Uptime: 0 Day(s), 3 Hour(s), 05 Min(s), and 30 Sec(s)
File: 121923-18531-01.dmp (Dec 19 2023 - 21:14:59)
BugCheck: [
DRIVER_POWER_STATE_FAILURE (9F)
]
Probably caused by: memory_corruption (Process:
System
)
Uptime: 0 Day(s), 6 Hour(s), 08 Min(s), and 05 Sec(s)
it looks to be storage drivers
try updating chipset drivers -
https://www.amd.com/en/support/chipsets/...t-am5/b650
you don't need raid mi
Did you update BIOS recently as there is one from this month. I can't tell if you on latest as the report grabs the wrong info for MSI motherboards. There is a beta bios from beginning of month, could be what you have. Not ideal to be on beta bios.
Question: PSU details requested including make, model, power rating, age, condition, and usage history. History of heavy use for gaming, video editing, or bit-mining is also needed.
History: Original to build, used with significant gaming and video editing activities, possibly involved in bit-mining.
The PSU is a fresh out of the box Corsair RM1000x, been using it for 6 months now. I mainly do gaming and video editing, no mining.
Honestly one of my theories is that the power draw is getting messed up somewhere, as the problem started happening after I plugged a space heater into a nearby outlet. It's entirely possible it's a power issue
Haha, I didn't include my motherboard in the parts list, which is good since it's a B650. After the first BSOD, I updated the chipset drivers and it kept happening. I might have accidentally downloaded the beta BIOS, but then I re-downloaded the latest drivers from the link you gave. Hope that fixed it!
If the issues persist, three actions can be taken right away:
1) Turn off the space heater to see if the problems cease. If it’s needed, attempt to connect it from another circuit using a different breaker.
2) Check the Reliability History/Monitor for any error messages, warnings, or events that emerged after the heater was first connected. Review the sequence of events.
3) Execute "dism" and "sfc /scannow". Either tool may detect and resolve corrupted files caused by power spikes or surges.
The heater has been unplugged, but after a BSOD occurred twice since then, the /sfc scannow reported three corrupted drivers that have now been fixed (see picture). I’m unsure what those drivers do, so could it be that their corruption was the main problem, or just a symptom after the crashes?
EDIT: I should note this—it’s actually a major breakthrough. Checking the reliability monitor each day of my crashes reveals something similar (see picture). The recurring issue is "ASUS Com Service." Even though I don’t use ASUS products, my Windows 10 was installed on an ASUS motherboard before upgrading to an MSI board. Is this all just leftover data causing conflicts?
Those drivers that Windows fixed for you come from the blue tooth device on your motherboard.
Based on the additional details you shared, I would definitely reinstall the OS. Switching from an Asus board to another manufacturer like MSI, and upgrading from version 10 to 11, would likely require a clean install (since there’s likely leftover "junk") rather than just an incremental update.
Download the latest Windows 11 package from MS and perform a clean installation. When Windows asks for the first time, instruct it to completely format your designated storage device for the C drive. Make sure to boot into BIOS with default settings, then proceed with the usual setup steps afterward, and check if the BSODs persist.