How to Fix Blue Screen Errors in Windows 11 and 10

A Windows blue screen—also called a stop-code error, bug check, or BSOD—appears when Windows encounters a serious kernel-level problem and stops to protect the system. A driver, hardware failure, low-level security or virtualization software, corrupted system files, or a recent update can be responsible. The stop code is a clue, not a complete diagnosis.

First: record the error

Take a photo of the screen before Windows restarts. Record:

• the exact stop code, such as MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA;
• the name shown after What failed, if present;
• what you were doing when it happened;
• any hardware, driver, Windows update, security tool, game, or application installed shortly beforehand;
• whether the crash happens at startup, during sleep/resume, under graphics load, or at random.

One isolated crash after a power event is different from a repeatable crash. Microsoft's stop-code troubleshooting page explains the information Windows displays.

Protect your data before extensive testing

A blue screen does not normally delete saved files by itself, but open documents may lose unsaved changes. More importantly, repeated crashes caused by failing memory or storage can corrupt data. If Windows still starts, back up important files before running repairs, resizing partitions, resetting Windows, or repeatedly stressing the machine.

If the drive clicks, disappears from firmware or Disk Management, reports health errors, or the laptop has liquid or impact damage, minimize use and seek professional diagnosis. Continued writes can make data recovery harder.

1. Undo the most recent change

Shut down and disconnect newly added nonessential hardware such as USB adapters, docks, external drives, expansion devices, or extra displays. Restart and test. If the crash began after installing an app, driver, or update, remove or roll back that specific change rather than updating everything at once.

For a recent driver:

1. Right-click Start and open Device Manager.
2. Open the device's Properties > Driver tab.
3. Choose Roll Back Driver when available, restart, and retest.

If the driver must be reinstalled, download the correct package from the laptop or component manufacturer's official support page first. Do not use a generic driver-updater utility.

2. Install supported Windows updates

If Windows remains usable, open Settings > Windows Update, install pending recommended updates, and restart. Check Optional updates only for a driver relevant to the failing device. Avoid installing several unrelated optional drivers during diagnosis because that makes cause and effect harder to identify.

3. Start Windows in Safe Mode

Safe Mode loads a limited set of drivers and services. If the PC is stable there, a third-party driver, service, startup app, or device becomes more likely.

From a working desktop, hold Shift while selecting Power > Restart. In Windows Recovery Environment choose Troubleshoot > Advanced options > Startup Settings > Restart, then select Safe Mode. If Windows repeatedly fails to start, it may enter the recovery environment automatically.

Safe Mode is a diagnostic environment, not proof of a single cause. Back up data and remove only the most likely recent change.

4. Use a clean boot to isolate software conflicts

If normal Windows crashes but Safe Mode is stable, a clean boot can isolate a non-Microsoft service or startup program:

1. Press Windows + R, enter msconfig, and open System Configuration.
2. On Services, select Hide all Microsoft services before choosing Disable all.
3. On Startup, open Task Manager and disable enabled startup apps.
4. Restart and test the action that normally causes the crash.
5. If stable, re-enable items in groups until the problem returns, then narrow the group.
6. Restore normal startup when testing is complete.

Do not skip “Hide all Microsoft services”; disabling core services can create new problems. TipsMake's Windows 11 clean-boot guide shows the process and how to return to normal startup.

5. Check Windows system files

When crashes follow an interrupted update or other signs of system corruption, open Terminal or Command Prompt as administrator. Run DISM first:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for it to finish successfully, then run:

sfc /scannow

Do not close the window until verification reaches 100%. Restart and retest. These tools repair Windows components and protected system files; they do not diagnose defective RAM, a failing SSD, or an incompatible third-party driver. Microsoft's DISM and SFC instructions explain the result messages.

6. Test memory and storage

Memory

Search for Windows Memory Diagnostic, choose to restart and check, then allow the test to complete. A reported error is significant and should be followed by model-specific hardware service or more extensive testing. Passing one quick test does not rule out every intermittent RAM fault.

On systems with removable memory, reseating or testing modules individually can help, but only if the laptop's service manual permits it and you are comfortable with electrostatic-discharge precautions. Otherwise, use a qualified technician. TipsMake's RAM testing guide explains how to retrieve the Windows diagnostic result.

