⚠️ How to View and Generate CRITICAL System Crash Reports in Windows 10 and 11
When your Windows PC suddenly freezes, restarts, or shows a Blue Screen of Death (BSOD), the system records detailed crash data that can help you identify what went wrong.
These logs are called system crash reports, and they capture key information about hardware failures, driver issues, and system-level errors.
This guide explains — step by step — how to view, analyze, and generate these critical error reports in Windows 10 and 11 using built-in tools and PowerShell commands.
🧩 What Are System Crash Reports?
Every time Windows experiences a serious problem (like a power failure, kernel panic, or system bug check), it writes an entry in the Event Log and may create a memory dump file.
These logs store:
- The error code (stop code)
- The faulting driver or module
- The timestamp and system state
- Related hardware or power events
They’re essential for diagnosing the root cause of a system crash.
🧭 Step 1: Use Event Viewer to Check System Crash Logs
The Event Viewer is the most direct way to find critical system crash reports.
🔹 Open Event Viewer
- Press Win + X → choose Event Viewer.
- In the left pane, go to Windows Logs → System.
- In the right pane, select Filter Current Log.
- Under Event Level, check Critical and Error, then click OK.
You’ll now see a list of all critical system events.
🔹 Key Event IDs to Watch
| Event ID | Type | Description |
|---|---|---|
| 41 | Kernel-Power | System rebooted without clean shutdown — common in BSODs or power loss. |
| 1001 | BugCheck | Windows detected a crash and created a memory dump file. |
| 6008 | EventLog | Unexpected system shutdown. |
| 1000 | Application Error | A program caused Windows to crash or hang. |
Double-click any event to open details such as the source file, faulting driver, and error message.
💡 Tip: You can right-click and select “Copy → Copy Details as Text” to share the event log with IT or support teams.
📊 Step 2: Use Reliability Monitor for a Visual Overview
For a more user-friendly way to review crashes and warnings, use the Reliability Monitor.
🔹 How to Open
- Press Win + R, type
perfmon /rel, and hit Enter. - The Reliability Monitor shows a daily timeline of system stability.
- Look for red X marks — these indicate system or app failures.
- Click a red X to view details like:
- Faulting application or driver
- Error signature
- Event time and stability impact
It also tracks Windows updates, app installations, and critical events, so you can pinpoint what caused instability (e.g., a driver update or hardware issue).
⚙️ Step 3: Generate a Full System Health Report
To get a comprehensive snapshot of your PC’s health and recent errors:
🔹 Steps
- Press Win + R → type
perfmon /report→ press Enter. - Windows collects diagnostic data for about 60 seconds.
- When done, it displays a System Diagnostics Report containing:
- Hardware configuration
- Driver status
- System performance metrics
- Critical events and warnings
This report is detailed and ideal for administrators or IT professionals who want a full system overview.
You can save or export the report for future analysis by right-clicking it and selecting Save As HTML.
🧠 Step 4: Locate and Analyze Memory Dump Files
When Windows crashes with a BSOD, it generates a memory dump file containing technical details about the crash.
🔹 Default Dump Locations
| Type | File Path |
|---|---|
| Full Memory Dump | C:\Windows\MEMORY.DMP |
| Mini Dumps | C:\Windows\Minidump\ |
🔹 How to Analyze
Use one of the following tools:
- WinDbg Preview (Microsoft Store): Microsoft’s official tool for deep analysis.
- BlueScreenView (NirSoft): Simple viewer showing the driver or file that caused the crash.
- WhoCrashed: User-friendly utility that explains the crash cause in plain English.
⚠️ Note: These tools can identify which driver (e.g.,
nvlddmkm.sysorntoskrnl.exe) triggered the error, helping you find the exact problem.
🧰 Step 5: Export or Share Event Logs
If you need to send your logs to Microsoft support or your IT department:
- Open Event Viewer → select System.
- Click Action → Save All Events As…
- Choose a file name and save it in
.evtxformat. - Compress the file if it’s large before sending.
This makes it easier for technicians to reproduce and analyze the error sequence.
💻 Step 6: Generate System Error Reports with PowerShell
You can also generate a list of critical and error events using a one-line PowerShell command:
Get-WinEvent -FilterHashtable @{LogName='System'; Level=1,2; StartTime=(Get-Date).AddDays(-7)} |
Format-List TimeCreated, Id, LevelDisplayName, Message |
Out-File "$env:USERPROFILE\Desktop\Critical_Error_Report.txt"
This command:
- Collects Critical (Level 1) and Error (Level 2) logs from the last 7 days.
- Exports them to a text file on your Desktop.
You’ll get a readable summary with timestamps and messages — perfect for quick troubleshooting.
🧾 Step 7: Common Crash Causes and Fixes
| Cause | Description | Suggested Action |
|---|---|---|
| Driver Failure | Outdated or corrupt hardware driver | Update or reinstall drivers via Device Manager or OEM site |
| Overheating | CPU or GPU temperature spikes | Clean fans, reapply thermal paste, or improve ventilation |
| Power Supply Issues | Unstable voltage or sudden power loss | Use a UPS or check power cables |
| Faulty RAM | Memory errors during system load | Run Windows Memory Diagnostic |
| Windows Updates | Buggy updates causing system instability | Roll back recent updates via Settings → Windows Update → Update history |
✅ Summary: Best Tools for Viewing System Crash Reports
| Tool | Purpose |
|---|---|
| Event Viewer | Deep dive into kernel-level errors |
| Reliability Monitor | Graphical timeline of stability events |
| System Health Report | Full diagnostic of system and hardware |
| Memory Dumps | In-depth crash file analysis |
| PowerShell Command | Quick report export for admins |
