Repair shops will quote you £150 to £250 for this. Most of the time, you don't need them. Windows 11 BSOD recovery is something you can work through yourself, even when System Restore and Startup Repair have already given up. This guide covers every layer of the problem, from a five-minute peripheral check right through to disk repair and clean reinstall.

TL;DR

Windows 11 BSOD recovery when System Restore fails usually means driver corruption, failing hardware, or disk damage. Boot into Safe Mode, strip out dodgy drivers, run SFC and DISM from WinRE Command Prompt, test your RAM, and check your BIOS storage settings. If nothing works, a clean reinstall almost always sorts it.

⏳️ 13 min read ✅ 80% success rate 📅 Updated June 2026

Key Takeaways

Windows 11 BSOD recovery is possible from Safe Mode and WinRE even when normal boot fails completely.
Faulty drivers are the most common cause. Removing them in Safe Mode fixes a large proportion of cases.
SFC and DISM can repair corrupted system files without wiping your data.
If software fixes fail, test your RAM and check BIOS storage settings before assuming the worst.
A clean reinstall resolves virtually every software-related BSOD. Persistent crashes after reinstall point to hardware.

At a Glance

Difficulty: Advanced
Time Required: 30 to 90 mins depending on tier
Success Rate: Around 80% of cases resolved before clean reinstall

What Causes Windows 11 BSOD Recovery to Fail?

The reason System Restore and Startup Repair both fail is that they're designed to fix relatively minor Windows configuration problems. When the damage goes deeper, those tools simply don't have the reach. Here's what's actually going wrong underneath.

Faulty or incompatible drivers are the most common culprit by a significant margin. Microsoft's own stop code reference lists driver failures as the primary trigger for most blue screen errors. Storage drivers, GPU drivers, chipset drivers, and surprisingly often third-party antivirus drivers are the main offenders. An antivirus update that ships a broken kernel driver can take down an otherwise healthy machine overnight.

Recently added or failing hardware is the second big one. New RAM that's slightly incompatible, an SSD that's starting to fail, a GPU seated slightly wrong, or even a dodgy USB hub can all cause persistent BSODs. The tricky part is that the crash happens in Windows, so it looks like a software problem when the real fault is physical.

Disk and file system corruption is another layer. If the drive has developed bad sectors, or if a previous crash interrupted a write operation, Windows system files can end up damaged. That's why Startup Repair fails: it's trying to fix Windows using tools that are themselves broken. This is where dedicated data recovery software becomes relevant, because some of that file-level damage needs specialist tools to properly assess and recover before you can get Windows stable again.

BIOS and storage controller settings cause a specific type of BSOD called INACCESSIBLE_BOOT_DEVICE. This happens when the storage controller mode (Intel VMD, AHCI, or RAID) doesn't match what Windows was originally installed with. A BIOS update or an accidental settings change is enough to trigger it. And finally, overheating or power instability, less common but worth checking, particularly on desktops that have been running hot or laptops with a failing power supply.

Note the stop code when your machine crashes if you can. Codes like DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, and PAGE_FAULT_IN_NONPAGED_AREA all point toward drivers. INACCESSIBLE_BOOT_DEVICE points toward storage or BIOS. That distinction saves a lot of time.

Windows 11 BSOD Recovery: Quick Fixes First

Start here. These take five to fifteen minutes and fix a meaningful chunk of cases, particularly when the problem started after connecting something new or installing a specific piece of software.

Disconnect All Non-Essential Peripherals Easy

Power off completely.
Hold the power button until the machine is fully off. Don't just restart.
Unplug everything except keyboard, mouse, and monitor.
That means external hard drives, SSDs, USB hubs, dongles, SD cards, printers, and anything else connected via USB or other ports. If you added something new recently, that's your prime suspect.
Boot normally and wait.
Give it a few minutes of normal use. If the BSOD doesn't appear, reconnect devices one at a time with a reboot between each until the crash returns. The last device you connected before the crash is your culprit.

If BSODs stop after removing peripherals, you've found the cause. Don't reconnect the offending device until you've updated its drivers or confirmed it's working on another machine.

Uninstall Recent Software in Safe Mode Easy

Boot into Safe Mode.
From the Recovery options screen, go to Troubleshoot, then Advanced options, then Startup Settings, and press 4 to enable Safe Mode. If you're getting into Safe Mode from a BSOD loop, Windows may offer the Recovery environment automatically after two or three failed boots.
Open Apps and Features.
Press Win + X and select Apps and Features (or Installed apps in newer builds). Sort by install date.
Uninstall anything installed just before the BSODs started.
Focus on GPU utilities, overclocking tools like MSI Afterburner or HWiNFO, system optimisers, and third-party antivirus suites. These are the most common software triggers. Reboot normally after removing them.

