Critical Process Died Windows 11: Complete Fix Guide for BSOD Stop Code

Understanding the 'Critical Process Died' Error in Windows 11

The Critical Process Died BSOD (Blue Screen of Death) displays the stop code 0x000000EF and appears when Windows 11 detects that a process flagged as critical to system operation has unexpectedly terminated. The full error screen typically reads:

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

Windows deliberately crashes rather than continuing to run in a potentially unsafe or unstable state. Critical processes include:

• ntoskrnl.exe – Windows NT OS Kernel
• csrss.exe – Client/Server Runtime Subsystem
• winlogon.exe – Windows Logon Process
• wininit.exe – Windows Initialization
• smss.exe – Session Manager Subsystem
• lsass.exe – Local Security Authority Subsystem

If any of these are terminated outside their normal shutdown procedure, the 0x000000EF bug check fires immediately.

Phase 1: Initial Diagnosis — Can You Boot Windows?

Scenario A: Windows 11 Still Boots (Intermittent Crashes)

If the machine occasionally BSODs but you can reach the desktop, start here.

Step 1: Check the Event Viewer Mini-dump

Press Win + X → Event Viewer → Windows Logs → System. Look for Critical or Error events timestamped at the crash time. Note the faulting module name.

Alternatively, open WinDbg or use the built-in Reliability Monitor: Control Panel → Security and Maintenance → View Reliability History.

Step 2: Run SFC in an Elevated Terminal

Open Windows Terminal as Administrator and run the System File Checker:

sfc /scannow

Wait for the scan to complete (do not interrupt). If it reports "Windows Resource Protection found corrupt files but was unable to fix some of them," proceed to DISM:

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

After DISM completes successfully, re-run SFC to allow it to repair files using the freshly restored component store.

Step 3: Identify the Problematic Driver

Open Device Manager (Win + X → Device Manager). Look for any device with a yellow warning triangle. Right-click → Properties → Driver tab → Roll Back Driver if the option is available.

To find recently installed drivers via PowerShell:

Get-WinEvent -LogName System | Where-Object {$_.Id -eq 7045} | Select-Object TimeCreated, Message | Sort-Object TimeCreated -Descending | Select-Object -First 20

If a specific driver is suspect, uninstall it:

pnputil /delete-driver oem<number>.inf /uninstall /force

Step 4: Check Disk Health

# Check for disk errors and schedule repair on next reboot
chkdsk C: /f /r /x

For NVMe or SSD, also use:

Get-PhysicalDisk | Get-StorageReliabilityCounter | Select-Object DeviceId, ReadErrorsTotal, WriteErrorsTotal, Temperature

Scenario B: Windows 11 Cannot Boot — Boot Loop with Critical Process Died

If the machine enters a BSOD loop and cannot reach the desktop, you need to access Windows Recovery Environment (WinRE).

Accessing WinRE:

1. Force shutdown the PC 3 times in a row by holding the power button during boot — Windows 11 will automatically enter Automatic Repair mode on the 3rd attempt.
2. Alternatively, boot from a Windows 11 USB installation media and select "Repair your computer."

Step 1: Run Startup Repair

From WinRE: Troubleshoot → Advanced Options → Startup Repair. Let it run automatically. This resolves bootloader corruption and some critical system file issues.

Step 2: Use Command Prompt in WinRE

If Startup Repair fails: Troubleshoot → Advanced Options → Command Prompt.

:: Identify your Windows drive letter (may not be C: in WinRE)
diskpart
list volume
exit

:: Run SFC offline against the Windows installation
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

:: Run DISM offline repair
Dism /Image:C:\ /Cleanup-Image /RestoreHealth

:: Repair the Boot Configuration Data (if boot issues persist)
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

Step 3: Attempt System Restore from WinRE

Troubleshoot → Advanced Options → System Restore. Choose a restore point dated before the crashes began. This rolls back drivers, registry changes, and system files without affecting personal files.

Step 4: Disable Automatic Restart to Read the Full Stop Code

In WinRE Command Prompt:

bcdedit /set {default} recoveryenabled No
bcdedit /set {default} bootstatuspolicy ignoreallfailures

This forces Windows to display the BSOD instead of auto-restarting, giving you time to read the full stop code and faulting module.

Phase 2: Hardware Diagnostics

RAM Testing

From WinRE or Windows Search: Windows Memory Diagnostic. Restart and let it run. For more thorough testing, use MemTest86 from a bootable USB (run for at least 2 full passes).

Disk Health

In WinRE Command Prompt, run CHKDSK against your system partition:

chkdsk C: /f /r

If the drive shows thousands of bad sectors, replace it before reinstalling Windows.

Phase 3: Advanced Recovery Options

In-Place Upgrade (Repair Install Without Losing Data)

1. Download the Windows 11 ISO from Microsoft and mount it.
2. Run setup.exe from within Windows (or from WinRE using the USB).
3. Choose "Keep personal files and apps."
4. Let setup reinstall Windows 11 over itself, repairing corrupted components.

This is the most effective non-destructive fix for severe system file corruption.

Reset This PC (Keep My Files)

Settings → System → Recovery → Reset this PC → Keep my files. This reinstalls Windows 11 while preserving your personal documents but removes apps and settings.

Phase 4: Prevention

• Enable Driver Isolation via Windows Security → Device Security → Core Isolation.
• Avoid beta/unsigned drivers — always download drivers from the OEM's official site.
• Create restore points before major updates: checkpoint-computer -Description "Pre-Update" -RestorePointType MODIFY_SETTINGS
• Keep Windows Update current — many Critical Process Died bugs are patched in cumulative updates.
• Monitor system health with tools like CrystalDiskInfo (disk S.M.A.R.T.) and HWiNFO64 (temperatures, voltages).