Windows 0x0000005A CRITICAL_SERVICE_FAILED: Causes and Fixes

Quick Answer

The Windows stop code 0x0000005A CRITICAL_SERVICE_FAILED indicates that Windows encountered a critical service failure and stopped operating. This is a relatively uncommon Blue Screen of Death (BSOD) error that can prevent Windows from starting normally.

Microsoft documents this bug check as CRITICAL_SERVICE_FAILED with the value 0x0000005A. The exact cause must be identified from diagnostic information; it should not automatically be attributed to a specific driver, update, or hardware component.

Start by disconnecting unnecessary peripherals and attempting to enter the Windows Recovery Environment (WinRE). Run Startup Repair first. If the problem began after a Windows update, driver installation, or system configuration change, consider uninstalling the relevant update or using System Restore. If these options fail, investigate offline system files and drivers before considering a Windows reset or reinstallation.

What Does 0x0000005A CRITICAL_SERVICE_FAILED Mean?

The stop code 0x0000005A is a Windows bug check associated with a critical service failure. A bug check is a protective stop that Windows uses when it encounters a condition that prevents it from continuing safely.

Windows relies on essential services and system components during startup and normal operation. If a critical component fails in a way that prevents Windows from continuing, the operating system may display this stop code.

Microsoft's technical reference identifies this bug check as uncommon. The stop code alone does not establish which service or component failed. Additional diagnostic information, such as the bug-check parameters, crash dump, recent system changes, and recovery logs, may be needed to determine the cause.

Symptoms of the CRITICAL_SERVICE_FAILED Error

A computer affected by this error may exhibit one or more of the following symptoms:

• A blue screen displays the stop code CRITICAL_SERVICE_FAILED or 0x0000005A.
• Windows restarts automatically after displaying the error.
• The computer repeatedly crashes during startup.
• Windows enters Automatic Repair or the Windows Recovery Environment.
• The system fails to reach the sign-in screen.
• The error appears after a recent system change, although this timing alone does not prove the cause.

The exact symptoms depend on when the failure occurs and which component is affected.

Common Causes and Diagnostic Clues

There is no single cause that can be inferred from the stop code alone. Investigate the following possibilities when the available evidence supports them.

These are investigation paths, not confirmed causes of every 0x0000005A failure. Avoid replacing hardware or deleting drivers solely because this stop code appeared.

Before You Begin

• Disconnect nonessential USB devices, external drives, docks, and other peripherals. Keep the keyboard, mouse, display, and required input devices connected.
• Record the exact stop code and any additional error details displayed on the blue screen.
• Think about recent changes, including Windows updates, driver installations, system utilities, or firmware changes.
• Locate your BitLocker recovery key if device encryption is enabled. WinRE may require it to access certain recovery tools or protected drives.
• If important data is not backed up and the storage device may be failing, prioritize data protection before running intensive repair operations.

Step 1: Enter the Windows Recovery Environment

If Windows cannot start normally, use WinRE to access the built-in recovery tools.

Method A: Use Automatic Repair

1. Turn on the computer and wait for the Windows logo or manufacturer's logo to appear.
2. If Windows fails to start, interrupt startup by holding the power button until the computer shuts down.
3. Repeat the interrupted startup once more, then turn on the computer again. Windows may enter Automatic Repair.
4. When the recovery screen appears, select Advanced options.
5. Select Troubleshoot to access the recovery options.

Interrupting startup repeatedly should be used only when necessary to enter recovery. Do not interrupt a Windows update, firmware update, disk operation, or recovery process that is actively running.

Method B: Use Windows Installation Media

If WinRE does not appear automatically, use official Windows installation media created on a working computer.

1. Obtain appropriate Windows installation media from Microsoft.
2. Boot the affected computer from the USB drive.
3. On the Windows Setup screen, select the language and keyboard preferences if prompted.
4. Select Repair your computer rather than starting a new installation.
5. Open Troubleshoot and proceed to the available recovery tools.

Booting from USB may require selecting the correct boot device in the computer's firmware settings. If device encryption is enabled, have the BitLocker recovery key available.

Step 2: Run Startup Repair

Startup Repair is the recommended first recovery option when Windows cannot boot normally. It diagnoses and attempts to repair certain problems that prevent startup.

1. Open the Windows Recovery Environment.
2. Select Troubleshoot > Advanced options > Startup Repair.
3. Select the Windows installation if prompted.
4. Enter the requested credentials or BitLocker recovery information if required.
5. Allow the repair process to complete.
6. Restart the computer and check whether Windows reaches the sign-in screen.

Expected result: Windows starts normally without repeating the 0x0000005A stop error.

If it fails: Record any message displayed by Startup Repair. Continue to the next step rather than repeatedly running the same tool without investigating further.

Startup Repair cannot resolve every critical service failure. A failed repair does not necessarily mean that Windows must be reinstalled.

Step 3: Uninstall a Recently Installed Windows Update

If the error began immediately after a Windows update, removing the relevant update may help restore startup. Use this option only when the timing or available evidence makes an update-related problem plausible.

