To fix a Blue Screen of Death, note the stop code on the screen, undo the most recent change you made, and boot into Safe Mode if Windows will not start. From there you update or roll back drivers, run SFC and DISM to repair system files, test the RAM, and check temperatures and disk health. The stop code points you at the cause, and most blue screens trace back to a driver, faulty memory, corrupt system files, or overheating. Note that in Windows 11 version 24H2 the same crash now shows on a black screen rather than a blue one, but the fix is identical.
What Causes the Blue Screen of Death?
A blue screen is a stop error: Windows hits a fault it cannot safely recover from and halts to protect your data. Four causes account for most of them.
Faulty or incompatible drivers
Faulty RAM
Corrupt system files
Overheating and disk faults
The stop code on the screen narrows this down fast. A specific code such as DRIVER_POWER_STATE_FAILURE points straight at a driver, which the guide on driver power state failure walks through, while the full list is decoded in BSOD stop codes and their meanings.
How Do You Fix a Blue Screen of Death?
Work through these steps in order. The early steps are the quickest and resolve most cases, so stop as soon as the crashes do.
- Read the stop code. Note the keyword on the screen, such as MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL, and its hex value. This is your starting clue, so look it up before changing anything.
- Undo the most recent change. Crashes that started after a driver update, a Windows update, or new hardware usually trace to that change. Reverse it first, because it is the fastest fix.
- Boot into Safe Mode. If Windows will not start, force the recovery menu (power off during boot three times) and choose Safe Mode. It loads with minimal drivers, so a stable Safe Mode points to a third-party driver or app rather than hardware.
- Update or roll back drivers. In Device Manager, roll back the suspect driver, or uninstall it and install the latest version from the vendor. Graphics and network adapters are the usual culprits.
- Run SFC, then DISM. In an admin Command Prompt run
sfc /scannowto repair corrupt system files. If it cannot fix everything, runDISM /Online /Cleanup-Image /RestoreHealthand then SFC again. The detail lives in the guide on fixing corrupt system files. - Test the RAM. Run Windows Memory Diagnostic (mdsched.exe). If it reports errors, reseat the sticks and test them one at a time to find the bad module.
- Check temperatures and disk health. Clean dust from the fans, watch CPU and GPU temperatures under load, and run
chkdsk /scanplus a SMART check on your drive. If crashes persist, System Restore from Safe Mode returns Windows to a known-good point.
If a single named code keeps recurring, treat it as the fastest route to the cause: the meaning of each one, with its likely fix, is listed in common BSOD stop codes. A blue screen is also just one of a wider set of faults covered in the guide to common PC problems.
How Do You Read the Stop Code and Find the Failing Driver?
The stop code names the type of fault; the minidump file names the exact driver behind it.
- Read it off the screen. Modern Windows shows a plain-language keyword (for example PAGE_FAULT_IN_NONPAGED_AREA). On older releases the QR code linked to the same lookup; on 24H2 the screen instead prints the faulty driver name directly.
- Stop automatic restart. If the machine reboots too fast to read, disable automatic restart in Startup and Recovery, or in the recovery menu, so the screen stays up.
- Open the minidump. Each crash writes a file to C:\Windows\Minidump. Open it in WinDbg and run
!analyze -v; the IMAGE_NAME and FAULTING_MODULE fields name the driver that caused the crash. - Cross-check Event Viewer. Under Windows Logs, a System error logged at the crash time confirms the bug check and timing.
When Should You Suspect Hardware?
If the software steps above do not stop the crashes, the fault is most likely physical. Three signs point that way.
- Crashes survive Safe Mode. Safe Mode loads almost no third-party software, so blue screens there strongly suggest RAM, disk, or overheating rather than a driver.
- The codes keep changing. A different stop code on each crash is a classic sign of bad RAM, which corrupts whatever happens to be in memory at the time.
- Heat or load triggers it. Crashes that arrive only under gaming, rendering, or a warm room point at temperatures or a power supply that cannot hold up.
Confirm memory with Windows Memory Diagnostic, watch temperatures with a hardware monitor, and check the drive’s SMART status. A failing disk or a marginal stick of RAM needs replacing, not reconfiguring.
Last Thoughts on the Blue Screen of Death
A blue screen looks alarming, but it is a controlled stop, not a broken computer. The fastest path is almost always the same: read the stop code, undo whatever you changed last, and use Safe Mode to roll back a driver, repair system files with SFC and DISM, or run System Restore. Most cases end there. When they do not, the cause is usually hardware, and a memory test, a temperature check, and a disk health check will find it.
It is also worth knowing that the screen itself changed: Windows 11 version 24H2 shows the same stop error on a black screen rather than a blue one. The mechanism and the fixes are unchanged. A blue screen is one of many faults a PC can throw, and the hub on common PC problems connects this guide to the rest.
Key Takeaways:
- A blue screen is a stop error: Windows halts to protect data, so the machine is not broken by the crash itself.
- Start by reading the stop code and undoing your most recent change (a driver, an update, or new hardware).
- Use Safe Mode to roll back drivers, repair files with SFC and DISM, or run System Restore when Windows will not boot normally.
- Persistent crashes that survive Safe Mode point to hardware: test the RAM, check temperatures, and check disk health.
- Most blue screens come from drivers, faulty RAM, corrupt system files, or overheating, not from a virus.
- In Windows 11 version 24H2 the crash screen is now black, not blue, but it is the same mechanism and the same fixes apply.
Frequently Asked Questions (FAQs)
What is the first thing to do when you get a Blue Screen of Death?
Write down the stop code shown on the screen, then think about what changed just before the crash, such as a new driver, update, or piece of hardware. Undoing that most recent change, or booting into Safe Mode if the system will not start, resolves the majority of blue screens.
Why is my Windows 11 crash screen black instead of blue?
Microsoft replaced the blue crash screen with a black one in Windows 11 version 24H2, delivered through update KB5062660. It is the same stop-error mechanism with a simpler layout: the screen still shows the stop code and now names the faulty driver, but the frowny face and QR code have been removed.
How do I fix a blue screen if Windows will not start?
Force the recovery menu by powering off during boot three times, then choose Startup Settings and boot into Safe Mode. From Safe Mode you can roll back the last driver, uninstall a recent update, or run System Restore to return to a working state.
Can a Blue Screen of Death damage my computer?
The crash itself does not damage hardware; it is a safety stop that halts Windows to prevent corruption. Repeated blue screens can point to a real hardware fault such as failing RAM, an overheating component, or a dying disk, which is what needs attention.
Is the Blue Screen of Death caused by a virus?
Usually no. Most blue screens come from faulty drivers, bad RAM, corrupt system files, or overheating rather than malware. Some malware can trigger crashes, so a scan is worth running, but driver and hardware checks resolve far more cases.
What do SFC and DISM do for a blue screen?
SFC (sfc /scannow) scans Windows for corrupt or missing system files and repairs them from a local cache. DISM (DISM /Online /Cleanup-Image /RestoreHealth) repairs that cache itself from Windows Update, so you run DISM first when SFC cannot fix everything, then run SFC again.
