ErrorFix Pro
Diagnostics/BSOD Crash Dump Analyzer
Direct BugCheck & Event Log Parser

Interactive Windows BSOD Crash Dump & Minidump Log Analyzer

Paste your Blue Screen BugCheck code, Minidump text excerpt, or Event Viewer Event ID 1001/41 log. Our offline-ready engine extracts the failing driver, analyzes root causes, and generates verified PowerShell repair scripts.

Try a real-world crash sample:
Tip: You can export Event Viewer logs via Event Viewer > Windows Logs > System > Filter Event 41 / 1001.
Advertisement

Quick Diagnostics & TL;DR Summary

⏱️ 5–10 minutes⚡ Difficulty: Beginner to Intermediate🔄 Reboot Needed
  • Kernel dumps are saved in C:\Windows\Minidump and logged as Event ID 1001 in Event Viewer.
  • Common culprit drivers include nvlddmkm.sys (GPU), ntoskrnl.exe (OS kernel), and stornvme.sys (SSD).
  • Hardware instability (RAM bit-flips or unstable CPU overclocks) triggers BugChecks 0x1A and 0x124.
Required Utilities:Command Prompt (Admin)System Restart

Where Can I Find My Windows Crash Dump Files and Event Viewer Logs?Log Extraction

When Windows crashes, it writes telemetry information to two primary storage locations on your local drive:

  • Small Memory Dumps (Minidumps): Located at C:\Windows\Minidump\. These compact files (~256KB to 1MB) contain the BugCheck code, failing module name, and stack frame of the thread that crashed.
  • Kernel Memory Dump: Located at C:\Windows\MEMORY.DMP. Contains the complete kernel-mode memory space at the moment of the crash.
  • Windows Event Viewer: Open Event Viewer (Win + X > Event Viewer), navigate to Windows Logs > System, and look for entries tagged with Source: BugCheck (Event ID 1001) or Kernel-Power (Event ID 41).
💡PowerShell Fast Extraction
You can export your last 3 crash events directly to your desktop by running this one-line PowerShell command as Administrator:
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-Kernel-Power'} -MaxEvents 3 | Export-Clixml $HOME\Desktop\crashes.xml

What Are the Most Common Blue Screen Stop Codes and Their Solutions?Diagnostic Reference

CRITICAL_PROCESS_DIED (0xEF)
A critical Windows system process (such as csrss.exe, wininit.exe, or svchost.exe) terminated abruptly.
Fix: Run DISM and SFC to restore damaged Windows system binaries.
DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x0A)
A kernel-mode driver attempted to access pageable memory at an improper Interrupt Request Level (IRQL).
Fix: Update network, audio, and chipset drivers; run Driver Verifier.
SYSTEM_SERVICE_EXCEPTION (0x3B)
An exception occurred while executing system code, often referencing graphics drivers like nvlddmkm.sys.
Fix: Reinstall GPU drivers cleanly using DDU in Safe Mode.
WHEA_UNCORRECTABLE_ERROR (0x124)
Windows Hardware Error Architecture caught a fatal CPU core, cache, or bus parity mismatch.
Fix: Reset BIOS overclocking / EXPO profiles; inspect CPU thermal paste and voltages.

Frequently Asked Questions About Windows Blue Screen CrashesFAQ