Windows keeps records of all events on the computer. These logs are a collection of files that contain details of actions and changes in settings as well as all the daily tasks that we interact with while using the computer. Fortunately, these logs keep all the errors and technical problems that face the computer when it does not work properly, and this is the most important benefit of the logs that we know as Logs and can be examined using the Event Viewer.
What is the reason for the computer suddenly freezing and not responding correctly ?, What is the reason for restarting on its own ?, What was the reason behind the BSOD blue screen ?, Why did the installation of a program not complete properly ?, What was the reason for the system crash Windows completely? The idea of the Event Viewer is to answer all these questions and in as many details as possible. Therefore, you will not need to ask anyone else about the causes of all these faults, because he is the only one who has the correct answer and presents it to you in an accurate, clear and detailed way. All you need to know is how to access it and how to view its details in order to explore the causes of faults yourself when you encounter you and how to solve and deal with them.
How to find, understand, and deal with an Event Viewer
Not one, not two, but many ways in Windows ultimately lead to Event Viewer. The easiest way is to type Event Viewer into the Windows search bar or the Start menu. But before we interact with Event Viewer, let's take a peek at what logs Windows keeps when it is running and how difficult it would be for us to deal with them if Microsoft hadn't been blessed with Event Viewer for us. So we will go to File Explorer and open the C-sector and then in the search box on the far right at the top write this symbol "* .log" without the parentheses and then hit the Enter key.
After completing, you will notice that the results are very few compared to the number of results that were in the thousands. These records can be opened in the form of a notebook normally, and now, see for yourself what is inside, you will notice that the content inside will only be understood by the developers and programmers themselves, some details may help you find some clues or notifications that help you understand the problem, for example you find A statement suggesting that the file is missing or the value is incorrect. But to be honest, although the answer to the cause of the malfunctions is already inside these records, we will not be able to understand and deal with it, right?
As you have seen yourself how difficult it is, but just bear in mind that you may need it in one case, which is that you encounter a problem and want to inquire about it on the Microsoft support page, then they will ask you for the latest records, because it will help them understand your problem and deal with you on the basis of it.
But the Event Viewer integrated into Windows makes it necessary for the average user to examine problems and clearly understand their causes. Now, type the Event Viewer command in the Windows search bar, and after the result appears, click on the Event Viewer to open it.
Now all you need to do first is to extend the Event Viewer window so that you can see the details better. On the left you will find that the most current events are recorded in the Windows Logs box. This is where you can find the real culprit causing all kinds of problems. Click on Windows Logs once with the left mouse button.Now you have to wait and think a little about the problem that you just faced with your computer, is it related to Windows or an application. We will assume that the computer entered a freeze phase for several moments, encountered the blue screen, or restarted itself while you were in a game or during the installation of some applications or while returning from an idle state, all of these scenarios and most of their problems are stored inside the Applications command interface. But at the same time the System Registry stores many extremely important processes.
In order to narrow the search in a more wise and effective way, click from the right of the window on the Filter Current Log command and then activate the small boxes next to Critical and Error. You can filter the time only on the last hour that has passed or even choose the time range by the second. But of course, filtering errors and problems according to the last hour will arrest the perpetrator directly in front of you, because in most cases you will not find any Critical or Error except during the last hour in which the problem occurred with you. Now that we have filtered the results according to error and problem situations, we got results classified according to their severity, which contain serious errors and critical technical problems that you encountered during the last hours of using the computer.
Try to check the timeline that coincides with exactly when the problem occurred. But in reality you will not need to search and examine much, because the problem will be directly in front of your eyes in time and moment. Then you have to think a little: Does the problem in front of you and its time actually coincide with the time when the problem occurred? If the time is correct, then you put your hand on the problem easily. If the time is not correct, try to look for faults that coincide with their occurrence. But as we mentioned earlier, you are only searching in the last hour, meaning that you most likely will not find another in front of you with all the faults related to it alone.
After you put your hand on the perpetrator, click on this malfunction with the left mouse button twice to open the details window. From the previous image, you will find that I encountered an error due to a bad sector on the storage disk memory, which was the cause of the problem at this particular time.
Of course, the problems are numerous and the results are endless. But the Event Viewer is super skilled at recognizing all the errors and problems a computer goes through while it is running. Remember that some of the results of Errors are not necessarily fatal errors, or more correctly, they are not always errors worth looking for their causes. But what deserves to be carefully researched and examined is the error that results specifically while we are facing a real problem with the computer. The details will display the error codes that will help you search for it on the Internet easily, in case you are unable to understand the malfunction.
Sometimes it will be reported to you immediately that you faced a problem at that time as a result of running a certain application and it conflicts with the Windows system, or that this application contains programming errors. In the end, you will put your hand on the error and you will understand its cause in detail, and you will be able to treat and deal with it easily, or at least it will help you display its contents to others on the Internet in order to help you get rid of it.
Remember also to look at the System interface, as it sometimes has some evidence of technical errors that may be related to cutting hardware, and remember to legalize your search for technical errors and problems by filtering the search as we mentioned earlier. Finally, the Event Viewer will be your first guide and guide that answers all your questions regarding any problems you encounter while using your computer.
Comments