Latest 11th generation setup continues to face BSOD issues.
Latest 11th generation setup continues to face BSOD issues.
We recently launched this setup about two weeks ago, initially supporting XMP alongside all standard BIOS configurations. It would boot but would trigger a BSOD and shut down during gaming or streaming with OBS. The crash always occurred as CRITICAL PROCESS DIED. We suspected the CPU or RAM was faulty since XMP was using the default profile for 3600MHz memory, which kept failing. Disabling XMP resolved the problem temporarily, lasting a week without issues. Once streaming resumed via OBS, it would crash again—this time showing a mix of watchdog and critical process died errors. We tested with different RAM configurations: one stick, two sticks, and four sticks. We opted for his original RAM (ballistix sport 2400MHz, two 8GB units) which worked briefly before another BSOD during streaming or gameplay. We attempted a few fixes—reinstalling Windows, updating BIOS, and replacing the SSD—but nothing resolved it. The issue persisted even after a full Windows reinstall, which restored everything except the problematic memory. We’re still unsure what caused it. This has been a challenge for over a decade of building, and we’ve seen similar reports online, but no one seems to have a solution. We’re open to trying more options and would appreciate any advice or test ideas. Parts used and tested include Intel 11900k, ASUS Z590-E motherboard, GTX 3080 Ti, G.SKILL TridentZ Neo memory, Samsung SSD, and various cooling components.
Windows 10 stopping because the critical process failed indicates a problem with system files, faulty drivers, malware, compatibility issues, bad sectors, or similar. Use the Deployment Imaging and Servicing Management Tool to fix a corrupted system image. The tool offers three options: /ScanHealth, /CheckHealth, and /RestoreHealth.
Ended up resetting the CMOS after reinstalling the ballistix RAM, and it performed perfectly throughout the night while streaming and gaming. We identified the issue as the RAM itself. Switched to a 3200MHz Corsair Vengeance RGB module and everything is now working flawlessly. It seems the problem was related to the NEO memory type, which is mainly for Ryzen systems. Anyone having similar issues should try using slower RAM that isn't marked for Ryzen. It's working great now!