Common Computer Blue Screen Error Codes and Their Fixes

Laptop with Windows BlueScreen Error

Blue Screen of Death (BSOD) Error Codes: Complete Fix Guide 2026

Quick Summary

Blue screen errors crash your computer to prevent data corruption. Each error code points to specific hardware or software problems. This guide covers the 15 most common BSOD errors with step-by-step fixes you can try at home, plus clear signs when professional help is needed.

Bottom Line Up Front

Most blue screens are caused by faulty RAM, failing hard drives, or outdated drivers. If you see the same error repeatedly, back up your data immediately and focus on those three areas first.

1. MEMORY_MANAGEMENT 0x0000001A

What it means: Windows cannot properly manage your computer’s RAM. This points to faulty memory hardware or software conflicts affecting memory allocation.

Common Causes

  • Physically failing RAM modules
  • Incompatible RAM speeds or brands mixed together
  • RAM running at wrong speeds after BIOS updates
  • Corrupted system files affecting memory management
  • Outdated chipset or memory controller drivers

Step-by-Step Solutions

  1. Run Windows Memory Diagnostic: Press Windows + R, type “mdsched.exe” and hit Enter. Choose “Restart now and check for problems.” Your computer will restart and test RAM automatically.
  2. Reseat RAM modules: Power down completely, unplug the power cord, open your computer case, remove RAM sticks, and firmly reinsert them until they click into place.
  3. Test RAM individually: If you have multiple RAM sticks, remove all but one and use your computer normally. If crashes stop, test each stick individually to identify the faulty one.
  4. Update motherboard drivers: Visit your motherboard manufacturer’s website and download the latest chipset drivers for your exact model.
  5. Check BIOS settings: Reset BIOS to default settings, then verify RAM is running at manufacturer-specified speeds (check the sticker on your RAM).

2. KERNEL_DATA_INPAGE_ERROR 0x0000007A

What it means: Windows cannot read critical data from your storage drive. This is usually a sign of hard drive failure or loose connections.

Critical Warning: This error often indicates hardware failure. Back up your important files immediately before attempting fixes.

Common Causes

Step-by-Step Solutions

  1. Secure your data first: Boot from a Windows installation USB and copy critical files to an external drive before proceeding with other fixes.
  2. Check all cables: Power down, open your case, and ensure SATA data cables and power cables are firmly connected to your hard drive and motherboard.
  3. Run CHKDSK: Open Command Prompt as Administrator and type: chkdsk C: /f /r (replace C: with your main drive letter). This will scan and attempt to repair bad sectors.
  4. Check drive health: Download CrystalDiskInfo (free) to check your drive’s SMART status. If it shows “Caution” or “Bad,” prepare for drive replacement.
  5. Scan for malware: Run a full system scan with Windows Defender and Malwarebytes to rule out virus damage to system files.

3. SYSTEM_SERVICE_EXCEPTION 0x0000003B

What it means: A system service crashed due to faulty drivers or malware. This error commonly occurs after driver updates or malware infections.

Common Causes

Step-by-Step Solutions

  1. Boot into Safe Mode: Hold Shift while clicking Restart, then go to Troubleshoot > Advanced options > Startup Settings > Restart > press 4 for Safe Mode.
  2. Update critical drivers: In Safe Mode, visit manufacturer websites to download latest graphics, network, and chipset drivers. Avoid Windows Update for drivers initially.
  3. Run comprehensive malware scan: Use Windows Defender offline scan and Malwarebytes to detect and remove stubborn malware.
  4. Repair system files: Open Admin Command Prompt and run: sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth
  5. Uninstall recent changes: In Safe Mode, uninstall any recently installed programs or drivers that might have caused the issue.

4. CRITICAL_PROCESS_DIED 0x000000EF

What it means: An essential Windows process stopped working. This indicates serious system corruption or hardware problems affecting core Windows operations.

Common Causes

Step-by-Step Solutions

  1. Run System File Checker: Open Command Prompt as Administrator and type: sfc /scannow to scan and repair corrupted Windows files.
  2. Perform Windows Startup Repair: Boot from Windows installation media, select “Repair your computer” > Troubleshoot > Advanced options > Startup Repair.
  3. Use System Restore: If you have restore points, boot to Advanced Startup Options and restore to a point before the errors began.
  4. Check for Windows Updates: Install any pending updates that might contain fixes for known issues causing this error.
  5. Run Memory Diagnostic: Since this can be RAM-related, test your memory using the Windows Memory Diagnostic tool (mdsched.exe).

