The CRITICAL_PROCESS_DIED blue screen is one of the most alarming errors Windows 11 can throw. Your screen goes blue, shows the stop code CRITICAL_PROCESS_DIED, and your computer restarts — sometimes in an endless loop. The good news: in most cases this is completely fixable without losing your files, if you follow the right steps in the right order.
This guide covers 10 proven methods to eliminate the CRITICAL_PROCESS_DIED error on Windows 11, starting with the safest and fastest fixes and working toward the more advanced options. Each method is written as clear, step-by-step instructions you can follow right now.
Emergency: Windows Crashing in a Loop?
If Windows 11 keeps restarting and you can't log in: Force three consecutive shutdowns by holding the power button during boot. On the third attempt, Windows launches the Windows Recovery Environment automatically. From there: Troubleshoot → Advanced options → Startup Settings → Restart → F4 (Safe Mode). Safe Mode disables third-party drivers so you can diagnose without crashing. Then follow the steps below.
What Is CRITICAL_PROCESS_DIED?
The CRITICAL_PROCESS_DIED stop code means that a process Windows considers essential to its operation has either crashed or been terminated unexpectedly. These are not normal applications — they are kernel-level processes that Windows needs running at all times, such as lsass.exe (Local Security Authority), winlogon.exe, or csrss.exe. When one of these exits suddenly, Windows has no safe option except to stop entirely and reboot.
The most common underlying causes of CRITICAL_PROCESS_DIED on Windows 11 are:
- Corrupt or incompatible device drivers — particularly GPU (graphics card) drivers after an update
- Damaged Windows system files — caused by power loss, abrupt shutdowns, or disk errors
- Faulty RAM — bad memory modules cause unpredictable crashes in any process
- Failing hard drive or SSD — bad sectors corrupt system files over time
- Malware that interferes with or injects itself into critical system processes
- A problematic Windows Update that ships with a driver conflict
- Overclocking instability — CPU or RAM pushed beyond stable limits
Before diving into repairs, open Event Viewer to look for clues. Press Win + X and choose Event Viewer, then navigate to Windows Logs → System. Look for Critical or Error entries timestamped at the exact time of the crash — these often name the specific process or driver responsible for the CRITICAL_PROCESS_DIED stop code.
Quick-Reference: 10 Fixes at a Glance
| Method | Best For | Time | Risk to Files |
|---|---|---|---|
| 1. Safe Mode diagnosis | Isolating the cause | 5 min | None |
| 2. SFC /scannow | Corrupted system files | 20–40 min | None |
| 3. DISM /RestoreHealth | Damaged Windows image | 15–30 min | None |
| 4. Update/rollback GPU drivers | Driver-caused crashes | 10 min | None |
| 5. Uninstall recent updates | Crash after Windows update | 10 min | None |
| 6. CHKDSK | Disk errors / bad sectors | 30–120 min | None |
| 7. Disable Fast Startup | Corruption from incomplete shutdown | 2 min | None |
| 8. Windows Memory Diagnostic | Faulty RAM | 20–60 min | None |
| 9. Clean Boot | Third-party software conflict | 15 min | None |
| 10. Reset / Reinstall Windows | When nothing else works | 1–3 hours | Minimal (keep files) |
Method 1: Boot Into Safe Mode to Isolate the Cause
Safe Mode starts Windows with only the minimum drivers and services required to run. If the CRITICAL_PROCESS_DIED blue screen does not appear in Safe Mode, a third-party driver or startup program is almost certainly responsible. If it still crashes in Safe Mode, the problem is corrupted Windows files or hardware (RAM or disk).
Access Windows Recovery Environment
If Windows boots normally: go to Settings → System → Recovery → Advanced startup → Restart now. If Windows loops: force three shutdowns with the power button; on the third attempt recovery launches automatically.
Navigate to Safe Mode
In the recovery menu: Troubleshoot → Advanced options → Startup Settings → Restart. After the restart, press F4 for Safe Mode or F5 for Safe Mode with Networking (needed if you want to download drivers or tools).
Test in Safe Mode
Use your computer for 15–30 minutes in Safe Mode. If stable: the issue is a third-party driver or software — proceed to Methods 4 and 9. If it still crashes in Safe Mode: proceed to Methods 2, 6, and 8 (system files, disk, or RAM).
Method 2: Run SFC /scannow to Repair System Files
System File Checker (SFC) scans every protected Windows file and replaces corrupted versions with a known-good cached copy. It is the first repair tool to run when you suspect corrupted system files are causing CRITICAL_PROCESS_DIED on Windows 11.
Open an Elevated Command Prompt
Press Win + S, type cmd, right-click Command Prompt, and select Run as administrator. Click Yes on the UAC prompt.
Run the Scan
Type the following and press Enter:
sfc /scannow
Do not close this window. The scan takes 20–40 minutes. You will see "Verification 100% complete" when done.
Read the Result
"Windows Resource Protection did not find any integrity violations" — files are clean, move to Method 3.
"Windows Resource Protection found corrupt files and repaired them" — success, reboot and test.
"Windows Resource Protection found corrupt files but was unable to fix some of them" — proceed immediately to Method 3 (DISM).
Run SFC Offline If Windows Won't Stay Stable
In the Windows Recovery Environment, open Command Prompt (Troubleshoot → Advanced options → Command Prompt) and type: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows — this scans the Windows installation without needing it to be running.
Method 3: Run DISM /RestoreHealth
DISM (Deployment Image Servicing and Management) repairs the Windows component store — the reference files that SFC uses to fix corrupted files. If SFC failed to repair everything, it is often because the Windows image itself is corrupted. DISM downloads fresh components from Windows Update to rebuild it. Run this in sequence with Method 2 for the most effective repair of CRITICAL_PROCESS_DIED caused by system file corruption.
Open Administrator Command Prompt
Press Win + S → type cmd → right-click → Run as administrator.
Run DISM RestoreHealth
Type each command and wait for it to complete before typing the next:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
The last command requires an internet connection and takes 15–30 minutes.
Re-run SFC After DISM
After DISM completes, run sfc /scannow again. Now that the Windows image is repaired, SFC can successfully fix the remaining corrupted files. Reboot when both commands are done.
Method 4: Update or Roll Back GPU Drivers
A corrupted or incompatible graphics driver is the single most common hardware driver trigger of CRITICAL_PROCESS_DIED on Windows 11. Both NVIDIA and AMD release driver updates that occasionally introduce instability on specific hardware configurations. If your blue screen started after a recent GPU driver update, roll it back. If your drivers are outdated, update them.
Open Device Manager
Press Win + X and click Device Manager. Expand Display adapters to see your GPU.
Update Drivers
Right-click your GPU (e.g., NVIDIA GeForce RTX 4060 or AMD Radeon RX 7600) and select Update driver → Search automatically for drivers. For best results, download directly from nvidia.com/drivers or amd.com/support, as these are always more current than what Windows Update offers.
Roll Back If the Crash Started After a Recent Update
Right-click your GPU in Device Manager → Properties → Driver tab → Roll Back Driver. If this is greyed out, use Display Driver Uninstaller (DDU) in Safe Mode for a completely clean uninstall, then reinstall the previous driver version from the manufacturer's website.
Update Other Critical Drivers
Also update your chipset driver (from Intel or AMD's website), network adapter driver, and storage controller driver. All can contribute to CRITICAL_PROCESS_DIED if outdated or corrupted.
Blue Screen Still Persisting? We Fix It Remotely
Our certified technicians diagnose and resolve CRITICAL_PROCESS_DIED blue screens remotely — no need to bring your computer anywhere. Average resolution time: under 90 minutes.
Method 5: Uninstall Recent Windows Updates
Microsoft occasionally ships cumulative updates that introduce driver conflicts or system incompatibilities causing CRITICAL_PROCESS_DIED. If your blue screen appeared within a few days of Windows installing an update, removing that update is a fast and reversible fix.
Open Windows Update History
Go to Settings → Windows Update → Update history → Uninstall updates. This opens the Control Panel view of installed updates.
Identify and Remove the Problematic Update
Sort by Installed On date. Right-click the most recent update (typically a KB number like KB5034123) and click Uninstall. Target the update whose install date correlates with when the crashes began.
Pause Windows Update Temporarily
After uninstalling, pause updates for 1–2 weeks: Settings → Windows Update → Pause updates. Microsoft typically releases a corrective patch within two weeks of a problematic update being widely reported.
Method 6: Run CHKDSK to Repair Disk Errors
Hard drive and SSD errors — including bad sectors and file system corruption — are a significant cause of CRITICAL_PROCESS_DIED. When Windows tries to read a critical system file that sits on a bad sector, the process fails and triggers the blue screen. CHKDSK scans for and repairs these disk-level errors.
Open Administrator Command Prompt
Press Win + S, type cmd, right-click, and select Run as administrator.
Schedule CHKDSK for the System Drive
Type the following command and press Enter:
chkdsk C: /f /r /x
Windows will say it cannot run now and ask to schedule at next restart. Type Y and press Enter, then reboot.
Wait for the Scan to Complete
CHKDSK runs before Windows loads, showing a text screen with progress percentage. On a hard drive, this takes 1–2 hours. On an SSD, usually 10–30 minutes. Do not turn off the computer during this process.
Hard Drive Failing? Back Up Immediately
If CHKDSK reports a large number of bad sectors, or if you hear clicking from your hard drive, your storage device may be physically failing. Back up all important data to an external drive or cloud immediately before continuing. A failing drive can deteriorate rapidly and become unreadable.
Method 7: Disable Fast Startup
Windows 11's Fast Startup feature saves the kernel session state to a hibernation file instead of performing a full shutdown. This can leave driver states in a corrupted or inconsistent state between boots, triggering CRITICAL_PROCESS_DIED. Disabling Fast Startup forces a clean cold boot every time — a simple change that resolves the blue screen for many users.
Open Power Options
Press Win + S and search for Choose a power plan. In the left sidebar, click Choose what the power buttons do.
Disable Fast Startup
Click Change settings that are currently unavailable. Under "Shutdown settings," uncheck Turn on fast startup (recommended). Click Save changes.
Perform a Full Shutdown and Reboot
Use Shut down (not Restart) to get a completely clean boot. Test over the next day of normal use to confirm the CRITICAL_PROCESS_DIED error is gone.
Method 8: Run Windows Memory Diagnostic
Faulty RAM can cause almost any Windows error, including CRITICAL_PROCESS_DIED. When a critical process attempts to read or write to a bad memory address, it crashes instantly. Windows Memory Diagnostic is built into Windows 11 and tests your RAM across multiple passes.
Launch Windows Memory Diagnostic
Press Win + S and search for Windows Memory Diagnostic. Click the result and select Restart now and check for problems. Save any open work first.
Wait for the Test to Complete
The tool runs before Windows loads. It runs two full passes (BASIC test by default). Press F1 to change to the EXTENDED test for more thorough checking — this takes 1–2 hours but catches more errors.
Check the Results
After Windows restarts, check results via: Win + X → Event Viewer → Windows Logs → System, then search for "MemoryDiagnostics-Results." If errors are found, your RAM module is faulty and must be replaced.
For More Thorough RAM Testing: MemTest86
MemTest86 (free at memtest86.com) is more comprehensive than Windows Memory Diagnostic. Boot from a USB drive and let it run overnight. It catches intermittent RAM faults that the Windows tool misses on a quick two-pass run, making it the gold standard for diagnosing hardware-level CRITICAL_PROCESS_DIED causes.
Method 9: Perform a Clean Boot
A clean boot starts Windows with only Microsoft services and drivers — all third-party software (antivirus, backup tools, gaming launchers, overclocking utilities like MSI Afterburner) is disabled. If CRITICAL_PROCESS_DIED stops occurring in a clean boot, a third-party program is the cause. You then re-enable services in groups to isolate the culprit.
Open System Configuration
Press Win + R, type msconfig, and press Enter.
Disable All Non-Microsoft Services
In the Services tab, check Hide all Microsoft services, then click Disable all. Switch to the Startup tab and click Open Task Manager. Disable every startup item, close Task Manager, and click OK in msconfig.
Restart and Test
Restart and use the computer in this clean boot state. If the CRITICAL_PROCESS_DIED blue screen does not appear, re-enable services in halves (enable half, reboot, test) to narrow down which service is responsible. Once found, update, reinstall, or uninstall that software.
Return to Normal Startup When Done
Open msconfig again, go to the General tab, select Normal startup, and click OK. Reboot to restore your normal startup programs and services.
Method 10: Reset or Reinstall Windows 11
If you have worked through all nine methods above and CRITICAL_PROCESS_DIED persists, the Windows installation itself is likely too corrupted to repair with standard tools. A Windows Reset replaces all system files while preserving your personal files. A clean reinstall is the nuclear option but guarantees a fresh, stable system.
Back Up Your Data First
Even with "Keep my files," always back up documents, photos, and anything important to an external drive or cloud storage (OneDrive, Google Drive) before resetting Windows.
Open Windows Reset
Go to Settings → System → Recovery → Reset this PC → Reset PC. Choose Keep my files to preserve personal files, or Remove everything for a completely fresh start.
Choose Cloud Download for Best Results
When asked, select Cloud download rather than Local reinstall. This downloads a fresh, uncorrupted copy of Windows 11 from Microsoft's servers — more reliable if local system files are damaged.
Complete the Reset
The process takes 1–3 hours depending on your internet speed. Windows will restart several times. After completion, reinstall your applications. Your personal files will be in their original locations if you chose "Keep my files."
When to Suspect Hardware
If CRITICAL_PROCESS_DIED persists even after a clean Windows reinstall, the problem is almost certainly hardware. The three most likely culprits:
- RAM: If Windows Memory Diagnostic or MemTest86 found errors — or even if they didn't but crashes continue — try running with one RAM stick at a time (if you have two), or swap into different slots.
- Storage drive: Use CrystalDiskInfo (free) to check the SMART health status of your drive. If it reports "Caution" or "Bad" for reallocated sectors, pending sectors, or uncorrectable sectors, the drive is failing and must be replaced.
- Overheating: Use HWiNFO64 (free) to monitor CPU and GPU temperatures under load. If your CPU exceeds 95°C or GPU exceeds 90°C, clean the dust from your cooling system, reapply thermal paste, and ensure adequate airflow.
Preventing CRITICAL_PROCESS_DIED in the Future
Once you have resolved the immediate CRITICAL_PROCESS_DIED error, these habits will prevent it from returning:
- Keep Windows updated — but monitor tech forums before installing major updates on day one
- Update drivers through manufacturer websites (NVIDIA, AMD, Intel) rather than relying solely on Windows Update, which sometimes installs older driver versions
- Enable automatic backups with Windows Backup or File History so you can roll back if a bad update causes issues
- Maintain your hardware: clean dust from vents every 6–12 months, ensure good airflow, and monitor drive health with CrystalDiskInfo
- Avoid aggressive overclocking unless you have thoroughly stability-tested your CPU and RAM settings with Prime95 and MemTest86
Still Getting CRITICAL_PROCESS_DIED? Get Expert Help Now
If you have tried these 10 fixes and the blue screen persists, our certified Windows technicians can diagnose your specific system remotely. Most CRITICAL_PROCESS_DIED cases are resolved in a single session — no appointment needed.
Frequently Asked Questions
CRITICAL_PROCESS_DIED is triggered when a critical Windows system process exits unexpectedly or becomes corrupted. The most common causes are: corrupted or incompatible device drivers (especially GPU drivers after an update), damaged Windows system files, failing RAM or hard drive hardware, malware that interferes with core processes, or a bad Windows update that conflicts with existing software. Outdated GPU drivers are the leading cause in over 60% of cases reported in 2025-2026.
Methods 1 through 9 in this guide (Safe Mode, SFC, DISM, driver updates, uninstalling updates, CHKDSK, disabling fast startup, Memory Diagnostic, clean boot) do not delete any personal files. Only Method 10 — Windows Reset or Reinstall — has the potential to affect files, but the "Keep my files" option preserves your documents, photos, and desktop files. Always back up to an external drive or cloud before attempting any system repair.
If Windows 11 crashes immediately at boot, force it into the Windows Recovery Environment by pressing and holding the power button to shut down, then powering on again — repeat 3 times. Windows will automatically launch the recovery menu. Choose: Troubleshoot → Advanced options → Startup Settings → Restart → press F4 for Safe Mode. Once in Safe Mode, follow Methods 2 through 10 in this guide.
Yes — a bad or incompatible GPU driver update is one of the most frequent triggers of CRITICAL_PROCESS_DIED on Windows 11. NVIDIA and AMD periodically release driver versions with known issues. If your blue screen started immediately after a driver update, boot into Safe Mode, open Device Manager, find your display adapter, right-click and choose "Roll Back Driver." Use Display Driver Uninstaller (DDU) in Safe Mode for a completely clean removal before reinstalling.
The SFC scan typically takes between 15 and 45 minutes depending on your hard drive speed. On an SSD it usually completes in under 20 minutes. Do not close the Command Prompt window or interrupt the scan. If SFC reports "found corrupt files but was unable to fix some of them," run the DISM command next (Method 3), which repairs the Windows image that SFC uses as its reference.