How to Fix Blue Screen of Death (BSOD) Error on Windows 10/11

The Blue Screen of Death (BSOD) is one of the most alarming errors you can see on a Windows PC. Also known as a stop error or bug check, it appears when Windows encounters a critical problem that it cannot recover from, so it crashes to prevent further damage.

When a blue screen occurs, the system stops, the screen turns blue, and Windows shows:

• A brief error message (e.g., “Your PC ran into a problem and needs to restart”), and
• A stop code such as MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, etc.

Well, BSOD errors can be caused by:

• Faulty or incompatible device drivers
• Hardware failures (RAM, disk, GPU, power supply)
• Corrupted system files
• Software conflicts or buggy third‑party apps
• Malware infections
• Overheating or power issues

This Article explains:

• What BSOD errors are and what causes them
• The most common BSOD stop codes and what they usually mean
• A step‑by‑step troubleshooting checklist that works for Windows 10 and Windows 11
• When you should move on to more advanced or specific guides

What Is a Blue Screen of Death (BSOD)?

A Blue Screen of Death (BSOD) is a critical stop error that occurs when Windows detects a problem it cannot safely recover from. To prevent damage or data loss, Windows:

• Immediately stops all running processes
• Shows a blue screen with an error message and a stop code
• Creates a memory dump file with technical details so the problem can be analyzed later
• Then restarts the computer

A BSOD is not just a random crash. It usually means something is seriously wrong with:

• Hardware (RAM, disk, GPU, motherboard, power),
• Drivers, or
• Core system components.

Understanding the stop code and the context (what you were doing and what changed recently) is key to fixing it.

What Causes Blue Screen of Death (BSOD) Errors?

Blue screen errors usually appear when Windows hits a serious low‑level problem that it cannot safely recover from. Some of the most common real‑world causes are:

• Driver issues – Device drivers are small pieces of software that enable Windows to communicate with your hardware (graphics card, network adapter, storage controller, etc.). If a driver is outdated, buggy, or incompatible, it can access memory incorrectly or crash the kernel, causing a BSOD.
• Hardware problems – Failing RAM, damaged hard drives/SSDs, overheating GPUs or CPUs, or a weak power supply can all cause sudden crashes and blue screens. In many cases, repeated BSODs are the first sign of hardware problem.
• Software conflicts – Poorly coded or incompatible third‑party software (especially antivirus, VPN, backup tools, tweaking utilities) can hook deeply into the system and conflict with Windows, leading to blue screens.
• Corrupted or missing system files – System files are critical for Windows to start and run safely. If these files become corrupted or go missing (due to a bad update, a sudden shutdown, malware, or disk errors), Windows can become unstable and crash with various BSOD codes.
• Malware or viruses – Malicious software can modify system files, inject rogue drivers, or interfere with core services, which often results in crashes instead of normal error messages.
• Overheating and power issues – If components run too hot, they may start to behave unpredictably. Likewise, unstable power from a failing PSU can cause sudden shutdowns and BSODs under load.