5. VIDEO_TDR_FAILURE 0x000000116

What it means: Your graphics card stopped responding and couldn’t recover. This is common with overheating GPUs or driver conflicts.

Common Causes

  • Overheating graphics card
  • Overclocked GPU running unstably
  • Outdated or corrupted graphics drivers
  • Insufficient power supply for graphics card
  • Failing graphics card hardware

Step-by-Step Solutions

  1. Monitor GPU temperatures: Download MSI Afterburner or HWiNFO to check GPU temps. If over 80°C under load, clean dust from graphics card fans and case.
  2. Reset GPU overclocks: If you’ve overclocked your graphics card, reset it to factory defaults using MSI Afterburner or similar software.
  3. Completely reinstall graphics drivers: Download DDU (Display Driver Uninstaller), boot to Safe Mode, use DDU to remove all graphics drivers, then install fresh drivers from NVIDIA/AMD websites.
  4. Check power connections: Ensure all power cables are firmly connected to your graphics card. Consider testing with a higher wattage PSU if available.
  5. Reseat graphics card: Power down, remove GPU from PCIe slot, clean contacts with isopropyl alcohol, and reinstall firmly.

6. DPC_WATCHDOG_VIOLATION 0x00000133

What it means: A system process took too long to complete, usually due to driver or firmware issues with storage devices or network adapters.

Common Causes

  • Outdated SSD firmware
  • Incompatible storage controller drivers
  • Problematic Wi-Fi or Bluetooth drivers
  • Failing SSD or hard drive
  • Third-party antivirus software conflicts

Step-by-Step Solutions

  1. Update SSD firmware: Visit your SSD manufacturer’s website (Samsung, Crucial, WD, etc.) and download their SSD management software to check for firmware updates.
  2. Update storage drivers: In Device Manager, expand “IDE ATA/ATAPI controllers” and update all storage-related drivers from manufacturer websites.
  3. Update network drivers: Download latest Wi-Fi and Bluetooth drivers directly from your laptop manufacturer or motherboard maker’s website.
  4. Disable third-party antivirus: Temporarily uninstall non-Microsoft antivirus software to test if it’s causing conflicts.
  5. Run storage diagnostics: Use manufacturer tools (Samsung Magician, Intel SSD Toolbox, etc.) to test your SSD health and performance.

7. NTFS_FILE_SYSTEM 0x00000024

What it means: Windows detected corruption in your hard drive’s file system structure, preventing proper data access.

Common Causes

  • Bad sectors on hard drive
  • Corrupted file system due to improper shutdowns
  • Failing hard drive or SSD
  • Loose data cables
  • Malware damaging file system structures

Step-by-Step Solutions

  1. Run thorough CHKDSK: Boot to Command Prompt and run: chkdsk C: /f /r /x (this may take several hours but repairs file system errors and bad sectors).
  2. Check drive cables: Ensure SATA data and power cables are securely connected to your drive and motherboard.
  3. Test drive health: Use CrystalDiskInfo or manufacturer tools to check drive SMART status and overall health.
  4. Scan for malware: Boot from antivirus rescue disk to scan for malware that might be corrupting your file system.
  5. Consider drive replacement: If CHKDSK finds many bad sectors or drive health shows deterioration, plan for drive replacement.

8. IRQL_NOT_LESS_OR_EQUAL 0x0000000A

What it means: A driver tried to access a memory area it shouldn’t have, typically indicating faulty drivers or hardware problems.

Common Causes

  • Faulty or incompatible device drivers
  • Defective RAM modules
  • Corrupted system files
  • Hardware conflicts between devices
  • Overclocked system components

Step-by-Step Solutions

  1. Boot Safe Mode and check recent changes: Remove or roll back any recently installed drivers, especially network, graphics, or audio drivers.
  2. Test RAM thoroughly: Run Windows Memory Diagnostic and consider overnight MemTest86 for comprehensive RAM testing.
  3. Update all critical drivers: Focus on motherboard chipset, graphics, network, and audio drivers from manufacturer websites.
  4. Disable overclocking: Reset CPU, RAM, and GPU to default speeds to eliminate overclocking as a cause.
  5. Check for hardware conflicts: In Device Manager, look for devices with yellow warning signs and resolve conflicts.

