Blue Screen: CRITICAL_PROCESS_DIED (Stop code 0x000000EF)
A process Windows can’t run without (csrss, wininit, smss…) stopped unexpectedly, so the system halted.
Seen on:
Windows
Meaning
Usually caused by corrupted system files, failing storage, bad drivers or an interrupted update. If it happens at every boot, use Windows Recovery (WinRE) to repair.
Common causes
- Corrupted system files after a failed update
- Failing SSD/HDD (bad sectors)
- Faulty driver
- Malware tampering with system processes
⚡ Quick fix
- Run
sfc /scannowand DISM RestoreHealth - Check the disk:
chkdsk C: /f /rand the drive’s SMART status - Uninstall the latest update from WinRE if it started afterwards
- Use System Restore
Detailed fix by platform
Windows
- From WinRE Command Prompt (offline repair):bat
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows chkdsk C: /f /r
How to diagnose
- Trigger — After an update, driver install or randomly?
- Disk health — SMART status / chkdsk results
- System files — SFC/DISM results
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Windows
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026