Safe Mode loads only essential Microsoft drivers and services. If Windows runs fine in Safe Mode but crashes normally, that's a strong signal a third-party driver or service is the cause.

Check Free Disk Space Easy

Open File Explorer in Safe Mode.
Right-click your C: drive and select Properties.
Verify at least 10 to 15 percent free space.
Microsoft recommends this minimum for stable operation and paging. If your drive is nearly full, delete large files from Downloads and Temp folders, or uninstall applications you don't use. The Temp folder lives at C:\Windows\Temp and your user temp at %APPDATA%\Local\Temp.

A drive that was 98 percent full and causing crashes will often stabilise immediately once you free up space. Not glamorous, but it works.

Intermediate Windows 11 BSOD Recovery Steps

If the quick fixes didn't sort it, the problem is likely a specific driver or a Windows component that needs updating or removing. These steps take fifteen to thirty minutes and have a solid success rate for driver-related crashes.

Remove or Roll Back Problematic Drivers Medium

Open Device Manager from Safe Mode.
Right-click Start and select Device Manager. Look for any devices showing a yellow exclamation mark. Those are your immediate suspects.
Target Display adapters and Storage controllers first.
Right-click a suspect device and choose Properties. Go to the Driver tab. If Roll Back Driver is available and greyed out, a previous version doesn't exist. If it's clickable, use it. Otherwise, choose Uninstall device and tick the box to delete the driver software.
Reboot normally.
Windows will load a basic Microsoft driver for the device. This won't give you full GPU performance but it will tell you whether the driver was the problem. If the BSOD stops, download the latest official driver from the manufacturer's website (Nvidia, AMD, Intel) rather than letting Windows Update pick one automatically.

Don't uninstall your storage controller driver unless you're certain it's the problem. Removing the wrong storage driver can make the drive temporarily inaccessible.

Install Windows 11 Updates via Safe Mode with Networking Easy

Boot into Safe Mode with Networking.
From WinRE, go to Troubleshoot, then Startup Settings, and press 5 or F5. This gives you internet access in Safe Mode.
Open Settings and go to Windows Update.
Click Check for updates and install everything available. Some BSODs are caused by known bugs that Microsoft has already patched. If you're hitting a Windows Update error like 0x80240034 during this step, that guide covers how to clear the update cache and retry.
Reboot normally after updates complete.
Give the system a proper workout before declaring it fixed.

Reset This PC (Keep Files) Medium

Boot into WinRE.
Select Troubleshoot, then Reset this PC.
Choose Keep my files.
This preserves your personal documents and photos but removes all installed applications and drivers. Choose Local reinstall if you don't have reliable internet. Cloud download is cleaner but needs a decent connection and around 4GB of data.
Follow the on-screen instructions and wait.
This takes anywhere from 20 minutes to over an hour depending on your hardware. Don't interrupt it.

Reset This PC with Keep my files has a high success rate for software-caused BSODs. It's essentially a Windows reinstall without touching your personal data.

Advanced Windows 11 BSOD Recovery Fixes

This is where most persistent cases get resolved. These steps require using Command Prompt from WinRE, which sounds intimidating but is actually just copying and pasting a few commands. Take your time with each one.

Run SFC and DISM to Repair System Files Advanced

Open Command Prompt from WinRE.
Go to Troubleshoot, then Advanced options, then Command Prompt. You may need your Microsoft account credentials or a local admin password.
Identify your Windows drive letter.
Type the following and press Enter after each line:
diskpart
list volume
exit
Look for the volume labelled Windows or the one with the largest size. It's usually C: but can appear as D: or E: from WinRE.
Run System File Checker.
Type:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
Replace C: with your actual drive letter if different. This scans and repairs corrupted Windows system files. It takes five to fifteen minutes.
Run DISM if SFC reports unfixed errors.
Type:
dism /image:C:\ /cleanup-image /restorehealth
DISM pulls replacement files from Windows Update (or the local image) to repair deeper damage that SFC can't fix on its own. Run SFC again afterwards to confirm repairs.

SFC and DISM together fix the majority of corruption-related BSODs. Microsoft's own stop code troubleshooting documentation recommends this combination as the primary repair method for system file damage.

Check Disk Health with chkdsk Advanced

From WinRE Command Prompt, run:
chkdsk C: /f /r
The /f flag fixes file system errors. The /r flag locates bad sectors and attempts to recover readable data from them. If prompted to schedule on next reboot, type Y and press Enter.
Let it run completely.
This is not a quick process. A 1TB drive typically takes two to four hours. A 2TB drive can take longer. Do not interrupt it. Interrupting chkdsk mid-run can make things worse.
Review the results.
If chkdsk reports a large number of bad sectors, the drive itself is failing. At that point, back up everything you can immediately. A drive with significant bad sectors needs replacing, not repairing. This is where dedicated data recovery software becomes important for getting your files off before the drive fails completely.

