Using Windows Event Viewer to Diagnose Crashes and Errors
Published 2026-10-16 · Marion Remote Fix
Your computer crashed, showed a blue screen, froze, or an application keeps failing — and you want to know why. Windows records detailed logs of system events, errors, and crashes in a tool called Event Viewer. These logs contain the information needed to diagnose what went wrong, including the exact error code, the application or driver responsible, and the time and circumstances of the failure. Event Viewer can be intimidating because it shows thousands of entries, but knowing where to look and what the entries mean makes it a powerful diagnostic tool.
Opening Event Viewer
- Press Windows+R, type eventvwr.msc, and press Enter. Event Viewer opens showing the overview page
- Alternatively, right-click the Start button and select Event Viewer (on Windows 11) or search for Event Viewer in the Start menu
- The left panel shows a tree of log categories. The center panel shows the events in the selected log. The right panel shows actions you can take
Where to look for crash information
Windows Logs section
- System log: This is where you find operating system level events — blue screen crashes, driver failures, service start and stop events, disk errors, and hardware problems. Start here for system crashes and blue screens
- Application log: This contains events from applications — application crashes, errors from specific programs, installation events, and application-specific warnings. Start here for application crashes and failures
- Security log: This records login attempts, permission changes, and audit events. Useful for security investigations but rarely needed for crash diagnosis
Filtering to find crash events
- The logs contain thousands of entries. To find relevant crash information, use the Filter Current Log option in the right panel
- Under Event Level, check Critical and Error. Uncheck Information and Warning (these are informational entries, not problems). This immediately reduces the list to only actual failures
- Set the time range to cover the period when the crash occurred. If the crash happened today, filter to the last 24 hours. If you know the approximate time, narrow the filter further
- Click OK and the filtered list shows only Critical and Error events within your time range. The crash event should be visible near the time the problem occurred
Understanding event entries
Event structure
- Each event entry contains several fields: Level (Critical, Error, Warning, Information), Date and Time, Source (the component that generated the event), Event ID (a numeric code identifying the specific event type), and a Description with details
- The Description field is the most useful — it contains the human-readable explanation of what happened, including error codes, file names, and other specific information
Critical events
- Critical events indicate complete failures — system crashes, blue screens, unexpected shutdowns, and service failures that cause system instability
- The most common critical event after a blue screen is Event ID 41 from the Kernel-Power source, which indicates the system rebooted without cleanly shutting down. This confirms a crash occurred but does not by itself explain why
- Look for other Critical or Error events logged just before the Kernel-Power event — these usually contain the actual cause (the driver that crashed, the hardware that failed, the condition that triggered the blue screen)
Error events
- Error events indicate failures that may not crash the entire system but affect specific components or applications. Repeated Error events from the same source often indicate a persistent problem that will eventually cause a bigger failure
- Application error events typically include the name of the application that failed, the module (DLL or component) that caused the failure, and an exception code
Common crash-related events
BugCheck (Event ID 1001, source BugCheck)
- This event is logged after a blue screen crash. The description includes the blue screen stop code (the error number displayed on the blue screen) and the four associated parameters
- The stop code identifies the type of crash. Common codes: 0x0000007E (system thread exception), 0x0000000A (IRQL not less or equal), 0x00000050 (page fault in nonpaged area), 0x000000D1 (driver IRQL not less or equal)
- The parameters often include the address of the failing instruction and the driver file name, which identifies the responsible component
Application Error (Event ID 1000)
- Logged when an application crashes. The description includes the application name, the version, the faulting module name, and the exception code
- The faulting module is particularly useful — if the module is a DLL belonging to a specific component (a GPU driver DLL, an audio DLL, a third-party library), that component is the cause of the crash
- Exception code 0xc0000005 is an access violation (the program tried to access memory it should not). This is the most common crash exception and indicates a bug in the application or one of its components
WHEA-Logger (Event ID 18 or 19)
- WHEA (Windows Hardware Error Architecture) events indicate hardware errors — CPU errors, memory errors, PCI bus errors. These point to hardware problems rather than software issues
- Frequent WHEA events can indicate failing RAM, an overheating CPU, or a hardware defect. If WHEA events correlate with crashes, hardware diagnostics should be run
Disk errors (Event ID 7, source Disk)
- Disk error events indicate read or write failures on a storage drive. Occasional events may be transient, but frequent disk errors indicate a failing drive
- Check which drive is affected (the description includes the device identifier). Run drive health diagnostics if disk errors appear in the logs
Using Event Viewer for blue screen analysis
- After a blue screen crash and reboot, open Event Viewer immediately. Filter the System log to Critical and Error events from the last hour
- Look for BugCheck events, WHEA events, and driver-related error events logged around the crash time
- Note the stop code from the BugCheck event and any driver names mentioned. Search these online for specific guidance — many stop codes have well-documented causes and fixes
- If the blue screen mentioned a specific driver file name (shown on the blue screen itself, like ntfs.sys, nvlddmkm.sys, etc.), search for Error events from that driver in the log. Previous Error events from the same driver suggest it has been having problems before the crash
Saving and sharing event logs
- You can save filtered event logs to share with technical support or for later analysis. Right-click the log name and select Save Filtered Log File As (to save only the filtered results) or Save All Events As (to save everything)
- Event logs can be saved as .evtx files (which can be opened in Event Viewer on another computer) or as .txt or .csv files for plain text viewing
- When reporting a problem to technical support, providing the relevant Event Viewer entries gives them specific diagnostic information instead of just a description of symptoms
Event Viewer limitations
- Event Viewer records events but does not analyze them. It shows what happened but not always why. The descriptions can be cryptic and require technical knowledge to interpret
- Not all problems generate event log entries. Some types of hangs, freezes, and performance issues may not produce specific error events because the problem is a resource bottleneck rather than an error condition
- Events marked as Error or Warning in the log are not always problems that need fixing. Some Error events are expected during normal operation (certain service failures during shutdown, driver negotiations during startup). Patterns of events matter more than individual entries
Need help interpreting crash logs?
If your computer is crashing and you have checked Event Viewer but cannot determine the cause from the log entries, or if you need help understanding the error codes and acting on the information, Marion Remote Fix can remotely review your event logs, analyze crash dumps, identify the root cause, and implement the fix to stabilize your system.