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

Understanding the 'Critical Process Died' Error in Windows 11

When you see a blue screen with the message CRITICAL_PROCESS_DIED and stop code 0x000000EF, Windows has detected that a process essential to the operating system's operation terminated unexpectedly. Unlike user-mode application crashes, these are kernel-level failures where Windows cannot continue safely and forces an immediate shutdown to prevent data corruption.

The exact screen you see reads:

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

Processes that commonly trigger this error include:

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

Any of these exiting without authorization causes Windows to issue stop code 0x000000EF immediately.

Step 1: Identify the Triggering Driver or Process via Minidump

If Windows can boot at all, examine the minidump file to pinpoint the exact cause.

1. Press Win + R, type %SystemRoot%\Minidump, press Enter.
2. Look for .dmp files with timestamps matching your BSOD.
3. Open Event Viewer (Win + X → Event Viewer) → Windows Logs → System → filter for Critical and Error entries around the crash time.
4. Use WhoCrashed (free tool) or WinDbg to analyze the dump file and identify the faulting module.

In WinDbg, run:

!analyze -v

This outputs the faulting driver name (e.g., nvlddmkm.sys for NVIDIA, amdkmdag.sys for AMD).

Step 2: Run System File Checker (SFC) and DISM

Corrupt system files are the most common fixable cause. Run these commands in order from an elevated Command Prompt (Run as Administrator):

Step 2a — SFC scan:

sfc /scannow

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

Step 2b — DISM repair:

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

After DISM completes, run sfc /scannow again to allow it to repair any files DISM restored.

Reboot after both complete.

Step 3: Fix Drivers (Update, Roll Back, or Remove)

Driver conflicts are the second most common cause, particularly after Windows Update installs new driver versions automatically.

To roll back a driver:

1. Press Win + X → Device Manager.
2. Expand the category (Display Adapters, Network Adapters, Storage Controllers).
3. Right-click the device → Properties → Driver tab → Roll Back Driver.

To uninstall a problematic driver completely:

pnputil /delete-driver <oemNN.inf> /uninstall /force

Replace <oemNN.inf> with the INF file name shown in Device Manager under Driver Details.

For GPU drivers specifically, use Display Driver Uninstaller (DDU) in safe mode for a clean removal before reinstalling the correct version.

To update all drivers via Windows Update:

usoclient StartScan

Or navigate to Settings → Windows Update → Advanced Options → Optional Updates → Driver Updates.

Step 4: Disable Fast Startup

Fast Startup (hybrid shutdown) can cause stale kernel states that trigger CRITICAL_PROCESS_DIED on subsequent boots, especially on systems with certain storage or chipset drivers.

1. Press Win + R → type powercfg.cpl → Enter.
2. Click Choose what the power buttons do.
3. Click Change settings that are currently unavailable.
4. Uncheck "Turn on fast startup (recommended)".
5. Click Save changes.

Alternatively via command line:

powercfg /h off

Step 5: Run Windows Memory Diagnostic

Faulty RAM causes unpredictable kernel failures including CRITICAL_PROCESS_DIED.

MdSched.exe

Choose "Restart now and check for problems." The tool runs before Windows loads and reports errors on next login.

For more thorough testing, use MemTest86 (bootable USB) which runs outside Windows and tests all RAM independently.

Step 6: Check Disk for Storage Errors

chkdsk C: /f /r /x

You will be prompted to schedule the scan on next reboot (type Y). Restart and allow the scan to complete — this can take 30–60 minutes on large drives.

Step 7: If Windows Won't Boot — Using WinRE Without Safe Mode

A common problem reported on Reddit and forums is Windows 11 Critical Process Died on boot with no access to safe mode. Windows 11 significantly shortened the automatic repair trigger window, but you can force it:

Force WinRE entry:

1. Power on your PC.
2. As soon as the Windows logo appears, hold the power button to force shutdown.
3. Repeat 3 times — on the 4th boot, Windows automatically enters Automatic Repair mode.
4. Click Advanced Options → Troubleshoot → Advanced Options.

From WinRE Advanced Options you can:

• Startup Repair — automated fix for boot issues.
• Command Prompt — run SFC, DISM, chkdsk manually.
• System Restore — revert to a previous restore point.
• Uninstall Updates — remove a recently installed update that caused the BSOD.

Running SFC from WinRE Command Prompt:

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

Running DISM from WinRE:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth

Step 8: Uninstall Recent Windows Updates

If the BSOD began after a specific Windows Update:

1. From WinRE: Advanced Options → Uninstall Updates → Uninstall latest quality update.
2. From within Windows: Settings → Windows Update → Update History → Uninstall Updates.

Or via Command Prompt:

wusa /uninstall /kb:XXXXXXX

Replace XXXXXXX with the KB number visible in Update History.

Step 9: Reset Windows 11 (Last Resort)

If all above steps fail:

1. Settings → System → Recovery → Reset this PC.
2. Choose Keep my files (reinstalls Windows, removes apps and settings) or Remove everything (full wipe).
3. Select Cloud download for the freshest Windows files, especially if local files are suspected corrupt.

Alternatively, perform a clean install using the Windows 11 Installation Media from Microsoft, which completely replaces all system files.

Preventive Measures

• Enable System Restore and create restore points before major updates.
• Keep drivers updated through manufacturer websites rather than relying solely on Windows Update.
• Run sfc /scannow monthly as a health check.
• Avoid third-party kernel-level tools (game anti-cheat software, aggressive antivirus with kernel drivers) unless necessary.
• Ensure your system is thermally healthy — overheating can corrupt memory and cause process failures.