Sometimes a BSOD is just a one‑time glitch, but if it keeps happening, you should assume there’s a deeper problem with drivers, hardware, or system files and start troubleshooting.`1

First Steps When You See a BSOD

When a Blue Screen appears:

1. Note the stop code (and any file name like ntoskrnl.exe, nvlddmkm.sys, etc.) – This will help you find more specific solutions later.
2. Let Windows collect the memory dump and restart. Don’t power off abruptly unless it’s stuck.
3. After reboot, note if the error happens:
   • Only once, or
   • Every time you start Windows or run specific apps/games.

If it happens more than once, follow the checklist below.

Disconnect External Devices

External devices such as USB drives, printers, scanners, and external hard disks load their own drivers and can sometimes conflict with Windows or with each other. By disconnecting them, you create a more controlled environment and can quickly see whether a specific device or its driver is behind the BSOD.

1. Shut down your computer completely.
2. Unplug all external devices except keyboard and mouse:
   • USB drives and external HDDs/SSDs
   • Printers, scanners, webcams
   • Game controllers, docking stations, etc.
3. Power on your PC and use it normally.

• If the BSOD does not occur again, reconnect devices one by one until you find the one causing the problem.
• If the BSOD still occurs, continue with the next steps.

Start Windows in Safe Mode

If you frequently get a Windows blue screen error during normal startup, booting into Safe Mode can help. In Safe Mode, Windows loads only essential drivers and services, create a clean environment for troubleshooting such problems.

If you can still boot into Windows

1. Press and hold the Shift key.
2. Click Start > Power > Restart while holding Shift.
3. On the Choose an option screen, click Troubleshoot > Advanced options > Startup Settings > Restart.
4. After restart, press 4 (or F4) for Safe Mode, or 5 (F5) for Safe Mode with Networking.

Alternatively, you can:

1. Press Windows + R, type msconfig and press Enter.
2. Go to the Boot tab.
3. Under Boot options, check Safe boot and select Minimal.
4. Click Apply, then OK, and restart.

If Windows won’t boot normally

If your system restarts too quickly or you can’t reach the desktop:

• Boot from Windows 10/11 installation media (USB/DVD),
• Choose Repair your computer > Troubleshoot > Advanced options > Startup Settings, then restart and choose Safe Mode.

In Safe Mode, see if the BSOD still appears:

• If there is no BSOD in Safe Mode, the problem is likely related to drivers, third‑party software, or startup apps.
• If BSODs still happen even in Safe Mode, suspect hardware or deep system corruption.

Disable Fast Startup

Fast Startup makes Windows boot faster by partially saving the system state to disk when you shut down. On some systems, this “hybrid” startup can cause driver initialization problems or prevent hardware from fully resetting, which may trigger blue screen errors. Disabling Fast Startup helps some users fix the Blue Screen of Death error on their computers.

1. Open the Control Panel and go to Power Options.
2. Click Choose what the power buttons do.
3. Click Change settings that are currently unavailable.
4. Under Shutdown settings, uncheck Turn on fast startup (recommended).
5. Click Save changes and restart your PC.

Check whether the BSOD still occurs.

Update, Roll Back, or Reinstall Device Drivers

Device drivers enable communication between Windows and your hardware. If they’re outdated, corrupt, or simply not designed for your version of Windows, they can cause the system to access invalid memory or hardware states and crash with a BSOD. Updating or rolling back drivers often resolves blue screens that started right after you installed new hardware or a driver update.

Update drivers

Updating fixes known bugs and compatibility issues, especially if BSODs started after a recent hardware or Windows update.

1. Right‑click the Start button and choose Device Manager.
2. Look for devices with a yellow warning icon, or for devices recently installed or changed (especially Display adapters, Network adapters, Storage controllers).
3. Right‑click the device and select Update driver.
4. Choose Search automatically for updated driver software.

You can also download the latest drivers directly from:

• Your PC or motherboard manufacturer (Dell, HP, Lenovo, ASUS, etc.),
• Or the hardware vendor (NVIDIA, AMD, Intel, Realtek, etc.).

Roll back a driver

If BSODs started right after you updated a driver:

1. In Device Manager, right‑click the device and choose Properties.
2. Go to the Driver tab.
3. Click Roll Back Driver if the option is available.
4. Follow the prompts and restart your PC.

Reinstall a driver

Reinstalling is helpful when a driver installation became corrupted

1. In Device Manager, right‑click the problem device and select Uninstall device.
2. Check Delete the driver software for this device if available, then click Uninstall.
3. Restart your PC. Windows will try to reinstall the driver automatically, or you can install the latest version from the manufacturer’s website.

You can also refer to our detailed article explains how to update or reinstall device drivers on windows 11/10

Repair Windows System Files (SFC and DISM)

Corrupted or missing system files are another very common reason for frequent BSODs. System files are essential for Windows to boot, manage memory, and communicate with hardware. If they become damaged (for example, after a bad update, sudden power loss, malware, or disk errors), Windows can crash with different blue screen error codes. The SFC and DISM tools scan these files and replace or repair any that are broken.

Run SFC (System File Checker)

1. Press Windows + S, type cmd.
2. Right‑click Command Prompt and choose Run as administrator.
3. In the Command Prompt, type: sfc /scannow and press Enter.
4. Wait for the scan to reach 100%. If SFC finds issues, it will try to repair them.
5. Restart your computer.

Run DISM (Deployment Image Servicing and Management)

If SFC cannot repair everything or BSODs continue:

1. Open Command Prompt as administrator again.
2. Run the following command: DISM /Online /Cleanup-Image /RestoreHealth
3. Wait for the command to finish scanning 100% (this may take a while).
4. Restart your PC and run sfc /scannow again.

After SFC and DISM complete, restart your PC. If the BSODs were caused by system file corruption, they often stop or at least become less frequent.

Check for Disk Errors (CHKDSK)

Your system drive holds both Windows system files and your page file. If the disk develops bad sectors or the file system becomes corrupted, Windows may try to read or write to damaged areas, causing a blue screen crash. The chkdsk command scans the drive for errors and attempts to repair them, which can fix BSODs related to disk problems.

1. Open Command Prompt as administrator.
2. Type: chkdsk C: /f /r and press Enter.
3. When prompted to schedule the check on next restart, type Y and press Enter.
4. Restart your PC and let CHKDSK run. This may take some time, depending on the drive size and number of errors.

Afterward, check if BSODs are reduced or gone. If CHKDSK reports serious problems, back up your data and consider replacing the drive.

Test RAM with Windows Memory Diagnostic

Faulty RAM (memory) is a very common cause of BSODs.

Faulty or unstable RAM (memory) is one of the most common causes of BSODs such as MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA. The Windows Memory Diagnostic tool runs a series of tests on your RAM to detect hardware errors that normal use may not reveal.

1. Press Windows + R, type: mdsched.exe and press Enter.
2. In the Windows Memory Diagnostic window, click Restart now and check for problems.
3. Let the test run. Your PC will reboot, test the memory, and restart again.
4. After logging in, check the results in Event Viewer if needed.

If the tool finds errors, test each RAM stick individually and replace any faulty modules

Optional: Reset virtual memory to automatic

If you have previously changed the virtual memory (page file) settings to a custom size, set them back to “Automatically manage paging file size for all drives”. Incorrect page file settings can sometimes contribute to memory‑related BSODs.

• Right‑click This PC and choose Properties → Advanced system settings.
• Under Performance, click Settings → go to the Advanced tab → click Change… under Virtual memory.
• Check Automatically manage paging file size for all drives, click OK, then restart your PC.

Check for Windows Updates

Microsoft frequently releases updates that fix bugs, improve stability, and address security issues that can cause crashes. Keeping Windows up to date ensures you’re not fighting a problem that’s already been fixed.

1. Open Settings (Windows + I).
2. Go to Update & Security > Windows Update (Windows 10) or Windows Update directly (Windows 11).
3. Click Check for updates.
4. Download and install all important or recommended updates.
5. Restart your PC if required.

After installing the latest Windows update, monitor your system to see if BSODs stop.

Scan for Malware

Malware can inject itself into system processes, modify drivers, or corrupt system files, all of which can lead to blue screen errors instead of normal program crashes. Running a full scan with Windows Security (Defender) and a reputable antimalware tool helps rule out infections as a root cause.

1. Open Windows Security (Windows Defender) from the Start menu.
2. Go to Virus & threat protection.
3. Click Scan options, select Full scan, then click Scan now.
4. Wait for the scan to complete and follow any recommendations to remove threats.

You can also run an additional scan with a reputable third‑party antivirus or antimalware tool for a second opinion.

Check for Overheating and Hardware Issues

When your CPU, GPU, or other components run too hot, they may begin to throttle, miscalculate, or shut down abruptly to protect themselves. Under heavy load, this can appear as random BSODs. Monitoring temperatures and improving cooling often resolves blue screens that only happen during gaming or other intensive tasks.

1. Use a temperature monitoring tool (e.g., HWMonitor, Core Temp, HWiNFO) to check CPU and GPU temperatures.
2. Ensure your PC has proper airflow:
   • Clean dust from fans and heatsinks.
   • Make sure vents are not blocked.
3. If temperatures are very high:
   • Reapply thermal paste if you know how, or
   • Improve cooling (more fans, better case airflow), or
   • Consult a technician.

Also consider:

• Testing RAM and disk thoroughly.
• Try a different power supply if the voltage is unstable (for desktops).

Use System Restore (if you have restore points)

If BSODs started recently after installing a driver, update, or program, and you have System Restore enabled, you can roll your system back to an earlier working state.

1. Press Windows + R, type sysdm.cpl and press Enter.
2. Go to the System Protection tab and click System Restore.
3. Choose a restore point from before the BSODs started, then follow the wizard.
4. Windows will restart and restore system files and settings to that snapshot.

System Restore doesn’t affect your personal files, but it can remove apps and drivers installed after the chosen restore point.

Use Reset this PC (when the system is badly damaged)

If you still get BSODs after all the steps above and System Restore is unavailable or doesn’t help, a Reset this PC or a clean reinstall of Windows may be the best way forward.

1. Go to Settings > System > Recovery.
2. Under Reset this PC, click Reset PC.
3. Choose Keep my files (recommended first) to reinstall Windows while keeping your personal data.
4. Follow the on‑screen instructions.

Note: Reset this PC will remove your installed apps and drivers, so make sure you back up important data first.

Common BSOD Stop Codes and What They Mean

There are many possible BSOD stop codes. Here are some of the most common ones you’ll see, what they usually point to, and a typical first step.

You can keep your table, but I recommend formatting it clearly. Here is a simplified bullet version you can use or adapt into a table block:

DATA_BUS_ERROR

• Typical cause: Memory (RAM) failure or serious hardware issue.
• First steps: Test your RAM with Windows Memory Diagnostic or MemTest86, then reseat or replace the RAM modules.

INACCESSIBLE_BOOT_DEVICE

• Typical cause: Windows cannot access the system drive (boot device). Often, driver or storage controller issues.
• First steps: Check SATA/NVMe cables, controller mode (IDE/AHCI) in BIOS, update storage drivers, scan disk for errors.

UNEXPECTED_KERNEL_MODE_TRAP

• Typical cause: Hardware failure, overheating, or buggy drivers.
• First steps: Check temperatures and fans, clean dust, update or roll back recent drivers.

NTFS_FILE_SYSTEM

• Typical cause: File system errors or disk problems.
• First steps: Run chkdsk on the system drive, look for high disk activity and failing drives.

IRQL_NOT_LESS_OR_EQUAL

• Typical cause: Incompatible or faulty drivers accessing invalid memory.
• First steps: Roll back or update recently installed drivers, especially network, storage, and antivirus drivers.

BAD_POOL_CALLER / BAD_POOL_HEADER

• Typical cause: Faulty memory operations by drivers or software, sometimes bad RAM.
• First steps: Update or remove recent drivers/software; test RAM if issues continue.

FAT_FILE_SYSTEM

• Typical cause: File system corruption on FAT partitions (usually removable drives).
• First steps: Run chkdsk on the affected drive, safely remove and reattach external drives.

OUT_OF_MEMORY / MEMORY_MANAGEMENT / PAGE_FAULT_IN_NONPAGED_AREA

• Typical cause: Memory (RAM) failure, driver bugs, or low resources.
• First steps: Test RAM, check for driver updates, close heavy apps, and check virtual memory settings.

UNABLE_TO_LOAD_DEVICE_DRIVER / KMODE_EXCEPTION_NOT_HANDLED

• Typical cause: Defective or incompatible drivers, or buggy software.
• First steps: Disable or remove recently installed drivers and software; update to the latest compatible versions.

Frequently Asked Questions

Robeg

I am Robeg founder of this blog. My qualification. completed Bachelor of Arts (BA) and Microsoft Certified Professional (MCP). With a strong background in computer applications love write articles on Microsoft Windows (11, 10, etc.) Cybersecurity, WordPress and more.

Related Articles

Windows System Restore Explained: What It Is and How to Enable and Use It

Windows 10 Reached End of its lifecycle on October 14, 2025 (What does it mean for you)

How to Use Windows Memory Diagnostic Tool to Test RAM

6 Things You Must Do After Install or Upgrade Windows 11 25H2

Download Windows 11 ISO (Version 25H2) Direct From Microsoft server for FREE

What is the OSI Model? 7 Layers Explained for Beginners (2026)