Share this article
This article is translated in
Improve this guide
Windows 11 Error Logs: How to Quickly Check the Crash Log
Learn how to check, understand, and filter error logs on your PC
7 min. read
Updated onSeptember 24, 2024
updated onSeptember 24, 2024
Share this article
This article is translated in
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Resolve multiple Windows PC issues and speed up your PC effortlessly with specialized software.
Whenever you encounter an error in Windows, it certainly is a cause for concern. But, we often do not bother discovering what caused it or don’t know how to.
Error logs, as the name suggests, are the log files that store all the information as to why the error happened, the program or process that led to it, along the exact date and time of it.
How do I view error logs in Windows 11?
Here are a few ways to see error logs in Windows 11:
It’s pretty simple and quick to access the error logs on your Windows 11 OS, but in case you didn’t used before, the steps below will surely help you find them.
-
PressWindows+Sto launch theSearchmenu, enterEvent Viewerin the text field at the top, and click on the relevant search result.
-
Double-click onWindows Logsin the navigation pane on the left.
-
You will now find the five different categories. Select any of these, and all the error logs under it will be listed on the right.
-
Now, click on any of the error logs to view all the relevant information about them.
You now know how to check the Windows 11 error logs, but just knowing that won’t suffice.
There’s still a lot out there to understand before you can actually make some sense out of these logs, and use them to your advantage.
How to understand Windows 11 error logs?
When you view a Windows 11 crash log, the general details and the Event ID is critical in identifying and eliminating the error. Apart from that, there’s anEvent Log Online Helplink at the bottom, which may provide some valuable insights.
For instance, here’s a Windows 11 error log when the relevant driver for a device failed to load.
The 219Event IDhelped find out a lot of information along with the relevant fixes for the problem.
We just did a Google search for this Event ID and there were a plethora of results. But this requires a proper understanding of Windows 11 error logs.
But, it’s important to mention here that not all error logs will be as descriptive. Some might have things that you wouldn’t be able to comprehend or use jargon excessively. No matter the case, a simple Google search would suffice.
And ifEvent Viewer is not working in Windows 10 and 11, rest assured that our detailed guide will help you.
What are the different types of error logs?
When you go through the Windows 11 error logs, there arethree important categories, referred to asEvent Level, under which these are placed.
And, the categories define the severity of the event for which the log is created. The three categories are as follows:
If you are identifying problems with the PC, ignore theInformation logs, go through theWarninglogs, but pay special attention to the ones categorized asError, since these are most likely to record the problem you are looking for.
When you open the Event Viewer in Windows 11, it will list out all three. The view will remain the same if you have not changed the Windows 11 Error Reporting logs location in the in the Group Policy.
However, identifying all logs for one of these levels will take up a lot of your time. This is where filtering error logs come to your aid. Check the next section to find out how you can do that.
How can I filter error logs?
We selected the duration as24 hours, and level asError, and filtered the logs. Event Viewer then listed the four Windows 11 error logs that were created during that time.
How to create a custom view to check a particular category and level of logs in Windows 11?
How can I clear error logs in Windows 11?
The OS creates thousands of logs for each type of event, be it the successful launch of a driver and service or the most fatal errors. Like any other file, these too consume space on your hard disk, no matter how small it is.
So, if you are running out of space, or just want a more organized Event Viewer, clearing the Windows 11 error logs may help.
Checking the error logs can help you understand theBSoD errors like 139, and point you in the right direction to fix it.
How do I create my own log file in Windows 11?
A log file is used to record data. Windows uses it for errors, warnings, and information, while you can use it for other purposes.
Creating a log file is simple, and so is maintaining it. Say you want to record the progress for a book you are reading, just create a log file and enter the number of pages you read each day, or as you may please.
Why do I need to check Windows 11 error logs?
Checking error logson Windows 11 allows you to find the underlying cause of an issue such asa BSOD(Blue Screen of Death).
That’s all you need to know about Windows 11 system logs. From now on, identifying the underlying cause of errors should no longer be a problem.
Also, if you feel that Event Viewer does not meet all your requirements, check thebest apps to view errors logs in Windows 11.
Do not hesitate to comment if you have any questions or would like us to add a related topic.
More about the topics:event log viewers,Windows 11
Kazim Ali Alvi
Windows Hardware Expert
Kazim has always been fond of technology, be it scrolling through the settings on his iPhone, Android device, or Windows PC. He’s specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem.
Long-time Windows user, Kazim is ready to provide a solution for your every software & hardware error on Windows 11, Windows 10 and any previous iteration. He’s also one of our experts in Networking & Security.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Kazim Ali Alvi
Windows Hardware Expert
Kazim is specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem.
