sodcalculator

10 Tech How-To

Windows 10 Error Log: How to Access Error Logs

Guide 10-46309 · Updated · Step by step

To access Windows 10 error logs, open the Event Viewer by typing Event Viewer into the Start menu search box and pressing Enter. Then expand Windows Logs and select System (for driver and system errors) or Application (for software crashes) to see detailed error records. This built-in tool logs nearly everything that goes wrong on your PC, and this guide shows you exactly how to read and use it.

What the Windows Error Log Actually Contains

Windows 10 records three main types of logs that matter for troubleshooting:

  • Application logs – errors from installed programs, like a game crashing or a backup tool failing.
  • System logs – errors from Windows components, drivers, and hardware, such as a disk failing or a driver not loading.
  • Setup logs – events from Windows Update and system upgrades.

Each log entry has a date/time, a source (the program or component that generated it), an event ID (a numeric code), and a severity level: Information, Warning, or Error. Critical errors appear with a red icon and are the ones you usually care about first.

How to Open Event Viewer (The Main Error Log Tool)

  1. Press Win + R, type eventvwr.msc, and press Enter. This is the fastest method.
  2. Alternatively, right-click the Start button and choose Event Viewer from the power-user menu.
  3. In the left panel, expand Windows Logs and click System or Application.
  4. Click the Level column header to sort by severity, so errors appear at the top.

If you are looking for a specific error, use the Filter Current Log action on the right panel. Set the level to Error and optionally pick a date range to narrow down the noise.

Reading an Error Entry: Event ID, Source, and Details

Double-click any error to open its full details. The General tab gives a plain-language description, but the Details tab is where the real info lives. The Event ID is the key – it is a unique number that identifies the specific problem. For example, Event ID 41 (Kernel-Power) means the system rebooted without a clean shutdown, often due to a power supply or overheating issue. Event ID 1000 (Application Error) means a program crashed, and the description usually names the .exe file.

When you see an error, copy the Event ID and the source name, then search the web for that combination. You will almost always find a Microsoft support page or a community thread explaining the exact fix.

How to Find Crash Logs for Specific Apps (Reliability Monitor)

Event Viewer is powerful but cluttered. For a friendlier view of recent crashes and failures, use Reliability Monitor. Type reliability into the Start menu and open the View reliability history result. This shows a timeline of system and application failures, with red X marks for errors and blue i marks for informational events. Click any point on the timeline to see what happened that day. It is the best place to start if you just want to know why a specific app keeps closing or why Windows restarted unexpectedly.

Viewing Blue Screen (BSOD) Logs

Blue screen errors are logged in the System log under Event ID 41 (Kernel-Power) or Event ID 1001 (BugCheck). However, the actual crash details are stored in a minidump file. To analyze a minidump, you need a debugging tool like WinDbg (part of the Windows SDK) or a third-party utility. A simpler alternative is to check the System log around the time of the crash – the BugCheck entry often includes the stop code (e.g., 0x0000007E). Write that code down and search it; that is usually enough to identify the faulty driver.

Common Problems When Accessing Error Logs

  • Log is huge and slow – Use the filter option to show only errors from the last 24 hours.
  • You see hundreds of errors but nothing is actually wrong – Many errors are harmless and expected (e.g., a service that failed to start once). Focus on repeated errors or those that match the time of your actual problem.
  • Event Viewer is blank or won’t open – Run sfc /scannow in an elevated Command Prompt to repair system files, then restart.
  • You can’t find a specific error – Use the Find action (Ctrl+F) in Event Viewer and search for the program name or error code.

How to Export and Share Error Logs

If you need to send a log to a support forum or a technician, you can export it. Right-click the log (e.g., System) and choose Save All Events As. Save it as an .evtx file, which can be reopened in Event Viewer on another machine. Alternatively, save as CSV or XML if you want to open it in Excel or a text editor. To copy a single event, select it and press Ctrl+C, then paste it into a text file or email.

Alternatives to Event Viewer

Event Viewer is not the only way to see error logs. For specific scenarios, these are better tools:

  • Reliability Monitor – for a user-friendly timeline of failures (as covered above).
  • PowerShell – run Get-WinEvent -LogName System -MaxEvents 50 | Where-Object {$_.LevelDisplayName -eq 'Error'} to get a quick list of recent errors in the console.
  • Windows Admin Center – if you manage multiple PCs, this gives a centralized view of event logs.
  • Third-party log viewers – tools like NirSoft’s FullEventLogView can export and filter logs more flexibly than the built-in viewer.

Each has its place, but Event Viewer remains the standard because it is free, built-in, and covers everything.

Frequently Asked Questions

How do I find the error log for a specific program?

Open Event Viewer, go to Windows Logs > Application, and use the Filter Current Log action. In the Event sources dropdown, select the program’s name (or its company name). If the program is not listed, it may log to its own folder in %ProgramData% or %AppData% – check the program’s documentation.

Why does Event Viewer show errors but my PC works fine?

Many errors are transient or non-critical. For example, a service might fail to start once because it was already running, or a driver might report a warning that doesn’t affect functionality. Look for patterns: if the same error repeats every few minutes or occurs exactly when you experience a problem, then it’s worth investigating. Otherwise, ignore it.

Can I delete error logs to free up space?

Yes. In Event Viewer, right-click a log (e.g., System) and choose Clear Log. You can also set a maximum log size and choose to overwrite old events. This does not fix any underlying issues – it only clears the history. If you are clearing logs to solve a problem, that won’t work; you need to fix the cause.

How do I find the blue screen error code in Event Viewer?

Open the System log, filter for Event ID 1001 with source BugCheck. The general description will contain the stop code (e.g., 0x0000007E) and sometimes the faulty driver name. If you don’t see it, check the minidump file in C:\Windows\Minidump with a debugger.

Is there a way to get a plain text copy of all errors?

Yes. Use PowerShell with the command Get-WinEvent -LogName System -Level 2 | Out-File errors.txt (Level 2 = Error). This exports all system errors to a text file. For Application logs, change -LogName to Application. You can also use the Export-Csv cmdlet to get a CSV file.

What is the difference between a warning and an error in Event Viewer?

A warning indicates a potential problem that didn’t cause a failure yet – for example, a disk that is nearing capacity. An error means something actually failed, like a driver not loading or a service crashing. Both are worth reviewing, but errors are the priority.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →