How to Fix Critical Service Failed BSOD on Windows

This guide explains how to fix the “CRITICAL_SERVICE_FAILED” Blue Screen of Death (BSOD) on Windows 10 and Windows 11. This stop code appears when a core Windows service fails to start during boot, often after a driver update, a corrupted system file, or a recent software change. The steps below walk you through the most effective fixes, from safe mode recovery to system restore and driver rollback, so you can get your PC booting normally again.

What You’ll Need

A Windows PC that can reach the recovery environment (WinRE) or the login screen
Another computer (optional) to download a Windows installation media or recovery tools
An 8 GB or larger USB drive (optional) to create installation media
Your Windows product key (not usually needed for repairs, but handy)

Step-by-Step

Force Windows to enter the Recovery Environment. If your PC repeatedly fails to boot, Windows will automatically show the blue “Automatic Repair” screen after a few attempts. If it doesn’t, turn the PC off completely (hold the power button for 10 seconds), turn it on, and as soon as the Windows logo appears, press and hold the power button again to force shutdown. Do this two or three times; on the next boot, Windows should display the recovery screen.
Boot into Safe Mode. From the recovery screen, click Troubleshoot > Advanced options > Startup Settings > Restart. After the PC restarts, press 4 or F4 to enable Safe Mode (or 5/F5 for Safe Mode with Networking, which you’ll need if you want to download drivers or run online tools). If you can boot into Safe Mode, the problem is likely a driver or service that runs only during normal boot.
Run the System File Checker (SFC). Once in Safe Mode, open Command Prompt as administrator (right-click the Start button and select Terminal (Admin) or Command Prompt (Admin)). Type sfc /scannow and press Enter. This scans and repairs corrupted Windows system files. It can take 10–20 minutes. When it finishes, restart the PC normally.
Run the DISM tool. If SFC doesn’t fix the issue, open Command Prompt as administrator again and run DISM /Online /Cleanup-Image /RestoreHealth. This repairs the Windows system image itself. It may take 20–30 minutes. After it completes, run sfc /scannow again to make sure everything is consistent.
Roll back recent driver updates. If the BSOD started after a driver update, especially a graphics or chipset driver, roll it back. In Safe Mode, right-click the Start button and select Device Manager. Expand the relevant category, right-click the device, select Properties, go to the Driver tab, and click Roll Back Driver. If that button is greyed out, you can also try uninstalling the device and restarting—Windows will reinstall a previous driver.
Uninstall recently installed software. If the problem began after installing a new program, uninstall it. Go to Settings > Apps > Installed apps, find the program, click the three-dot menu, and select Uninstall. If you’re not sure which program caused it, think about what you installed just before the BSODs started.
Use System Restore. If you have a restore point from before the issue, you can roll back your system to that point. From the recovery screen, go to Troubleshoot > Advanced options > System Restore. Follow the prompts and choose a restore point that predates the problem. This won’t affect your personal files, but it will remove recently installed drivers and software.
Check for disk errors. Run chkdsk /f /r from an elevated Command Prompt. You may need to restart the PC for it to run. This checks the hard drive for bad sectors and file system errors. If the drive is failing, you’ll see errors, and you should back up your data immediately.
If Safe Mode doesn’t work, use the Command Prompt from the recovery environment. From the recovery screen, choose Troubleshoot > Advanced options > Command Prompt. Then run the same SFC and DISM commands, but note that the Windows drive letter may be different (often D: instead of C:). To find it, type dir D:\ and see if it contains the Windows folder. Then run sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows.
Reset your PC. If nothing else works, you can reset Windows. From the recovery screen, choose Troubleshoot > Reset this PC. You can choose to keep your personal files or remove everything. This reinstalls Windows and can clear up any persistent system corruption. Make sure you back up important files first if you can.

Common Mistakes

Skipping Safe Mode. Some users jump straight to a reset without trying safe mode. Safe mode often lets you fix the issue with a simple driver rollback or uninstall.
Not running DISM before SFC. SFC can fail if the system image is corrupted. Always run DISM first if SFC doesn’t fix the issue.
Using the wrong drive letter in recovery. In the recovery command prompt, the system drive is often not C:. Running SFC against the wrong drive will do nothing.
Ignoring disk errors. If chkdsk reports bad sectors, the drive may be failing. Continuing to use it without backing up can lead to data loss.

Tips

Create a restore point before installing new drivers or major updates. That way you can easily roll back.
Keep Windows and drivers updated. Many BSODs are caused by outdated or buggy drivers. Use Windows Update and your manufacturer’s update tool.
Use the Windows Memory Diagnostic tool to test your RAM if you suspect a hardware issue. Search for “Windows Memory Diagnostic” in the Start menu.
Check the Event Viewer after you boot back into Windows to see which service or driver failed. Look under Windows Logs > System for errors with the source “Service Control Manager” or “BugCheck”.

Troubleshooting

If the steps above don’t resolve the issue, try the following:

If you can’t boot into Safe Mode: Use the recovery environment’s command prompt to run DISM and SFC. If that fails, you may need to use Windows installation media to repair the system. Create a bootable USB with the Windows Media Creation Tool, boot from it, and choose “Repair your computer” instead of “Install now”.
If the BSOD appears during the reset process: The reset may fail if the system image is too corrupted. In that case, download the Windows installation media and perform a clean install (back up your files first).
If the BSOD occurs randomly even after fixes: This could indicate a hardware problem, such as failing RAM or a failing hard drive. Run the Windows Memory Diagnostic and check the drive’s SMART status (using tools like CrystalDiskInfo). If you suspect hardware, contact a professional.
If the BSOD happens after a specific update: You can uninstall the update from the recovery environment or use the “Uninstall updates” option in Advanced options. If you know the KB number, you can also use the command line: wusa /uninstall /kb:XXXXXXX.

Frequently Asked Questions

What does “Critical Service Failed” mean?

It means a Windows service that is essential for the system to run failed to start during boot. This is often caused by a corrupted driver, a recent update, or a system file issue.

Will I lose my files if I use System Restore?

No, System Restore only affects system files, drivers, and installed programs. Your personal files (documents, photos, etc.) are not changed, but it’s always a good idea to back up anyway.

Can I fix this without a Windows installation disc?

Yes, most fixes can be done from the built-in recovery environment or Safe Mode. You only need installation media if the recovery environment is also corrupted.

How long does the DISM command take?

It can take 20 to 30 minutes, sometimes longer on older hard drives. Let it run to completion; don’t interrupt it.

Is this BSOD caused by a virus?

It’s possible but not common. If you suspect malware, run a full antivirus scan after you boot back into Windows. The SFC and DISM scans can also repair damage caused by malicious software.

Should I try a clean install of Windows?

Only as a last resort. If no other fix works and you have backed up your data, a clean install will definitely resolve the issue, as it replaces all system files and drivers.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →