BSOD Recovery Checklist: what to do when nothing else stops the crash loop

This page assumes the reversible fixes are already behind you. If you haven't yet read the stop code, rolled back a recent driver, or run the system-file repair, do that first — see the blue screen master guide and the crash-loop guide. This is the page for the moment after those steps, when the machine is still looping and you need to decide what's next.

Two starting states change what's available. If the PC still reaches the desktop (even if it crashes later), you can use some reversible options from inside Windows and from Safe Mode. If it won't boot at all, everything runs from the Windows Recovery Environment. The ladder below works for both; the available first steps differ by state.

The highest-value action here isn't a recovery tool. It's making sure your files exist somewhere safe before you run anything irreversible. A mistaken or failed Reset is recoverable if your data is on separate storage — and it's a disaster if your only copy was on the drive you're about to wipe.

1. If you can boot at all, copy documents, photos and other personal folders to an external drive or cloud now — don't wait until you're choosing a wipe.
2. If you can't boot, you may still read the drive from another PC (remove it and connect via a USB/SATA adapter) or from the WinRE command prompt — carefully, and read-only where you can.
3. Locate your BitLocker recovery key before you need it: it's in your Microsoft account, a printout, or a USB you saved earlier. Without it, an encrypted drive after a reset can be unreadable.
4. Note how the PC is activated (Microsoft account, digital entitlement, or product key) and list the apps you'll need to reinstall if a method removes them.

Every recovery option sits on a ladder from fully reversible to gone forever. Climb it in order, and the risk to your data stays as low as possible for as long as possible.

• 1
  Reversible

  Safe Mode, driver/app rollback, remove an update, System Restore.

• 2
  Automated / low-risk repair

  Startup Repair, offline system-file repair (SFC/DISM).

• 3
  Reinstall, keep files

  Reset "keep my files", in-place repair install.

• 4
  Full wipe

  Reset "remove everything", clean install.

• 5
  Hardware

  Once software recovery is exhausted.

Three rules keep it safe: don't skip tiers; confirm each step actually stopped the loop before moving on; and once you cross into the destructive tiers there is no undo, so your backup and BitLocker key must already be in hand.

The diagram shows the shape of the process: a crash feeds the recovery environment, which offers the four method families, and any one of them can lead back to a stable system. The color of each method is its risk.

The whole ladder in one table, so you can see data risk, boot requirements and typical use side by side. Filter to the tier you're currently at.

10 methods

Use the Level column to stay in your lane — if you're still in the non-destructive tier, don't jump to a wipe. Each method's full steps live in its own guide in the series below.

Almost everything on this ladder lives in the Windows Recovery Environment (WinRE), so the first real step is getting there.

