What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Error 0x0000005A is the Windows stop code CRITICAL_SERVICE_FAILED. It means a service that Windows considers essential failed during startup or operation. The code does not identify one universal bad driver, file, or device, so the reliable fix is to work backward from your latest hardware or software change, Safe Mode behavior, Event Viewer entries, the blue screen’s “What failed” line, and any crash dump. The sequence below is designed for Windows 11 and Windows 10 and usually lets you isolate the cause without reinstalling Windows.
What 0x0000005A means
Microsoft’s bug-check reference defines 0x0000005A as CRITICAL_SERVICE_FAILED and notes that this bug check appears very infrequently. A critical service can fail because a recently installed driver or service is incompatible, a configuration change prevents startup, or a hardware change exposes a lower-level problem. The number itself is a category, not a diagnosis: it does not tell you which service failed.
As an Amazon Associate I earn from qualifying purchases.
Windows may show a blue screen, restart immediately, or enter a repeating restart cycle. If the stop screen includes a What failed module, record its exact name before the machine reboots. That name can point toward the device or driver involved, but it still needs to be checked against logs and recent changes. A dump file preserves crash information for deeper analysis; Microsoft directs advanced users to WinDbg and its !analyze extension.
Choose the path that matches your boot state
| Current state | Start here | What the step changes | Evidence it can provide |
|---|---|---|---|
| You can reach the desktop | Review recent changes, Event Viewer, and Device Manager | Usually removes or rolls back one driver, service, or device | System and service errors around the crash time |
| Windows starts only in a loop | Enter Safe Mode or Windows Recovery Environment (WinRE) | Loads a reduced set of drivers and services, or repairs startup | Whether a third-party driver or service is required to trigger the failure |
| Windows will not reach the sign-in screen | Startup Repair, System Restore, then Safe Mode from WinRE | Repairs boot components or reverses system state | Recovery results and restore-point history |
| A dump file exists | Open it in WinDbg and run !analyze |
Does not alter Windows; it examines the recorded crash | Faulting module, parameters, and a call stack for a more specific lead |
| No software lead remains | Run the computer maker’s memory and storage diagnostics | Tests hardware according to the manufacturer’s procedure | Hardware test codes or a failing component identified by the vendor tool |
Before changing anything
- Write down the stop code, the time of the crash, and any text shown beside What failed.
- If the desktop is available, copy important files to another disk or cloud location before uninstalling a driver or using recovery tools.
- Note anything installed or changed immediately before the first crash: a graphics card, USB device, storage drive, firmware update, driver package, security product, backup agent, or Windows service.
- Disconnect nonessential peripherals while troubleshooting. Leave the keyboard, mouse, display, and the system drive connected so you can tell whether removing one device changes the behavior.
- Do not repeatedly force power off while Windows is writing data. If a loop prevents normal shutdown, use the power button only long enough to reach WinRE, then use its controlled recovery options.
1. Undo the latest hardware change
Microsoft’s blue-screen guidance puts newly added hardware among the first things to check. Shut the computer down completely, unplug the newly installed component, and disconnect its cable or external adapter. For an internal component, follow the computer or motherboard maker’s instructions; do not open a device that is still under service coverage if doing so would affect that coverage.
#1 Best Overall
- 🔑 RESET WINDOWS PASSWORDS IN MINUTES Quickly reset forgotten local Windows user and administrator passwords without reinstalling Windows or losing important files. Fast and simple offline recovery process.
- 💻 WORKS WITH MOST WINDOWS PCS & LAPTOPS Compatible with many Windows desktop and laptop systems. Supports USB boot startup for convenient and reliable password recovery access.
- ⚡ EASY PLUG & PLAY USB DESIGN No complicated setup required. Simply insert the USB, boot from it, and follow the included step-by-step instructions to reset passwords quickly.
- 🔒 SAFE OFFLINE PASSWORD RECOVERY Runs completely offline with no internet connection required. Helps protect your privacy while keeping your files and operating system intact.
- 🛠 BEGINNER-FRIENDLY WITH INCLUDED INSTRUCTIONS Designed for home users, students, technicians, and IT professionals. Includes easy-to-follow written instructions and boot menu guidance for hassle-free recovery.
Start Windows with the hardware removed. If the crash stops, power down again and inspect the component’s seating, power connector, firmware requirements, and driver package. Reinstall it only after confirming that the maker supports your Windows edition. If the machine still crashes with the component disconnected, the change may have replaced a driver or service rather than being a physical fault; continue with Safe Mode and log review.
2. Start Windows in Safe Mode
Safe Mode loads a reduced environment. That makes it a low-impact diagnostic step: a recently installed third-party driver or service that is required for a normal boot may not load there.
From a working desktop
- On Windows 11, open Settings > System > Recovery. On Windows 10, open Settings > Update & Security > Recovery.
- Under Advanced startup, select Restart now.
- At the recovery menu choose Troubleshoot > Advanced options > Startup Settings > Restart.
- After the restart, press 4 or F4 for Safe Mode. Choose 5 or F5 for Safe Mode with Networking only when you need network access for a specific diagnostic task.
You can also hold Shift while selecting Restart from the Start menu or sign-in screen, then follow the same recovery path.
Recommended Free Tools
When normal startup never reaches the desktop
Windows can enter Automatic Repair after several interrupted starts. Turn the computer on and, when Windows begins loading, interrupt startup with the power button; repeat only as needed until Preparing Automatic Repair or WinRE appears. In WinRE select Troubleshoot > Advanced options > Startup Settings, choose Restart, and then select Safe Mode. If BitLocker is enabled, WinRE may ask for the recovery key.
Once in Safe Mode, test whether the restart loop occurs. If it does not, the reduced environment has narrowed the suspect list to something that normal startup adds. Do not assume Safe Mode has repaired anything; it has only isolated the conditions.
Rank #2
- NOTE: This USB flash drive does not include a Windows key, you must have a Windows key to activate Windows, but you can still clean install or reinstall Windows 7.
- Latest Version: Deployed with the latest official original version of Windows 7 (SP1), no viruses, no spyware, 100% clean.
- Professional: Using professional Windows 7 production tool to ensure product quality.
- Compatibility: Compatible with all PC brands, laptop or desktop, 64-bit/32-bit, Dell, HP, Sony, Lenovo, Samsung, Acer, Toshiba and more.
- Plug & Play: Includes user guide and online technical support services. Plug it in and you are ready to go.
3. Check Device Manager and reverse a recent driver change
In Safe Mode or on the desktop, press Windows key + X and open Device Manager, or run devmgmt.msc. Expand the category connected to the recent change, such as Display adapters, Storage controllers, Network adapters, Bluetooth, Sound, video and game controllers, or Universal Serial Bus controllers.
- A yellow warning icon indicates that Windows has recorded a problem with the device or its driver. Open Properties and read the status on the General tab.
- On the Driver tab, use Roll Back Driver when it is available and the problem began after an update. Windows may disable this button when no previous package is retained.
- If rollback is unavailable, choose Uninstall Device. Read the confirmation carefully; select the option to remove the driver package only when you have a known-good replacement from the device maker. Restart and let Windows redetect the hardware.
- To stop a suspect device from loading while you test, choose Disable device. This is reversible, but the device will not function until you enable it again.
- Use Update driver only with a package intended for your exact device and Windows release. A driver that merely has a newer date is not automatically compatible.
Change one device at a time and restart after each change. If the blue screen returns, restore the previous state and test the next suspect instead of uninstalling several unrelated drivers at once.
4. Read the blue screen and Windows logs
Capture the displayed module
If the stop screen names a file or module under What failed, photograph it or write it down. Compare that name with the device or service you changed. A module name is a lead, not proof: a driver can appear in the crash path while another service or hardware fault caused the failure.
Use Event Viewer
- Press Windows key + R, enter
eventvwr.msc, and press Enter. - Open Windows Logs > System.
- Choose Filter Current Log and select Critical and Error, then set the time window around the restart.
- Inspect entries from Service Control Manager, the Windows bug-check provider, and Kernel-Power. Open each event’s details and record the service name, driver name, status code, and timestamp.
Event Viewer can show that a service failed to start or that Windows recorded a bug check, but it may not identify the original cause. Correlate several entries at the same time instead of treating the last event in the list as the culprit. Reliability Monitor (perfmon /rel) provides a calendar view that can help you match the first failure with an installation or update.
5. Undo recent software and service changes
Microsoft specifically recommends removing or updating recently added drivers and system services when a stop-code failure follows a change. Start with the newest change that matches the log or displayed module.
Rank #3
- Emergency Boot USB compatible with Windows 98, 2000, XP, Vista, 7, and 10. It has never ben so easy to repair a hard drive or recover lost files
- Plug and Play type usb - Just boot up the usb and then follow the onscreen instructions for ease of use
- Boots up any PC or Laptop model and brand.
- Virus and Malware Removal made easy for you
- This is your one stop shop for PC Repair of any need!
Remove a recently installed program
Open Settings > Apps > Installed apps on Windows 11 or Settings > Apps > Apps & features on Windows 10. Sort by installation date, remove the suspect program, and restart. In Safe Mode, some uninstallers will not run; use WinRE or normal startup after first disabling the related service if the program’s vendor documents that procedure.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Inspect a service without disabling Windows broadly
Run services.msc and locate the service named in Event Viewer. Open its properties and record Startup type, Service status, and the executable path before changing anything. If it belongs to software you just installed, use that software’s documented uninstall or repair option. Do not disable groups of Microsoft services or change random startup types: that can create a second failure and erase the evidence you need.
Use System Restore when a suitable point exists
System Restore reverses system files, drivers, services, and registry settings to an earlier restore point while normally leaving personal documents untouched. On a working desktop, run rstrui.exe. In WinRE choose Troubleshoot > Advanced options > System Restore. Select a point dated before the first 0x0000005A event, review the affected programs and drivers, and let the process complete without powering off. Restore points are not created on every system, and a restore cannot help if no point predates the failure.
6. Repair startup when Windows will not boot
When the machine cannot reach the desktop, use WinRE rather than repeatedly attempting normal startup. From the Automatic Repair screen choose Troubleshoot > Advanced options > Startup Repair. Windows checks startup components and attempts repairs automatically. The operation may restart the computer more than once.
If Startup Repair reports that it could not repair the PC, return to Advanced options and try System Restore if a suitable point exists. You can also select Startup Settings to reach Safe Mode and remove the recent driver or service there. These recovery choices target different problems: Startup Repair addresses the boot process, while System Restore reverses a prior system state.
Rank #4
- Dual USB-A & USB-C Bootable Drive – compatible with nearly all laptops, desktops, mini-PCs, Windows tablets or servers, supporting both Legacy BIOS and UEFI boot modes.
- Reset or Recover Forgotten Passwords – unlock Windows or Linux user accounts in minutes without reinstalling the system or losing files. Broad Compatibility – supports Windows 2000, XP, Vista, 7, 8, 8.1, 10, 11, and most Linux distributions.
- Simple & Secure to Use – user-friendly interface with on-screen guidance and step-by-step instructions; no internet connection required.
- Trusted by IT Professionals – a reliable tool for technicians, administrators, and power users to restore system access quickly and safely. For advanced workflows, the USB is fully customizable, allowing you to easily Add / Replace / Upgrade compatible bootable ISO apps, installers, or utilities.
- Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
If WinRE itself cannot be reached, use another Windows computer to create official installation media and boot the affected PC from it, then choose Repair your computer instead of installing. The exact boot-key sequence depends on the computer maker. Keep the installation media matched to the installed Windows edition when possible.
7. Analyze a crash dump with WinDbg
A dump is the strongest software evidence available for this stop code, but interpreting one requires technical skill. Windows may keep a small dump or a larger memory dump depending on its crash settings. Look for a newly created dump after the failure, commonly under the Windows system directory or its Minidump subfolder.
- Install and open WinDbg from Microsoft’s debugging tools.
- Choose File > Open dump file and select the dump created at the crash time.
- Allow symbols to load, then run
!analyzein the command window. The verbose form,!analyze -v, displays additional fields when available. - Record the bug-check parameters, the reported faulting module, and the call stack. Compare the module with the name from the blue screen, Device Manager, and Event Viewer.
- Use the result as a lead to roll back, remove, or update the implicated driver or service. If the analysis points to a generic Windows component, investigate the third-party driver or hardware appearing lower in the stack rather than deleting the Windows file.
A dump can be incomplete or point only to the component that detected the failure. Keep the original file unchanged if you plan to send it to the computer maker or a qualified technician. Never download a replacement DLL from an unknown site because a dump mentions its name.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.8. Test hardware when software evidence is inconclusive
If Safe Mode, rollback, restore, and dump analysis do not implicate a driver or service, use the computer manufacturer’s hardware diagnostics. Run the memory and storage tests offered for your exact model and follow the maker’s instructions for interpreting codes. A failing system drive can prevent a critical service from loading, while faulty memory can corrupt data used by many unrelated services.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsRecord every diagnostic code and the test version. If a test identifies a component, power the computer down before reseating or replacing it and observe electrostatic precautions. If all tests pass but the crashes continue, provide the manufacturer or repair professional with the stop-screen photo, Event Viewer entries, and dump analysis rather than repeating random driver installations.
Best Value
- COMPATIBILITY: Designed for both Windows 11 Professional and Home editions, this 16GB USB drive provides essential system recovery and repair tools
- FUNCTIONALITY: Helps resolve common issues like slow performance, Windows not loading, black screens, or blue screens through repair and recovery options
- BOOT SUPPORT: UEFI-compliant drive ensures proper system booting across various computer makes and models with 64-bit architecture
- COMPLETE PACKAGE: Includes detailed instructions for system recovery, repair procedures, and proper boot setup for different computer configurations
- RECOVERY FEATURES: Offers multiple recovery options including system repair, fresh installation, system restore, and data recovery tools for Windows 11
Windows 10 and Windows 11: what differs
The diagnostic logic is the same on both releases: isolate recent hardware, use Safe Mode, inspect Device Manager and logs, reverse a recent driver or service, then use WinRE or dump analysis. Microsoft Support publishes its blue-screen and unexpected-restart guidance for both Windows 10 and Windows 11.
The visible menus differ. Windows 11 places recovery under Settings > System > Recovery; Windows 10 uses Settings > Update & Security > Recovery. The stop screen design and wording can also vary, and some manufacturers add their own recovery screens. Follow the labels shown on your machine rather than assuming that a Windows 10 screenshot exactly matches Windows 11.
Common restart-loop branches
The loop began after a device or driver update
Disconnect the device, enter Safe Mode, roll back or uninstall its driver, and restart normally. If the loop stops, install only the manufacturer’s package that supports your Windows release.
The loop began after a program or service installation
Use Safe Mode to uninstall the program or stop its service, then check Event Viewer for the service name. If no uninstall is possible, use a restore point from before the installation.
The loop occurs even in Safe Mode
That makes a normal third-party startup item less likely. Use WinRE’s Startup Repair and System Restore, then examine any dump and run the manufacturer’s hardware tests.
No dump or useful log was created
Absence of a dump does not prove hardware failure. Recovery environments, abrupt power loss, full system drives, or dump settings can prevent a usable file. Continue with the displayed module, Event Viewer timestamps, restore points, and vendor diagnostics.
Pitfalls to avoid
- Do not delete a system driver merely because its name appears on the stop screen. Confirm the associated device and keep a recovery path.
- Do not install several driver packages simultaneously; you will lose the ability to identify which change mattered.
- Do not disable security or core Windows services as a general experiment. Change only the service connected to your evidence.
- Do not treat a successful Safe Mode boot as a permanent fix. It means only that the reduced environment avoids the failing component.
- Do not reset or reinstall Windows before trying a restore point and preserving logs and dumps. Reinstallation removes useful evidence and may not correct a failing component.
When to escalate
Contact the computer or component manufacturer when its diagnostic test returns a failure code, when the machine crashes with newly removed hardware, or when a warranty repair may be required. A technician will be able to work faster if you provide the exact stop code, crash time, displayed module, Event Viewer entries, Device Manager changes, restore-point result, and any dump file. Microsoft publishes no numeric success rate for these individual remedies, no percentage breakdown of 0x0000005A causes, and no hardware-failure statistic; the only frequency statement is that the bug check appears very infrequently.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
As an optional shortcut after trying the manual steps, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements and shared DLL problems, and can provide an app-crash log and vulnerability checks. It runs on Windows 11, 10, 8, and 7, offers a free trial by category for at least two days before a subscription, complements an antivirus rather than replacing one, and results vary; no tool repairs every crash.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
