Error Codes Wiki

Windows Event Viewer — Reading Critical Errors and System Logs

Warningsystem

Overview

Guide to using Windows Event Viewer to diagnose critical errors, read system and application logs, and identify the root cause of crashes and failures.

Key Details

  • Event Viewer (eventvwr.msc) collects system, security, and application event logs
  • Critical and Error level events indicate failures that need attention
  • Event ID combined with Source uniquely identifies the type of event
  • Custom Views > Administrative Events shows all errors and warnings across all logs
  • Events include timestamps, source process, error codes, and detailed descriptions

Common Causes

  • System crashes generating critical events in the System log
  • Application failures creating error events in the Application log
  • Driver failures logging errors with source names like disk, WHEA, or the driver name
  • Security events tracking login failures, permission denials, and audit events

Steps

  1. 1Open Event Viewer: Win+R > eventvwr.msc or right-click Start > Event Viewer
  2. 2Check recent critical events: Custom Views > Administrative Events (pre-filtered for errors)
  3. 3For BSODs: System log > source 'BugCheck' shows the stop code and parameters
  4. 4For app crashes: Application log > source 'Application Error' or 'Windows Error Reporting'
  5. 5Filter events: right-click a log > Filter Current Log > select Level and time range
  6. 6Export logs for support: right-click log > Save All Events As > .evtx file

Tags

event-viewerevent-logsystem-logcritical-errordiagnostic

Related Items

More in System

Frequently Asked Questions

Check the System log for source 'BugCheck' (the BSOD stop code). Also check 'Microsoft-Windows-WER-SystemErrorReporting' and 'WHEA-Logger' for hardware errors.