Blue Screen or Boot Loop — First Steps

Applies to: Windows 7, 8, 8.1, 10, and 11 — Desktop PCs and laptops of all makes and models. Blue screens and boot loops are among the most alarming things a Windows user can experience — but in most cases they are fixable without losing your data.

🚨 STAY CALM: A blue screen or boot loop looks terrifying but it does not automatically mean your PC is destroyed or your data is gone. In many cases the cause is a software issue, a recent driver update, or a failed Windows update — all of which are fixable. Work through this guide carefully before assuming the worst.

💙 What is a Blue Screen of Death (BSOD)? A Blue Screen of Death — or BSOD — is Windows’ way of protecting itself when it encounters a critical error it cannot recover from. Windows stops everything, displays a blue screen with an error code, and restarts. A single occasional BSOD can happen to any PC. Repeated BSODs or a PC stuck in a boot loop — where it restarts over and over without ever fully loading Windows — indicates a problem that needs to be addressed.

⚠️ Common Causes of Blue Screens and Boot Loops:

A recently installed driver that is incompatible or corrupted
A Windows update that failed or installed incorrectly
Failing or faulty RAM
A failing hard drive or SSD with bad sectors
Corrupted Windows system files
Overheating causing the system to crash
A newly installed hardware component causing a conflict
Malware that has corrupted critical system files
A failing power supply unit delivering unstable power

⚡ Act ASAP — When You See a Blue Screen or Boot Loop

When a blue screen appears or your PC is stuck in a restart loop, here is what to do immediately.

1

Read and write down the error code. When a blue screen appears, look for the error code displayed on the screen — it usually appears as a short phrase in capital letters such as IRQL_NOT_LESS_OR_EQUAL or SYSTEM_SERVICE_EXCEPTION, and sometimes as a code like 0x0000007E. Write it down or take a photo with your phone — this code is your biggest clue to what went wrong.
2

Note what you were doing when it happened. Was a program open? Did it happen immediately after installing something? Did it occur during a Windows update? The circumstances surrounding the crash are important clues for diagnosis.
3

Allow Windows to restart on its own. After a blue screen, Windows will usually attempt to restart automatically. Allow it to do so and watch what happens — does it load normally, show another blue screen, or get stuck in a loop?
4

If stuck in a boot loop — interrupt it. If Windows keeps restarting without ever loading the desktop, you need to interrupt the loop to access recovery options. Hold the power button for 5 seconds to force it off, wait 10 seconds, then power on again. After two or three failed boot attempts Windows 10 and 11 will automatically enter the Windows Recovery Environment — a special menu with repair tools.
5

Do not panic about your data. A blue screen or boot loop does not automatically mean your files are gone. In most cases your data is still intact on the drive — the issue is with Windows itself, not your personal files.

⚠️ Do NOT Do This

Do NOT repeatedly restart the PC over and over hoping it will fix itself. Repeated forced restarts during a boot loop can corrupt Windows files further and make recovery harder.
Do NOT immediately reinstall Windows as your first response. A Windows reinstall should be a last resort — most blue screen and boot loop issues can be resolved without losing your data or reinstalling Windows.
Do NOT ignore the error code. The error code on the blue screen is Windows telling you exactly what went wrong. Searching that error code online will often lead you directly to the solution.
Do NOT install new software or drivers while trying to resolve a blue screen issue — adding new software during a crisis can complicate diagnosis and make things worse.
Do NOT assume your data is lost without attempting recovery first. Even in severe cases, data recovery from a blue-screening PC is often possible.
Do NOT skip backing up your data once you regain access to Windows. After a blue screen event, back up your important files immediately in case the underlying cause leads to further instability.

🔧 Step by Step — Diagnosing and Recovering

1

Search the error code online. Take the error code you wrote down or photographed and search for it online using another device such as your phone. Microsoft’s own support site and many reliable tech communities have specific solutions for most BSOD error codes.
2

Try booting into Safe Mode. Safe Mode starts Windows with only the most essential drivers and services — bypassing most of what could be causing the blue screen. To access Safe Mode, restart the PC and press F8 repeatedly before Windows loads, or access it through the Windows Recovery Environment. If Windows loads successfully in Safe Mode, the problem is likely caused by a driver, program, or service.
3

Uninstall any recently installed drivers or programs. If the blue screen started after installing a new driver, program, or Windows update, uninstalling it is often the fastest fix. In Safe Mode go to Settings — Apps to remove recently installed software, or Device Manager to roll back a recently updated driver.
4

Use Windows Recovery Environment. If you cannot boot into Windows at all, access the Windows Recovery Environment by interrupting the boot process three times — Windows 10 and 11 will enter it automatically. From here you can access Startup Repair, System Restore, Command Prompt, and other recovery tools.
5

Run Startup Repair. Inside the Windows Recovery Environment, select Troubleshoot — Advanced Options — Startup Repair. Windows will attempt to automatically diagnose and fix the issue preventing it from loading. This resolves many boot loop situations without any manual intervention.
6

Use System Restore. If the blue screens started recently and you have a restore point from before the problem began, System Restore can roll Windows back to a working state without affecting your personal files. Access it through the Windows Recovery Environment under Advanced Options — System Restore.
7

Run the System File Checker. Corrupted Windows system files are a common cause of blue screens. Open Command Prompt — either in Safe Mode or through the Recovery Environment — and type: sfc /scannow — this will scan and repair corrupted system files automatically.
8

Run a memory diagnostic. Faulty RAM is a frequent but often overlooked cause of blue screens. Run the Windows Memory Diagnostic tool by searching for it in the Start menu or accessing it through the Recovery Environment. Allow it to complete — it will report any memory errors found.
9

Check the hard drive health. A failing hard drive can cause blue screens and boot loops. In Command Prompt type: chkdsk C: /f /r to schedule a disk check on the next restart. Listen for any clicking or grinding sounds from the drive — these are signs of imminent physical failure and the drive should be replaced immediately.
10

Check for overheating. If the blue screens happen after the PC has been running for a while or during demanding tasks, overheating may be forcing the crash. Check temperatures using HWMonitor after the PC boots and refer to our Extreme Heat or Summer Overheating guide if temperatures are excessive.
11

Remove recently added hardware. If new hardware was recently installed — RAM, a graphics card, a new drive — remove it and test whether the blue screens stop. A hardware conflict or incompatible component is a common cause of sudden blue screen issues.
12

Reset or reinstall Windows as a last resort. If all other steps fail and the PC cannot be stabilized, a Windows Reset — which can preserve your personal files — or a clean reinstall of Windows may be necessary. This should only be done after exhausting all other options and after backing up your data.

💡 Tip: The error code displayed on a blue screen is one of the most valuable diagnostic tools available. Even a quick search of the error code on your phone while sitting in front of the blue-screened PC will often point you directly to the cause and solution. Never ignore or dismiss the error code — write it down every time.

✅ How to Know the Emergency is Over

The blue screen or boot loop emergency is resolved when all of the following are true:

✅ Windows loads successfully and reaches the desktop without blue screening
✅ The PC runs stably through normal tasks without crashing or restarting
✅ The root cause has been identified and addressed — faulty driver removed, update rolled back, RAM replaced, or drive repaired
✅ System File Checker and disk check have completed without critical errors
✅ The PC has run stably for several hours or through a full day of normal use

✅ Important data has been backed up to a safe external location

✅ Windows is fully up to date with no pending failed updates

Even after resolving a blue screen issue, monitor the PC closely over the following days. If blue screens return — even occasionally — the underlying cause may not have been fully resolved and further investigation is needed.

🔁 If the Problem Persists

If blue screens or boot loops continue after working through all the steps in this guide, there are two paths forward:

Continue troubleshooting: If you are comfortable with advanced diagnostics, further steps such as testing RAM sticks individually, replacing a suspected failing hard drive or SSD, updating the motherboard BIOS, or performing a clean reinstall of Windows may resolve persistent issues.

Seek professional help: If you are unsure of the cause, cannot access Windows at all, or have exhausted the steps above without success, we strongly recommend taking your PC to a qualified repair technician. A technician can perform in-depth hardware and software diagnostics, recover data from an unstable system, and identify the exact cause of the blue screens — whether it is hardware failure, driver conflicts, or corrupted system files.

Remember — persistent blue screens are a serious warning sign that should not be ignored. The sooner the cause is identified and resolved, the less risk there is of permanent data loss or hardware damage.