Windows 11 shows an unfixable error following another BSoD.
Windows 11 shows an unfixable error following another BSoD.
I'm working with Insider Preview 22623.1037. Occasionally I encounter video memory issues or driver .dll problems, but once those blue (and sometimes green) warnings appear and the PC restarts, I see another BSoD indicating an uncorrectable WHEA error. While most of this points to a hardware fault, it usually follows another BSoD beforehand, and since my machine is only a month old, it shouldn't be a hardware problem. This doesn’t interfere with my regular tasks, but I suspect something in my Insider setup might be faulty. I’ve also observed that the WHEA error appears darker and less intense compared to the original Insider BSoD that precedes it. It also triggers with NotMyFault.exe crashes and manually initiated CRITICAL_PROCESS_DIED events. Attachment: Video memory issue before a WHEA error. (likely a poor quality image, but it helps) My laptop specs: Intel i5 11400H, NVIDIA RTX 3050 Ti GPU, 8+8 GB Crucial ct8g4sfra32a RAM, Windows 11 Insider, 500 GB Samsung M.2 drive with an old external Seagate HDD that had a SATA-to-Micro USB adapter which I removed and replaced with the real SATA port. The HDD seems suspect because it’s old and was swapped twice; Windows might be flagging it as faulty.
You're relying on an insider preview and hoping for a smooth experience. The tool you mentioned, crystaldiskinfo, is meant to check if a hard drive is about to fail. Hard drives tend to deteriorate rapidly, so it's wise to consider a backup. Updated January 3, 2023 by Bombastinator
If I had faced the same problem last week, I was attempting to boost my Ryzen CPU and ended up stuck in a persistent BSoD loop with the WHEA error. My initial attempt also landed my old HDD, which was nearing the end of its life, but that wasn’t the case. After a complete Windows reinstall, the problem partially resolved. Only when I reset Ryzen Master to autoclock and stopped trying the overclock did it work—running smoothly for almost a week. My thought is that Windows might have an issue with a BIOS setting, though I’m just guessing.
It seems like you're reflecting on a situation where an overclock didn't go as expected. Typically, such failures bring up various issues, but this one was different. Whenever something odd happens, I try to remove any overclocks that might be stuck or unstable—usually by resetting the CMOS, checking connections, and questioning hardware. I often make that assumption myself. Edited January 3, 2023 by Bombastinator
There’s a PCI port available, which means the device is quite old. I’ve used a Z97 model that had just one PCI slot, seen as outdated. The rest of the system uses PCI.