When Windows 11 crashes, freezes, or shows a Blue Screen of Death (BSOD), the system records details in crash logs that can help you find the root cause. This guide shows you how to view those logs using built-in tools like Event Viewer and Reliability Monitor, plus how to analyze minidump files for deeper debugging. You don’t need any special software—just a Windows 11 PC and a few minutes.
What You’ll Need
- A Windows 11 PC with administrator access (to view certain logs)
- Basic familiarity with navigating the Start menu and Control Panel
- Optional: WinDbg or BlueScreenView (free tools) for minidump analysis
Step-by-Step
Method 1: Use Event Viewer (Most Detailed)
- Press Win + R to open the Run dialog, type
eventvwr.msc, and press Enter. Alternatively, search for “Event Viewer” in the Start menu and click the app. - In the left sidebar, expand Windows Logs and select System. This log contains events from Windows system components, including crashes.
- Click Filter Current Log… in the right-hand Actions pane.
- Under Event sources, check the boxes for BugCheck, Kernel-Power, and Windows Error Reporting. These are the most common sources for crash-related events. Click OK.
- Look for events with Event ID 41 (Kernel-Power) – indicates the system rebooted without a clean shutdown, often due to a crash or power loss. Event ID 1001 (BugCheck) shows the actual BSOD error code. Event ID 1000 or 1002 (Windows Error Reporting) relate to application crashes.
- Click on any event to see details in the bottom pane. The General tab shows a description; the Details tab shows raw XML with more specifics like the bug check code.
Method 2: Use Reliability Monitor (User-Friendly)
- Open the Start menu, type
reliability, and select View reliability history (or search for “Reliability Monitor”). - The monitor shows a timeline of system events, including crashes (red circles with an X), warnings (yellow triangles), and informational events.
- Click on a red circle to see details about that crash. The panel below displays the date, the problem, and which application or component failed.
- Click View technical details for a more detailed report, including the faulting module and exception code.
Method 3: Analyze Minidump Files (For BSODs)
- By default, Windows creates a minidump file at
C:\Windows\Minidumpwhen a BSOD occurs. Open File Explorer and navigate to that folder. - If you see .dmp files, you can analyze them with a free tool like BlueScreenView (download from a trusted source) or WinDbg (from the Microsoft Store).
- For BlueScreenView: download and run it—it automatically scans the Minidump folder and lists crashes. Click a crash to see the bug check code and the drivers involved.
- For WinDbg: open WinDbg, click File > Open Crash Dump, select the .dmp file, and run
!analyze -vin the command line. This gives a detailed analysis, but it requires some familiarity with debugging.
Method 4: Check Application Crash Logs
- If a specific app crashes, look in Event Viewer under Windows Logs > Application.
- Filter by source Application Error or .NET Runtime to find events with Event ID 1000 or 1026.
- These logs show the faulting module (e.g., a .dll file) and the exception code, which can help identify the cause.
Common Mistakes
- Looking only at the System log without filtering – you’ll miss crash events among thousands of informational entries. Always use the filter.
- Ignoring Event ID 41 (Kernel-Power) – many users assume it’s just a power issue, but it often indicates a hardware or driver problem that caused the crash.
- Assuming the minidump folder is always present – if the system crashes hard, the dump may not be written. Check if the folder exists; if not, you may need to enable it (see Tips).
- Deleting logs before analyzing – if you clear the logs, you lose the evidence. Always export or note the details first.
- Misreading bug check codes – a code like 0x0000007B (INACCESSIBLE_BOOT_DEVICE) requires specific interpretation; don’t guess. Use the code to search for known fixes.
Tips
- Enable automatic memory dumps – Go to Settings > System > About > Advanced system settings > Startup and Recovery > Settings. Under “Write debugging information,” select “Automatic memory dump” (or “Small memory dump” for minidumps). This ensures dumps are created on BSOD.
- Use the Event Viewer filter efficiently – Save a custom view (right-click > Create Custom View) with the sources you care about, so you don’t have to reapply filters each time.
- Look for patterns – If crashes happen at the same time or after a specific action, note it. This context is often more valuable than the raw log.
- Check for Windows updates – After identifying a crash, check if a recent update or driver change coincides. Roll back the driver or uninstall the update to test.
- Use the Windows Memory Diagnostic – If you suspect RAM issues (common cause of BSOD), run
mdsched.exeto test memory.
Troubleshooting
- Event Viewer shows nothing for the crash time – If the system crashed hard, the log may not have been written. Check the Reliability Monitor for a more user-friendly timeline. Also, check if the system time is correct; if the clock was wrong, events may appear at the wrong time.
- Minidump folder is empty or missing – Ensure that crash dumps are enabled (see Tips). If they are, but no dumps appear, the crash may be too severe to write a dump. In that case, focus on Event Viewer and the bug check code.
- You can’t open Event Viewer as a standard user – Some logs require admin rights. Right-click Event Viewer and select “Run as administrator.” If your account isn’t admin, you’ll need to ask the administrator.
- BlueScreenView shows no crashes – The tool looks in the default Minidump folder. If you changed the dump location, update the settings in BlueScreenView (Options > Advanced Options) to point to the correct folder.
- WinDbg gives an error like “Debugging details are not available” – This often happens when the dump file is corrupt or the symbol files are missing. Run
.symfixand.reloadin WinDbg to download symbols, then retry!analyze -v. - Crash logs point to a driver, but you don’t know which one – Use the bug check code and the faulting module name from the log. Search the web for “[module name] Windows 11 crash” to find known issues. You can also use a tool like Driver Verifier (though it’s advanced and can cause boot loops, so use with caution).
Frequently Asked Questions
Where are crash logs stored in Windows 11?
Crash logs are stored in the Windows Event Log (accessible via Event Viewer) as events, and minidump files are stored in C:\Windows\Minidump for BSODs. Application crashes are logged in the Application log.
How do I find the Blue Screen of Death error code?
In Event Viewer, filter the System log for source BugCheck (Event ID 1001). The error code appears in the event details, often as a hexadecimal number like 0x0000007E. Alternatively, use BlueScreenView to see the code from the minidump.
What is Event ID 41 Kernel-Power?
Event ID 41 means the system rebooted without a clean shutdown. It’s logged when Windows crashes, loses power, or experiences a hardware failure. It doesn’t give a specific cause, but it confirms a crash occurred.
Can I delete crash logs?
Yes, you can clear logs in Event Viewer (right-click a log > Clear Log) and delete .dmp files. However, it’s wise to keep them until you’ve resolved the issue, as they contain diagnostic information.
Do I need third-party software to read crash logs?
No, Event Viewer and Reliability Monitor are built-in and sufficient for most users. Third-party tools like BlueScreenView are only needed for deeper minidump analysis, which is optional.
Why does my PC crash but no logs appear?
If the crash is severe (e.g., hardware failure), Windows may not have time to write logs. Also, if you have disabled crash dumps, no minidump will be created. Check your dump settings and ensure write access to the system drive.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Schedule Tweets on X (Twitter) Web App
- PlayStation Games Still Physical After Store Closures
- Fix Standby Mode Not Working on iPhone
- Madden 19 Crashing on PC: Fixed
- macOS Sierra USB Installer: How to Make One
- Fix System PTE Misuse BSOD on Windows