Open Event Viewer by pressing Win R, typing eventvwr.msc, and navigate to Windows Logs > Application and System to find error or critical events linked to crashes. 2. Check crash dump files in C:\Windows\Minidump\ for BSODs or C:\Users\\AppData\Local\CrashDumps\ for application crashes, ensuring dump settings are enabled in System Properties. 3. Use Reliability Monitor by typing perfmon /rel to view a timeline of failures with app names, exception codes, and crash times. 4. Look for application-specific logs in directories like Chrome’s Crashpad folder, Java’s hs_err_pid*.log files, or game log folders. 5. Analyze dumps using tools like BlueScreenView, WhoCrashed, or WinDbg for deeper insights. Crash logs are typically available in Windows, and following these steps systematically helps identify the root cause of failures.

When a program or system component crashes on Windows, it often leaves behind crash logs that can help identify the cause. Finding and interpreting these logs can be useful for troubleshooting issues. Here's how to locate crash logs on Windows:

1. Check Event Viewer for Application and System Logs

The Event Viewer is the primary tool for accessing crash-related logs.

Steps:

• Press Win R, type eventvwr.msc, and press Enter.
• In Event Viewer, navigate to:
  • Windows Logs > Application – Look for errors or critical events related to crashing apps.
  • Windows Logs > System – Check for system-level crashes or driver issues.
• Look for entries with "Error" or "Critical" level, especially around the time the crash occurred.
• Double-click an entry to see details. Common crash-related sources include:
  • Application Error
  • .NET Runtime
  • Faulting application name (includes executable and version)

? Tip: Right-click a log entry and choose "Save Selected Event As…" to export it for further analysis or sharing.

2. Look for Crash Dumps in Default Dump File Locations

Windows can generate memory dump files when a program or the system crashes.

Common dump file locations:

• Blue Screen (BSOD) dumps:
  • C:\Windows\Minidump\ – Contains .dmp files from system crashes.
  • C:\Windows\Memory.dmp – Full memory dump (if enabled).
• Application crashes:
  • Some apps create dumps in:
    • C:\Users\<yourusername>\AppData\Local\CrashDumps\</yourusername>
    • Or within the app’s own log folder (e.g., game or software-specific directories).

? To enable or verify dump settings:

• Open Control Panel > System > Advanced system settings > Startup and Recovery > Settings.
• Ensure "Write debugging information" is set to generate minidumps.

3. Use Reliability Monitor for a User-Friendly Crash History

Reliability Monitor provides a timeline view of system and application failures.

Steps:

• Press Win R, type perfmon /rel, and press Enter.
• You’ll see a chart with stability index over time.
• Red "X" marks indicate critical events like app crashes, Windows failures, or updates.
• Click on a red event to see details like:
  • Faulting application name
  • Exception code
  • Time of crash

This is a great starting point if you're not familiar with Event Viewer.

4. Check Application-Specific Logs

Some programs (especially games, development tools, or browsers) write their own crash logs.

Examples:

• Google Chrome: chrome://crash (to test), logs may be in:
  • C:\Users\<user>\AppData\Local\Google\Chrome\User Data\Crashpad\</user>
• Java apps: Look for hs_err_pid*.log files in the working directory.
• Games (Steam, etc.): Often log crashes in their installation folder or My Documents\GameName\Logs.

Check the app’s documentation or support site for log locations.

Bonus: Use Tools for Deeper Analysis

• BlueScreenView (by NirSoft): Scans minidump files and shows readable BSOD info.
• WinDbg (Windows SDK): Analyze .dmp files to pinpoint crash causes.
• WhoCrashed: Simplifies crash dump analysis for BSODs.

Crash logs are often the fastest way to diagnose why something failed. Start with Reliability Monitor for a quick overview, then dive into Event Viewer and dump files for technical details. Most issues will show a faulting module or exception code that can guide your fix.

Basically, if something crashed, Windows probably logged it — you just need to know where to look.

The above is the detailed content of How to find crash logs on Windows. For more information, please follow other related articles on the PHP Chinese website!