How to View System Errors in Windows 11 Event Viewer

This guide provides a straightforward walkthrough on how to find, filter, and inspect system error events using the built-in Windows 11 Event Viewer. Learning to navigate this tool allows you to identify underlying hardware faults, driver crashes, and operating system errors, making it easier to diagnose and troubleshoot stability issues on your PC.

Step 1: Open the Windows 11 Event Viewer

You can access the Event Viewer using multiple methods in Windows 11:

  1. Press Windows Key + X on your keyboard to open the Power User menu.
  2. Select Event Viewer from the list.

Alternatively, press Windows Key + R, type eventvwr.msc into the Run dialog box, and press Enter.

Step 2: Navigate to the System Logs

Once the Event Viewer window opens:

  1. In the left-hand navigation pane, expand the folder labeled Windows Logs.
  2. Click on System.

The center pane will populate with thousands of events generated by the Windows operating system and its core components.

Step 3: Filter for Error and Critical Events

To isolate system problems without scrolling through informational logs:

  1. In the right-hand Actions pane, click on Filter Current Log….
  2. In the filter window, locate the Event level section.
  3. Check the boxes next to Critical and Error.
  4. Click OK to apply the filter.

The middle pane will now display only critical failures (such as unexpected shutdowns) and error events (such as driver load failures or service crashes).

Step 4: Inspect Event Details

To review the specifics of an error:

  1. Click on any error listed in the middle pane.
  2. Look at the lower half of the middle pane under the General tab to read a plain-text description of what went wrong.
  3. Note the following key fields:
    • Source: The specific system component, driver, or application that generated the error.
    • Event ID: A unique numerical identifier assigned to that specific type of event.
  4. Click the Details tab and switch to the XML View if you need advanced technical data, such as binary error codes or specific file paths.

Step 5: Use Event Data for Troubleshooting

Copy the Source name and the Event ID to search for solutions in technical forums or Microsoft documentation. If an error is linked to a specific service or device driver, this data will pinpoint whether you need to update a driver, repair system files via the System File Checker (sfc /scannow), or inspect hardware components.