TB
Tech Boss Interactive Tools Suite
๐Ÿ›ก๏ธ Windows 11 Diagnostics

Windows BSOD Stop Code & Event ID Lookup

โšก Instant Kernel Crash Triage Select or search any Windows 11 BugCheck hex code or Event Viewer ID below to isolate whether the crash stems from RAM/XMP instability, storage controller latency, GPU driver timeouts, or PSU transient power loss.

How to Read Windows 11 Crash Dumps Before Changing Hardware

Most Windows 11 Blue Screen of Death (BSOD) crashes look identical on screen, which leads PC owners to reinstall Windows or replace healthy parts unnecessarily. Separating software driver faults from physical hardware instability starts with two built-in logs: Event Viewer (System Log) and Kernel Minidumps stored under C:\Windows\Minidump.

1. Distinguish BugCheck Codes from BugcheckCode 0

When Windows catches a bad driver or memory address in time, it halts execution and writes a non-zero hex stop code such as 0x0000000A or 0x00000133. If your PC simply clicks off and reboots with Event ID 41 and BugcheckCode: 0, the OS never had a chance to log a dumpโ€”pointing directly toward power delivery transients, motherboard VRM protection, or BIOS idle C-state voltage drops.

2. Use WinDbg !analyze -v to Name the Exact Driver

Install the official WinDbg app from the Microsoft Store, open the latest .dmp file, and run !analyze -v. Scroll down to MODULE_NAME and IMAGE_NAME. Drivers like nvlddmkm.sys (NVIDIA), amdkmdag.sys (AMD), storahci.sys (storage), or rt640x64.sys (Realtek Ethernet) tell you the exact component to update or roll back cleanly.

3. Always Test Stock BIOS Defaults First

DDR5 XMP/EXPO profiles and CPU undervolts (AMD Curve Optimizer / Intel adaptive offsets) are the number-one hidden trigger behind intermittent 0x0000000A, 0x0000001A, and 0x00000124 crashes. Returning memory to stock JEDEC speeds for 48 hours confirms immediately whether your silicon or your drivers are at fault.

Explore More Free Interactive Tools

View All 17 Tools →