How to check Windows Event Viewer for error messages

Introduction

Windows Event Viewer can be a valuable tool for diagnosing and troubleshooting various system issues. While it may not always be able to pinpoint the root cause of an issue (for example: some system crashes don't leave any trace in the log), it is worth checking to see if it can give you any hints.

This guide will help you understand when to use Event Viewer, how to navigate it, and how to filter logs effectively.

When to check Event Viewer

It's useful to check Event Viewer when you encounter system issues such as unexpected crashes, application errors, hardware failures, or other unexplained behavior. The logs in Event Viewer are sometimes able to provide valuable insights into the underlying causes of these problems.

Remember the time and date

Before you open Event Viewer, make a note of the date and exact time when the issue occurred. This will help you quickly locate the corresponding error messages in the log files.

Opening Event Viewer

Press the Windows key, type "Event Viewer" in the search box, and press Enter to open the application. Alternatively, right-click the Windows Start Menu and select Event Viewer from the Context Menu.

Understanding Application and System logs

Event Viewer has several log categories, but the most important ones for troubleshooting are "Application" and "System" logs:

• Application: Contains events related to software applications, such as crashes or errors in third-party programs.
• System: Contains events related to the operating system, drivers, and hardware components. Most of the crucial logs are in this category.

Example screenshot of Event Viewer with a Wi-Fi-related error in the System log.

Applying a filter to the logs

To create a filtered view displaying only Warnings, Errors, and Critical events from the last 24 hours:

• In Event Viewer, expand the "Windows Logs" folder in the left pane.
• Click in the "System" protocol and wait for it to finish loading.
• Right-click on "System" and select "Filter Current Log."
• In the "Filter Current Log" window, under the "Event level" section, check the boxes for "Critical," "Error," and "Warning."
• Under the "Logged" section, select "Last 24 hours" from the drop-down menu and click "OK."

Right-click on System, Filter Current Logu2026

Filters for Critical, Warning and Error in the last 24 hours.

Interpreting the logs

Be cautious not to overvalue the importance of some errors or warnings in the logs. Some messages may be harmless or unrelated to your issue, leading you in the wrong direction if you focus too much on them. Use your recorded date and time to pinpoint relevant logs.

Some warnings and even some errors may not be relevant to the troubleshooting purpose.

Taking screenshots for tech support

When you find relevant error messages, take screenshots to share with tech support or for your own reference. Press the "Print" key on your keyboard to capture the entire screen, or use the "Snipping Tool" or "Snip & Sketch" apps for more precise screenshots.

Example screenshot with details on a specific and relevant error event.

Conclusion

By understanding when to use Event Viewer, how to navigate and filter logs, and how to interpret error messages, you'll be better equipped to diagnose and resolve system issues on your Windows computer. Remember to take screenshots of relevant logs to share with tech support or other community members.