CRITICAL_PROCESS_DIED — Causes & Fix
Windows Stop code 0x000000EF (CRITICAL_PROCESS_DIED) means a process Windows relies on to run unexpectedly stopped — losing a critical system process forces the shutdown.
- Applies to
- Any Windows PC
- Time to fix
- 30 minutes – 2 hours
What it means
Causes include corrupt system files, a bad driver, malware, or disk corruption. This is a Windows Stop error (a "bugcheck" / blue screen) documented by Microsoft. The blue screen shows this code; more detail sits in the crash dump (%SystemRoot%\Minidump), which usually names the specific driver or component at fault — a free tool like BlueScreenView or WinDbg can read it.
Symptoms
- Blue screen citing CRITICAL_PROCESS_DIED
- Sudden crashes; sometimes boot loops
How to fix it
- 1
Repair system files
1. Run "sfc /scannow" and "DISM /Online /Cleanup-Image /RestoreHealth". 2. Run chkdsk on the system drive.
- 2
Undo recent changes
1. Uninstall a recently added driver/app or use System Restore; scan for malware.
Frequently asked questions
How do I fix CRITICAL_PROCESS_DIED?
Repair system files with SFC and DISM, run chkdsk, and undo recent driver/app changes. If it won't boot, use Safe Mode or Startup Repair.
Last updated July 20, 2026
Guidance only — always consult a qualified professional or the official service manual before carrying out repairs.