9. BAD_POOL_HEADER 0x00000019

What it means: Windows detected corruption in system memory allocation, usually caused by defective RAM or problematic drivers.

Common Causes

  • Failing or incompatible RAM
  • Corrupted device drivers
  • Malware infections
  • Recent hardware changes
  • Overclocking instability

Step-by-Step Solutions

  1. Run extended memory test: Use Windows Memory Diagnostic in extended mode, or boot MemTest86 for several hours to thoroughly test RAM.
  2. Boot Safe Mode and remove recent software: Uninstall any recently added programs, especially system utilities or drivers.
  3. Scan for malware comprehensively: Use multiple tools including Windows Defender offline, Malwarebytes, and ESET online scanner.
  4. Check system file integrity: Run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth
  5. Test with minimal hardware: Disconnect unnecessary devices and test with only essential components to isolate hardware conflicts.

10. KMODE_EXCEPTION_NOT_HANDLED 0x0000001E

What it means: A kernel-mode program encountered an error it couldn’t handle, typically pointing to driver or hardware problems.

Common Causes

  • Corrupt or incompatible drivers
  • Defective RAM modules
  • Hard drive errors
  • Overclocked hardware instability
  • Virus or malware damage

Step-by-Step Solutions

  1. Identify the problematic driver: Check the blue screen for specific driver names (usually ending in .sys) and update or remove those drivers first.
  2. Test RAM extensively: Use both Windows Memory Diagnostic and MemTest86 to verify RAM stability under load.
  3. Check hard drive health: Run chkdsk C: /f /r and use drive health monitoring tools to rule out storage issues.
  4. Remove overclocking: Return all hardware (CPU, GPU, RAM) to manufacturer default speeds and test stability.
  5. Perform clean boot: Boot with minimal drivers and services to isolate software conflicts causing the exception.

11. PAGE_FAULT_IN_NONPAGED_AREA 0x00000050

What it means: Windows tried to access memory that should always be available but wasn’t there, indicating RAM problems or driver issues.

Common Causes

  • Faulty RAM hardware
  • Incompatible or corrupted drivers
  • Overclocked memory running unstably
  • Antivirus software conflicts
  • Recently installed hardware causing conflicts

Step-by-Step Solutions

  1. Test RAM immediately: Run Windows Memory Diagnostic and MemTest86 to identify failing memory modules.
  2. Boot Safe Mode and update drivers: Focus on recently changed drivers and update them from manufacturer websites.
  3. Remove recent hardware: Disconnect any recently added components and test system stability.
  4. Disable antivirus temporarily: Test with third-party security software disabled to check for conflicts.
  5. Reset memory speeds: In BIOS, set RAM to default JEDEC speeds rather than XMP profiles and test.

12. DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000D1

What it means: A device driver attempted to access memory at the wrong permission level, almost always indicating a problematic driver.

Common Causes

  • Faulty network adapter drivers
  • Corrupted graphics drivers
  • Incompatible USB device drivers
  • Third-party system utilities interfering
  • Hardware driver conflicts

Step-by-Step Solutions

  1. Check blue screen details: Look for the specific driver file mentioned in the error (usually ends with .sys) to identify which device is causing problems.
  2. Boot Safe Mode and remove problematic drivers: Uninstall the identified driver completely, then download fresh version from manufacturer.
  3. Update network drivers first: Network drivers commonly cause this error. Download latest versions from your motherboard or laptop manufacturer.
  4. Disable problematic devices: In Device Manager, disable devices showing warning signs and test system stability.
  5. Roll back recent driver updates: If errors started after recent driver updates, use Device Manager to roll back to previous versions.

13. UNEXPECTED_KERNEL_MODE_TRAP 0x0000007F

What it means: The processor generated an exception that the kernel couldn’t handle, usually indicating serious hardware problems.

Common Causes

  • Overheating CPU or other components
  • Defective RAM modules
  • Failing motherboard
  • Unstable overclocking
  • Power supply problems

