Fix the CRITICAL_PROCESS_DIED Blue Screen, Step by Step
Independent guide — no official affiliation with the platforms mentioned.
Short answer
CRITICAL_PROCESS_DIED means a critical Windows process crashed — usually corrupted drivers or disk errors. Boot into Safe Mode, run SFC/DISM repair and a 'chkdsk /f' scan, or remove the latest update for an instant fix.
01 — Step-by-step fix
Step-by-step fix
Boot into Safe Mode
Force-restart the PC 3 times during boot to reach Recovery, then Troubleshoot > Advanced options > Startup Settings > Restart and press 4 (Safe Mode with Networking).
Uninstall the latest update
From Recovery, choose 'Uninstall latest quality update'. If the error started after a Windows update, this fixes it directly.
Run SFC and DISM
In Safe Mode open admin CMD and run 'sfc /scannow' then 'DISM /Online /Cleanup-Image /RestoreHealth'.
Scan the disk
Run 'chkdsk C: /f /r' and confirm the restart. The scan takes 20–60 minutes and repairs disk errors.
Don't power off during chkdsk. If the drive makes clicking sounds, back up immediately.
Check drivers
In Device Manager find devices with warnings; update GPU and chipset drivers from the vendor's site, or roll back a recently updated driver.
Tips
- Logging blue screen codes speeds up diagnosis of recurring issues.
- If the loop continues, check SSD health with CrystalDiskInfo.
02 — Frequently asked questions
Frequently asked questions
What causes CRITICAL_PROCESS_DIED?
Most often corrupted system files, incompatible drivers, disk errors or RAM issues. If it started after an update, the update is the prime suspect.
The PC is stuck in a boot loop — what now?
Force-restart 3 times to reach Recovery. If that fails, use a Windows installation USB and choose 'Repair your computer'.
How do I test my RAM?
Search 'Windows Memory Diagnostic', run it and let the reboot test run. Results appear in Event Viewer.
Links in this guide point to official platform pages. Steps may change with platform updates; check the page date.
03 — Related guides