1. Boot into WinRE.
2. Select Troubleshoot > Advanced options > Uninstall Updates.
3. Choose the available option for uninstalling the latest quality update or the latest feature update.
4. Follow the on-screen instructions.
5. Restart Windows and check whether the error returns.

Quality updates and feature updates are different types of updates. Select the option that matches the recent change and is available on the affected system.

Verification: If Windows starts successfully after the update is removed, review the update history and system stability before attempting the update again.

Security consideration: Removing a security update can expose the computer to vulnerabilities. Once the system is stable, investigate the underlying problem and install an appropriate supported update when possible.

Step 4: Use System Restore

System Restore can return system files, settings, drivers, and installed software configuration to an earlier restore point. It is useful when the problem started after a system change and a suitable restore point exists.

1. Open WinRE.
2. Select Troubleshoot > Advanced options > System Restore.
3. Select the Windows installation and provide credentials if requested.
4. Choose a restore point dated before the error first appeared.
5. Review the affected programs or changes, if the option is available.
6. Confirm the restoration and allow it to finish without interrupting power.
7. Restart the computer and test Windows startup.

System Restore is designed to roll back system configuration without affecting personal files. However, it can remove or revert applications, drivers, and updates installed after the selected restore point. Back up important data whenever possible.

If System Restore is unavailable or no suitable restore point exists, continue with the next diagnostic step.

Step 5: Investigate Recently Changed Drivers

A driver or system-component change may be relevant if the crash started after a specific installation. Do not assume that a driver is responsible without supporting evidence.

• Identify any driver or system utility installed immediately before the first crash.
• If Windows can start in Safe Mode, review Device Manager and the relevant device manufacturer's documentation.
• Use the supported rollback option for the affected driver when available.
• If Windows cannot start, prefer System Restore or another appropriate recovery method over manually deleting driver files.
• After recovery, obtain compatible drivers from Windows Update or the computer or component manufacturer's official website.

Safe Mode is available through WinRE > Troubleshoot > Advanced options > Startup Settings > Restart, followed by the appropriate Safe Mode option. Availability and displayed choices can vary by system configuration.

Verification: Restart Windows normally after the suspected change has been reversed. If the BSOD persists, investigate other causes instead of repeatedly removing unrelated drivers.

Step 6: Check System Files from Recovery

If the previous recovery options fail, an experienced technician can investigate Windows system files from WinRE. Offline repairs require the correct Windows volume and a valid source of repair files when required.

Identify the Windows Volume

1. Open WinRE > Troubleshoot > Advanced options > Command Prompt.
2. Enter the following command to list available volumes.

diskpart
list volume
exit

These commands run in the Windows recovery Command Prompt. They list volumes and then exit DiskPart; they do not intentionally change partition configuration.

Identify the volume containing the Windows installation. You can check likely drive letters with the following command, replacing D: with a candidate volume:

dir D:\Windows

A successful directory listing can help confirm the location of the Windows directory. If the directory is not found, check another candidate volume rather than assuming that Windows is installed on drive C:.

Run Offline System File Checker

System File Checker (SFC) can scan and attempt to repair protected Windows system files. From the recovery Command Prompt, use the following command only after confirming the Windows volume and the appropriate system boot volume.

sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Replace the example paths with the correct paths for the affected installation. The /offwindir parameter identifies the offline Windows directory, while /offbootdir identifies the offline boot directory. Depending on the system's partition layout, the boot directory may be on a different volume. Do not assume that the example paths apply to every computer.

If you cannot confidently identify the required directories, stop and obtain assistance from a technician familiar with offline Windows recovery. A repair command with incorrect paths may fail to provide useful results.

Verification: Review the SFC result, close Command Prompt, and restart the computer. If SFC reports that it could not repair some files, do not assume that the system is fixed; investigate the reported issue and the availability of a valid repair source.

Step 7: Review Crash Dumps and Recovery Logs

If the computer still crashes, additional diagnostic evidence can help narrow the problem.

• Record the exact stop code and any displayed parameters.
• After Windows becomes accessible, check whether a crash dump was generated in the standard Windows dump locations.
• Use an appropriate debugger and Microsoft's bug-check documentation to interpret available dump data.
• Review relevant system and recovery logs for errors that occurred around the time of the crash.
• For managed systems, collect diagnostic information before making further changes and involve the IT administrator when appropriate.

Microsoft's bug-check reference recommends using the debugger's !analyze extension to help analyze this stop code. Interpreting a crash dump may require technical experience and does not always identify a definitive root cause.

Step 8: Check for Underlying Hardware Problems

Hardware troubleshooting is appropriate when additional evidence suggests a physical problem, such as repeated storage errors, manufacturer diagnostic failures, or crashes that persist independently of a particular software change.

• Run the computer manufacturer's built-in hardware diagnostics where available.
• Check storage health using supported diagnostic tools from the computer or drive manufacturer.
• Review firmware or hardware changes that immediately preceded the failure.
• If memory or another component is suspected, use a suitable manufacturer-supported diagnostic procedure.

