How to Read and Use Windows Event Viewer to Find Errors
Published 2026-10-16 · Marion Remote Fix
Event Viewer is a built-in Windows tool that records everything that happens on your computer — application crashes, driver failures, blue screen causes, service errors, login attempts, and hardware warnings. When your computer crashes, freezes, or behaves strangely and you do not know why, Event Viewer usually has the answer. Here is how to open it, navigate the logs, find the errors that matter, and understand what they mean.
Open Event Viewer
There are several ways to open Event Viewer:
- Right-click the Start button → Event Viewer (the fastest method)
- Press Win+R → type
eventvwr.msc→ press Enter - Search for Event Viewer in the Start menu
- The Event Viewer window shows a tree on the left, a list of events in the middle, and event details at the bottom. The tree is organized into categories that we will explore in the sections below
Understand the log structure
Event Viewer organizes logs into two main sections:
- Windows Logs — the most useful section for troubleshooting:
- Application: errors and warnings from programs (Office crashes, browser errors, antivirus alerts)
- System: errors from Windows services, drivers, and hardware (blue screens, driver failures, disk errors, network problems)
- Security: login attempts, permission changes, audit events. Useful if you suspect unauthorized access
- Setup: Windows Update and installation events
- Applications and Services Logs — detailed logs for specific Windows components (more granular but usually only needed for advanced troubleshooting)
Understand event levels
Each event has a level that indicates its severity:
- Critical (red circle with X): a major failure that usually means something crashed or stopped working entirely. These are the most important events to investigate
- Error (red circle with X): something went wrong but the system continued. Frequent errors often point to the root cause of ongoing problems
- Warning (yellow triangle): something unusual happened that could become a problem. Not all warnings are actionable, but patterns of repeated warnings often precede failures
- Information (blue circle with i): normal operations, like a service starting or an update installing. These are not problems — they document what happened for reference
- Focus on Critical and Error events first. Warnings are useful context but rarely the direct cause of a problem
Find the error that caused a crash or blue screen
If your computer crashed, blue-screened, or froze and you want to know why:
- Open Event Viewer → Windows Logs → System
- Look for events around the time of the crash. If the computer restarted after the crash, look at the events just before the most recent Event ID 6008 (unexpected shutdown) or Event ID 41 (Kernel-Power, meaning the system rebooted without a clean shutdown)
- For blue screens specifically, look for events from source BugCheck. The event details contain the blue screen stop code (like IRQL_NOT_LESS_OR_EQUAL or CRITICAL_PROCESS_DIED) and the parameters that identify the failing component
- Also check Windows Logs → Application for events from source Windows Error Reporting and WER. These contain crash details for application-level failures
- The events immediately before the crash are the most important — they often show the driver, service, or hardware that failed and triggered the crash
Filter events to find what matters
Event Viewer can contain thousands of events. Filtering helps you find the relevant ones:
- In the right panel, click Filter Current Log
- Check only Critical and Error to hide informational events and warnings
- Set the time range: click the Logged dropdown and select Custom range → enter the date and time window around when the problem occurred
- You can also filter by Event source (the component that generated the event) or Event ID (a specific error number). These are useful when you are tracking a known issue
- Click OK to apply the filter. The list now shows only the events matching your criteria
Common Event IDs and what they mean
These are the most frequently encountered error events and their typical causes:
- Event ID 41 (Kernel-Power): the computer shut down unexpectedly. Causes: power loss, overheating, hardware failure, driver crash, or pressing and holding the power button
- Event ID 6008 (EventLog): the previous shutdown was unexpected. This confirms a crash or forced power-off occurred
- Event ID 7 (Disk): a bad block was found on the disk. If this appears repeatedly, the hard drive is failing and should be replaced
- Event ID 11 (Disk): the driver detected a controller error. Often related to a flaky SATA cable, failing drive, or USB drive disconnecting
- Event ID 1000 (Application Error): an application crashed. The event details show the program name, the module that faulted, and the exception code
- Event ID 1001 (Windows Error Reporting): a detailed crash report following Event ID 1000. Contains the bucket hash that can be searched online for known fixes
- Event ID 10016 (DistributedCOM): a DCOM permission error. These are extremely common and almost always harmless — they have been present in Windows for years and Microsoft has acknowledged they can usually be ignored
- Event ID 7031 or 7034 (Service Control Manager): a Windows service crashed or terminated unexpectedly. The event names the specific service that failed
Investigate a specific error
When you find a relevant error event, here is how to extract useful information from it:
- Click the event to see its details in the bottom panel. The General tab shows a human-readable description
- Note the Source (which component reported the error), Event ID (the specific error number), and the description text
- Click the Details tab for raw data. The XML View shows all parameters, which can be useful for online searches
- Search online for the combination of Source + Event ID + key phrases from the description. For example, searching for Kernel-Power Event ID 41 Task Category 63 often leads to specific solutions
- If the error mentions a specific file (like a .dll or .sys file), that file is the component that failed. Search for that filename to identify which driver or program it belongs to
Create a custom view for ongoing monitoring
If you are troubleshooting a recurring problem, create a custom view to monitor only the relevant events:
- In Event Viewer, right-click Custom Views → Create Custom View
- Select the event levels you want to monitor (Critical and Error for most troubleshooting)
- Select which logs to include (System and Application cover most problems)
- Optionally filter by event source or event ID if you are tracking a specific issue
- Give the view a descriptive name and click OK. Your custom view appears under Custom Views in the left panel and updates automatically as new matching events appear
Export logs for remote analysis
If someone is helping you troubleshoot remotely, you can export your event logs:
- Right-click the log (like System or Application) → Save All Events As
- Save as .evtx format — this preserves all event details and can be opened in Event Viewer on another computer
- For a simpler text format, choose .txt or .csv when saving. These can be opened in any text editor or spreadsheet but lose some formatting
- You can also right-click a single event → Copy → Copy Details as Text to paste a specific error into an email or support request
Events that are safe to ignore
Event Viewer always shows errors and warnings, even on perfectly healthy systems. These are typically harmless:
- DistributedCOM 10016 errors — a long-standing Windows permission mismatch that does not affect functionality
- Occasional Application Error events for programs that recovered on their own — if you did not notice a crash, it was likely handled internally
- ESENT (Extensible Storage Engine) warnings — these relate to Windows Search and Edge database operations and are normal
- SideBySide errors about assembly generation — usually related to Visual C++ runtime version conflicts that do not affect the programs themselves
- Do not try to fix every error in Event Viewer. Focus only on errors that correlate with a problem you actually experience
Remote Event Viewer analysis
If you need help interpreting Event Viewer errors or diagnosing a recurring crash, Marion Remote Fix can review your event logs remotely — identifying the root cause of crashes, blue screens, and service failures through a secure remote session.