Skip to content
PCDecoder
0x0000005ACRITICAL_SERVICE_FAILEDStop codeWidely reported

CRITICAL_SERVICE_FAILED (0x5A): what it means and how to fix it

Updated Oct 18, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

CRITICAL_SERVICE_FAILED (0x0000005A) is a rare Windows stop code indicating that a vital system service or driver failed during startup. It typically happens after a corrupted update or boot driver issue. The first step to resolve it is booting into the Windows Recovery Environment to uninstall recent updates or run Startup Repair.

What it means

Windows relies on a collection of core system services and device drivers to start up properly. When you power on your computer, the Windows boot loader loads these critical components into memory before handing control over to the operating system desktop.

What the stop code indicates

Bug Check 0x5A, named CRITICAL_SERVICE_FAILED, has a numeric value of 0x0000005A. It appears very infrequently compared to other blue screen crashes. The error triggers when Windows attempts to initialize an essential system service or driver required for the operating system to function, but that component fails to start, crashes, or returns an unrecoverable status.

Because the failed service is marked as critical, Windows cannot bypass it or safely continue loading. Halting the system with this blue screen protects data integrity and prevents corrupt instructions from executing at the system core.

Why it happens

Users commonly encounter this crash loop right after applying cumulative Windows updates or system patches. If an update process is interrupted, or if an essential driver fails to register correctly during a reboot, the affected service cannot launch.

Hardware driver conflicts—especially those involving disk controllers, virtual machine extensions, or server components—can also trigger 0x5A. When the driver required to access system storage or hardware controls cannot initialize, the entire boot sequence stalls.

Common causes

  • A damaged or incomplete Windows update that corrupted core system files.
  • A failure in a critical boot-start driver or storage controller driver.
  • System file corruption affecting fundamental Windows services.
  • Driver compatibility conflicts following an operating system patch.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Uninstall the most recent Windows update

    Use this when the 0x5A error appears immediately after your computer reboots from a system update.

    1. Force your computer to shut down three consecutive times during boot to trigger the Windows Recovery Environment.
    2. Select Troubleshoot on the Choose an option screen.
    3. Click Advanced options.
    4. Select Uninstall Updates.
    5. Choose Uninstall latest quality update (or Uninstall latest feature update if you recently upgraded versions), and follow the on-screen prompts.
    6. Restart your PC normally once the process completes.
    Did this fix it?

  2. Run Startup Repair

    Use this when Windows cannot reach the login screen and you need the system to automatically repair boot-critical files.

    1. Boot into the Windows Recovery Environment by interrupting the boot process twice or using Windows installation media.
    2. Select Troubleshoot, then click Advanced options.
    3. Click Startup Repair.
    4. Select your user account and enter your password if prompted.
    5. Allow the tool to scan and repair boot files, then restart your computer.
    Did this fix it?

  3. Perform a System Restore

    Use this if you have restore points saved and need to roll back driver or service changes without losing personal files.

    1. Enter the Windows Recovery Environment.
    2. Navigate to Troubleshoot > Advanced options.
    3. Select System Restore.
    4. Choose a restore point dated before the CRITICAL_SERVICE_FAILED error began.
    5. Confirm the selection and allow the restoration process to finish.
    Did this fix it?

  4. Repair system files with SFC and DISM in Command Prompt

    Use this if your system files or core services are damaged and preventing Windows from starting.

    1. Open Advanced options in the Windows Recovery Environment.
    2. Select Command Prompt.
    3. Type sfc /scannow and press Enter to scan and repair offline Windows system files.
    4. Type dism /image:C:\ /cleanup-image /restorehealth (replace C: with your system drive letter if different) and press Enter.
    5. Close the Command Prompt window once the process completes and select Continue to boot Windows.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 15, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

Can I boot into Safe Mode with error 0x0000005A?

Sometimes Safe Mode works if the failing service is non-essential in minimal boot environments, but because 0x5A indicates a critical core service, Safe Mode may also fail. If Safe Mode does not load, use the Windows Recovery Environment instead.

Does CRITICAL_SERVICE_FAILED mean my hard drive is broken?

No, it rarely indicates a physical drive failure. It almost always points to software or driver corruption where an essential startup service cannot launch.

How do developers determine the exact cause of 0x5A?

Developers and technicians use the !analyze debug extension in the Windows debugger to inspect the memory dump file generated during the crash to identify the exact service that failed.

More stop codes decoded