When Windows is looping, the usual route is to force a shutdown (hold the power button until it's off) and repeat it a few times — Windows then offers Automatic Repair, which drops you into the recovery environment's Advanced options. If that doesn't work, or the machine won't get that far, you boot from recovery media created on another PC; the same menu appears either way.

What you should see is a set of options under Troubleshoot → Advanced options — System Restore, Startup Repair, Uninstall Updates, Command Prompt, and UEFI Firmware Settings. If you can't reach that menu at all, the recovery partition or the hardware may be the problem, and that's a distinct case worth its own path.

Before any "big" tool, exhaust the reversible ones — they're fast, carry no data risk, and are often the actual fix.

In order: roll back the driver or uninstall the app that started it (if you can reach Safe Mode); remove the Windows update that preceded the crashes; then use System Restore to a point from before the problem. Each is more involved than the last, but all of them keep your personal files and can be undone.

If any of these stops the loop, stop there — you don't need the heavier options. If none do, that's the signal to move down the ladder, not to repeat the same step.

System Restore is the cleanest reversible fix — when a suitable point exists.

It rolls Windows back to a restore point, a snapshot of system files and drivers from a chosen date. It does not touch your documents or other personal files, but it does remove programs and drivers installed after that point, so a few things may need reinstalling. It's the right tool when you can name a "last good day" that's close to an available point.

If it fails, or no usable point exists, don't keep retrying — a failed restore has specific causes and specific next steps, covered in its own guide.

Two targeted tools for the "it won't boot" and "an update did it" cases.

Startup Repair is Windows' automatic attempt to fix boot problems. It's low-risk but narrow: it handles a specific set of common boot failures and will tell you plainly when it can't. A "Startup Repair couldn't repair your PC" result isn't a dead end — it just means the fault is outside its scope, so you escalate.

If the loop clearly began after an update, removing that update from WinRE is more targeted than a general repair and frequently the real fix. Quality and feature updates are removed differently, and rollback has limits — the dedicated guide covers which updates can be undone and what to do when one can't.

If the machine reaches Safe Mode, you have a stable place to act — and the most common cause of a new loop is a driver or app.

In Device Manager, roll back the recently changed driver (check GPU, network, storage, and chipset first) or uninstall a recently added program. Prefer rollback over uninstall when an older driver version is available — it's reversible. Then test a normal boot.

Be deliberate about driver sources: use the manufacturer's driver or Windows Update, not third-party "driver updater" sites, which can install the wrong version and re-break the machine. And if Safe Mode itself crashes, the fault is below the driver layer — move to offline repair.

When you can't boot normally, you can still repair the offline Windows installation from the recovery command prompt.

The standard pair is DISM (repairs the component store and system image) and SFC (repairs protected system files); offline, they point at a specific drive letter instead of the running system. This is the tier where a wrong command can do real harm, so identify the Windows volume first and stick to safe, well-documented commands.

Reset this PC reinstalls Windows — and the mode you pick changes everything.

"Keep my files" removes installed programs but preserves your personal files; "Remove everything" wipes the drive. If you only need your data, the keep-files mode is the lower-risk middle step; if the system is deeply broken and you can't keep apps anyway, a full remove is cleaner.

Reset can be started from Settings → Recovery (if you can boot) or from WinRE (if you can't). It's disruptive — you lose apps and settings — but it uses the local image and is a legitimate step before a manual clean install. When Windows won't boot, the process and the failure modes differ, so use the recovery-mode guide rather than guessing.

The strongest "keep everything" repair — when Windows can still boot.

An in-place repair install runs setup over your existing installation, replacing system files while, in most cases, keeping your files, settings, and apps. It's the right answer for a corrupted Windows that still reaches the desktop.

The key limitation: you generally must be able to boot (or at least run setup from a working state) to do it, and you need installation media that matches your edition. If the machine can't boot, an in-place repair is usually off the table and Reset or a clean install take over. Because "repair install" and "Reset" are commonly confused, there's a dedicated side-by-side comparison.

A clean install erases the drive and starts Windows from scratch — the definitive software fix, and genuinely last.

If the reversible and reinstall steps have all failed and the problem is a broken OS, a clean install resolves it. But it's fully destructive, so nothing about it should be rushed.

If a clean install fixes it, investigate the original trigger so it doesn't return. If a clean install from known-good media does not fix it, that is a strong sign the fault is hardware, not Windows.

Recovery tools fail more often than people expect — and a failure is information, not a dead end.

A System Restore that errors, a Startup Repair that "couldn't repair your PC," or a Reset that aborts each points somewhere. Common causes: no usable restore point, a corrupt recovery partition, an encrypted drive without its key, or hardware that no software fix can repair.

The pattern to watch: if several unrelated recovery methods fail in sequence, or a fresh clean install still crashes the same way, stop treating it as a Windows problem. At that point the most likely explanation is hardware.

Some crash loops are not software, and no amount of reinstalling will fix them.

The tells: crashes that only appear under load while the machine runs hot; a loop that began right after a hardware change; a drive reporting SMART or pred-fail warnings; memory that fails a diagnostic; or a machine stable for years that suddenly cycles.

The cleanest single test is a clean install from known-good media that still produces the identical crash — Windows can't be "misinstalled" the same way twice from the same media, so a repeat points at the silicon. Test RAM and storage before replacing anything, and back up first.

If you'd rather have a guided route than a map, answer a few questions and this will point you to the specific guide for your situation. It's a navigator, not a guarantee — and a full visual version lives in its own quick-reference page.

The whole path as tickable steps, in escalation order. Your progress is saved in this browser, so you can work through it across several sessions.

Recovery connects to the wider troubleshooting library. These guides naturally follow on.