0x0000005A: What It Means and How to Fix It in Windows
Stop code 0x0000005A means CRITICAL_SERVICE_FAILED. Microsoft’s debugger documentation lists the bug check value as 0x0000005A, says it appears very infrequently, and notes that !analyze can help determine the root cause. Guessing at the cause can waste time, so start with the last system change and work from there. neosmart.net
This guide is part of our Windows BSOD stop codes: full list and fixes series.
What 0x0000005A means on Windows
It is a blue-screen stop error with the alias CRITICAL_SERVICE_FAILED. Microsoft’s debugger docs list the bug check value as 0x0000005A. (source) ritridata.com
Because this bug check appears very infrequently, the exact sequence of events around the crash matters more than the screen color or any single symptom. Check whether the problem began after a driver change, a Windows update, or new hardware was installed.
What the screen often tells you
Check whether Windows reaches the logo, the spinning dots, or the sign-in screen before the crash. A failure before sign-in often points to a recent driver or device change, or to a startup component that Windows needs very early.
If the machine restarts too fast to read the stop screen, take a photo. The exact timing matters more than the color of the screen.
According to Bug Check 0x5A CRITICAL_SERVICE_FAILED – Windows drivers — The bug check value for CRITICAL_SERVICE_FAILED is 0x0000005A. (source)
What is most likely causing 0x0000005A?
The provided Microsoft documentation confirms the bug check value and that !analyze can help determine the root cause, but it does not rank one cause above the others. In practice, the next step is to look for the most recent change that lines up with the first crash.
Recent driver changes, Windows updates, new hardware, or damaged startup files are all possibilities to check. The safest approach is to test one branch at a time instead of assuming the cause up front.
Use this decision table before changing anything
| Trigger pattern | Likely root cause | Safest first action | When to stop DIY and escalate |
|---|---|---|---|
| Startup-only crash before sign-in | Recently changed driver, startup component, or damaged system files | Boot Safe Mode and remove the last changed driver or device | If Safe Mode also crashes or the PC cannot reach recovery options |
| Crash began right after a Windows update | Driver incompatibility or a corrupted update path | Roll back or uninstall the newest device driver first | If the same stop code returns after driver rollback |
| Crash began after new hardware was added | Driver, device, or firmware issue related to the new hardware | Leave the new hardware unplugged or removed, then boot again | If removal does not change the behavior or the machine will not stay up |
| Crash follows a power loss or disk error | Missing or corrupt system files, or storage damage | Run sfc /scannow, then chkdsk if needed | If file repair reports repeat damage or the disk checks fail |
Is 0x0000005A a driver problem or hardware problem?
It can be either, so start with whatever changed most recently. If the crash began after a driver install, Windows update, or device change, treat it as a software or driver branch first. If it appears after a power outage, disk error, or hardware swap, check storage and hardware next.
Hardware should not be the default guess. Bad RAM, storage, or an unstable add-in device can trigger the same symptom, but the quickest clue is whether one recent change lines up with the first crash.
What points to a bad driver
- Boot into Safe Mode.
- Open Device Manager.
- Find the last driver or device that changed.
- Choose Properties > Driver > Roll Back Driver, or select Uninstall device.
- Restart normally and check whether the stop code returns.
If the crash began after a Windows update, this is often the first branch to try. Driver rollback is usually easier to reverse than storage repair.
