Crash Logs in Windows 11: 6 Ways to Find and Read Them

When your PC freezes or shows a blue screen, the answer to why is almost always written down somewhere. This guide shows where to find crash logs in Windows 11 and how to read them, using Reliability Monitor, Event Viewer and the dump files Windows saves. Knowing the crash logs in Windows 11 makes fixing repeated crashes much faster.

Quick answer: open Reliability Monitor with perfmon /rel, check Event Viewer under Windows Logs, System for Critical errors and Event ID 41, and look in C:\Windows\Minidump for dump files that you can open with WinDbg.

What Causes Crash Logs in Windows 11?

Windows records crashes in several places, each with different detail: Problems like this often travel together, so it also helps to know the taskbar freezing guide and the Windows 11 update stuck at 46% guide.

• Reliability Monitor gives a simple timeline of crashes and failed updates.
• Event Viewer records detailed system and application errors.
• Minidump files store memory details when a blue screen occurs.
• Windows Error Reporting keeps reports for app crashes.
• The full memory dump, MEMORY.DMP, is saved when configured.

How to Fix Crash Logs in Windows 11: Step-by-Step

Step 1: Open Reliability Monitor

Press Win + R, type perfmon /rel, and press Enter. The chart shows a stability index and red X marks for crashes, failures and critical events. Click a day to see details, and use View technical details for the error and module name. If this first step does not solve it, the taskbar freezing guide and the Windows 11 update stuck at 46% guide cover related causes.

Step 2: Open Event Viewer

Search for Event Viewer and open Windows Logs, System. Click Filter Current Log and choose Critical and Error. Look at events near the time of the crash. Event ID 41 from Kernel-Power means the PC restarted without shutting down cleanly, and Event ID 1001 from BugCheck records a blue screen code.

Also Read: https://axeetech.com/how-to-view-a-dmp-file-in-windows-complete-guide/

Step 3: Find the minidump files

Open File Explorer and go to C:\Windows\Minidump. Each crash creates a dump file named with the date. You may need administrator rights to open it. If the folder is empty, minidumps may be switched off, so check Startup and Recovery settings.

Step 4: Enable crash dumps

Press Win + R, type sysdm.cpl, open Advanced, Startup and Recovery, Settings. Under Write debugging information choose Small memory dump or Automatic memory dump, and keep Automatically restart off for easier diagnosis. See our automatic repair loop guide for the related recovery options.

Step 5: Read the dump file

Open the file in WinDbg from the Microsoft Store and run !analyze -v. The probable cause, module name and bug check code appear near the top. Our guide to viewing a .dmp file explains the process in detail.

Step 6: Check app crash reports

For program crashes, open Event Viewer, Windows Logs, Application, and filter for Application Error. The Faulting application name and Faulting module name show which app and library failed. Search the module name along with the error code on the Microsoft support site.

What the Common Events Mean

Event 41 Kernel-Power signals an unexpected restart. Event 6008 says the previous shutdown was unexpected. Event 1001 with source BugCheck lists the stop code, such as MEMORY_MANAGEMENT. Combine the code with the time to match it to a driver or hardware change. For example, memory related stop codes are covered in the MEMORY_MANAGEMENT guide.

Tools That Make Reading Easier

Reliability Monitor is the easiest tool for beginners. For deeper analysis use WinDbg, which Microsoft documents in its debugging tools reference. Free viewers such as BlueScreenView show the driver names from minidump files in a simple table.

How to Share Crash Information With Support

If you need help from a vendor or a forum, give them clear facts. Note the exact time of the crash, what you were doing and what changed recently, such as a new driver or update. In Event Viewer, right-click the System log, choose Save Filtered Log File As, and attach it. In Reliability Monitor, use Save reliability history.

Copy the newest file from C:\Windows\Minidump, but remember that dumps may contain private data, so share them only with trusted support. A short, specific report gets better answers than a long description of the symptoms.

Common Mistakes When Fixing Crash Logs in Windows 11

• Looking only at the Application log for a blue screen.
• Turning off dump creation to save space.
• Forgetting that dump files need administrator rights to read.
• Fixing the symptom without matching the log time to the crash.

Quick Recap: Crash Logs in Windows 11

Start with Reliability Monitor, confirm the time in Event Viewer, then read the minidump if the PC crashed with a blue screen. With these crash logs in Windows 11, you can usually tell whether a driver, update or hardware fault is to blame.

Crash Logs in Windows 11 FAQ

Where are crash logs stored in Windows 11?

Minidumps are in C:\Windows\Minidump, and event logs are viewed in Event Viewer, with a simpler timeline in Reliability Monitor.

What is Event ID 41?

It is a Kernel-Power event meaning the PC restarted without a clean shutdown, often after a crash or power loss.

Why is my Minidump folder empty?

Dump creation may be off, or the system could not write the dump. Check Startup and Recovery settings.

Can I read the dump files without WinDbg?

Yes. Free viewers like BlueScreenView show the main details.