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

Understanding the Windows 11 Critical Process Died Error

The CRITICAL_PROCESS_DIED Blue Screen of Death (BSOD) appears with stop code 0x000000EF when Windows detects that a critical system process has been terminated unexpectedly or has entered an invalid state. This is a protective mechanism — the OS deliberately crashes to prevent data corruption or security breaches.

The exact error message you will see on screen is:

Your PC ran into a problem and needs to restart.
We're just collecting some error info, and then we'll restart for you.

Stop code: CRITICAL PROCESS DIED

Common culprits include smss.exe (Session Manager), csrss.exe (Client/Server Runtime), wininit.exe (Windows Initialization), winlogon.exe, and lsass.exe (Local Security Authority). When any of these die, Windows cannot continue safely.

Step 1: Determine if You Can Still Boot

Before attempting any fix, identify your boot state:

• If Windows 11 boots normally (at least into desktop): You can run repairs from within the OS.
• If Windows 11 crashes on boot (loops or stuck on BSOD): You need to access the Windows Recovery Environment (WinRE) first.
• If Safe Mode is unavailable: Force WinRE by hard-resetting the PC 3 times during boot (hold power button until shutdown, repeat 3 times). Windows will automatically enter Automatic Repair mode.

Step 2: Access Safe Mode or WinRE

Method A — From within Windows (if you can boot):

1. Press Win + R, type msconfig, press Enter.
2. Go to the Boot tab, check Safe boot > Minimal, click OK.
3. Restart your PC.

Method B — From the login screen:

1. Hold Shift and click Restart.
2. Navigate to Troubleshoot > Advanced options > Startup Settings > Restart.
3. Press F4 for Safe Mode or F5 for Safe Mode with Networking.

Method C — Windows 11 Critical Process Died with No Safe Mode (using installation media):

1. Create a Windows 11 bootable USB using the Media Creation Tool.
2. Boot from USB, choose language, then click Repair your computer.
3. Navigate to Troubleshoot > Advanced options > Command Prompt or Startup Repair.

Step 3: Run System File Checker (SFC)

System File Checker scans and repairs protected Windows system files. This is the most common fix for CRITICAL_PROCESS_DIED caused by file corruption.

Open Command Prompt as Administrator and run:

sfc /scannow

Wait for 100% completion. If it reports "Windows Resource Protection found corrupt files but was unable to fix some of them", proceed to DISM.

Step 4: Run DISM to Repair Windows Image

DISM repairs the Windows component store that SFC relies on. Run all three commands in order:

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

After DISM completes, run SFC /scannow again and restart.

Step 5: Check and Repair Disk (CHKDSK)

A failing hard drive or SSD with bad sectors can corrupt system files and cause this BSOD. Run:

chkdsk C: /f /r /x

You will be prompted to schedule the scan on next reboot. Type Y and restart. This scan can take 30–90 minutes depending on drive size.

Step 6: Identify and Roll Back Problematic Drivers

Drivers are the most common cause of CRITICAL_PROCESS_DIED, especially GPU, network, or storage drivers updated recently.

To find the problematic driver using Event Viewer:

1. Press Win + X and open Event Viewer.
2. Navigate to Windows Logs > System.
3. Look for Critical or Error entries timestamped around the crash time.
4. Note any driver (.sys) filenames mentioned.

To roll back a driver:

1. Right-click Start > Device Manager.
2. Find the device (e.g., Display adapters, Network adapters).
3. Right-click the device > Properties > Driver tab > Roll Back Driver.

To uninstall a driver completely (e.g., GPU):

pnputil /delete-driver oem##.inf /uninstall /force

Replace oem##.inf with the actual INF file name found in Device Manager > Properties > Details > Inf name.

Step 7: Check RAM with Windows Memory Diagnostic

Faulty RAM can cause random process terminations. Run:

mdsched.exe

Choose Restart now and check for problems. After reboot, results appear in Event Viewer under Windows Logs > System, source: MemoryDiagnostics-Results.

For a more thorough test, use MemTest86 (bootable USB tool) to run overnight.

Step 8: Use Startup Repair (For On-Boot Crashes)

If Windows 11 crashes on boot with CRITICAL_PROCESS_DIED and you cannot reach the desktop:

1. Boot from WinRE (see Step 2, Method C).
2. Go to Troubleshoot > Advanced options > Startup Repair.
3. Select your Windows 11 installation and let it run.

If Startup Repair fails, try System Restore from the same Advanced Options menu, selecting a restore point from before the crashes began.

Step 9: Analyze Minidump Files

Windows saves crash dump files at C:\Windows\Minidump\. Analyzing these reveals exactly which process or driver caused the crash.

Use WinDbg (from the Microsoft Store or Windows SDK):

windbg -z C:\Windows\Minidump\<dumpfile.dmp>

In WinDbg, run:

!analyze -v

Look for the faulting module in the output — this will be the driver or process responsible.

Alternatively, use the free tool WhoCrashed or BlueScreenView to parse minidump files with a simple GUI.

Step 10: Reset or Clean Install Windows 11 (Last Resort)

If all the above steps fail:

Reset This PC (Keep Files):

1. Go to Settings > System > Recovery > Reset this PC.
2. Choose Keep my files and follow the prompts.

Clean Install:

1. Back up all data to an external drive.
2. Create a bootable Windows 11 USB using the Media Creation Tool.
3. Boot from USB and select Custom Install, deleting the existing partition.

Prevention Tips

• Pause Windows Updates for 1–2 weeks to let known-bad updates be patched by Microsoft.
• Always create a System Restore point before installing new drivers.
• Keep your SSD/HDD firmware updated.
• Avoid third-party antivirus software that installs kernel-mode drivers (use Windows Defender).
• Monitor storage health using CrystalDiskInfo or PowerShell's Get-PhysicalDisk cmdlet.