Ad Space — Top Banner

CRITICAL_PROCESS_DIED

Microsoft Windows

Severity: Critical

Source: OnlyErrorCodes.com — Every error code. One place.

Windows CRITICAL_PROCESS_DIED BSOD — Stop Code Fix

What it means

Windows BSOD 'CRITICAL_PROCESS_DIED' is the bug check with stop code 0x000000EF, documented on Microsoft Learn at learn.microsoft.com/windows-hardware/drivers/debugger/bug-check-0xef--critical-process-died.
Microsoft's exact description: 'a critical system process died.'
Critical system processes are services Windows can't run without — csrss.exe, wininit.exe, services.exe, winlogon.exe, smss.exe, conhost.exe, logonui.exe.
When one of these terminates unexpectedly, Windows bug-checks because OS integrity is in question.
Most common cause is a buggy or misconfigured device driver.

Affected Models

  • Windows 11 (every version — 21H2, 22H2, 23H2, 24H2, 25H2)
  • Windows 10 (every version — most often after a driver update)
  • Windows Server 2016 / 2019 / 2022 / 2025
  • Often follows: GPU driver update, antivirus update, recent in-place Windows upgrade
  • Same Microsoft documentation and fix sequence apply across all versions

Common Causes

  • Buggy or misconfigured device driver — by far the most common cause
  • Failing RAM corrupting the memory used by a critical process
  • Corrupt system files in the Component Store
  • Malware that injected into a critical process and killed it
  • Failing SSD causing reads to fail when a critical process loads

How to Fix It

  1. Boot into Safe Mode.

    If the system is stuck in a BSOD loop, press F8 / Shift+F8 during boot (or boot from Windows install media and choose Repair > Troubleshoot > Advanced > Startup Settings > Restart > 4).
    Safe Mode loads with minimal drivers — if Safe Mode works, the issue is definitely a third-party driver.

  2. Uninstall the most recently updated driver.

    In Safe Mode, open Device Manager (devmgmt.msc).
    The most common culprits are display adapters and network adapters.
    Right-click your GPU driver > Properties > Driver tab > Roll Back Driver.
    If Roll Back isn't available, choose 'Uninstall device' and tick 'Delete the driver software'.
    Restart normally.
    Windows installs the default driver; if BSOD stops, the rolled-back third-party driver was the cause.

  3. Run Driver Verifier to identify the bad driver.

    If you can't tell which driver caused the BSOD, in normal mode (after the system boots) run: verifier.exe
    Choose 'Create standard settings' > 'Automatically select unsigned drivers' > Finish > restart.
    The system runs with extra checks on third-party drivers and BSODs again pointing at the specific bad one.
    Note the driver name in the new BSOD, then in Safe Mode run: verifier.exe /reset to disable Driver Verifier.
    Now uninstall the named driver.

  4. Run System File Checker and DISM RestoreHealth.

    Open Command Prompt as Administrator:
    sfc /scannow
    DISM /Online /Cleanup-Image /RestoreHealth
    If either reports and repairs corruption, restart and watch for the BSOD.
    Corrupt csrss.exe or wininit.exe is a documented (rare) cause.

  5. Run Windows Memory Diagnostic.

    Press Win+R, type mdsched.exe, Enter.
    Choose 'Restart now and check for problems'.
    The system reboots into the diagnostic tool, runs RAM tests for 5-30 minutes, then reports results.
    If errors are found, the RAM has a fault — try removing one stick at a time to identify which is bad, or run MemTest86 for an exhaustive test.

  6. Run chkdsk for SSD/HDD errors.

    Open Command Prompt as Administrator:
    chkdsk C: /f /r
    It prompts to schedule for next boot.
    Type Y, Enter, restart.
    chkdsk runs (can take 30 minutes to several hours) and repairs filesystem errors.
    If chkdsk reports unrecoverable errors, the drive is failing — back up data and replace it.

  7. Use System Restore to roll back recent changes.

    If the BSOD started after a specific change (Windows Update, app install, driver), boot from Windows install media > Repair your computer > Troubleshoot > System Restore.
    Pick a restore point from before the BSOD started.
    The system reverts settings and drivers; user files are untouched.

When to Call a Professional

CRITICAL_PROCESS_DIED needs hands-on troubleshooting but rarely a hardware repair.
If the system boots into Safe Mode and Driver Verifier identifies a specific driver, replacing that driver clears the bug check.
If the system won't boot at all (BSOD even in Safe Mode), Windows Recovery Environment > Startup Repair is the next step.
True hardware failure (failing RAM or SSD) is rare but possible — diagnose with Windows Memory Diagnostic and chkdsk before assuming software fault.

Frequently Asked Questions

How do I find which driver caused CRITICAL_PROCESS_DIED?

Three options, from easiest to hardest.
Easiest: check Reliability Monitor (type 'reliability' in Start) — recent BSODs often have a driver name in the technical details.
Middle: install WinDbg from the Microsoft Store, open the most recent .dmp file in C:\Windows\Minidump, run !analyze -v — the output names the driver that triggered the bug check.
Most thorough: enable Driver Verifier (step 3 on this page) which forces a BSOD pointing directly at the bad driver.
Driver Verifier is heavy-handed but unambiguous.