If chkdsk reports hundreds of bad sectors, stop using the drive for anything other than data recovery. A failing drive can become completely unreadable with little warning.

Test RAM with Windows Memory Diagnostic Medium

From Safe Mode, press Win + R, type mdsched.exe, and press Enter.
Select Restart now and check for problems. The PC will reboot into the memory test environment.
Let the test complete fully.
The standard test runs two passes. Extended mode runs more. Tom's Hardware has a good breakdown of what each test mode checks if you want to understand what's happening.
If errors appear, reseat your RAM first.
Power off, open the case, remove the RAM sticks, and firmly reseat them. Run the test again. If errors persist, test one stick at a time to identify the faulty module. Replace the bad stick.

RAM errors almost always cause BSODs with codes like MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL. Replacing a faulty stick resolves these reliably.

Check BIOS Storage Settings Advanced

Enter BIOS/UEFI during power-on.
The key varies by manufacturer: F2, Del, or Esc are most common. Check your laptop or motherboard manual if unsure.
Verify storage controller settings.
Look for Intel VMD, SATA Mode, or Storage Configuration. The setting must match what was in place when Windows was originally installed. Switching from RAID to AHCI, or enabling Intel VMD when it was previously off, will cause INACCESSIBLE_BOOT_DEVICE on every boot.
Revert any recent changes.
If a BIOS update ran recently, check whether storage defaults changed. Restore to the previous configuration and test. If you're unsure what the original setting was, search your laptop model plus AHCI or VMD to find the correct default.

This step is specifically relevant if your BSOD stop code is INACCESSIBLE_BOOT_DEVICE. It's also worth checking if the problem started immediately after a BIOS update.

Clean Reinstall Windows 11 (Last Resort) Advanced

Back up your files first.
Use WinRE Command Prompt to copy important files to an external drive, or use a bootable Linux USB to access the drive and copy data across. Don't skip this step.
Create a Windows 11 installation USB on another PC.
Download the Media Creation Tool from Microsoft's website, run it, and create a bootable USB with at least 8GB capacity. This gives you a clean, uncorrupted Windows installer.
Boot from the USB and choose Custom install.
Delete the existing Windows partition during setup (your files will be gone, so make sure the backup is done). Let the installer create a fresh partition and install Windows cleanly.
Test for BSODs before reinstalling anything.
Run the clean Windows installation for a day before adding drivers and software. If BSODs continue on a completely clean install, the fault is hardware, not software.

A clean reinstall wipes everything on the system partition. There is no undo. Back up first, every time, no exceptions.

Preventing Windows 11 BSOD Recovery Situations

Most of the cases I see could have been avoided. Here's what actually matters, in order of importance.

Keep drivers updated through official channels only. That means Windows Update and the OEM's own utility (Lenovo Vantage, Dell SupportAssist, HP Support Assistant, and so on). Unofficial driver packs and sites like DriverBooster are a genuine risk. They've caused more BSODs than they've fixed, in my experience. If you've had issues with Windows components behaving oddly after updates, the Windows 11 Settings System page crash guide covers a related class of post-update problems worth being aware of.

Use one antivirus solution. Running two real-time security products simultaneously is a reliable way to create kernel driver conflicts. Windows Security (Defender) is genuinely good in 2026 and doesn't need a companion product running alongside it. If you're seeing Defender behaving strangely, that's sometimes a sign of a deeper infection rather than a Defender fault. A trojan that keeps coming back despite Windows Defender needs a different approach entirely.

Maintain at least 10 to 15 percent free space on your system drive. Windows needs room for the page file, temporary files, and update staging. A drive at 97 percent capacity is an accident waiting to happen.

Create System Restore points regularly when the system is healthy. Before any major driver update, before installing new software, and once a month as routine. It takes thirty seconds and has saved hours of repair work on countless machines.

Monitor temperatures if you're overclocking or running demanding workloads. HWiNFO64 is free and reliable for this. Thermal throttling and sudden shutdowns under load are a sign the cooling system needs attention before it causes data corruption. And if you ever see a stop code you don't recognise, write it down. That code cuts diagnostic time in half if the problem comes back.

Windows 11 BSOD Recovery: Summary

Windows 11 BSOD recovery when System Restore and Startup Repair have both failed is a multi-layer problem. Start with the quick checks: peripherals, recently installed software, disk space. If those don't fix it, move to driver removal in Safe Mode and Windows updates. If you're still stuck, SFC, DISM, chkdsk, and RAM testing will resolve the majority of remaining cases. BIOS storage settings are worth checking if your stop code mentions boot devices. And if everything else fails, a clean reinstall will fix any software-related cause. Persistent crashes after a clean reinstall mean the fault is hardware, and that's a different conversation. Document your stop codes, keep your drivers from official sources, and you'll be much less likely to need Windows 11 BSOD recovery again.