CRITICAL_PROCESS_DIED (0x000000EF)? Isolate the Cause Before You Reinstall

Your PC blue-screens with CRITICAL_PROCESS_DIED (stop code 0x000000EF), sometimes in a restart loop.

What it means: a process Windows considers critical unexpectedly terminated. Microsoft’s guidance is to isolate the recent change — a driver, a corrupted system file, or a low-level utility (antivirus, disk, VPN, overclocking tools) — not to jump straight to a clean reinstall or registry cleaner like most posts suggest.

Fix 1: Undo recent changes

• Newly installed driver/app/utility? Uninstall it (especially AV, disk tools, VPN, RGB/overclock software).
• Device Manager → recently updated driver → Roll Back Driver.
• System Restore to a point before the crashes started (rstrui).

Fix 2: Repair system files

In an admin Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Reboot. Corrupted system files are a common 0xEF cause.

Fix 3: If it’s a boot loop — use Safe Mode / WinRE

Can’t stay booted long enough to fix it?

1. Force-power-off during boot 3 times → Automatic Repair → Advanced options → Startup Settings → Restart → 4 (Safe Mode).
2. In Safe Mode, do Fix 1 (roll back/uninstall the offending driver or app) and Fix 2.
3. Or use Uninstall latest quality update in WinRE if it started after an update.

Fix 4: Name the culprit from the dump

If it keeps crashing, the memory dump usually names the faulting driver. Use the dump-reading steps in find the driver behind a Blue Screen.

FAQ

Should I just reinstall Windows? Not first — 0xEF is usually one driver/app/file. Isolate it (Fix 1–2); save reinstall for last.

Hardware? Possible (check RAM/disk), but software causes dominate for 0xEF. If you also see WHEA codes, that points to hardware — see WHEA_UNCORRECTABLE_ERROR.

Sources: Microsoft Learn — Bug Check 0xEF CRITICAL_PROCESS_DIED