How to Check Blue Screen Log in Windows 11: A Step-by-Step Guide

By / September 22, 2025

A Blue Screen of Death (BSOD) can be one of the most frustrating experiences on a Windows 11 computer. One moment you’re working, the next your screen turns blue with an error message and your PC restarts. But here’s the good news: every BSOD creates a log file that helps you identify the cause.

In this guide, we’ll show you how to check blue screen logs in Windows 11, step by step, using built-in tools like Event Viewer, Reliability Monitor, and third-party utilities.

Key Takeaways

  • Blue screen errors are logged in Event Viewer under “System” events.

  • Windows creates dump files (minidumps) in the C:\Windows\Minidump folder.

  • Tools like Reliability Monitor and WhoCrashed make it easier to interpret logs.

  • Checking these logs helps you diagnose the cause of BSODs — often faulty drivers, RAM, or hardware conflicts.

Why Check Blue Screen Logs in Windows 11?

A BSOD can be caused by:

  • Corrupt or outdated drivers

  • Failing hardware (RAM, hard drive, GPU)

  • Overheating or power issues

  • Malware or corrupted system files

By checking the log files, you can:

  • Identify the error code (e.g., 0x0000007E)

  • Find the faulty driver or process

  • Take action to fix the root cause

Method 1: Check Blue Screen Logs Using Event Viewer

The Event Viewer is the primary tool for viewing BSOD logs.

Steps:

  1. Press Win + S and type Event Viewer, then open it.

  2. In the left pane, expand:

    Windows Logs > System

  3. Click Filter Current Log (right panel).

  4. In the Event sources drop-down, select:

    • BugCheck

    • EventLog

    • BlueScreen

  5. Click OK to filter.

  6. Double-click any log to see details like the error code and faulty driver.

✅ Example: You may see “The computer has rebooted from a bugcheck. Bugcheck was: 0x0000001E (parameter1, parameter2…).”

Method 2: Use Reliability Monitor

Reliability Monitor offers a user-friendly way to view BSOD events.

Steps:

  1. Press Win + S, type Reliability Monitor, and open View reliability history.

  2. Look for Critical Events marked with a red “X.”

  3. Click on the event to view details.

  4. Check the Technical Details section for error codes.

💡 This method is great for beginners since it presents data visually.

Method 3: Check Dump Files (Minidumps)

Windows creates dump files after a blue screen.

Steps:

  1. Navigate to:

    C:\Windows\Minidump

  2. Open the most recent .dmp file.

    • These require a debugging tool (see below).

Tools to Read Dump Files:

  • Windows Debugging Tools (WinDbg): Official Microsoft tool.

  • BlueScreenView (free, simple viewer).

  • WhoCrashed (analyzes dump files automatically).

Method 4: Use Command Prompt (Advanced Users)

You can also check crash details via Command Prompt.

Steps:

  1. Open Command Prompt (Admin).

  2. Run:

    wmic recoveros get DebugInfoType

  3. This shows the type of debugging information stored.

  4. For more details, open dump files using WinDbg.

Method 5: Use Third-Party Tools

If Event Viewer feels overwhelming, third-party tools simplify the process.

Recommended Tools:

  • BlueScreenView (NirSoft)

    • Automatically scans minidumps.

    • Highlights faulty drivers.

  • WhoCrashed

    • Easy-to-understand crash reports.

    • Suggests possible fixes.

Comparison of Methods

Method Difficulty Info Provided Best For
Event Viewer Medium Detailed logs & error codes IT & power users
Reliability Monitor Easy User-friendly history Beginners
Dump Files Advanced Deep debugging Developers
CMD Advanced Debug info type Tech-savvy users
Third-Party Tools Easy Simplified reports Everyday users

Step-by-Step Recap

  1. Event Viewer → Filter System logs for “BugCheck.”

  2. Reliability Monitor → Visual history of crashes.

  3. Minidump files → Stored in C:\Windows\Minidump.

  4. Command Prompt → View debug info type.

  5. Third-party tools → BlueScreenView/WhoCrashed for quick insights.

Conclusion

Blue screen crashes are scary, but they don’t have to remain a mystery. With tools like Event Viewer, Reliability Monitor, and dump file analyzers, you can quickly find out what went wrong and take steps to fix it.

👉 Next time you see the dreaded blue screen, don’t panic — just check the logs, identify the error, and apply the right fix.

FAQs

1. Where are blue screen logs stored in Windows 11?
In Event Viewer (System logs) and C:\Windows\Minidump.

2. Can I check BSOD logs without third-party tools?
Yes, using Event Viewer or Reliability Monitor.

3. What is a minidump file?
A small file that contains technical details about the crash, stored in the Minidump folder.

4. Do I need admin rights to view logs?
Yes, some tools like Event Viewer require administrator privileges.

5. How do I fix blue screen errors after checking logs?
Update drivers, run memory and disk diagnostics, check for overheating, or roll back recent updates.

Related Posts:

Scroll to Top