What is a Windows stop code?
A stop code (or bug check code) appears on a blue screen when Windows encounters a critical error. Each code identifies a specific type of failure.
Learn how to read a Windows error code: what the 0x prefix, HRESULT, NTSTATUS and stop codes mean, where to find the full code, and how to turn it into the right fix.
Reading a Windows error code means separating the part that identifies the failing component from the context that explains why it failed. The code itself is usually a hexadecimal HRESULT such as 0x80070005 or a named NTSTATUS stop code such as SYSTEM_SERVICE_EXCEPTION. What makes it useful is where it appeared: an app launch, a Windows Update run, a driver load or a blue screen.
Run these in an elevated Command Prompt or PowerShell unless stated otherwise.
eventvwr.msc
Get-WinEvent -FilterHashtable @{LogName='System'; Level=1,2} -MaxEvents 50
Escalate if the same code returns after the component-specific fix, if it appears during boot, or if it is accompanied by disk warnings or memory errors.
Reading a Windows error code means separating the part that identifies the failing component from the context that explains why it failed. The code itself is usually a hexadecimal HRESULT such as 0x80070005 or a named NTSTATUS stop code such as SYSTEM_SERVICE_EXCEPTION. What makes it useful is where it appeared: an app launch, a Windows Update run, a driver load or a blue screen.
The checks run in this order: Write down the exact code and context, Match the code to its component, Check Event Viewer for the surrounding event, Apply the fix for that component, not the code alone, Re-run the task and confirm the code is gone. Work through them in sequence instead of jumping to the last step, because each check rules out a layer of the problem and makes the next result easier to interpret.
Before you make changes, back up important data and create a system restore point. Run the commands in an elevated Command Prompt or PowerShell, read the output of each one, and stop if a result looks worse than the original symptom.
Start at step 1 of the guide and work down. The first check either confirms the cause or rules it out, so you do not skip straight to a destructive repair.
Start at step 1 of the guide and work down. The first check either confirms the cause or rules it out, so you do not skip straight to a destructive repair.
Start at step 1 of the guide and work down. The first check either confirms the cause or rules it out, so you do not skip straight to a destructive repair.
A stop code (or bug check code) appears on a blue screen when Windows encounters a critical error. Each code identifies a specific type of failure.
Enter your Windows error code (e.g., 0x0000001A or SYSTEM_SERVICE_EXCEPTION) in the search box. The tool will display possible causes and solutions.
Most fixes are safe, but we recommend backing up your data before making registry changes or driver updates. Consult a professional for hardware-related errors.
Most repair steps need an elevated prompt. Open Command Prompt or PowerShell with Run as administrator before running commands such as sfc, DISM, chkdsk, netsh or net stop. Read-only checks can often run without elevation.
Escalate if the same code returns after the component-specific fix, if it appears during boot, or if it is accompanied by disk warnings or memory errors.
No reviews yet. Be the first to review!