ERRORBlue screen0x000000EF
CRITICAL_PROCESS_DIEDStop code 0x000000EF
CRITICAL_PROCESS_DIED (stop code 0x000000EF) means a process Windows cannot run without has terminated unexpectedly, forcing a blue screen. The usual causes are corrupted system files, a bad driver, disk corruption or failing hardware. Repairing system files and checking the disk fixes most cases; if Windows will not boot, do it from the recovery environment.
What it means
CRITICAL_PROCESS_DIED, bug check 0x000000EF, fires when a process Windows treats as critical, one it cannot continue without, terminates unexpectedly. Core processes such as csrss.exe and lsass.exe are protected precisely so this does not happen; when one dies anyway, the kernel stops the system to prevent worse damage.
Most likely causes
- Corrupted system files, often after an interrupted update or disk problem.
- A faulty or incompatible driver, frequently one installed or updated just before the crashes began.
- Disk corruption or a failing drive, which starves critical processes of the files they need.
- Failing RAM, less commonly.
- Malware that has damaged protected files.
If Windows still boots
Repair system files and check the disk from an elevated prompt:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
chkdsk C: /fSee DISM, sfc and chkdsk. Reboot and let the scheduled chkdsk run.
If Windows will not stay up
Interrupt startup three times (power off as the logo appears) to reach the Windows Recovery Environment, then:
- Startup Repair (Troubleshoot → Advanced options → Startup Repair).
- System Restore to a point before the crashes, if available.
- Command Prompt to run repairs against the offline installation, and
chkdskto check the drive. - Uninstall the last update or driver via Advanced options if the timing points to one.
General blue-screen approach
Most stop codes are caused by drivers, hardware faults, or corrupted system files, in that order of likelihood. The efficient path is:
- Note what changed. A new driver, a Windows update, new hardware, or an overclock immediately before the crashes began is the prime suspect. Roll it back or remove it.
- Boot to Safe Mode if Windows will not stay up: hold Shift and restart, or interrupt boot three times to reach the recovery environment, then Troubleshoot → Advanced options → Startup Settings → Safe Mode.
- Update or roll back drivers, especially graphics, storage and chipset, from the vendor rather than only Windows Update.
- Repair system files from an elevated prompt:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow- Test hardware: Windows Memory Diagnostic for RAM, the drive vendor's tool and chkdsk for storage, and check temperatures.
- Read the dump. The minidump in
C:\Windows\Minidumpnames the faulting driver when analysed with WinDbg or a tool like BlueScreenView.
Frequently asked questions
What causes CRITICAL_PROCESS_DIED?
A process essential to Windows, such as one of the core system processes, stopped unexpectedly. That is usually triggered by corrupted system files, a faulty driver (often after an update), disk corruption, or occasionally failing RAM or storage. Malware that damages system files can also cause it.
How do I fix a CRITICAL_PROCESS_DIED loop?
If Windows keeps crashing before you can work, interrupt boot three times to reach the recovery environment, choose Troubleshoot → Advanced options, and run Startup Repair, then a command prompt to run DISM and sfc against the offline image, or System Restore to before the problem started.