How to Fix CRITICAL_PROCESS_DIED in Windows 11

•
My Technician
Windows 11BSODTroubleshootingFix

The Problem

CRITICAL_PROCESS_DIED (stop code 0x000000EF) means a process Windows needs to stay alive was killed unexpectedly—usually corrupt system files, a bad driver, or failing storage. Sometimes it blue-screens once; sometimes it loops on every boot.

New to blue screens? Start with the general guide: how to fix the Blue Screen of Death. For a different stop code, see DPC_WATCHDOG_VIOLATION.

Quick Fixes (Try These First)

Unplug Recently Added Hardware

If the crash started after adding RAM, a drive, or a USB device, remove it and test. New hardware with a bad driver is a frequent trigger.

Reboot and Note the Frequency

A single CRITICAL_PROCESS_DIED after an update may not recur. If it loops, go straight to Safe Mode below.

The Fix: Step-by-Step

Step 1: Boot into Safe Mode

If Windows won't stay up, force-shutdown at the logo three times to reach Automatic Repair → Advanced options → Troubleshoot → Advanced options → Startup Settings → Restart → press 4. Full steps: enter Safe Mode in Windows 11.

Step 2: Repair System Files (SFC + DISM)

Corrupt OS files are the most common cause. In Terminal (Admin) or the recovery Command Prompt:

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

Reboot after both complete.

Step 3: Update or Roll Back Drivers

  1. Right-click Start → Device Manager.
  2. Look for any device with a yellow !. Right-click → Update driver.
  3. If the BSOD began right after a driver update, use Properties → Driver → Roll Back Driver. More help: update outdated drivers.

Step 4: Run Disk and Memory Checks

  1. Check the disk (Terminal Admin): 
    chkdsk /f /r
    Type Y to schedule it on the next reboot, then restart.
  2. Check the RAM: Win + R → mdsched.exe → Restart now and check for problems.

Step 5: Uninstall a Bad Update or Use System Restore

Still Crashing?

Diagnose the cause faster: Windows Troubleshooter runs driver, RAM, and disk checks in one pass so you're not guessing which one threw the stop code.

Related guides