CRITICAL_PROCESS_DIED Windows 10: Complete Fix Guide (BSOD Stop Code 0x000000EF)

Understanding the CRITICAL_PROCESS_DIED Error

The CRITICAL_PROCESS_DIED Blue Screen of Death (BSOD) carries the stop code 0x000000EF. It fires when the Windows kernel detects that a process flagged as critical to system operation has terminated unexpectedly or entered an invalid state. Unlike user-mode process crashes (which just kill the app), a critical-process death is unrecoverable by design — Windows has no choice but to halt and reboot.

Processes most commonly implicated include:

• csrss.exe (Client/Server Runtime Subsystem)
• wininit.exe (Windows Initialization)
• winlogon.exe (Windows Logon)
• lsass.exe (Local Security Authority)
• services.exe (Service Control Manager)

You may also see it written on the blue screen as:

Your PC ran into a problem and needs to restart.
Stop code: CRITICAL PROCESS DIED

Step 1: Determine Whether You Can Boot at All

If you can still log in normally or reach Safe Mode, skip to Step 3.

If you are in a BSOD boot loop, follow these steps to access Windows Recovery Environment (WinRE):

1. Force three consecutive hard shutdowns by holding the power button during boot. After the third attempt, Windows 10 automatically enters Automatic Repair mode.
2. Navigate to Advanced Options → Troubleshoot → Advanced Options.
3. From here you can access: Startup Repair, System Restore, Command Prompt, or Uninstall Updates.

If Automatic Repair fails or loops, boot from a Windows 10 USB drive:

1. Download the Windows 10 Media Creation Tool on another PC.
2. Create a bootable USB (8 GB minimum).
3. Boot your PC from the USB (press F2/F12/Delete for BIOS boot menu — varies by OEM; on Dell it is F12, on HP it is F9).
4. Choose Repair your computer (do NOT click Install Now) to reach WinRE.

Step 2: Boot Into Safe Mode

Safe Mode loads a minimal set of drivers, which often lets you log in even when a faulty driver causes CRITICAL_PROCESS_DIED on normal startup.

From WinRE: Troubleshoot → Advanced Options → Startup Settings → Restart, then press 4 (Safe Mode) or 5 (Safe Mode with Networking).

If even Safe Mode fails with the same BSOD, your issue is likely a corrupted core system file or hardware failure. Proceed with Command Prompt from WinRE (Step 3) and the hardware checks (Step 6).

Step 3: Repair System Files with SFC and DISM

This is the most effective fix for CRITICAL_PROCESS_DIED caused by Windows Update corruption or file system damage.

Open an elevated Command Prompt (from Safe Mode or WinRE → Advanced Options → Command Prompt) and run the following commands in order:

# Step 3a — DISM restores the Windows component store first
DISM /Online /Cleanup-Image /RestoreHealth

# Step 3b — SFC scans and repairs protected system files
sfc /scannow

# If running from WinRE (offline), specify the Windows drive (usually D: or C:)
DISM /Image:C:\ /Cleanup-Image /RestoreHealth
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

After completion, restart the PC. If SFC reports Windows Resource Protection found corrupt files and successfully repaired them, the issue is likely resolved.

Step 4: Check the Disk for Errors

A failing SSD or HDD with bad sectors is a common hardware-side cause, especially on older Dell and HP laptops.

# Run CHKDSK on the system drive — /f fixes errors, /r locates bad sectors
chkdsk C: /f /r /x

This requires a reboot to run before Windows loads. Schedule it and restart. The scan can take 1-2 hours on large HDDs.

Step 5: Roll Back a Problematic Driver or Windows Update

Roll Back a Driver (Safe Mode)

1. Open Device Manager (devmgmt.msc).
2. Expand the suspect category (Display Adapters, Network Adapters, Storage Controllers).
3. Right-click the device → Properties → Driver tab → Roll Back Driver.

To uninstall a driver entirely via command line:

# List all third-party drivers
driverquery /fo list | findstr /i "module"

# Uninstall a specific driver package (replace OEMxx.inf with actual file)
pnputil /delete-driver OEM10.inf /uninstall /force

Uninstall a Problematic Windows Update

From WinRE: Troubleshoot → Advanced Options → Uninstall Updates. Select the latest cumulative update.

Or from Safe Mode Command Prompt:

# List installed updates
wmic qfe list brief /format:table

# Uninstall by KB number (replace KBxxxxxxx)
wusa /uninstall /kb:5034441 /quiet /norestart

Step 6: Test RAM with Windows Memory Diagnostic or MemTest86

Defective RAM can corrupt in-memory kernel structures, causing critical process termination.

From the Start menu, search Windows Memory Diagnostic and choose Restart now and check for problems. For a deeper test, boot from a MemTest86 USB and run at least two full passes. Any errors indicate faulty RAM modules that must be replaced.

Step 7: Perform an In-Place Repair Install (No Data Loss)

If all previous steps fail but you can still boot to the desktop or Safe Mode, a repair install overwrites Windows system files while preserving your files, apps, and settings.

1. Download the Windows 10 ISO using the Media Creation Tool.
2. Mount the ISO and run setup.exe.
3. Choose Upgrade this PC now → keep personal files and apps.
4. Complete the installation (60-90 minutes).

This resolves deep corruption that SFC and DISM cannot reach.

Step 8: Clean Install Windows 10 (Last Resort)

If CRITICAL_PROCESS_DIED persists even during or after a repair install, or if it appeared during a fresh install (critical process died installing windows 10), suspect:

• A corrupt Windows 10 ISO — re-download using Media Creation Tool and verify SHA256.
• Faulty USB drive — try a different USB stick or burn a DVD.
• Hardware incompatibility — check your motherboard/BIOS firmware version against Microsoft's hardware compatibility list and update UEFI firmware before attempting installation.

For clean install: boot from USB → Install Now → Custom → delete all partitions on the target drive → install fresh.