BSOD stop code list
A blue screen stop code, also called a bug check code, names the check Windows failed. Search the code shown on the blue screen, or browse the list below. Each entry explains what the bug check means, its common causes and the fixes to try.
Crashes that keep changing codes, or that need a minidump read, are better handled by the BSOD crash analyzer.
Searching error code database...
16 BSOD stop codes in the database
0x0000001A
MEMORY_MANAGEMENT
BSOD Stop Code
Indicates a critical memory management error. Typically caused by faulty RAM, incompatible memory modules, or corrupted page files.
🔍 Common Causes
- Faulty or incompatible RAM modules
- Corrupted paging file
- Driver conflicts accessing memory
- Overclocked memory timings
✅ How to Fix
- Run Windows Memory Diagnostic (mdsched.exe)
- reseat or replace RAM modules
- Disable XMP/DOCP in BIOS
- Run chkdsk /f to check for disk errors
- Update chipset and BIOS drivers
- Set virtual memory to system-managed size
0x0000001E
KMODE_EXCEPTION_NOT_HANDLED
BSOD Stop Code
A kernel-mode program generated an exception the handler did not catch. Usually caused by faulty device drivers or hardware incompatibility.
🔍 Common Causes
- Outdated or corrupted device drivers
- Recently installed incompatible software
- Hardware conflicts
- Corrupted system files
✅ How to Fix
- Boot into Safe Mode and uninstall recently installed software
- Update all device drivers
- Run System File Checker (sfc /scannow)
- Perform a system restore to a previous stable state
- Check for Windows updates
0x0000003B
SYSTEM_SERVICE_EXCEPTION
BSOD Stop Code
A system service generated an exception. Common causes include faulty drivers, corrupted system files, or incompatible software.
🔍 Common Causes
- Outdated or corrupted graphics drivers
- Damaged system files
- Recently installed incompatible software
- Overheating or hardware issues
✅ How to Fix
- Update graphics and network drivers
- Run DISM /Online /Cleanup-Image /RestoreHealth
- Run sfc /scannow
- Uninstall recently added software
- Check for Windows updates
- Test RAM with Windows Memory Diagnostic
0x00000050
PAGE_FAULT_IN_NONPAGED_AREA
BSOD Stop Code
The system referenced memory that does not exist. Caused by faulty hardware, corrupted drivers, or antivirus software conflicts.
🔍 Common Causes
- Faulty RAM or hard disk sectors
- Corrupted device drivers
- Antivirus software interference
- Recently installed buggy software
✅ How to Fix
- Run Windows Memory Diagnostic
- Disable antivirus temporarily and test
- Update all drivers, especially network and storage
- Run chkdsk /f /r on system drive
- Disable Fast Startup in power settings
0x0000007B
INACCESSIBLE_BOOT_DEVICE
BSOD Stop Code
Windows lost access to the system partition during startup. Often occurs after disk controller changes or drive failures.
🔍 Common Causes
- Incorrect SATA/RAID controller mode in BIOS
- Corrupted boot configuration data
- Failed hard drive or SSD
- Recent motherboard or disk hardware changes
✅ How to Fix
- Change SATA mode between AHCI/IDE/RAID in BIOS
- Boot from recovery media and run Bootrec /FixBoot /RebuildBcd
- Check disk health with CHKDSK and SMART status
- Replace failing drive and restore from backup
0x0000007E
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
BSOD Stop Code
A system thread generated an exception that the error handler did not catch. Usually driver-related.
🔍 Common Causes
- Faulty or incompatible drivers
- Corrupted system files
- Insufficient disk space
- Memory corruption
✅ How to Fix
- Boot into Safe Mode and remove recently installed drivers
- Run sfc /scannow
- Free up disk space on system drive
- Update chipset and graphics drivers
- Perform system restore
0x000000D1
DRIVER_IRQL_NOT_LESS_OR_EQUAL
BSOD Stop Code
A driver tried to access a pageable memory location at a too-high IRQL. Almost always driver-related.
🔍 Common Causes
- Faulty network or graphics driver
- Recently installed incompatible driver
- Corrupted driver files
- Memory corruption by a driver
✅ How to Fix
- Update all network and graphics drivers
- Roll back recently updated drivers
- Run networking in Safe Mode to isolate driver
- Use Driver Verifier to identify problematic driver
- Check for Windows updates
0x000000EA
THREAD_STUCK_IN_DEVICE_DRIVER
BSOD Stop Code
A device driver thread is stuck in an infinite loop. Typically a graphics driver issue.
🔍 Common Causes
- Corrupted or outdated graphics driver
- Overheating GPU
- Faulty graphics card hardware
- Incompatible display adapter
✅ How to Fix
- Boot into Safe Mode and uninstall graphics driver
- Install latest graphics driver from manufacturer
- Check GPU temperature and clean cooling fans
- Lower graphics acceleration in display settings
- Test with a different graphics card if available
0x000000F4
CRITICAL_OBJECT_TERMINATION
BSOD Stop Code
A critical system process terminated unexpectedly. Often caused by disk failure or corruption.
🔍 Common Causes
- Failing hard drive or SSD
- Corrupted Windows system files
- Malware infection
- Overclocking instability
✅ How to Fix
- Check disk health with CHKDSK and manufacturer tools
- Run sfc /scannow
- Perform malware scan with Windows Defender Offline
- Reset overclocking settings to default
- Restore from backup if disk is failing
0x00000124
WHEA_UNCORRECTABLE_ERROR
BSOD Stop Code
Windows Hardware Error Architecture detected an uncorrectable hardware error. Indicates a hardware problem.
🔍 Common Causes
- Overclocked CPU or GPU
- Faulty CPU, RAM, or motherboard
- Insufficient or failing power supply
- Overheating components
✅ How to Fix
- Reset all overclocking to stock settings
- Check CPU and GPU temperatures
- Test RAM with MemTest86
- Verify power supply is adequate and stable
- Update motherboard BIOS to latest version
- Check Windows Event Log for WHEA-Logger source
0x00000133
DPC_WATCHDOG_VIOLATION
BSOD Stop Code
A DPC (Deferred Procedure Call) watchdog timeout occurred. Often caused by faulty storage drivers.
🔍 Common Causes
- Outdated or incompatible storage driver (AHCI/NVMe)
- Faulty SSD firmware
- Overclocked system
- Corrupted system files
✅ How to Fix
- Update storage controller drivers from manufacturer
- Update SSD firmware
- Disable overclocking
- Run sfc /scannow
- Disable USB selective suspend in power settings
0x00000154
UNEXPECTED_STORE_EXCEPTION
BSOD Stop Code
An unexpected exception occurred in the store component (file system cache). Common with SSD issues.
🔍 Common Causes
- Failing SSD or corrupted NAND
- Outdated SSD firmware
- Corrupted file system cache
- Faulty SATA/ NVMe driver
✅ How to Fix
- Update SSD firmware using manufacturer tool
- Run chkdsk /f on system drive
- Run sfc /scannow
- Update chipset and storage drivers
- Check SSD health with manufacturer software
0x0000000A
IRQL_NOT_LESS_OR_EQUAL
BSOD Stop Code
A kernel-mode driver accessed pageable memory at an IRQL that is too high. One of the most common stop codes and almost always driver or hardware related.
🔍 Common Causes
- Faulty or outdated device driver
- Incompatible antivirus or filter driver
- Faulty RAM or memory corruption
- Recently installed hardware or software
✅ How to Fix
- Boot into Safe Mode and roll back recently updated drivers
- Update network, graphics and storage drivers
- Run Windows Memory Diagnostic (mdsched.exe)
- Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth
- Remove recently installed software or hardware
- Enable Driver Verifier for a specific suspect driver
0x0000009F
DRIVER_POWER_STATE_FAILURE
BSOD Stop Code
A driver failed to complete a power state transition, usually during sleep, hibernation or shutdown.
🔍 Common Causes
- Outdated or incompatible power-management driver
- USB device or dock preventing sleep
- Network adapter wake-on-LAN conflict
- Faulty chipset or storage driver
✅ How to Fix
- Update chipset, network and USB drivers
- Disable fast startup in power options
- Disable wake-on-LAN for the network adapter
- Disconnect USB devices and docks to isolate the trigger
- Run powercfg /energy and review the report
- Roll back the most recent driver update
0x000000EF
CRITICAL_PROCESS_DIED
BSOD Stop Code
A critical system process terminated unexpectedly. Windows cannot continue without it, so it halts.
🔍 Common Causes
- Corrupted system files
- Failing storage or bad sectors
- Malware tampering with system processes
- Faulty RAM
- Third-party security software interfering
✅ How to Fix
- Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth
- Check disk health with chkdsk /f and SMART tools
- Run a full malware scan with Windows Defender Offline
- Test RAM with Windows Memory Diagnostic
- Remove or update third-party antivirus and filter drivers
- Restore from a known-good backup if the problem persists
0x00000139
KERNEL_SECURITY_CHECK_FAILURE
BSOD Stop Code
The kernel detected corruption of a critical data structure. The first parameter names the check that failed.
🔍 Common Causes
- Corrupted system files or drivers
- Faulty RAM
- Incompatible or buggy driver
- Disk corruption
- Overclocking instability
✅ How to Fix
- Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth
- Run Windows Memory Diagnostic (mdsched.exe)
- Update or roll back the most recent driver
- Run chkdsk /f on the system drive
- Disable overclocking and XMP/DOCP
- Check Event Viewer for the faulting module before the crash
💡 Quick Tips
- Disable Automatically restart in Startup and Recovery so the next blue screen stays visible long enough to photograph.
- Most stop codes come from a driver, memory or storage fault; rule those out before reinstalling Windows.
- Run mdsched.exe and sfc /scannow before replacing hardware.
- Minidumps are stored in C:\Windows\Minidump for deeper analysis.
- If the stop code changes between crashes, suspect memory or power delivery rather than one driver.
Not what you were looking for?
How To Use BSOD Stop Code List & Lookup
- Read the stop code on the blue screen, or open Event Viewer and find the BugCheck event if the PC restarted too quickly.
- Enter the code with its 0x prefix, or type the stop code name if you only remember that.
- Open the matching result and read what the bug check means and which causes are most likely.
- Work through the fixes in order, starting with the read-only checks such as the memory diagnostic and SFC.
- If the same code returns after the software checks, use the BSOD crash analyzer to examine the dump and driver history in detail.
What is BSOD Stop Code List – Look Up Any Blue Screen Code?
A Blue Screen of Death is a controlled halt: Windows detected a condition it could not safely recover from and stopped. The bug check code on the screen identifies the check that failed, and the four parameters after it often point at the driver, memory address or object involved.
This page lists the common BSOD stop codes in a searchable database. Each entry explains what the bug check means, the causes that most often produce it and the fixes to try. The list covers MEMORY_MANAGEMENT, INACCESSIBLE_BOOT_DEVICE, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, DPC_WATCHDOG_VIOLATION and the other codes most often seen on Windows 10 and 11.
A stop code is a starting point, not a verdict. The same code can come from a faulty driver, failing RAM, an overheating component or a corrupted system file. Use the code to narrow the search, then confirm with the memory diagnostic, driver history and disk health checks before replacing hardware.
Benefits of Using BSOD Stop Code List & Lookup
- Searchable list of common BSOD stop codes with the meaning of each bug check.
- Every entry lists the most likely causes and an ordered set of fixes.
- Browse the full list when you do not know the code name.
- Covers the codes most often seen on Windows 10 and Windows 11.
- Links straight to the crash analyzer when you need dump-level analysis.
Best Practices
- Disable automatic restart so you can read the stop code and any named driver file.
- Rule out memory and storage first; they mimic driver faults and are cheap to test.
- Roll back or update the most recent driver before changing Windows settings.
- Create a restore point before running repair commands or changing boot configuration.
- Record every stop code you see; a changing code often points to hardware rather than one driver.
Practical Examples
0x0000001A - MEMORY_MANAGEMENT
A memory management fault. Start with the Windows Memory Diagnostic, then check the page file and memory-related drivers.
0x0000007B - INACCESSIBLE_BOOT_DEVICE
Windows cannot access the system partition. Check the SATA/RAID mode, boot configuration and disk health.
0x000000D1 - DRIVER_IRQL_NOT_LESS_OR_EQUAL
A driver touched pageable memory at the wrong interrupt level. Update or roll back network and graphics drivers.
0x00000133 - DPC_WATCHDOG_VIOLATION
A deferred procedure call ran too long. Usually a storage driver or SSD firmware problem.
Who Should Use This Tool
- Windows users who photographed a blue screen and need the code explained.
- Technicians triaging a crash before opening a dump file.
- Users deciding whether a stop code points to software or hardware.
- Anyone who wants the standard fix order for a known bug check.
FAQs
What is a BSOD stop code?
A stop code, or bug check code, is the number Windows displays when it halts to protect data. Examples include 0x0000007B INACCESSIBLE_BOOT_DEVICE and 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL. The code names the check that failed.
Where can I find the stop code if the PC restarts immediately?
Open Event Viewer, go to Windows Logs > System, and filter for the source BugCheck. The event records the stop code and its parameters. You can also disable Automatically restart in Startup and Recovery so the screen stays visible.
Does the stop code tell me which driver caused the crash?
Not directly. The first parameter sometimes points at the driver or memory address, and the minidump names the loaded module. The stop code narrows the category; the dump identifies the specific driver.
Should I reinstall Windows when I see a stop code?
No, not as a first step. Most stop codes are caused by a driver, memory or storage fault that can be diagnosed and fixed without reinstalling. Reinstall only after the hardware and driver checks fail.
How is this different from the BSOD crash analyzer?
This page looks up a stop code in a database of known bug checks. The BSOD crash analyzer takes pasted crash text or minidump output and produces a root-cause analysis for that specific machine.