Experiencing BSOD with the message "WHEA_UNCORRECTABLE_ERROR" during gameplay in CS2
Experiencing BSOD with the message "WHEA_UNCORRECTABLE_ERROR" during gameplay in CS2
During the CS2 beta testing, I managed to play smoothly for about 1.5 to 2 hours without issues. Beyond that point, I started experiencing freezes where pressing certain keys seemed problematic, or it simply crashed with a Windows BSOD displaying the error code WHEA_UNCORRECTABLE_ERROR. After restarting my PC, I could rejoin the game briefly, but it would crash again shortly afterward. After roughly five crashes, I chose to remove CS2 from my system, though it continued to fail with the same error even after uninstallation. This has never happened before I started playing CS2. My setup includes an Intel Core i9-10900k processor, an ASUS TUF RTX 3080 graphics card, two 16GB modules of 3200MHz DDR4 RAM (operating at 2133 MHz due to disabled XMP profiles), a 1000W power supply, and no overclocking. The temperatures of all components stayed within normal ranges during these incidents. Many of these failures occurred almost right after attempting to download Counter Strike onto my machine, leading me to suspect hardware problems like RAM or storage issues. While checking the RAM and drives with diagnostics came back normal, I disassembled and reassembled the PC—removing the CMOS battery—and successfully re-downloaded CS2 without any crashes. I’ve also updated all drivers. Recently, when encountering the same errors again, I began using Task Manager to monitor hardware activity just before crashes. I observed that the C: drive, which also hosted CS2, would spike to full usage but show 0Kb/s read/write for a short time before the crash occurred.
Do you have any dump files? Navigate to C:\Windows\Minidump and verify the presence of any dump files. If available, return to the Windows directory and transfer the Minidump folder to the Downloads folder (using your desktop if needed). Compress the copied folder and include it in a post. Please adhere strictly to the instructions since Windows doesn't allow modifications in this area.
WHEA crashes may stem from storage issues, making it hard to save dump files. Two steps are recommended. We recently encountered a Windows bug that triggers this crash due to faulty storage drivers, so we investigate first. Open Command Prompt with admin privileges and execute "fltmc". Capture the output as a screenshot. Since you don’t receive a dump, adjust the BSOD display to show more details. To achieve this, add a registry field under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl. Create a DWORD value named "DisplayParameters" and set its value to 1 (hex or decimal). After saving, reboot to apply changes. The next BSOD should include these extra details in the top-left corner. If the system restarts automatically and you need more time, refer to guides on changing dump types and uncheck automatic restart. Use the power button for a manual restart.
I've handled the screenshot you asked for. Other tasks like updating the registry field and adding the new registry entry are complete. The Minidump folder is still missing. Regarding the BSOD, it appears inconsistent rather than a standard BSOD; the monitors may become black or distort colors in the final clear frame, but it doesn't reliably trigger the blue screen.
The driver we know about isn't loading, so it shouldn't be the cause. You might want to reset the OS and reinstall if a storage driver is likely corrupted. The issue seems linked to the NVMe, though it can't distinguish between a faulty NVMe and a damaged M.2 slot or motherboard. A defective SSD is more frequent than a bad NVMe. If the OS reinstall didn't resolve it, verify the latest firmware for the SSD and monitor the NVMe temperature—keep it below 70°C, except briefly.
I've attempted to reset the OS and reinstall Windows, but the issue persists. It might depend on the specific game (CS2 Limited Beta) and its interaction with the SSD drivers. Other games in my Steam library and a different SSD model produced similar results. I've reinstalled the game on my hard drive with some encouraging but limited outcomes. I'll keep you updated if I encounter the same problems on another drive.