How to Read and Fix BSOD Stop Codes

A BSOD stop code is the alphanumeric identifier Windows shows on a blue screen to name the exact type of fault, and reading it correctly is the fastest way to a targeted fix. The most common cause behind a stop code is a faulty driver, followed by defective RAM and corrupt system files. This article explains what a stop code is and where to find it, how to look one up, and what the most common codes mean.

A large reference table lists each common stop code with its likely cause and first fix, including IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, SYSTEM_SERVICE_EXCEPTION, KMODE_EXCEPTION_NOT_HANDLED, MEMORY_MANAGEMENT, VIDEO_TDR_FAILURE, DPC_WATCHDOG_VIOLATION, and CRITICAL_PROCESS_DIED. The article then explains how to use minidump files and the Driver Verifier tool to confirm the failing driver, and gives the general targeted-fix method that applies to any stop code. Use the code as the starting point and apply only the fix that matches it.

What Is a BSOD Stop Code?

A BSOD stop code is a kernel error identifier that Windows assigns when it halts to prevent data loss, shown both as a readable name and a hexadecimal value. The points below explain what the code represents.

• A named error type. The text name, such as MEMORY_MANAGEMENT, describes the class of fault the kernel detected.
• A hexadecimal value. A code such as 0x0000001A maps to the same error and appears in logs and Microsoft documentation.
• An optional parameter set. Four bug-check parameters give the precise address or condition that triggered the stop.
• A possible driver name. Many screens list the failing .sys file under “What failed,” which names the component at fault.

Where to Find the Stop Code

The stop code appears on the blue screen, but it is also recorded in Windows so it can be read after the system restarts. Four sources hold the code.

1. Read the stop-code name and any file under “What failed” directly on the blue screen.
2. Scan the on-screen QR code to open the Microsoft support page for that code.
3. Open Windows Event Viewer, expand Windows Logs, select System, and find the BugCheck error.
4. Open the latest file in C:\Windows\Minidump with BlueScreenView to read the code and the driver.

How to Look Up a Stop Code

Looking up the stop code on Microsoft documentation gives the official description and recommended action for that exact error. The lookup uses either the name or the hex value.

1. Note the full stop-code name and the 0x bug-check value from the screen or Event Viewer.
2. Search the Microsoft Learn bug-check reference for that name or value.
3. Read the listed parameters to identify the precise condition, such as an invalid memory address.
4. Cross-check the failing .sys file against the device it belongs to in Device Manager.

Common BSOD Stop Codes Reference Table

The table below lists the most common Windows stop codes with the likely cause and the first fix to apply for each. Match the code shown on the screen to its row before changing anything.

Read the Failing Driver from a Minidump

Reading the minidump confirms which driver caused the stop, turning a code into a single file to update or remove. Windows saves a minidump after every stop error.

1. Confirm minidumps are enabled under System Properties, Startup and Recovery, with a small memory dump selected.
2. Open C:\Windows\Minidump in BlueScreenView to list every crash and its Caused By Driver.
3. For full analysis, install the Windows Debugging Tools and open the dump in WinDbg.
4. Run !analyze -v in WinDbg to print the probable cause and the failing module.
5. Match the named .sys file to its device in Device Manager.

Use Driver Verifier to Confirm the Culprit

Driver Verifier forces an immediate crash when any third-party driver misbehaves, naming the offender when minidumps alone are inconclusive. The tool ships with Windows.

1. Create a System Restore point before enabling Driver Verifier.
2. Type verifier in Windows Search and open Driver Verifier Manager.
3. Select Create standard settings, then Select driver names from a list.
4. Check all non-Microsoft drivers and click Finish, then restart.
5. After the next crash, read the named driver in the minidump, then run verifier /reset to turn it off.

If the system cannot boot after enabling Driver Verifier, enter Safe Mode and run verifier /reset to disable it.

Read the Bug-Check Parameters

Reading the four bug-check parameters narrows a stop code from a class of fault to the exact condition that triggered it. Every stop error carries four parameters after the main code.

1. Open the latest minidump in WinDbg and read the line beginning with Arguments after !analyze -v.
2. Note the four values, which differ in meaning for each stop code.
3. For PAGE_FAULT_IN_NONPAGED_AREA, read the first parameter as the memory address that could not be read.
4. For KMODE_EXCEPTION_NOT_HANDLED, read the first parameter as the exception code that was not handled.
5. Cross-reference the parameter meanings on the Microsoft Learn bug-check reference for that code.

The parameters confirm whether a fault is a read or write error, a timeout, or an unhandled exception, which guides the choice between a memory test and a driver replacement.

Check Whether a Stop Code Is Hardware or Software

Classifying a stop code as hardware or software directs the fix toward component tests or driver and file repairs. A few checks separate the two.

• Repeating the same code with no driver named. A consistent code such as WHEA_UNCORRECTABLE_ERROR with no .sys file points to hardware.
• Different codes on each crash. Varying stop codes across crashes usually indicate failing RAM or a failing drive corrupting different data.
• One code tied to one driver. The same .sys file across crashes points to a single software driver to update or remove.
• Crashes only under load or heat. Stop errors that appear during gaming or heavy work point to overheating or a marginal power supply.

Apply the Targeted Fix for the Code

Each stop-code class maps to a small set of fixes, so the targeted method applies only the action that matches the cause. The groups below cover the common codes.

• Memory-related codes. For MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA, test RAM with Windows Memory Diagnostic and MemTest86, then reseat or replace modules.
• Driver-related codes. For IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, and KMODE_EXCEPTION_NOT_HANDLED, update or roll back the named driver.
• Graphics codes. For VIDEO_TDR_FAILURE, perform a clean reinstall of the graphics driver and check GPU temperatures.
• Storage codes. For DPC_WATCHDOG_VIOLATION, update SSD firmware and the SATA AHCI driver, and check disk health.
• System-file codes. For CRITICAL_PROCESS_DIED, run SFC and DISM, then run chkdsk on the system drive.

Stop Codes That Point to Failing Hardware

A small set of stop codes points almost always to hardware rather than software, so these codes lead straight to component tests. The codes below indicate physical faults.

• WHEA_UNCORRECTABLE_ERROR (0x00000124). The Windows Hardware Error Architecture reported an uncorrectable fault in the CPU, memory, or bus, often from overheating or instability.
• CLOCK_WATCHDOG_TIMEOUT (0x00000101). A processor core stopped responding to interrupts, pointing to a CPU fault or an unstable overclock.
• MACHINE_CHECK_EXCEPTION (0x0000009C). The CPU detected an internal hardware error, commonly from heat, power, or a failing processor.
• UNEXPECTED_KERNEL_MODE_TRAP (0x0000007F). A hardware trap such as a divide error often indicates faulty RAM or an unstable overclock.

For each of these codes, reset any overclock to stock, confirm temperatures, run Windows Memory Diagnostic, and verify the power supply before suspecting software.

How to Prevent BSOD Stop Codes

Preventing future stop codes depends on keeping drivers, system files, and hardware in a known-good state. A few routine actions reduce crash frequency.

• Keep drivers current from the maker. Install graphics, chipset, and storage drivers from the device manufacturer rather than third-party updaters.
• Install Windows updates promptly. Quality updates fix kernel bugs that trigger stop codes.
• Maintain free disk space and run SFC periodically. A healthy file system prevents corruption-related codes.
• Monitor temperatures. Keeping the CPU and GPU within thermal limits prevents heat-related hardware codes.

Key Takeaways

• The stop code names the fault. Read it from the screen, Event Viewer, or a minidump before applying any fix.
• The hex value maps to documentation. Look up the 0x value on Microsoft Learn for the official cause and action.
• Minidumps name the driver. BlueScreenView and WinDbg read the failing .sys file from the crash file.
• Driver Verifier confirms the culprit. Use it when minidumps do not name a driver, then reset it afterward.
• Each code has a matching fix. Apply only the fix that fits the code class rather than guessing.

Last Thoughts on BSOD Stop Codes

A BSOD stop code is the starting point for every blue screen repair, because the code names the fault and the minidump names the driver behind it. Reading the code, looking it up in Microsoft documentation, and applying the matching fix resolves the crash without trial and error.

The general workflow for any crash is covered in the guide to fixing the Blue Screen of Death, while specific codes are handled in the steps to fix DRIVER_POWER_STATE_FAILURE, fix KERNEL_SECURITY_CHECK_FAILURE, fix SYSTEM_SERVICE_EXCEPTION, and fix CRITICAL_PROCESS_DIED. Because faulty memory triggers several codes, the explanation of how RAM works helps confirm a module fault before replacement.