Storage

Back up first, then check the drive manufacturer's health and diagnostic tools. File-system checks can modify metadata, so do not start repair commands blindly on a disk that may be physically failing or contains the only copy of valuable data.

Low free space can interfere with updates and dump creation, but it does not explain every stop code. Free space safely through Settings > System > Storage rather than deleting unfamiliar Windows folders.

7. Check overheating and unstable hardware settings

Return CPU, GPU, and RAM overclocks, undervolts, and custom memory profiles to supported defaults while testing. Use the laptop on a hard surface, clear blocked external vents, and run the manufacturer's diagnostics. Do not disassemble a system under warranty or blow debris deeper into the chassis.

Crashes under sustained load can be caused by heat, power delivery, memory, or the GPU; temperature alone is not a diagnosis. WHEA-related stop codes deserve particular attention to hardware, firmware, and official driver updates.

8. Scan for malware when there are other warning signs

Open Windows Security > Virus & threat protection > Scan options and run an appropriate scan. An offline scan can be useful when persistent malware is suspected. Malware is only one possible cause, so a clean scan should not end hardware or driver diagnosis.

Do not install multiple real-time antivirus products to “double-check”; competing low-level drivers can themselves create instability.

Do not guess from the stop code alone

Stop code example	Common areas to investigate	What not to assume
PAGE_FAULT_IN_NONPAGED_AREA	Driver, RAM, storage corruption, security/filter software	It does not automatically prove RAM is defective
MEMORY_MANAGEMENT	RAM stability, driver memory corruption, system files	Replacing memory is not the first step without testing
WHEA_UNCORRECTABLE_ERROR	Hardware, firmware, power, thermals, supported drivers	A Windows reinstall cannot repair failed hardware
VIDEO_TDR_FAILURE	Graphics driver, GPU stability, heat, power, hardware	The newest graphics package is not always the most stable for a specific laptop

The module named on the screen may be where Windows detected corruption rather than the component that caused it. Correlate the code with timing, recent changes, diagnostics, and crash dumps.

Advanced evidence: Reliability Monitor and dump files

Search for View reliability history to see crashes, failed updates, and application installations on a timeline. Event Viewer can confirm that an unexpected shutdown occurred, but a generic Kernel-Power event usually records the consequence, not the root cause.

Windows may store small crash dumps in C:WindowsMinidump. Experienced users or support technicians can analyze them with Microsoft's debugging tools. Avoid uploading dumps publicly without considering privacy because memory data can contain device, path, and process information.

Use Windows recovery options in the right order

If the problem began recently, use the least destructive option that matches the change:

• Startup Repair: when Windows does not start.
• Uninstall Updates: when a recent Windows update clearly preceded the issue.
• System Restore: when a restore point exists from before a driver, app, or settings change.
• Reinstall Windows using Windows Update: for supported repair scenarios while preserving apps, files, and settings where the option is available.
• Reset this PC: a later resort when narrower repairs fail.
• Clean installation: a final software step after backup, license, encryption-key, and driver preparation.

Review Microsoft's Windows recovery-options table before choosing. “Keep my files” during Reset removes applications and settings and is not a substitute for a backup. Save the BitLocker recovery key before entering recovery tools on an encrypted device.

When to stop troubleshooting at home

Seek professional service when the laptop has liquid or impact damage, a burning smell, battery swelling, abnormal heat, storage health warnings, repeated WHEA errors, memory-test failures, crashes before Windows loads, or important files that are not backed up. Also stop if opening the case would breach warranty terms or the repair requires soldered components.

Give the technician the stop-code photos, crash pattern, recent-change timeline, diagnostic results, and any dump files. That evidence is more useful than saying only that the laptop “sometimes turns blue.”

A safe troubleshooting order

1. Photograph the error and note recent changes.
2. Back up important data.
3. Disconnect newly added hardware and reverse the most likely recent change.
4. Install relevant supported updates.
5. Compare normal startup with Safe Mode, then use a clean boot if appropriate.
6. Run DISM and SFC when system corruption is plausible.
7. Test memory, storage, thermals, and manufacturer diagnostics.
8. Use a matching Windows recovery option only after preserving data and keys.
9. Obtain professional help for hardware warnings or unresolved repeated crashes.