CRITICAL_PROCESS_DIED: causes and fixes
A process that Windows cannot run without has stopped. The cause is usually damaged system files, a bad driver or a failing disk.
What you seeStop code: CRITICAL_PROCESS_DIED
What the code means
Windows depends on a handful of core processes that must run from start-up to shut-down. If one of them ends or is damaged, Windows has no safe way to continue, so it stops with this code. The message does not say which process died or why; the steps below work through the usual reasons.
Likely causes
- Damaged system files, after a power cut during an update, a forced shut-down, or disk errors.
- A faulty or mismatched driver, often for storage or graphics, installed by a recent update.
- A failing SSD or hard disk, or a loose disk cable in a desktop.
- Bad memory (RAM).
- Malware, or an over-eager security or "cleaner" program.
If Windows still starts
- Restart once and note when it happens: at start-up, when waking from sleep, when opening one program. A pattern points to the cause.
- Install updates: Settings › Windows Update, including Optional updates for drivers.
- Repair system files. Open Terminal or Command Prompt as administrator (right-click Start › Terminal (Admin)) and run these two commands, one after the other. Each can take ten to twenty minutes.
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
- Check the disk for errors. This asks to run at the next restart; type Y and restart.
chkdsk C: /f
- Undo the last change: uninstall the most recent update (Settings › Windows Update › Update history › Uninstall updates) or the last program or driver you added.
- Scan for malware: Windows Security › Virus & threat protection › Scan options › Microsoft Defender Antivirus (offline scan).
- Test the memory with
mdsched(Windows key + R). - If the crash appears only on waking from sleep, update the storage and chipset drivers from the computer maker's support page, and turn off Fast startup: Control Panel › Power Options › Choose what the power buttons do › Change settings that are currently unavailable.
If Windows will not start
Let it fail to start two or three times; the blue recovery screen appears. Then:
- Troubleshoot › Advanced options › Startup Repair.
- If that fails: Advanced options › System Restore, and pick a date before the trouble.
- Next: Advanced options › Uninstall Updates › Uninstall latest quality update.
- Then: Advanced options › Startup Settings › Restart, and press 4 for Safe Mode. If Safe Mode works, a driver or program is the cause; remove what was added last.
- From Advanced options › Command Prompt you can run
chkdsk C: /fandsfc /scannow /offbootdir=C:\ /offwindir=C:\Windows. - Last resort: Troubleshoot › Reset this PC › Keep my files. See Reset this PC.
Signs that the disk is failing
Very slow starts, files that will not open, clicking sounds from a hard disk, chkdsk reporting bad sectors, or the code returning after a clean reset. Copy your files off the disk before anything else. A replacement SSD is usually the cure.
Is CRITICAL_PROCESS_DIED a virus?
Rarely. Damaged system files, drivers and failing disks are far commoner causes. An offline Defender scan rules malware out.
Will resetting Windows fix it?
It fixes software causes. If the code comes back after a reset, the disk or memory is at fault.
For Windows 11 and Windows 10. Written in November 2026. Menus move between updates; use the search box in Settings if a name differs. Back up important files before any step that resets, repairs a disk or opens the computer. This is an independent guide, not connected with Microsoft.