CRITICAL_PROCESS_DIED in Windows: causes and ways to fix it

What does CRITICAL_PROCESS_DIED (0xEF) mean

CRITICAL_PROCESS_DIED is a BSOD that occurs when Windows detects the termination or corruption of a critical system process (such as csrss.exe, wininit.exe, services.exe, etc.). To prevent further data corruption, the system halts and displays a blue screen.

Typical symptoms:

• boot loop;
• BSOD immediately after login or during boot;
• the error appeared after a Windows/driver update, antivirus installation, SSD/HDD replacement, or overclocking.

Common causes

1. Corruption of system files or Windows component store.
2. File system errors or degradation of SSD/HDD (bad blocks, controller issues, cable problems).
3. Problematic drivers (video driver, storage/NVMe/SATA, network, antivirus filter).
4. Incorrect Windows updates or software conflicts after an update.
5. Memory (RAM): unstable modules, XMP/overclocking, errors.
6. Third-party antivirus/EDR or system "tweakers" interfering with processes.

Before you start: minimal diagnostics

1) Disconnect external devices

Disconnect for the duration of diagnostics:

• USB drives, docking stations, external disks;
• printers/scanners;
• non-standard USB adapters (Wi-Fi/BT).

2) Check for dumps

If Windows manages to create a dump, it is usually located here:

• C:\Windows\Minidump\
• C:\Windows\MEMORY.DMP

For basic analysis (without a debugger), you can check the Event Viewer:

• eventvwr.msc → Windows Logs → System
• filter by sources: BugCheck, WHEA-Logger, Disk, Ntfs

Solution 1: Boot into Safe Mode

If Windows boots at least sometimes:

1. Open Settings → System → Recovery (Windows 11)
   or Settings → Update & Security → Recovery (Windows 10).
2. Advanced startup → Restart now.
3. Troubleshoot → Advanced options → Startup Settings → Restart.
4. Press 4 (Safe Mode) or 5 (Safe Mode with Networking).

If Windows does not boot: enter WinRE (interrupt the boot process 3 times using the power button at the Windows logo) → then follow the same steps.

Solution 2: Repair system files (SFC)

Open Command Prompt as Administrator and execute:

sfc /scannow

If SFC reports that it cannot fix some files — proceed to DISM.

Solution 3: Repair component store (DISM)

In the same console:

DISM /Online /Cleanup-Image /RestoreHealth

Then repeat:

sfc /scannow

On Windows Server, DISM may sometimes require a source (install.wim). In this case, use the installation ISO and the /Source parameter.

Solution 4: Check disk and file system (CHKDSK)

Disk errors are one of the most common causes of 0xEF.

Run:

chkdsk C: /f /r

• /f fixes file system errors
• /r locates bad sectors and attempts to recover readable data

If prompted to perform the check on the next boot — agree (Y) and restart.

Additionally: check SMART (quick assessment)

In PowerShell (admin):

wmic diskdrive get status,model

If you see anything other than OK — it’s worth checking the disk with the manufacturer’s utility (Samsung Magician, WD Dashboard, etc.) and considering a replacement.

Solution 5: Roll back/update drivers (especially storage and GPU)

1) Roll back the problematic driver

1. devmgmt.msc → find the device (video adapter, storage controllers, network adapter).
2. Properties → Driver → Roll Back.

2) Clean reinstall the video driver (if BSOD is graphics-related)

• Remove the driver in Device Manager (with the option to delete the driver software).
• Install a stable version from the manufacturer’s website (NVIDIA/AMD/Intel).
• Avoid "beta" and drivers from questionable builds.

3) Storage/NVMe/SATA drivers

If the error started after a BIOS/chipset update or NVMe driver installation:

• update the chipset driver from the motherboard/laptop manufacturer’s website;
• temporarily revert to the standard Microsoft driver (if available through rollback).

Solution 6: Uninstall the latest Windows update

If the BSOD appeared "yesterday/today" after updates:

Settings → Windows Update → Update history → Uninstall updates.

If Windows does not boot:

• WinRE → Troubleshoot → Advanced options → Uninstall updates
  • first uninstall the latest quality update
  • then (if necessary) the feature update

Solution 7: System Restore

If you have restore points enabled:

• WinRE → Advanced options → System Restore
• select a point before the CRITICAL_PROCESS_DIED appeared

This often helps when the cause is a driver/update/software.

Solution 8: Check RAM

Built-in Windows Memory Diagnostic

1. mdsched.exe
2. Restart and check

If errors are found:

• disable XMP/overclocking in BIOS/UEFI;
• test the modules one by one;
• if confirmed — replace the faulty module.

For deep testing, use MemTest86 (bootable), but this will take more time.

Solution 9: Repair boot (if failure occurs at startup)

In WinRE:

1. Advanced options → Startup Repair

If that didn’t help, you can check the system partition and boot records (carefully, especially on UEFI):

bootrec /scanos
bootrec /rebuildbcd

The commands bootrec /fixmbr and bootrec /fixboot on modern UEFI systems may be inappropriate and sometimes lead to additional issues. Use them only if you understand the current boot scheme.

Solution 10: Conflict with antivirus/system utilities

If a third-party antivirus/EDR, "optimizers," tweakers, or acceleration utilities are installed:

• remove them in Safe Mode;
• restart;
• temporarily use Microsoft Defender.

If nothing helped

Option A: "Reset this PC" while keeping files

WinRE → Troubleshoot → Reset this PC → Keep my files.

Option B: In-place repair (repair by installation)

If Windows boots:

• mount the ISO of the same version of Windows
• run setup.exe
• choose to keep files and applications

This often fixes component corruption without a full reinstall.

Option C: Check hardware

If the BSOD recurs even after a clean install:

• disk (SMART/surface tests),
• RAM (MemTest86),
• power supply (voltage drops),
• overheating (CPU/GPU temperatures),
• BIOS/UEFI (update to a stable version).

Prevention

• Do not turn off power during updates.
• Keep chipset/storage drivers and BIOS up to date in a stable state.
• Monitor disk health (SMART) and backups.
• Avoid "optimizers" and questionable tweaks to system services.

Quick checklist (if needed in 15 minutes)

1. Boot into Safe Mode / WinRE.
2. Execute:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth
   chkdsk C: /f /r
   

3. Roll back/uninstall the latest update or driver (GPU/storage).
4. Restart and check for recurrence of the error.