Another crash log showing a power failure issue with the driver system, specifically linked to ntoskrnl.exe.
Another crash log showing a power failure issue with the driver system, specifically linked to ntoskrnl.exe.
I have been trying to fix myself for ages but checking other posts didn't help so I am posting here to see if anyone knows why. Every few hours or more when I use my computer I get a BSOD with the message Driver_Power_System_Failure. I have checked all drivers and used tools like BlueScreenViewer which said it was ntoskrnl.exe. That doesn't say much for me. Here are the files: https://drive.google.com/drive/folders/1...drive_link And here are my computer parts: CPU: Ryzen 7950x GPU: RTX 3070 Storage: WD Blue SN550 500gig (this is the main drive, I think it is causing the problem) WD Black SN750 1tb (game drive) Samsung 990 Pro 2tb (storage for videos) OS: Windows 11 on top of Windows 10 (it was not a fresh install which could be the cause too). RAM: 64 gig kit from G.Skill TridentZ RGB I am completely lost because this started only a few days ago. If anyone can look at these files and tell me what is wrong, that would help! Thank you!
While waiting to get feedback on the lost files, maybe try this instead: backup all your important stuff, take out the hard drives, swap them for faster storage sticks, plug it back in and check if things work better now.
It feels like reinstalling windows just to check if your driver broke things... actually that's too much trouble. BSV always blames ntoskrnl because it was the thing that crashed, but it really wasn't causing anything directly; it's just the victim. We're going to need a different kind of driver though, we'll have to figure out which one.
Here is what I'm seeing in my logs:
File 122223-16031-01.dmp (Dec 23 2023 - 7:32 AM) BugCheck says DRIVER_POWER_STATE_FAILURE, and it looks like memory_corruption happened to the System process. This was back when I had been using it for zero days, one hour, two minutes, and one second.
File 122123-18156-01.dmp (Dec 22 2023 - 5:33 AM) BugCheck says DRIVER_POWER_STATE_FAILURE again. The memory_corruption happened while I had been running for two days, eight hours, sixteen minutes, and fifty-five seconds.
File 122123-16437-01.dmp (Dec 22 2023 - 8:59 AM) BugCheck says DRIVER_POWER_STATE_FAILURE. Memory_corruption happened while I had been running for zero days, three hours, twenty-four minutes, and twenty-seven seconds.
File 122123-16000-01.dmp (Dec 22 2023 - 12:25 PM) BugCheck says DRIVER_POWER_STATE_FAILURE. Memory_corruption happened while I had been running for zero days, three hours, five minutes, and thirty seconds.
File 121923-18531-01.dmp (Dec 19 2023 - 9:15 PM) BugCheck says DRIVER_POWER_STATE_FAILURE. Memory_corruption happened while I had been running for zero days, six hours, eight minutes, and five seconds.
It looks like it might be related to storage drivers or maybe chipset drivers. You can check the AMD support page here: https://www.amd.com/en/support/chipsets/...t-am5/b650
You don't need to worry about RAID-MI right now. Did you update your BIOS recently? I saw a beta version starting at the beginning of last month, and it might be what you have. Being on a beta isn't ideal.
Do you know the power supply unit's brand, model number, how much it uses in watts, and when it was made or if it is old? Did someone have to use this thing a lot for games, making movies, or trying to mine coins online?
The PSU came with me in new condition from Corsair, and I have been running it for about six months now. I mostly game on my PC and edit videos, but I don't mine anything. Honestly, I think the power draw might be off somewhere because things started acting weird right after I plugged a space heater into an outlet nearby. It's possible the issue is just with the power supply itself.
Haha I forgot to put my motherboard in the list, glad you figured out it was a b650. First thing I did after my computer froze on the blue screen was update the chip drivers and it kept happening again. Maybe I downloaded that beta version of the BIOS like you said by mistake? Anyway, I went ahead and downloaded the newest drivers from the link you gave me. Maybe that fixed it, thanks!
If things keep going bad, here are three simple steps to fix them right now: 1) Turn off the space heater. Check if things stop when you do it. If you really need the heat, try plugging it into a different breaker. 2) Go to your Reliability History or Monitor and look for any error messages, warnings, or cool notes that show up after you plugged in the heater. Look at the time line. 3) Run "dism" and "sfc /scannow". One of those tools might find bad files caused by power spikes or surges. Here are some links to help: https://www.windowscentral.com/how-use-d...s-10-image, https://www.lifewire.com/how-to-use-sfc-...stem-files, and https://www.windowscentral.com/how-use-d...s-10-image
The heater stopped working because it wasn't plugged in, but I have already restarted the computer three times since that happened. After running a repair scan tool, it found and fixed 3 drivers that looked bad (see picture). I don't know exactly what those drivers do, so can you guess if these bad drivers caused the crashes or were just a symptom? EDIT: I forgot to tell you this is huge progress! Every day of my computer crashes shows something similar on the reliability monitor (see picture). The main thing that pops up is "ASUS Service". Even though my Windows 10 started on an ASUS motherboard before I moved to a new one with MSI, maybe all these things were just leftover junk data causing fights?
Those drivers that Windows fixed are just from a blue tooth device attached to your motherboard. Also, looking at the extra info you shared, I think it's best to reinstall the operating system because changing from an Asus board to another brand like MSI and upgrading from version 10 to 11 would definitely be better with a clean install (since leftover junk causes problems) rather than just adding drivers incrementally. Go download the latest Windows 11 package from Microsoft and start a fresh install. When it asks you to format your main storage drive for the C drive, say yes completely. Make sure to run your BIOS settings back to default before finishing what you usually do after all the software is set up. Then check if these blue screen errors keep happening.