Question PC BSODs with "Critical Process Died"?
Question PC BSODs with "Critical Process Died"?
From what I understand, the "Critical Process Died" issue is typically related to hardware, though it can vary. I’ve experienced this problem for some time now, but it’s become more frequent lately. Initially, it would cause booting issues in games like CS2 and League of Legends, but after disabling XMP, it stopped. However, it still crashed in games such as Elden Ring and GTA 5, especially since I disabled XMP.
I haven’t encountered any problems with my system for about a year now. It was built by hand, and most of the PC components are new since then. I’ve stress-tested it thoroughly, and it doesn’t boot when pushed to full capacity. The only exception is my second-hand RTX 2070 Super.
Hardware: Gigabyte H470m-k F5
CPU: i5 11400F with Arctic Freezer 34 Esports Duo Red and Arctic MX-4
GPU: RTX 2070 Super (used)
RAM: G.Skill aegis 2x16GB 3000mhz
Case: DeepCool CC 560 with 4 fans included
PSU: nJoy 620W
These are the typical steps for troubleshooting:
Update system drivers, including bios and gpu.
Perform a clean boot.
Execute SFC /Scannow command.
Use DISM to fix corrupted system image.
Remove any problematic windows update.
Attempt restoring to an older version.
Test with one RAM stick at a time to identify issues.
Check that the CPU and GPU are not overheating.
Thank you for your quick reply. I tested all the options and the only one that gave different results was using the RAM. Recently, when I started my game after the BSOD, it crashed after 2 to 5 minutes. Every time I tried a different RAM stick, I encountered just one issue—an Unexpected Store Exception. I’ve been playing with all RAM sticks for about 30 minutes each and nothing happened until now. My PC has gone through high, low, average usage, and still nothing. If this happens again, I have no idea what will happen.
I also tried playing after 2 hours and it crashed again, but this time with the Unexpected Store Exception instead of the Critical Process Died error.
EDIT: I ran a driver verifier just in case. Here’s the link to the result:
https://prnt.sc/FtyuUrNjMrJ3
Attaching only a photo, not a file, because I can’t upload it on Google Drive, Pixeldrain or Mega.
Eh, even at a low level it's sufficient to maintain Windows satisfaction. We just need enough space for updates, usually not exceeding 10GB. The first thing to do would be to execute a memory checker (memtest86 is best, though Windows also has a reliable built-in option) to ensure the simplest components are functioning properly. Following that, running SFC /scannow would be the next logical step.