Repair
CRITICAL_PROCESS_DIED: what it means and how to fix it
The blue screen that stops Windows cold. Here's how to find the cause without losing your files.
CRITICAL_PROCESS_DIED means a core Windows process stopped unexpectedly, so Windows shut itself down to protect your data. The usual causes, in rough order of likelihood:
- Corrupted system files, often after an interrupted update
- A bad or incompatible driver
- A failing SSD or hard drive
- Faulty RAM
First: protect your files
If the machine still boots sometimes, back up your important files now, before you try anything else. If it doesn't boot at all, don't reset or reinstall yet. The files can usually still be recovered.
1. Boot into Safe Mode
If Windows fails to start twice in a row, it opens the recovery screen. Go to Troubleshoot → Advanced options → Startup Settings → Restart, then press 4 for Safe Mode.
If Safe Mode is stable, a driver or startup program is the likely cause.
2. Repair system files
Open Command Prompt as administrator and run:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Let both finish, then restart.
3. Check the drive
chkdsk C: /scan
If it reports errors, or the drive is making noises, stop and back up. A failing drive gets worse every time it's used.
4. Roll back recent changes
- Updates: Settings → Windows Update → Update history → Uninstall updates
- Drivers: Device Manager → right-click the device → Properties → Driver → Roll Back Driver
- System Restore: from the recovery screen, pick a restore point from before the problem began
5. Test the RAM
Search for Windows Memory Diagnostic, run it and let the machine restart. Any errors mean a RAM module needs replacing.
When to get help
If the blue screen keeps coming back after these steps, or you see drive errors, the fix is usually hardware. Send us a photo and the story and we'll give you a clear quote before touching anything.