Step-by-Step Solutions

  1. Check system temperatures: Use HWMonitor to verify CPU, GPU, and motherboard temps are within normal ranges (CPU under 70°C, GPU under 80°C).
  2. Remove all overclocking: Reset BIOS to defaults and ensure CPU, RAM, and GPU are running at stock speeds.
  3. Test RAM extensively: Run both Windows Memory Diagnostic and MemTest86 for at least 4 hours to detect intermittent RAM failures.
  4. Check power supply stability: Use a multimeter to test PSU voltage rails, or try a different PSU if available.
  5. Clean and reseat all components: Remove and reinstall CPU, RAM, and expansion cards to ensure proper connections.

14. PFN_LIST_CORRUPT 0x0000004E

What it means: Windows detected corruption in the Page Frame Number database, which tracks physical memory usage. This almost always points to RAM hardware failure.

Common Causes

  • Physically failing RAM modules
  • Incompatible memory timings
  • Motherboard memory controller problems
  • Extreme overclocking damage
  • Age-related RAM degradation

Step-by-Step Solutions

  1. Test each RAM stick individually: Boot with only one RAM module at a time to isolate the failing stick.
  2. Run comprehensive memory tests: Use MemTest86+ for at least 8 hours on each working RAM module.
  3. Check RAM compatibility: Verify your RAM is on your motherboard’s qualified vendor list (QVL).
  4. Reset memory timings: In BIOS, disable XMP/DOCP and use JEDEC standard timings.
  5. Consider professional RAM replacement: This error usually requires new memory modules to resolve permanently.

15. DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000C4

What it means: Driver Verifier detected a driver violating Windows rules, or you have a legitimate driver problem that Verifier helped identify.

Common Causes

  • Driver Verifier is actively testing drivers
  • Faulty third-party drivers
  • Incompatible system utilities
  • Corrupted driver installations
  • Hardware drivers not designed for your Windows version

Step-by-Step Solutions

  1. Disable Driver Verifier: Boot to Safe Mode, open Command Prompt as Admin, and type: verifier /reset then restart.
  2. Identify the problem driver: The blue screen should list the specific driver file. Update or remove that driver completely.
  3. Update all drivers systematically: Download latest versions for graphics, network, audio, and chipset drivers from manufacturer websites.
  4. Remove third-party system tools: Uninstall registry cleaners, driver updaters, and system optimization software that might have corrupted drivers.
  5. Perform selective driver testing: If needed, re-enable Driver Verifier for specific drivers only to isolate problems systematically.

Additional Common Blue Screen Errors

CLOCK_WATCHDOG_TIMEOUT 0x00000101

Quick fix: Usually caused by overheating or overclocked processors. Check CPU temperatures and reset BIOS to defaults.

WHEA_UNCORRECTABLE_ERROR 0x00000124

Quick fix: Hardware error detected by Windows Hardware Error Architecture. Check CPU, RAM, and motherboard for overheating or instability.

HYPERVISOR_ERROR 0x00000020

Quick fix: Disable virtualization features in BIOS if you’re not running virtual machines, or update hypervisor software.

REGISTRY_ERROR 0x00000051

Quick fix: Registry corruption from malware or failed updates. Run sfc /scannow and scan for malware immediately.

When to Call a Professional

While many blue screen issues can be resolved with patience and the right steps, some situations require expert diagnosis. Contact a professional technician if you experience:

  • Multiple different blue screen errors occurring frequently
  • Crashes during Windows startup before you can log in
  • The same error persists after following all troubleshooting steps
  • You’re not comfortable opening computer hardware or using Command Prompt
  • Data loss concerns or files becoming inaccessible
  • Errors started after physical incidents like spills, drops, or power surges

Experiencing Persistent Blue Screen Errors?

Stop guessing what’s wrong. Our RSAG-accredited technicians provide accurate diagnosis and permanent solutions.

Professional Hardware Testing

We accurately test your RAM, storage drives, and components to find the exact problem.

Advanced Software Repair

We repair corrupted Windows installations and driver conflicts that simple tools miss.

Data Backup and Recovery

We safely secure your files before performing any repairs or replacements.

Available Through:

  • Remote Support: Secure connection to diagnose and fix software issues nationwide
  • In-Home Service: Direct hardware service in New Jersey and Boulder, Colorado
Call (201) 400-0936 for Professional Diagnosis
30-Day Labor Guarantee on All Services

🎉 Limited Time: Save 20% on Any Computer Service!