How to Fix a Computer Stuck in a Boot Loop
A boot loop is when your computer starts to power on, begins loading Windows, and then restarts automatically — over and over, never reaching the desktop. You see the manufacturer logo or the Windows loading animation, then the screen goes black, and the startup process begins again. Sometimes you get a brief error message (a blue screen or an automatic repair prompt) before the restart. Sometimes the restart happens so fast you cannot read anything. Boot loops have several distinct causes, and the fix depends on what changed right before the loop started.
What causes boot loops
A boot loop means something in the startup sequence is failing badly enough that Windows cannot continue loading, and the automatic restart-on-failure setting kicks in before you can see the error. The most common triggers:
- Bad Windows update: A partially installed or incompatible update corrupts boot-critical files. This is the most common cause — the computer was fine before the update, and now it loops
- Driver conflict: A newly installed or automatically updated driver (especially GPU, chipset, or storage controller drivers) causes a crash during startup. The driver loads, crashes, triggers a restart, and the cycle repeats because the driver loads again on the next attempt
- Corrupted system files: One or more files that Windows needs to start (the Boot Configuration Data, the registry hives, or core system DLLs) are damaged. Power loss during a write operation is a common cause
- Failing storage drive: The drive containing Windows has bad sectors in the area where boot files are stored. The system tries to read those sectors, fails, and restarts. SSD firmware bugs can also cause this
- Overheating: The CPU reaches its thermal shutdown temperature during the boot process. This usually means the cooler is not making proper contact, the thermal paste has dried out, or the fans are dead. The system powers off to protect the CPU and then restarts because the power supply is still on
- Bad RAM: A faulty memory module causes data corruption during the boot process. Errors appear in different places each cycle because the corruption is random
- Recent hardware change: A new SSD, RAM stick, or GPU installed improperly or incompatible with the system can prevent boot
Fix 1: Let Windows attempt automatic repair
Windows 10 and 11 detect repeated boot failures and eventually enter the Windows Recovery Environment (WinRE) automatically. If your computer has looped three or more times, it should show a blue Automatic Repair screen or a Choose an option screen. If you see this:
- Select Troubleshoot, then Advanced options
- Try Startup Repair first — it scans for and attempts to fix common boot problems automatically. It takes 5 to 15 minutes and restarts when done
- If Startup Repair says it could not fix the problem, return to Advanced options for the other fixes below
If the computer restarts too fast for Windows to detect the failure pattern, force it: power on the computer and as soon as you see the manufacturer logo or Windows loading animation, press and hold the power button to force a shutdown. Repeat this three times. On the fourth attempt, Windows should enter WinRE.
Fix 2: Boot into Safe Mode
Safe Mode loads Windows with only essential drivers and services, bypassing the problematic driver or software that causes the loop:
- From the WinRE screen, go to Troubleshoot, Advanced options, Startup Settings, Restart
- After the computer restarts to the Startup Settings screen, press 4 (Safe Mode) or 5 (Safe Mode with Networking)
- If Windows boots successfully in Safe Mode, the boot loop is caused by a driver, service, or startup program — not a fundamental system file corruption
In Safe Mode, try these:
- Uninstall recent Windows updates: Settings, Windows Update, Update history, Uninstall updates. Look for updates installed on or just before the date the boot loop started. Uninstall them, newest first
- Roll back a driver: Open Device Manager, expand the category of the recently updated driver (usually Display adapters for GPU drivers), right-click the device, Properties, Driver tab, Roll Back Driver. If the button is grayed out, the previous driver is not available — use Uninstall device instead, then restart and let Windows install a generic driver
- Disable startup programs: Open Task Manager (Ctrl+Shift+Esc), go to the Startup tab, and disable everything. Restart normally. If the boot loop is gone, re-enable startup items one at a time to find the culprit
- Run System File Checker: Open Command Prompt as administrator and run
sfc /scannow. This checks Windows system files for corruption and replaces damaged files from a cached copy. Takes 10 to 20 minutes
Fix 3: Uninstall recent update from WinRE
If you cannot reach Safe Mode (the computer loops before Startup Settings appears or crashes in Safe Mode too), uninstall updates directly from WinRE:
- From WinRE, go to Troubleshoot, Advanced options, Uninstall Updates
- Choose Uninstall latest quality update (for monthly cumulative updates) or Uninstall latest feature update (for major Windows version upgrades)
- The process takes 5 to 15 minutes. Restart when prompted
This is the fix that resolves the majority of update-caused boot loops.
Fix 4: Use System Restore
System Restore reverts Windows system files, drivers, and registry to a previous state without affecting your personal files:
- From WinRE, go to Troubleshoot, Advanced options, System Restore
- Select a restore point dated before the boot loop started. If multiple restore points exist, pick the most recent one that predates the problem
- The restore takes 15 to 30 minutes. Do not interrupt it — power loss during a restore can cause worse corruption
System Restore only works if restore points exist. If you see no restore points available, this option will not help and you need to try the command-line fixes instead.
Fix 5: Rebuild boot configuration from Command Prompt
If the Boot Configuration Data (BCD) is corrupted, Windows cannot find or load its own boot files. To rebuild it:
- From WinRE, go to Troubleshoot, Advanced options, Command Prompt
- Run these commands in order:
bootrec /fixmbr — rewrites the master boot record without affecting the partition table
bootrec /fixboot — writes a new boot sector to the system partition. If you get an Access is denied error, run bootsect /nt60 sys first, then retry
bootrec /rebuildbcd — scans all drives for Windows installations and rebuilds the BCD store. When prompted to add an installation to the boot list, type Y and press Enter
After running all three commands, type exit and restart the computer.
Fix 6: Run DISM from recovery
If SFC cannot repair files because the cached copies are also corrupted, DISM can restore them. From the WinRE Command Prompt:
DISM /Online /Cleanup-Image /RestoreHealth
This downloads fresh copies of corrupted system files from Windows Update (requires internet access from WinRE, which may require Safe Mode with Networking instead). If you have no internet access in recovery, you can use a Windows installation USB as a repair source by adding the source flag and pointing it to the install.wim file on the USB drive.
Fix 7: Check for hardware problems
If no software fix resolves the boot loop, the cause is likely hardware:
RAM
Bad RAM causes random corruption that manifests differently each boot cycle. From WinRE Command Prompt, run mdsched to launch Windows Memory Diagnostic, or boot from a USB drive with MemTest86 for a more thorough test. If you have multiple RAM sticks, try booting with only one stick at a time — if the loop stops with a specific stick removed, that stick is faulty.
Storage drive
A failing SSD or HDD causes boot loops when it cannot reliably read boot files. From WinRE Command Prompt, run chkdsk C: /r — this checks for and attempts to recover data from bad sectors. Takes 30 minutes to several hours depending on drive size. If chkdsk finds a large number of bad sectors (more than a few), the drive is failing and needs replacement. Check the drive SMART data if you can boot from a USB drive — look for Reallocated Sector Count, Current Pending Sector Count, and Uncorrectable Sector Count values above zero.
Overheating
Enter BIOS (press Delete, F2, or F12 during startup — the key varies by manufacturer) and check the CPU temperature reading. If the CPU is above 80 degrees Celsius at idle in BIOS (before Windows even loads), the cooler is not working. Check that the cooler fan spins, that the cooler mounting screws are tight, and that thermal paste has not dried to a chalk-like consistency. On laptops, check that the air vents are not blocked by dust.
Recent hardware changes
If you recently installed new hardware (RAM, GPU, SSD, any expansion card), remove it and try booting with the original hardware. If the boot loop stops, the new hardware is either incompatible, defective, or not properly seated in its slot. Reseat it firmly and try again — a GPU or RAM stick that is not fully clicked into place can cause boot loops that mimic software problems.
Fix 8: Reset Windows (keep files)
If nothing above works and the drive is healthy, a Windows reset reinstalls the operating system while preserving your personal files. From WinRE, go to Troubleshoot, Reset this PC, Keep my files. This removes all installed applications and drivers and reinstalls Windows from the recovery partition. It takes 30 to 60 minutes. You will need to reinstall your applications afterward.
Computer repair in Columbus and Delaware County
LuxuriousComputers diagnoses and repairs boot loop issues — identifying whether the cause is a bad update, corrupted files, failing hardware, or driver conflict, and applying the targeted fix.
Related Articles
More Articles
Browse our full library of guides and tutorials.