CRITICAL_SERVICE_FAILED Blue Screen — Every Fix Explained

CRITICAL_SERVICE_FAILED (stop code 0x0000005A) is a Windows blue screen error that occurs when a critical operating system service fails in an unrecoverable way during startup or operation. It typically forces an immediate restart and can become a boot loop. The underlying cause is almost always a corrupted driver, a damaged system file, or a conflicting third-party service.

Part 1. What Causes CRITICAL_SERVICE_FAILED?

Stop code 0x0000005A signals that Windows could not recover from a critical service failure. Several categories of causes are responsible:

• Corrupted or incompatible driver — A newly installed or recently updated driver (graphics, network, storage, antivirus kernel drivers) fails during initialization.
• Damaged system files — Disk errors, sudden shutdowns during updates, or malware can corrupt core Windows service binaries.
• Third-party antivirus or security software — Deep-kernel security tools sometimes conflict with Windows services, especially after a major update.
• Failed Windows Update — An incomplete cumulative update can leave service binaries in a half-written state.
• Faulty RAM — Memory errors during service loading produce unpredictable stop codes including this one.
• Corrupted Windows registry — Service registration entries that point to missing or damaged files cause service initialization failures.

💡 Tip: Check the minidump file in C:\Windows\Minidump\ for the exact driver name. Open it with WinDbg Preview (free from the Microsoft Store) and look for the "Caused by Driver" line — this pinpoints the exact culprit.

Part 2. Boot Into Safe Mode

Most CRITICAL_SERVICE_FAILED fixes require Safe Mode because normal boot is blocked. Here are the two main methods:

Method A — Force WinRE via interrupted startups:

1. Power on the PC. As soon as the Windows logo appears, hold the power button to force shutdown.
2. Repeat this two more times. On the third attempt, Windows automatically opens the Recovery Environment.
3. Go to Troubleshoot → Advanced options → Startup Settings → Restart.
4. Press 4 or F4 to boot into Safe Mode (or 5/F5 for Safe Mode with Networking).

Method B — From an existing Windows session:

1. Press Win + R → type msconfig → Boot tab.
2. Check Safe boot → Minimal, click OK, restart.
3. After fixing the issue, return to msconfig and uncheck Safe boot.

⚠️ Important: If you cannot access Safe Mode through the above steps, boot from a Windows installation USB. Download the Windows Media Creation Tool on another PC, create bootable media, and access Troubleshoot → Advanced options from there.

Part 3. Fix 1 — Uninstall Recently Installed Drivers

If the BSOD appeared after installing a driver, rolling back or removing it in Safe Mode often resolves the issue immediately:

1. In Safe Mode, press Win + X → Device Manager.
2. Look for any device with a yellow warning icon — this often indicates the problem driver.
3. Right-click the device → Properties → Driver tab → Roll Back Driver.
4. If rollback is unavailable, right-click → Uninstall device → check Delete the driver software.
5. Restart normally.

If you identified the driver name from the minidump file, target that specific device in Device Manager.

🗣️ r/techsupport user: "CRITICAL_SERVICE_FAILED appeared right after installing my new GPU driver. Booted into Safe Mode, uninstalled the driver, reinstalled a stable older version, and the BSOD was gone."

Part 4. Fix 2 — Remove Conflicting Security Software

Deep-kernel security tools (antivirus, VPN clients, DRM software) are a well-known source of CRITICAL_SERVICE_FAILED. In Safe Mode, these tools typically do not load, giving you a window to remove them:

1. In Safe Mode, go to Control Panel → Programs and Features.
2. Uninstall any recently installed antivirus, VPN, firewall, or security suite.
3. Restart normally and test.
4. If the BSOD clears, reinstall the security software — preferably the latest version, which may have a fix for the incompatibility.

Known problematic software categories include endpoint protection suites, kernel-level anti-cheat systems (common in games), and hardware monitoring tools with kernel drivers.

💡 Tip: If you cannot uninstall antivirus software normally (some protect themselves from removal), use the vendor's dedicated removal tool. Most major antivirus companies offer one. For example, Symantec's Norton Removal Tool, ESET's Uninstaller Tool, and McAfee's Consumer Products Removal Tool are all available from their respective support pages.

