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

Understanding the CRITICAL_PROCESS_DIED Error

The full error message you will see on the blue screen reads:

Your PC ran into a problem and needs to restart.
Stop code: CRITICAL_PROCESS_DIED

The underlying Windows stop code is 0x000000EF. Windows uses this bugcheck when a process or thread that is essential to the operating system terminates in an unexpected or illegal way. The kernel cannot continue operation without that process, so it immediately raises a bugcheck (BSOD) to prevent data corruption.

Common critical processes whose death triggers this BSOD include:

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

Root Causes

1. Corrupted system files — ntfs.sys, ntoskrnl.exe, or other kernel components corrupted by a failed update, forced shutdown, or disk error.
2. Bad or incompatible device drivers — Graphics drivers (NVIDIA, AMD, Intel), storage controller drivers, or network adapter drivers that are unsigned, outdated, or incompatible with a new Windows 10 version.
3. Failed Windows Update — Cumulative updates and feature updates (e.g., 21H2, 22H2) can sometimes leave the system in a half-updated state that triggers this BSOD.
4. Faulty RAM (memory) — Bad memory cells cause random data corruption that can kill critical processes.
5. Failing HDD/SSD — Bad sectors on the boot drive corrupt OS files at runtime.
6. Malware — Rootkits or bootkits that modify or terminate system processes.
7. Fresh install media corruption — If you see CRITICAL_PROCESS_DIED during a Windows 10 installation, your ISO or USB drive is likely corrupted.

Step 1: Access Safe Mode or Windows Recovery Environment (WinRE)

Before you can run any fix, you need a working command line.

Option A — Access WinRE via Automatic Repair

If Windows 10 fails to boot three times in a row, it automatically opens the Automatic Repair screen. From there:

1. Click Advanced options.
2. Select Troubleshoot → Advanced options.
3. Choose Command Prompt or Startup Settings → Enable Safe Mode with Networking (press F5).

Option B — Force WinRE

If the automatic repair loop does not start, power off the PC mid-boot (hold the power button for 4 seconds) three consecutive times. On the fourth start Windows will enter the recovery environment.

Option C — Bootable USB Media

Download the Windows 10 Media Creation Tool from Microsoft, create a bootable USB, boot from it, select Repair your computer, then Troubleshoot → Command Prompt.

Step 2: Run System File Checker (SFC)

SFC scans and repairs corrupted Windows system files. Open an elevated Command Prompt and run:

sfc /scannow

If you are in WinRE Command Prompt (offline mode), you must specify the Windows drive. First identify the drive letter:

dir C:\
dir D:\

Then run SFC offline (replace D: with your Windows drive and E: with the WinRE scratch space):

sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Wait for the scan to complete. If it reports "Windows Resource Protection found corrupt files and repaired them," reboot and test.

Step 3: Run DISM to Repair the Windows Image

DISM (Deployment Image Servicing and Management) fixes issues that SFC cannot resolve by downloading clean files from Windows Update:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

For offline repair from WinRE (replace D: with your Windows partition):

DISM /Image:D:\ /Cleanup-Image /RestoreHealth /Source:wim:C:\Sources\install.wim:1 /LimitAccess

After DISM completes, re-run sfc /scannow, then reboot.

Step 4: Check the Disk for File System Errors

chkdsk C: /f /r /x

The /f flag fixes errors, /r locates bad sectors and recovers readable data, and /x forces an unmount. You may be prompted to schedule the scan on next reboot — type Y and press Enter, then restart.

Step 5: Uninstall the Problematic Driver or Windows Update

Uninstall a Problematic Driver (Safe Mode)

1. Boot into Safe Mode.
2. Press Win + X → Device Manager.
3. Look for devices with a yellow warning icon.
4. Right-click the suspect device → Uninstall device → check Delete the driver software for this device.
5. For display drivers, use Display Driver Uninstaller (DDU) in Safe Mode for a clean removal.

Uninstall a Recent Windows Update

1. Go to Settings → Update & Security → Windows Update → View update history → Uninstall updates.
2. Sort by date installed and right-click the most recent update → Uninstall.
3. Alternatively, from Command Prompt:

wusa /uninstall /kb:5034441

Replace 5034441 with the KB number of the problematic update.

Step 6: Run Windows Memory Diagnostic

From the Start menu search, open Windows Memory Diagnostic and select Restart now and check for problems. Alternatively, from Command Prompt:

mdsched.exe

For a more thorough test, boot from a MemTest86 USB and run at least two full passes. If errors are detected, replace the faulty RAM stick.

Step 7: Perform Startup Repair

From WinRE:

1. Troubleshoot → Advanced options → Startup Repair.
2. Select your account and enter your password.
3. Windows will attempt to automatically diagnose and fix startup issues.

Alternatively from Command Prompt:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

Step 8: System Restore

If a restore point exists from before the BSOD started:

1. WinRE → Troubleshoot → Advanced options → System Restore.
2. Choose a restore point dated before the problem began.
3. Confirm and let the process complete (~20–40 minutes).

Step 9: In-Place Upgrade Reinstall (Last Resort Before Clean Install)

An in-place upgrade reinstalls Windows 10 while preserving your files, apps, and settings. Boot normally (if possible) or from bootable USB:

1. Mount or run the Windows 10 ISO setup.
2. Choose Upgrade this PC now.
3. When prompted, select Keep personal files and apps.
4. Let the installation complete (~1–2 hours).

This replaces all system files without wiping your data and resolves deep OS corruption.

Special Scenarios

CRITICAL_PROCESS_DIED During Windows 10 Installation

This almost always means corrupted installation media. Re-download the ISO from Microsoft's official site, verify the SHA256 hash, re-create your USB with Rufus or the Media Creation Tool, and retry the installation. Also try a different USB port (preferably USB 2.0) and run memtest86 to rule out RAM issues.

CRITICAL_PROCESS_DIED on Dell or HP Laptops

OEM laptops often have BIOS/UEFI firmware and bundled drivers that conflict with Windows 10 feature updates. Steps:

1. Update the BIOS/UEFI to the latest version from the manufacturer's support site.
2. Visit Dell SupportAssist or HP Support Assistant and update all drivers.
3. Disable Secure Boot temporarily to rule out driver signing conflicts.

Cannot Boot into Safe Mode (F8 not working)

On Windows 10, legacy F8 Safe Mode is disabled by default. Use one of these alternatives:

• WinRE → Startup Settings → Restart → press F4/F5.
• From an elevated CMD (if you can reach it): bcdedit /set {default} safeboot minimal then reboot. After fixing, run bcdedit /deletevalue {default} safeboot to restore normal boot.

Stuck in an Automatic Repair Loop

If Startup Repair keeps failing and looping:

1. Open WinRE Command Prompt.
2. Disable automatic repair temporarily: bcdedit /set {default} recoveryenabled No
3. Run SFC and DISM as described above.
4. Re-enable: bcdedit /set {default} recoveryenabled Yes