Do not update BIOS or UEFI firmware, reset firmware settings, or disassemble a computer solely because the 0x0000005A error appeared. Such actions introduce additional risks and should be considered only when justified by diagnostic evidence and the manufacturer's guidance.

If the storage device is making unusual noises, disconnecting unexpectedly, or reporting serious health problems, minimize unnecessary use and prioritize data recovery.

Step 9: Consider Resetting or Reinstalling Windows

Resetting or reinstalling Windows should be considered only after less disruptive recovery methods have failed or are unsuitable.

• Reset this PC: Available through WinRE on supported Windows installations. Depending on the selected option, personal files may be retained, but applications and settings are removed. Keeping files is not a substitute for a backup.
• Reinstall using recovery media: May be appropriate when Windows remains unusable and other recovery methods fail.
• Clean installation: Can remove existing files, applications, and configuration, depending on the installation choices and disk operations performed.

For a work-managed computer, contact the IT administrator before resetting or reinstalling Windows because organization-specific encryption, management, and security settings may need to be restored.

How to Verify That the Error Is Resolved

After applying a recovery method, use the following checks to confirm that the system is stable.

1. Restart the computer normally rather than booting into recovery media.
2. Confirm that Windows reaches the sign-in screen and the desktop.
3. Restart the computer again to check whether the same stop code returns.
4. Review Windows Update and device status after the system becomes accessible.
5. Check for new crashes or relevant system errors if the problem recurs.
6. Back up important data after successful recovery.

If the computer boots once but crashes again, treat the issue as unresolved. Record the circumstances of the second failure and continue investigating rather than assuming that a temporary successful boot proves the underlying cause has been fixed.

Recovery and Rollback Considerations

• Startup Repair: Attempts to fix startup problems automatically. Review any failure details if it cannot complete the repair.
• Uninstall Updates: Reverses a selected update, which may reduce security protection until an appropriate replacement is installed.
• System Restore: Reverts system configuration to a previous state and may remove recent applications, drivers, or updates.
• Offline system repair: Can modify Windows system files. Confirm paths and review the command output before restarting.
• Reset or reinstall: May remove applications, settings, or personal files. Recovery may not be straightforward without a suitable backup.

If a recovery operation fails, avoid repeatedly applying increasingly destructive fixes without gathering diagnostic evidence. Preserve important files and consult a qualified technician if the Windows installation or storage device may be damaged.

Frequently Asked Questions

What is Windows stop code 0x0000005A?

It is the CRITICAL_SERVICE_FAILED bug check. Microsoft identifies it as an uncommon Windows stop error. The exact failed component must be investigated using available diagnostic information.

Does CRITICAL_SERVICE_FAILED always mean a driver is faulty?

No. A driver problem is one possibility, but the stop code alone does not establish the cause. System components, recent changes, and other underlying problems may need investigation.

Can Startup Repair fix error 0x0000005A?

Startup Repair may resolve related startup problems, but it does not fix every critical service failure. If it fails, consider the timing of the crash and use an appropriate recovery option.

Will System Restore delete my personal files?

System Restore is designed to roll back system files and settings without affecting personal files. However, it can revert applications, drivers, and updates installed after the selected restore point. Keep a separate backup whenever possible.

Can a Windows update cause this BSOD?

An update may be relevant if the crash began immediately afterward, but timing alone does not prove causation. If the evidence supports an update-related problem, consider uninstalling the relevant update through WinRE.

What if Windows cannot enter the Recovery Environment?

Try booting from appropriate Windows installation media and select Repair your computer. If recovery remains inaccessible, obtain technical assistance before attempting disk or partition modifications.

Is it safe to run SFC from WinRE?

Offline SFC is a supported system-file troubleshooting technique when used with the correct paths. WinRE drive letters can differ from normal Windows drive letters, so confirm the Windows and boot directories before running the command.

Should I reset my PC immediately?

No. Try appropriate, less disruptive recovery options first. Resetting or reinstalling Windows can remove applications, settings, or data, depending on the chosen procedure.

When should I contact a technician?

Seek technical assistance if recovery tools repeatedly fail, the storage device may be failing, BitLocker access is unavailable, offline repair paths cannot be identified confidently, or the system continues to crash after reasonable recovery attempts.

Conclusion

The 0x0000005A CRITICAL_SERVICE_FAILED BSOD indicates a critical service failure, but the stop code alone does not identify the precise cause. Begin with WinRE and Startup Repair, then consider update removal, System Restore, driver investigation, and carefully targeted offline diagnostics as appropriate.

Verify each recovery attempt, protect important data, and avoid destructive repair methods until less disruptive options have been considered. If the error persists, use crash-dump and system diagnostic evidence to guide further troubleshooting.

Sources

• Microsoft Learn: Bug Check 0x5A — CRITICAL_SERVICE_FAILED
• Microsoft Support: Windows Recovery Environment
• Microsoft Support: Startup Repair
• Microsoft Support: How to Uninstall a Windows Update
• Microsoft Support: Recovery Options in Windows
• Microsoft Support: Reset Your PC