Part 5. Fix 3 — Repair System Files With SFC and DISM

Corrupted Windows service binaries are a primary cause of this BSOD. Run these built-in repair tools in order:

Step 1 — DISM image repair:

1. Open Command Prompt as Administrator (search "cmd" → right-click → Run as administrator).
2. Run: DISM /Online /Cleanup-Image /RestoreHealth
3. Wait for completion (may take 15–30 minutes).

Step 2 — System File Checker:

1. In the same Command Prompt, run: sfc /scannow
2. SFC scans all protected system files and replaces corrupted ones from the Windows cache.
3. Restart after completion.

🗣️ r/WindowsHelp user: "Got CRITICAL_SERVICE_FAILED after a Windows Update. Ran DISM first, then SFC — found 3 corrupted files and replaced them. PC has been stable since."

Part 6. Fix 4 — Run Windows Update Troubleshooter and Repair

If a failed Windows Update triggered the error:

1. Go to Settings → System → Troubleshoot → Other troubleshooters.
2. Click Run next to Windows Update.
3. Follow the prompts.

For deeper update repair, reset the Windows Update components via Command Prompt (as Administrator):

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

This forces Windows Update to rebuild its database on the next run and may clear corrupted update files that caused the service failure.

💡 Tip: After resetting Windows Update components, run Windows Update again from Settings → Windows Update → Check for updates. This ensures any partially applied patches are cleanly reapplied.

Part 7. Fix 5 — Use System Restore

If the BSOD started after a specific date (such as after installing software or an update), System Restore can roll Windows back to a point before the issue:

1. From WinRE Advanced options → System Restore.
2. Choose a restore point dated before the BSOD started.
3. Follow the prompts. System Restore does not affect personal files, only system settings and installed programs.
4. Restart and test.

Part 8. Recover Lost Files With Ritridata

A boot loop caused by CRITICAL_SERVICE_FAILED can sometimes corrupt file system metadata, making files appear inaccessible or deleted. Once you restore Windows stability, Ritridata can scan your drive to recover any lost files from Windows HDDs, SSDs, and USB drives.

Step 1 — Select the drive/location

Step 2 — Run a safe scan

Step 3 — Preview and recover to another drive

FAQ

Q: What is stop code 0x0000005A? 0x0000005A is the hexadecimal code for CRITICAL_SERVICE_FAILED. It indicates that a critical Windows service or driver failed during initialization in a way Windows could not handle or recover from internally.

Q: Is CRITICAL_SERVICE_FAILED caused by a virus? It can be, but it is less common. Malware that infects system service files or driver components can trigger this BSOD. If standard fixes do not resolve it, running an offline antivirus scan from bootable media is a reasonable next step.

Q: How do I find which driver caused CRITICAL_SERVICE_FAILED? Open C:\Windows\Minidump\ after a crash and load the most recent .dmp file into WinDbg Preview (free from the Microsoft Store). The analysis output typically names the driver module responsible.

Q: Will System Restore delete my files? System Restore reverts system settings, drivers, and installed applications to an earlier state. It does not delete personal files stored in Documents, Desktop, Downloads, or similar locations.

Q: Can RAM cause CRITICAL_SERVICE_FAILED? Yes. Memory errors during service loading can produce unpredictable stop codes including this one. If other fixes do not work, test RAM with MemTest86 (free bootable tool) or Windows Memory Diagnostic.

Q: Does this error affect Windows 11 more than Windows 10? Both versions are affected equally. Windows 11's stricter driver signing requirements may actually reduce occurrences from unsigned drivers, but legitimate signed drivers and antivirus tools can still cause this BSOD on either platform.

Q: What if none of the fixes work? If SFC, DISM, driver rollback, system restore, and security software removal all fail to resolve the BSOD, a Windows Reset (Settings → System → Recovery → Reset this PC) may be necessary. Choose "Keep my files" when available to minimize data loss.

References

• Microsoft: Bug Check 0x5A — CRITICAL_SERVICE_FAILED
• Microsoft: Use the System File Checker tool
• Microsoft: DISM Overview
• WinDbg Preview — Microsoft Store
• r/techsupport — BSOD Help Thread