Documentation
Complete guide to using BSOD AI Analyzer for Windows crash analysis
Getting Started
BSOD AI Analyzer is a free, web-based tool that helps you understand and resolve Windows Blue/Black Screen of Death errors. Our AI-powered system analyzes crash dump files to identify the root cause and provide actionable solutions. Supports both classic blue screens and Windows 11's modern black screens.
What You'll Need
- A Windows crash dump file or supported archive - typically found in C:\Windows\Minidump
- A modern web browser (Chrome, Firefox, Edge, or Safari)
- An internet connection for AI-powered analysis
- No installation or technical knowledge required
Understanding Windows Crash Dumps
What is a Memory Dump?
A memory dump (also called a crash dump) is a snapshot of your computer's memory at the exact moment a Blue or Black Screen of Death occurs. Windows creates these files to help diagnose what caused the system to crash. The screen color depends on your Windows version.
Types of Dump Files
- Minidump (Small Memory Dump)
- Typically 64KB to 2MB in size. Contains minimal information: stop code, parameters, loaded driver list, and basic system information. Located in
C:\Windows\Minidump. - Kernel Memory Dump
- Usually 1/3 of RAM size. Contains all kernel-mode memory, loaded drivers, and kernel data structures. More detailed than minidumps but doesn't include user-mode memory.
- Complete Memory Dump
- Size equals total RAM. Contains the entire contents of physical memory. Most comprehensive but requires significant disk space and longer to generate.
Finding Your Dump Files
Default Locations
- Minidumps:
C:\Windows\Minidump\ - Kernel/Complete dumps:
C:\Windows\MEMORY.DMP
Checking Dump Settings
- Right-click "This PC" (or "My Computer") and select "Properties"
- Click "Advanced system settings" on the left
- Under the "Advanced" tab, in "Startup and Recovery," click "Settings"
- Check the "Write debugging information" dropdown - ensure it's not set to "(none)"
- Verify the dump file path (usually %SystemRoot%\MEMORY.DMP)
- Click OK to save any changes
Using the Analyzer
Step 1: Prepare Your Files
Supported formats:
- .dmp, .mdmp, .hdmp, and .kdmp files (any type of Windows dump)
- .zip, .7z, and .rar archives containing .dmp files
- Multiple files can be analyzed in one session
Step 2: Upload and Analyze
- Navigate to the Analyzer page
- Drag and drop your files or click to browse
- Click "Analyze" to start the analysis
- The backend uses WinDBG when available, or validated AI fallback when it is not
- Wait for results (typically 30-60 seconds for first analysis, instant for cached files)
Understanding Analysis Results
Each analysis report includes:
Summary Section
- Plain Language Explanation: What happened in simple terms
- Severity Level: Critical, High, Medium, or Low
- Crash Type: Driver, Hardware, System, or Application
Technical Details
- Stop Code: The specific BSOD error code
- Probable Cause: Most likely reason for the crash
- Culprit: Specific driver or component responsible
- Call Stack: Function calls leading to the crash
Recommendations
Our AI provides personalized, step-by-step solutions tailored to your specific crash:
- Immediate Actions: Quick fixes you can try right away
- Driver Updates: Specific drivers that need updating with download links
- Hardware Tests: Diagnostics to run if hardware issues are suspected
- System Configuration: Settings changes to prevent future crashes
- Follow-up Steps: Long-term solutions for system stability
Common BSOD Error Codes
Below is a comprehensive list of Windows Blue Screen error codes. Click on any error to expand for detailed information and solutions.
Most Frequent Errors
IRQL_NOT_LESS_OR_EQUAL (0x0000000A)
Usually indicates a driver attempting to access memory at an invalid IRQL level. Often caused by faulty drivers or hardware issues.
Common fixes: Update drivers, test RAM, check for overheating
PAGE_FAULT_IN_NONPAGED_AREA (0x00000050)
System tried to access non-existent memory. Can be caused by faulty RAM, corrupted drivers, or antivirus software.
Common fixes: Run memory diagnostic, update/remove antivirus, check drivers
SYSTEM_SERVICE_EXCEPTION (0x0000003B)
Exception occurred while executing a system service routine. Often related to graphics drivers or system file corruption.
Common fixes: Update GPU drivers, run SFC scan, check for Windows updates
KERNEL_SECURITY_CHECK_FAILURE (0x00000139)
Kernel detected corruption in a critical data structure. Usually indicates driver issues or memory corruption.
Common fixes: Update all drivers, check disk health, test RAM
CRITICAL_PROCESS_DIED (0x000000EF)
A critical system process terminated unexpectedly. Can be caused by system file corruption or incompatible software.
Common fixes: Run DISM and SFC, check for malware, boot in safe mode
DRIVER_VERIFIER_DETECTED_VIOLATION (0x000000C4)
Driver Verifier detected a driver behaving improperly. This typically occurs when testing drivers for compatibility issues.
Common fixes: Disable Driver Verifier, update problematic drivers, remove recently installed drivers
DPC_WATCHDOG_VIOLATION (0x00000133)
A DPC routine ran too long, indicating a driver compatibility issue. Often related to SSD firmware or old drivers.
Common fixes: Update SSD firmware, check SATA drivers, update chipset drivers
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E)
A system thread generated an exception that wasn't handled. Usually indicates driver or hardware issues.
Common fixes: Update or rollback recent driver updates, check for hardware issues
MEMORY_MANAGEMENT (0x0000001A)
Severe memory management error. Often caused by faulty RAM, driver issues, or software bugs.
Common fixes: Run Windows Memory Diagnostic, update drivers, check for disk errors
Driver-Related Errors
DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1)
A driver attempted to access pageable memory at an inappropriate IRQL. Common with network and USB drivers.
Common fixes: Update network/USB drivers, remove recently installed hardware
DRIVER_POWER_STATE_FAILURE (0x0000009F)
Driver failed to handle power state transition properly. Common during sleep/wake cycles.
Common fixes: Update device drivers, check power settings, disable fast startup
DRIVER_OVERRAN_STACK_BUFFER (0x000000F7)
A driver overflowed a stack-based buffer. Indicates a serious driver bug.
Common fixes: Identify and update/remove the faulty driver, check for driver updates
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (0x000000CE)
A driver unloaded without canceling pending operations. Usually a driver programming error.
Common fixes: Update the problematic driver, remove recently installed drivers
Hardware-Related Errors
MACHINE_CHECK_EXCEPTION (0x0000009C)
Fatal hardware error detected by CPU. Often indicates failing CPU, motherboard, or power supply.
Common fixes: Check CPU temperature, test with different PSU, run hardware diagnostics
WHEA_UNCORRECTABLE_ERROR (0x00000124)
Hardware error reported by Windows Hardware Error Architecture. Serious hardware problem detected.
Common fixes: Check all hardware components, update BIOS, check for overheating
CLOCK_WATCHDOG_TIMEOUT (0x00000101)
Processor core didn't respond within allocated time. Multi-core synchronization issue.
Common fixes: Update BIOS, check CPU cooling, disable overclocking
HAL_INITIALIZATION_FAILED (0x0000005C)
Hardware Abstraction Layer failed to initialize. Often indicates hardware incompatibility.
Common fixes: Check hardware compatibility, update BIOS, remove incompatible hardware
File System Errors
NTFS_FILE_SYSTEM (0x00000024)
Problem with the NTFS file system driver. Usually indicates disk corruption or failing hard drive.
Common fixes: Run chkdsk /f /r, check disk health, backup data immediately
FAT_FILE_SYSTEM (0x00000023)
Problem with FAT file system. Common with USB drives or older partitions.
Common fixes: Run chkdsk on the affected drive, check for disk errors
DATA_BUS_ERROR (0x0000002E)
Parity error in system memory. Usually indicates failing RAM or motherboard issues.
Common fixes: Test RAM modules individually, check motherboard for damage
KERNEL_DATA_INPAGE_ERROR (0x0000007A)
Kernel couldn't read requested data from pagefile. Often indicates disk or memory issues.
Common fixes: Check disk health, test RAM, check SATA cables
Security and System Errors
SECURITY_SYSTEM (0x00000029)
Security system encountered fatal error. Can be caused by security software conflicts.
Common fixes: Remove conflicting security software, check for malware
SYSTEM_LICENSE_VIOLATION (0x0000009A)
Software license agreement violation detected. Rare error related to system integrity.
Common fixes: Verify Windows activation, run system file checker
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (0x000000FC)
Attempt to execute non-executable memory. Security feature prevented code execution.
Common fixes: Update drivers, check for malware, verify DEP settings
SESSION_HAS_VALID_POOL_ON_EXIT (0x000000AB)
Session unloaded with pool allocations still active. Indicates driver memory leak.
Common fixes: Update graphics drivers, check for driver memory leaks
Boot and Initialization Errors
INACCESSIBLE_BOOT_DEVICE (0x0000007B)
Windows lost access to the boot partition during startup. Common after hardware changes.
Common fixes: Check BIOS settings, verify boot drive connection, repair boot configuration
UNMOUNTABLE_BOOT_VOLUME (0x000000ED)
Boot volume cannot be mounted. File system or disk controller issues.
Common fixes: Run startup repair, check disk for errors, verify SATA mode in BIOS
BOOT_INITIALIZATION_FAILED (0x0000006B)
Windows failed to initialize during boot process. Often caused by corrupted system files.
Common fixes: Use System Restore, run startup repair, check for disk corruption
STATUS_SYSTEM_PROCESS_TERMINATED (0x000000C00002E2)
Critical system process terminated during boot. Severe system file corruption.
Common fixes: Boot from installation media and repair, restore from backup
Memory and Resource Errors
OUT_OF_MEMORY (0x0000002D)
System ran out of memory resources. Can occur with memory leaks or insufficient RAM.
Common fixes: Add more RAM, check for memory leaks, increase pagefile size
POOL_CORRUPTION_IN_FILE_AREA (0x000000DE)
Memory pool corruption detected in file system structures. Driver or hardware issue.
Common fixes: Update storage drivers, check disk integrity, test RAM
BAD_POOL_HEADER (0x00000019)
Pool header corruption detected. Usually caused by driver bugs or failing RAM.
Common fixes: Update all drivers, run memory diagnostic, check for overheating
PFN_LIST_CORRUPT (0x0000004E)
Page Frame Number list is corrupted. Serious memory management issue.
Common fixes: Test RAM thoroughly, update chipset drivers, check motherboard
Network and Communication Errors
TCPIP_AOAC_NIC_ACTIVE_REFERENCE_LEAK (0x00000165)
Network adapter driver leaked an active reference. Power management issue with network card.
Common fixes: Update network drivers, disable power saving for network adapter
NETWORK_BOOT_INITIALIZATION_FAILED (0x0000006C)
Network boot failed to initialize. Common in diskless workstation environments.
Common fixes: Check network boot settings, verify PXE configuration
NDIS_INTERNAL_ERROR (0x0000007C)
Internal error in Network Driver Interface Specification. Network driver problem.
Common fixes: Update or reinstall network drivers, check for driver conflicts
USB and External Device Errors
BUGCODE_USB_DRIVER (0x000000FE)
USB driver encountered fatal error. Common with problematic USB devices or hubs.
Common fixes: Update USB drivers, remove USB devices, check for faulty USB ports
USB_DRIPS_BLOCKER_SURPRISE_REMOVAL_LIVEDUMP (0x00000180)
USB device was surprise-removed while blocking system sleep. Power management issue.
Common fixes: Safely remove USB devices, update USB controller drivers
INVALID_USB_DESCRIPTOR (0x00000166)
USB device provided invalid descriptor. Faulty or incompatible USB device.
Common fixes: Remove the problematic USB device, update device firmware
Graphics and Display Errors
VIDEO_TDR_FAILURE (0x00000116)
Display driver stopped responding and was recovered. GPU timeout detection and recovery.
Common fixes: Update graphics drivers, check GPU temperature, reduce GPU overclock
VIDEO_SCHEDULER_INTERNAL_ERROR (0x00000119)
Video scheduler encountered fatal error. Graphics subsystem problem.
Common fixes: Reinstall graphics drivers, check for GPU hardware issues
VIDEO_MEMORY_MANAGEMENT_INTERNAL (0x0000010E)
Video memory manager encountered unrecoverable error. VRAM or driver issue.
Common fixes: Update GPU drivers, test with different GPU, check VRAM integrity
DISPLAY_DRIVER_STOPPED_RESPONDING (0x00000117)
Display driver stopped responding. Similar to VIDEO_TDR_FAILURE but more severe.
Common fixes: Clean install graphics drivers, check display cable connections
Virtualization and Hyper-V Errors
HYPERVISOR_ERROR (0x00020001)
Hyper-V hypervisor encountered fatal error. Virtualization platform issue.
Common fixes: Update Hyper-V, check virtualization settings in BIOS
VMBUS_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED (0x00000151)
Virtual machine exceeded processor limit. Hyper-V configuration issue.
Common fixes: Reduce virtual processors, check Hyper-V limits
Miscellaneous System Errors
UNEXPECTED_KERNEL_MODE_TRAP (0x0000007F)
Kernel encountered unexpected condition. Can be hardware or software related.
Common fixes: Check for overheating, test RAM, update all drivers
KMODE_EXCEPTION_NOT_HANDLED (0x0000001E)
Kernel-mode program generated exception not handled. Driver or hardware issue.
Common fixes: Update drivers, check for hardware problems, run system diagnostics
REFERENCE_BY_POINTER (0x00000018)
Object reference count error. Usually indicates driver programming error.
Common fixes: Update or remove problematic drivers, check for driver conflicts
WORKER_THREAD_RETURNED_AT_BAD_IRQL (0x000000E1)
Worker thread returned at wrong IRQL. Driver didn't properly restore IRQL.
Common fixes: Identify and update the faulty driver
WinDBG Analysis Details
The primary analysis path runs real WinDBG debugging commands on your crash dump server-side. When this path is available, the output comes directly from WinDBG - not a simulation. Key commands include:
!analyze -vProvides verbose analysis including stack trace, error details, and follow-up suggestions
lm kvLists all kernel modules with version information and timestamps
!process 0 0Shows process information at the time of crash
!vmDisplays virtual memory usage and statistics
Symbol Resolution
On successful WinDBG analyses, the server automatically downloads and resolves Windows symbols from Microsoft's symbol servers, providing accurate function names and call stacks:
- Downloads PDB symbols for the exact Windows version from the crash
- Resolves driver and system function names automatically
- Provides accurate stack traces with module and offset information
- Symbols are cached on the server for faster subsequent analysis
Reading Stack Traces
Stack traces show the sequence of function calls leading to the crash. Our analyzer automatically interprets these for you, but understanding the basics can be helpful:
- Top of stack: The function where the crash occurred
- Call sequence: Each line shows a function that called the one above it
- Module names: Show which driver or system component each function belongs to
- Offsets: Help pinpoint the exact location within a function
Preventing Future Crashes
While our analyzer helps fix crashes after they occur, following these best practices can help prevent Blue Screens:
Regular Maintenance
- Keep Windows Updated: Install updates promptly to fix known issues
- Update Drivers Regularly: Especially graphics, chipset, and storage drivers
- Monitor System Health: Check Event Viewer for warnings before crashes occur
- Clean Boot Periodically: Remove unnecessary startup programs
Hardware Care
- Monitor Temperatures: Ensure proper cooling to prevent thermal issues
- Test RAM Periodically: Run Windows Memory Diagnostic monthly
- Check Disk Health: Use CrystalDiskInfo to monitor SSD/HDD health
- Stable Power Supply: Use a UPS for desktop systems
Software Best Practices
- Avoid Beta Drivers: Stick to stable, WHQL-certified drivers
- Uninstall Conflicting Software: Remove multiple antivirus programs
- Create Restore Points: Before major system changes
- Regular Backups: Protect your data in case of system failure
Troubleshooting Tips
Before Analysis
- Ensure dump files are not corrupted (check file size is greater than 0)
- Compress large files into ZIP, 7z, or RAR archives for faster upload
- Check that automatic dump creation is enabled in Windows
Common Solutions
- Update Drivers: Especially graphics, network, and chipset drivers
- Run Memory Test: Use Windows Memory Diagnostic or MemTest86
- Check Disk Health: Run
chkdsk /f /rand check SMART data - System File Check: Run
sfc /scannowandDISM /Online /Cleanup-Image /RestoreHealth - Update BIOS: Check manufacturer's website for updates
If Problems Persist
Consider these advanced steps:
- Boot in Safe Mode to isolate driver issues
- Use System Restore to revert recent changes
- Perform a clean boot to identify software conflicts
- Check Event Viewer for additional error details
Frequently Asked Questions
Is my dump file data kept private?
Yes. Your dump file is processed by our secure backend. The primary path uses the WinDBG server; fallback analysis uses local or sampled evidence. Files are not retained after processing. Analysis results are cached temporarily to speed up repeat queries. All communications are encrypted via TLS, and no personal information is collected.
Why can't I find any dump files?
Windows might not be configured to create dumps. Check your Startup and Recovery settings and ensure "Write debugging information" is not set to "None".
How accurate is the analysis?
When WinDBG is available, our analyzer runs real debugging on your crash dump, producing professional WinDBG output for AI interpretation. If WinDBG is unavailable, the report is generated from validated local or sampled dump evidence and is marked as fallback analysis. Complex hardware issues may still require additional diagnostic tools.
Can I analyze Linux or macOS crashes?
Currently, we only support Windows crash dumps. Support for other operating systems is planned for future updates.
What if the analyzer can't determine the cause?
Review the raw WinDBG output included with the report for more detailed information. If the issue persists, the crash might be caused by hardware failure or require professional diagnosis.
What's the difference between minidump and kernel dump?
Minidumps (64KB-2MB) contain essential crash information and are sufficient for most crash analysis. Kernel dumps (larger, ~1/3 of RAM) include all kernel memory and provide more detailed information for complex issues. Our analyzer handles both types automatically.
How often should I analyze crash dumps?
Analyze dumps whenever you experience a Blue Screen. If you have recurring crashes, analyze multiple dumps to identify patterns. Regular analysis helps catch driver issues before they become critical.
Where can I find more information about Windows crashes?
For additional resources and community support: