How To Check Crash Logs Windows 11: A Step-by-Step Guide For Users

Home » How-To

6 min. read

Published on October 30, 2025

Fix Windows errors with Fortect:
Fortect can repair common computer errors by scanning your entire system for damaged or missing OS files and replacing them with the original, working versions. Optimize your PC in 3 simple steps:

Download and Install Fortect on your PC
Use the PC Scan feature to look up any Windows issues (including drivers)
Right-click on Repair, and fix it within a few minutes.

Besides that, it helps you clean up junk files, fix stability problems, and get rid of annoying programs and malware traces.

Windows 11, despite its advancements, can still experience crashes. When your system unexpectedly shuts down or applications freeze, it’s crucial to understand why. Crash logs provide valuable insights into the root cause of these issues, helping you troubleshoot and resolve them effectively. This guide will walk you through the process of accessing and interpreting crash logs in Windows 11, empowering you to diagnose and fix system instability.

By examining these logs, you can identify problematic software, hardware conflicts, or driver issues that might be causing your system to crash. This step-by-step guide is designed to help both novice and experienced users navigate the process of finding and interpreting these logs, ultimately leading to a more stable and reliable Windows 11 experience.

Where Can I Find Crash Logs in Windows 11?

Using Event Viewer to Find System Crash Logs

The Event Viewer is a powerful tool in Windows 11 that records various system events, including crashes. Here’s how to use it to find system crash logs:

Press the Windows key + R to open the Run dialog box.
Type eventvwr.msc and press Enter to open the Event Viewer.
In the left pane, expand Windows Logs.
Click on System.
In the right pane, click Filter Current Log.
In the Filter Current Log window, select Error and Critical under the Event level section.
In the “Event sources” dropdown, select BugCheck.
Click OK to apply the filter.
Review the filtered logs for events related to system crashes. Look for entries with a date and time corresponding to when the crash occurred.

Accessing Application Crash Logs

Application crashes are logged separately. Here’s how to find them:

Open Event Viewer as described above.
In the left pane, expand Windows Logs.
Click on Application.
In the right pane, click Filter Current Log.
In the Filter Current Log window, select Error under the Event level section.
In the “Event sources” dropdown, select Application Error.
Click OK to apply the filter.
Examine the filtered logs for application-specific crash events. Note the application name and the error details.

Using Reliability Monitor

Reliability Monitor provides a user-friendly interface to view system stability and crash history.

Press the Windows key + R to open the Run dialog box.
Type perfmon /rel and press Enter to open the Reliability Monitor.
The Reliability Monitor displays a graph showing system stability over time.
Look for red circles or exclamation marks, which indicate crashes or errors.
Click on a specific date to view detailed information about the events that occurred on that day.

Checking for Minidump Files

Minidump files are small files that contain information about system crashes. These files can be analyzed to identify the cause of the crash.

Open File Explorer.
Navigate to C:\Windows\Minidump. If the folder doesn’t exist, it means minidumps are not enabled (see the Tips section below).
The folder contains .dmp files. These are the minidump files.
You can use tools like WinDbg (Debugging Tools for Windows) to analyze these files.

Reading the Blue Screen of Death (BSOD) Information

When Windows crashes, it often displays a Blue Screen of Death (BSOD). This screen contains valuable information about the crash.

When a BSOD appears, note the error message displayed on the screen. This message often provides clues about the cause of the crash.
Pay attention to the “Stop Code” or “Bug Check Code” displayed on the BSOD. This code can be used to research the specific type of error that occurred.
If the BSOD disappears too quickly, you can configure Windows to prevent automatic restarts after a crash (see the Tips section below).

Tips for Effective Crash Log Analysis

Enable Minidumps: Ensure that minidump files are enabled. To do this, right-click on This PC, select Properties, click on Advanced system settings, click on the Advanced tab, and then click Settings under Startup and Recovery. Make sure the “Write debugging information” option is set to “Small memory dump (256 KB)”.
Disable Automatic Restart: To prevent Windows from automatically restarting after a crash, go to the same “Startup and Recovery” settings and uncheck the “Automatically restart” option.
Update Drivers: Outdated or corrupted drivers are a common cause of crashes. Make sure your drivers are up to date, especially for your graphics card, network adapter, and storage devices.
Check Hardware: Faulty hardware can also cause crashes. Run diagnostics on your RAM, hard drive, and other components to check for errors.
Use Online Resources: Search the internet for the error messages or stop codes you find in the crash logs. Often, you’ll find solutions or workarounds posted by other users or experts.

Here’s a comparison of different methods for checking crash logs in Windows 11:

Method	Pros	Cons
Event Viewer	Detailed logs, comprehensive information	Can be overwhelming for beginners
Reliability Monitor	User-friendly interface, easy to understand stability graph	Less detailed information compared to Event Viewer
Minidump Files	Provides specific crash data for advanced analysis	Requires specialized tools and knowledge to interpret
BSOD Information	Immediate information about the crash, helpful for quick troubleshooting	The information might be too brief for in-depth analysis if the screen disappears

Troubleshooting Windows 11 Crashes

By following these steps, you can effectively check crash logs in Windows 11 and gain valuable insights into the causes of system instability. Remember to document your findings and any steps you take to resolve the issues.

FAQ

How do I interpret the error messages in the Event Viewer? Error messages in the Event Viewer often contain specific codes or descriptions that can help you identify the cause of the problem. Search online for these codes or descriptions to find more information.

What should I do if I can’t find any crash logs? Make sure that crash logging is enabled in Windows settings. Also, ensure that you are looking in the correct locations (e.g., Event Viewer, Minidump folder).

Can a virus cause system crashes? Yes, malware can cause system instability and crashes. Run a thorough scan with your antivirus software to check for infections.

How often should I check my crash logs? It’s a good practice to check your crash logs whenever you experience a system crash or instability. Regular monitoring can help you identify and address issues before they become more serious.

What is a Bug Check Code? A Bug Check Code, also known as a Stop Code, is a hexadecimal code displayed on the Blue Screen of Death (BSOD) that indicates the type of error that caused the system to crash. It’s crucial for diagnosing the root cause of the crash.