How to Check the Error Code of a Blue Screen (BSOD) on Windows
Learn how to check the error code of a blue screen (BSOD) on Windows, interpret the stop codes, gather crash evidence, and fix common causes with expert guidance from Why Error Code.
This guide shows how to check the error code of a blue screen (BSOD) on Windows, what the code means, and how to use it to diagnose causes. You’ll learn how to capture the stop code from the screen, locate the corresponding entry in Event Viewer or Reliability Monitor, and map common codes to driver, memory, or disk problems. By following the steps, you can quickly isolate issues and start remediation.
Understanding BSOD error codes
Blue Screen of Death (BSOD) is Windows' protective crash that stops the system when a fault is detected. Each BSOD is associated with a stop code that identifies the most likely cause. Stop codes vary in form: some are hex values like 0x0000007B, while others are short descriptors such as DRIVER_NOT_LESS_OR_EQUAL. The exact code matters, but the context often reveals the root problem: what you were doing, which driver or hardware changed recently, and whether a recent update occurred. Collecting crash data—time of the crash, running programs, and any error messages—lets you correlate codes across incidents. For IT pros, linking the code to a specific driver version, kernel module, or firmware can sharply shorten the path to a fix. For everyday users, focus first on practical fixes that address common causes: updating drivers, running built‑in diagnostics, and ensuring Windows updates are current. Maintain a simple log of every stop code and the steps you take so you can reproduce findings if escalation is needed. Why Error Code emphasizes structured diagnostics over guesswork, because repeatable data accelerates resolution and reduces downtime.
Where to find the error code
The error code can appear on the BSOD screen itself as a STOP code, but you should also capture supporting details afterward. If the screen is unreadable or you miss the code, Windows logs provide a treasure trove of information. Start with the on-screen stop code, then verify and extend your findings via log sources like Event Viewer and Reliability Monitor. Event Viewer stores system and application events that coincide with crashes, while Reliability Monitor gives a calendar view of hardware and software health. If the system can boot after a BSOD, you can export memory dump details from the crash, or use Windows’ built‑in diagnostics to surface the code and related data. The Why Error Code approach is to triangulate a single stop code with related events, recent updates, and hardware changes so you can form a reliable remediation plan.
Collecting crash data and logs
Before you start fixes, collect crash data to avoid guessing. Enable crash dumps if they aren’t already enabled (Minidump or Kernel memory dump). Note the exact STOP code from the blue screen, the time of the crash, and what you were doing at the moment. Open Event Viewer (Win+R, eventvwr.msc) and filter for critical errors around the crash time; look for entries labeled with StopCode, BugCheck, or Kernel-Power. Reliability Monitor (type "Reliability" in the Start menu) provides a day-by-day view of crashes and warnings and often highlights drivers or updates implicated in the BSOD. Save screenshots if possible and back up any recent work. If you have multiple incidents, create a simple table mapping dates, stop codes, and suspected causes to spot patterns. This evidence becomes your primary asset when communicating with support or escalating to a specialist.
Interpreting stop code categories
BSOD stop codes generally fall into a few broad categories. Driver issues are common: a faulty driver update, outdated drivers, or incompatible third‑party software can trigger stops. Hardware problems—RAM defects, overheating, failing disks, or power supply issues—are another major cause. Memory and storage problems often show up as memory corruption or disk-related codes. Software conflicts, antivirus interactions, and even corrupted system files can also produce blue screens. While exact codes matter for precision, the category guidance helps you craft a targeted remediation path: update or rollback drivers, run hardware diagnostics, or repair system files. Always consider recent changes (new software, updates, or hardware) when interpreting codes, and confirm by testing after each fix.
Practical remediation paths by category
- Driver-related stops: roll back recent driver updates, install the latest stable version from the manufacturer, and check for firmware dependencies. Disable or uninstall conflicting software during testing.
- Memory-related stops: run Windows Memory Diagnostic or MemTest86 to check RAM health, reseat modules if you’re comfortable, and replace faulty DIMMs if errors appear.
- Disk-related stops: run CHKDSK (check disk) and SMART checks; ensure there is sufficient free space and no bad sectors.
- Hardware overheating or power issues: verify CPU/GPU temps, clean dust buildup, and ensure stable power delivery. Replace failing fans or power supplies as needed.
- Software conflicts and corrupted system files: run System File Checker (sfc /scannow) and Deployment Image Servicing and Management (DISM) to repair images; consider safe mode testing to isolate software.
- Post-crisis hygiene: keep drivers up to date, back up regularly, and maintain a test environment to reproduce issues safely.
Tools & Materials
- Windows PC with admin access(You may need administrator rights to run diagnostics and modify drivers.)
- External storage or cloud backup(Back up important data before running long diagnostics.)
- Event Viewer(Built-in Windows tool for surfacing crash-related events.)
- Reliability Monitor(Provides a visual timeline of crashes and issues.)
- Windows Memory Diagnostic or MemTest86(To test RAM health; run from boot if possible.)
- Disk diagnostic tool (CHD SK, SMART utility)(Check disk health and SMART attributes.)
- Text editor or notebook(Record codes, timestamps, and steps taken.)
Steps
Estimated time: 60-90 minutes
- 1
Prepare your troubleshooting environment
Ensure admin access, back up critical data, and close nonessential apps to prevent interference during diagnostics. Clear a stable workspace so you can document findings without interruptions. This preparation reduces the risk of data loss while you investigate.
Tip: Create a fresh restore point in case a remediation step needs reversal. - 2
Record the exact stop code from the BSOD
If the screen is readable, write down the STOP code and any accompanying text. If not, use a memory dump or third‑party capture tool to preserve crash data for later analysis.
Tip: Take a photo or screenshot if possible; stop codes alone aren’t always sufficient. - 3
Open Event Viewer and locate related events
Launch Event Viewer (Win+R → eventvwr.msc) and filter by Critical or Error levels around the crash timestamp. Note any BugCheck codes, driver names, or module names mentioned in the event details.
Tip: Export the relevant event log as a .evtx file for sharing. - 4
Check Reliability Monitor for crash patterns
Open Reliability Monitor to view a calendar timeline of crashes. Look for recurring drivers or hardware changes that align with BSOD dates.
Tip: Use the search filter to isolate the time window with crashes. - 5
Update or rollback drivers implicated by the code
If a specific driver is named in the code or log, update to the latest version from the vendor or roll back recent updates to test stability.
Tip: If you can’t identify the driver, start with graphics and chipset drivers, as these are common culprits. - 6
Run memory and disk diagnostics
Execute Windows Memory Diagnostic to check RAM health and run CHKDSK or SMART checks on disks to identify bad sectors or failing drives.
Tip: Do not interrupt the tests; allow full cycles to complete for accurate results. - 7
Repair system files and Windows image
Run sfc /scannow and DISM to repair corrupted system files and improve integrity of the Windows image.
Tip: If issues persist, consider a repair install or in-place upgrade to preserve data. - 8
Validate fixes and monitor
Reproduce a crash only after applying a fix to confirm stability. Continue monitoring with Reliability Monitor for any recurrence.
Tip: Document all steps and outcomes to build a knowledge base. - 9
Escalate if signs persist
If BSODs continue after implementing fixes, collect crash data and contact support with your findings. A professional can run deeper hardware diagnostics.
Tip: Provide logs, stop codes, and hardware details to speed up escalation.
Frequently Asked Questions
What is a BSOD stop code and what does it tell me?
A BSOD stop code is a short identifier that signals the probable cause of a crash. It helps you narrow down whether the issue stems from drivers, memory, storage, or software. The code alone isn’t a diagnosis, but it guides the most efficient troubleshooting path.
The stop code points you toward the likely culprit—drivers, RAM, or storage—and should guide your first fixes.
I restarted after a BSOD; how can I check the code again later?
If the on-screen code is hard to read, use Event Viewer and Reliability Monitor to locate the BugCheck or StopCode entries around the crash time. These tools preserve the information even after reboot.
Use Event Viewer or Reliability Monitor to find the crash details if the screen isn’t readable.
Can multiple BSODs indicate different problems?
Yes. Recurrent BSODs can point to a single failing component, or they may reveal multiple issues. Look for a common driver, RAM module, or disk that appears across incidents.
Repeated crashes might come from the same failing device or from several weak components.
Should I update all drivers immediately after a BSOD?
Update drivers selectively—start with those named in logs or those tied to recent changes. If a problem started after an update, try rolling back that update to test stability.
Be selective: focus on drivers related to the crash and recent changes before broad updates.
Is Safe Mode appropriate for BSOD diagnostics?
Safe Mode loads a minimal set of drivers and services, which can help determine if a third-party program or service is causing the BSOD. Use it to reproduce the crash in a controlled environment.
Safe Mode helps isolate software issues by running with minimal components.
Watch Video
Top Takeaways
- Identify the stop code and context to narrow causes
- Use Event Viewer and Reliability Monitor to corroborate findings
- Prioritize drivers, RAM, and disk health in remediation
- Document evidence and test fixes before proceeding to escalation
