How to Fix Windows Blue Screen (BSOD) Errors Using Event Viewer

The Windows Blue Screen of Death (BSOD) is an emergency safety measure. When the Windows Kernel encounters an unrecoverable driver conflict or physical hardware anomaly, it halts execution immediately to prevent catastrophic data corruption. Windows Event Viewer records every single crash detail to disk. Here is how to find and fix it.

Step 1: Open Windows Event Viewer

You can launch the Event Viewer console directly using the Run dialog:

Run Shortcut

eventvwr.msc

Press Win + R, type eventvwr.msc, and hit Enter. Alternatively, press Win + X and select Event Viewer.

Step 2: Navigate to Windows Logs > System

In the left-hand navigation tree:

Expand the Windows Logs directory.
Click on System.
Wait 2–5 seconds while the operating system queries the event log database.

Step 3: Filter for "Critical" and "Error" Events

The System log contains tens of thousands of harmless informational entries. To isolate the crash:

Click "Filter Current Log..."

On the right-side Actions panel, click Filter Current Log....

Check "Critical" and "Error"

Under Event level, check the boxes for Critical and Error.

Filter by Event ID 41 & 1001

In the "All Event IDs" text box, enter 41, 1001 and click OK.

Step 4: Decoding Event ID 41 (Kernel-Power)

Event ID 41 signifies that the system rebooted without cleanly shutting down first. Click on the most recent Event 41 entry and look at the Details tab under XML view.

Examine the BugcheckCode value. This is a decimal representation of the Windows Stop Code:

Common Bugcheck Values

            • BugcheckCode 10: 0x0000000A (IRQL_NOT_LESS_OR_EQUAL) → Usually a faulty driver trying to access unmapped memory.

            • BugcheckCode 59: 0x0000003B (SYSTEM_SERVICE_EXCEPTION) → Graphics or anti-cheat kernel driver failure.

            • BugcheckCode 80: 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA) → Faulty RAM stick or broken L3 cache.

            • BugcheckCode 239: 0x000000EF (CRITICAL_PROCESS_DIED) → Core Windows binary corrupted or SSD disconnect.

Step 5: Inspect Event ID 1001 (The BugCheck Dump Record)

Right before or immediately after Event 41, Windows logs an Event ID 1001 (Source: BugCheck). This log entry contains the exact location of the saved memory minidump (e.g., C:\Windows\MEMORY.DMP or C:\Windows\Minidump\*.dmp).

Pro Tip: View the Offending Driver Name

Event 1001 description often explicitly lists the faulting module, such as nvlddmkm.sys (Nvidia GPU Driver), amdkmdag.sys (AMD GPU), or Netwtw10.sys (Intel Wi-Fi Driver).

Step 6: Step-by-Step Remediation Plan

If GPU Driver (nvlddmkm / amdkmdag): Boot Windows in Safe Mode, run Display Driver Uninstaller (DDU), and install the latest WHQL studio/game driver.
If Memory Management (0x1A or 0x50): Run Windows Memory Diagnostic (Read RAM Guide).
If Corrupted Core File: Run SFC and DISM to repair system binaries (Read SFC/DISM Guide).
If BugcheckCode is 0 with Event 41: The power abruptly died before Windows could write a dump. This indicates a failing Power Supply Unit (PSU), bad power cable, or motherboard VRM thermal shutdown.

Still Stuck? Submit Your Crash Dump Code

If you have your BugcheckCode and need diagnostic interpretation, submit your ticket at our Helpdesk Intake.