Error WHEA_UNCORRECTABLE_ERROR and boot drive missing
Error WHEA_UNCORRECTABLE_ERROR and boot drive missing
Hello, a few weeks ago my computer began shutting down during gameplay (such as when the power suddenly cut off), leading me to suspect a PSU issue. A few days later I disconnected everything from the PSU and reconnected it all. Now, when I put the PC under stress it displays WHEA_UNCORRECTABLE_ERROR. The Event Viewer shows only a critical kernel-power error with ID 41, and all details are at zero. Additionally, my boot drive often disappears from the system. I performed CHKDSK on the boot drive and found no issues, ran SFC which detected a corrupted file once but couldn’t replace it easily, and then found nothing again.
The WHEA here refers to Windows Hardware Error Architecture. It seems you've completed the chkdsk scan and everything was clean, but your boot drive has stopped working unexpectedly, the corrupted file isn't being repaired, and it vanishes. This suggests you might need to either A) back up data and reinstall Windows, or B) consider replacing the drive(s).
I attempted to reinstall Windows 10 but encountered an issue where the system couldn't create a partition on the selected drive, then it shut down after 30 seconds. I think the problem lies with the SSD, so I plan to replace it and try again.
Avoid overspending while still prioritizing a crucial component. Check out reputable brands within your budget.
Hello, I replaced my SSD 20 days ago and believed I had fixed the problem because everything worked fine for two weeks. However, the issue has started again. There are no issues with finding the OS, but my PC randomly shuts down after error 41 Kerner Power (recorded in the event viewer). I suspect it might be related to the anti-cheat from Valorant since it operates at the kernel level, and I've seen others on forums experiencing the same error. When the PC stops, I can't turn it on right away; I have to wait before switching it on. If I start it immediately, the fans don't spin, but if I wait a little while but not long enough, it shuts down again during boot. Also, when it finally boots and loads Windows, the time remains consistent with when the error happened.