How to Fix the CRITICAL PROCESS DIED Error in Windows 11

What CRITICAL PROCESS DIED means and what usually causes it

Windows keeps a short list of processes it cannot run without: the session manager (smss.exe), the Client/Server Runtime Subsystem (csrss.exe), wininit.exe, services.exe and a few others. Stop code 0x000000EF — CRITICAL_PROCESS_DIED — appears the moment one of them exits, or its threads die in a way the kernel cannot tolerate. The screen itself is honest but vague, because a hundred different faults end in the same dead process.

The statistics of support forums point to a handful of roots. Most often a Windows Update or a sudden power loss leaves system files half-written, and the critical process trips over the corruption on the next boot. Drivers and hardware come next: an antivirus filter driver, failing RAM or bad sectors on the system drive can kill a process just as dead as corrupt files, and the crash rarely announces which one it was.

The repair ladder: SFC, DISM and chkdsk

Open Terminal (Admin) from the power-user menu (Win + X) and work through the ladder in order. Each run takes five to twenty minutes, and a reboot after each step is not required but helps. If the crash happens before login, reach the same prompts via Settings → System → Recovery → Advanced startup, or by interrupting boot three times to force Automatic Repair into WinRE, then Troubleshoot → Advanced options → Command Prompt.

The checks are cumulative: DISM repairs the component store that SFC draws its spare parts from, and chkdsk fixes the disk errors that would corrupt files all over again. Run them in this order and skip nothing, even if the first scan reports no integrity violations — each tool sees a different layer of damage. If SFC fixes files but the crash returns days later, suspect the disk rather than the files.

• sfc /scannow — scans protected system files and restores the corrupted ones from the component store
• DISM /Online /Cleanup-Image /RestoreHealth — repairs the component store itself, the source SFC copies from
• chkdsk C: /f /r — schedules a full scan of the system drive at the next reboot; confirm with Y
• WinRE → Troubleshoot → Advanced options → Uninstall Updates — removes a quality or feature update that broke boot
• Device Manager → device Properties → Driver → Roll Back Driver — undoes the driver that shipped with the crash

When the ladder is not enough

If the crash survives all three tools, move to the bigger hammers in order of gentleness. System Restore from WinRE (Troubleshoot → Advanced options → System Restore) rolls the whole system state back past the point where the trouble started. An in-place repair install — mount a Windows 11 ISO, run setup.exe, choose to keep files and apps — rebuilds Windows from scratch while your data and programs stay in place.

Hardware deserves a look before any reset, though. Run the Windows Memory Diagnostic (mdsched.exe) to test RAM, check the SSD's SMART health, and keep the files in C:\Windows\Minidump: they carry the name of the driver that died, which turns guesswork into a diagnosis. Only after memory and disk test clean is a full reset honest advice.

Questions and Answers

Read next

All articles · FAQ