Repeated critical-process crashes can damage unsaved data
Back up accessible files before deep repair. If the SSD disappears, becomes extremely slow or reports errors, prioritise data recovery and hardware diagnostics. Do not disable security permanently or replace Windows system files from unofficial downloads.
Confirm the crash pattern
| When it crashes | Investigate first |
|---|---|
| Immediately after an update | Update removal, System Restore, component repair. |
| After installing security or disk software | Filter driver or service conflict. |
| Only at startup | Boot driver, storage, system files. |
| During file activity | SSD, file system, storage driver, RAM. |
| With several different codes | RAM, storage, tuning or power instability. |
1. Remove recent external and internal changes
Disconnect non-essential USB devices, docks and external storage. If the first crash followed a RAM, SSD or expansion-card change, return to the previous known-good configuration or reseat the part using the manufacturer’s instructions.
2. Use recovery options when Windows will not stay open
Choose Troubleshoot → Advanced options in Windows Recovery Environment. Try Startup Repair once. If the crash followed an update, select Uninstall Updates → Uninstall latest quality update. Use System Restore when a suitable point exists.
Repeatedly running Startup Repair after the same failure adds no new diagnosis.
3. Test Safe Mode
Open Startup Settings → Restart → Safe Mode. Stability here points toward a non-essential driver, service or application. Remove the recent security tool, disk utility or driver most closely tied to the first crash, then restart normally.
4. Repair the component store and protected files
From an elevated Terminal in Windows or Safe Mode run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Record the final result. Do not use online commands against an offline recovery installation or assume its drive is always C:.
5. Roll back the driver that changed
Prioritise storage, chipset, graphics and security filter drivers changed near the first failure. Roll back a specific recent driver or install the PC manufacturer’s stable package. A named driver in a minidump is a lead, not automatic proof.
6. Check storage and free space
Ensure practical free space on the Windows volume and run chkdsk C: /scan when Windows is stable. Use the SSD manufacturer’s diagnostic. Repeated file corruption, I/O errors, freezes or a missing drive require immediate backup and hardware attention.
7. Test memory and default firmware settings
Disable CPU, GPU and RAM overclocking or undervolting. Run Windows Memory Diagnostic followed by an extended manufacturer test if crashes remain. Changing stop codes alongside CRITICAL_PROCESS_DIED often increases suspicion of memory corruption.
8. Check security software and malware safely
Run Microsoft Defender Offline or the organisation’s approved scanner. If a third-party antivirus update directly preceded the crash, remove it using its official process from Safe Mode and retest. Do not leave the PC without active protection after diagnosis.
9. Repair-install or reset only after hardware checks
An in-place repair installation can replace Windows components while preserving more data when the desktop remains usable. Reset and clean installation are later options after backup. A reinstall that crashes or loses the drive points away from ordinary Windows corruption.
Avoid these common mistakes
- Do not download replacement system files from unofficial sites.
- Do not run offline commands against an unconfirmed drive letter.
- Do not ignore repeated storage or memory errors.
- Do not reset before backing up and checking hardware.
Frequently asked questions
What causes CRITICAL_PROCESS_DIED in Windows 11?
Frequent causes include damaged system files, interrupted updates, storage corruption, faulty drivers, security software conflicts, malware and unstable RAM or storage.
Can SFC fix CRITICAL_PROCESS_DIED?
SFC can replace protected Windows files when corruption is the cause. DISM should repair the component store first when Windows can run.
Why does it happen during startup?
A boot-critical driver, update, storage error or damaged Windows component may fail as the operating system loads.
Technical steps align with Microsoft guidance for stop errors, Windows Recovery Environment, update removal, System Restore, DISM, System File Checker and storage diagnostics.
Official references
For platform-specific behavior and recovery options, compare this guide with the current documentation from the relevant official source.