Ad Space — Top Banner

0x0000005A

Microsoft Windows

Severity: Critical

What Does This Error Mean?

The 0x0000005A blue screen means a critical Windows service or driver failed to start during boot. Certain Windows services are so essential that if they cannot start, the entire system must shut down. Think of it like a car engine — if the oil pump fails, the engine stops to prevent total destruction. This error is most often caused by a failed Windows Update, a missing or corrupted driver, or a damaged system file.

Affected Models

  • Windows 10
  • Windows 11
  • Windows Server 2016
  • Windows Server 2019

Common Causes

  • A Windows Update installed a driver or component that is incompatible with existing hardware or software
  • A critical system driver file (such as a storage or chipset driver) is missing or corrupted
  • Third-party security software (antivirus, endpoint protection) replaced or blocked a core Windows service
  • A recent hardware change left behind an incompatible or partially installed driver
  • Windows system files were corrupted by an unexpected shutdown, power failure, or disk error

How to Fix It

  1. Boot into Windows Recovery Environment. Restart your PC and interrupt the boot three times to trigger Automatic Repair, then choose Advanced options > Startup Repair.

    Startup Repair is designed to fix exactly this type of problem. Let it run to completion — it may restart your PC multiple times.

  2. From the Recovery Command Prompt (Advanced options > Command Prompt), run: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows to repair corrupted system files.

    The /offbootdir and /offwindir flags are needed when running SFC before Windows has fully started. Replace C: with your Windows drive letter if it is different.

  3. Run DISM to repair the Windows component store: DISM /Image:C:\ /Cleanup-Image /RestoreHealth

    DISM replaces damaged Windows components from Microsoft's servers. If your PC cannot reach the internet from the recovery environment, you will need a Windows USB drive as the source.

  4. Uninstall the most recent Windows Update using the Recovery Command Prompt. Type: dism /image:C:\ /get-packages to list updates, then: dism /image:C:\ /remove-package /packagename:[name] to remove the newest one.

    This step is particularly useful if the crashes started right after Windows Update ran. Removing the problematic update lets Windows boot normally again.

  5. Boot into Safe Mode (Advanced options > Startup Settings > Enable Safe Mode) and uninstall any recently added third-party antivirus or security software.

    Some security products install drivers that conflict with Windows services. Removing them in Safe Mode — where their own drivers are not loaded — is the safest approach.

When to Call a Professional

If Startup Repair, SFC, and DISM all fail to bring Windows back, a technician can perform an in-place upgrade install. This method replaces all Windows system files while keeping your personal data and applications intact. It is the most reliable recovery option short of a full reinstall.

Frequently Asked Questions

Which services does Windows consider 'critical'?

Critical services include things like the kernel security system, the Session Manager (smss.exe), the Windows Subsystem (winsrv), and core driver frameworks. If any of these fail to initialize, Windows has no safe way to continue running. The system crashes immediately rather than risk running in an unstable or insecure state.

Can I recover my files if Windows will not boot at all?

Yes. Boot from a Windows USB drive and choose Repair your computer > Troubleshoot > Advanced options > Command Prompt. From there you can copy files from your Windows drive to a USB stick. Alternatively, remove the hard drive and connect it to another PC as a secondary drive to access your data directly.

How do I stop Windows Update from causing this problem again?

You can delay Windows Updates by going to Settings > Windows Update > Advanced options > Pause updates. This gives Microsoft time to catch and fix any bad updates before they reach your PC. Most update-related BSODs are patched by Microsoft within a few days of reports coming in.