View windows error log windows 8

Wait for the list of search results to quit reshuffling, then right-click on the entry Event Viewer: Desktop app and select the command Run as Administrator. In the Event Viewer , navigate through the various categories called Views in the left-hand navigation pane in order to inspect the various events in the main section of the screen.

You can adjust your filter criteria until you find what you were looking for. For quicker access to particular types of logs, click or tap on Create Custom View. Enter your criteria and confirm. In order to export some of the logs for external diagnostics, make your selection in the list, then hit Save selected events…. If your computer is giving you a hard time with persistent crashes and the like, you may need to perform some repairs.

Start by repairing the file system see below. If that fails to resolve the issue, you can try and restore the boot directory. A major cause of persistent crashes, BSoD incidents and other malfunctions comes down to hardware defects due to faulty manufacturing, overheating or rough handling. The system or its individual components may overheat during prolonged use, particularly when overclocking. Before the iron melts on you, adding or replacing case fans and coolers can save you real money.

Adding fans to cool memory banks or fitting the system with liquid cooling can not only prevent damage—it can also improve performance. Once the users know the way to open Windows Event Log Viewer, the next step is how to troubleshoot the problems with the help of this tool.

When you opened the Event Viewer, a user can clearly view Windows Logs option on the left side navigation pane. And, when we click on Windows Logs, a drop-down list opened.

In order to fix issues, the System log is very much essential. In order to resolve any issue in the Windows Operating system, the first preference of administrator is to use Event Viewer tool to diagnose the problem. Orientation: You are in the Event Viewer, you pre-select the System log.

Here is where you put on your thinking hat, and experiment with each setting: my choices were: Event sources Microsoft Windows System settings Task category Logon, Logoff. Typical Microsoft, there are at least 3 ways of employing PowerShell to filter the logs.

My favourite, especially for learning is to pipe the output of Get-Eventlog into a where statement. Note 2: It may be clearer if you bolt on a Format-Table command. Note 4: The conditional operator -match may be better than -eq.