The Windows Event Viewer is an underlying instrument that logs all framework events, including mistakes, alerts, and data messages. This data can be utilized to troubleshoot a large number of Windows problems, like accidents, freezes, and execution issues.
Getting to the Windows Event Viewer
To get to the Windows Event Viewer:
1. Press Windows Key + R to open the Run discourse box.
2. Type eventvwr.msc and press Enter.
This will open the Windows Event Viewer window. The window is separated into three primary areas:
• Route sheet: This sheet shows the pecking order of event logs.
• Focus sheet: This sheet shows the events in the chose event log.
• Subtleties sheet: This sheet shows nitty gritty data about the chose event.
To see the events in a specific event log, extend the event sign in the route sheet. Then, double tap on an event in the middle sheet to see itemized data about the event in the subtleties sheet.
You can likewise utilize the Windows Event Viewer to make custom perspectives.
Custom perspectives permit you to channel the event logs by date, event type, source, and different models. To make a custom view, click on the Make Custom View connect in the right-hand sheet. This will open the Make Custom View discourse box.
The Windows Event Viewer is a useful asset that can be utilized to troubleshoot a large number of Windows problems.
Seeing Event Logs
The Windows Event Viewer is partitioned into three fundamental areas:
• Application: This part logs events connected with applications.
• Framework: This part logs events connected with the Windows working framework.
• Security: This part logs events connected with security, for example, login endeavors and record changes.
To see event logs, extend the ideal segment and double tap on an event to see more data.
The Event Viewer window shows the accompanying data for every event:
• Date and time: The date and time that the event happened.
• Event ID: An exceptional identifier for the event.
• Level: The seriousness level of the event, for example, Basic, Blunder, Cautioning, or Data.
• Source: The wellspring of the event, like a particular application or administration.
• Depiction: A printed portrayal of the event.
Understanding Event Types
The Windows Event Viewer utilizes the accompanying images to show the sort of event:
• Basic: A basic event is a serious mistake that has made Windows crash or become shaky.
• Blunder: A mistake is an issue that has happened, however Windows has had the option to recuperate.
• Caution: An admonition is a less difficult issue that might show a likely issue.
• Data: A data event is a message that gives data about a framework event, for example, an effective login or a help startup.
Here are a few instances of various kinds of event logs:
• A basic event from the Framework event log might show that an equipment gadget is coming up short.
• A blunder event from the Application event log might show that an application is ruined or not viable with your adaptation of Windows.
• An admonition event from the Security event log might demonstrate that somebody has attempted to get to your PC without approval.
• A data event from the Framework event log might show that a help has begun
Troubleshooting Windows Problems Using the Windows Event Viewer
The Windows Event Viewer can be utilized to troubleshoot a large number of Windows problems. The following are a couple of models:
• Framework crashes: Assuming Windows is crashing, you can check the Framework event log for basic blunders that might be causing the accidents. For instance, assuming you witness a basic event with the source “piece power” and the event ID “41”, this demonstrates that your PC is closing down out of the blue. You can utilize this data to troubleshoot the issue.
• Application mistakes: In the event that an application is crashing or not working as expected, you can check the Application event log for blunders connected with the application. For instance, assuming you see a mistake event with the source “chrome.exe” and the event ID “1000”, this shows that the Chrome program has crashed.
• Execution issues: Assuming Windows is running gradually or freezing, you can check the Framework and Application event logs for mistakes and alerts that might be causing the exhibition problems. For instance, assuming that you witness an admonition event with the source “winlogon” and the event ID “7001”.
Using Channels to Limit Event Logs
The Windows Event Viewer can create an enormous volume of event logs, which can make it hard to track down the particular event that you are searching for. To limit the event logs, you can utilize channels.
To utilize a channel, click on the Channel Current Log connect in the right-hand sheet. This will open the Channel Properties exchange box. You can utilize the channel choices to channel the event logs by date, event type, source, and different measures.
Here are a few instances of how to utilize channels to limit the event logs:
• Channel by date: Assuming you know the date and time when the issue happened, you can channel the event logs to show events that happened on that date and time as it were.
• Channel by event type: Assuming you know the kind of event that caused the issue, you can channel the event logs to show events of that sort as it were. For instance, assuming you realize that the issue was brought about by a basic blunder, you can channel the event logs to show basic mistakes as it were.
Conclusion
• While troubleshooting a particular issue, center around the event logs that are connected with the issue. For instance, on the off chance that you are troubleshooting a framework crash, you ought to zero in on the Framework event log.
• Search for designs in the event logs. For instance, assuming you witness a ton of events from a specific source, this might demonstrate that the source is the reason for the issue.
• Utilize the event depictions to grasp the issue. The event depictions give data about the reason for the event and how you might fix it.
• In the event that you are experiencing difficulty troubleshooting an issue, you can look for help on the web or contact Microsoft support.