Table of contents

BSODs are fairly common on Windows PCs. Usually, they indicate some serious trouble with your hardware that your operating system can’t handle. However, it could also be software problems, such as those with device drivers or system file corruption. 

While some can happen due to minor glitches and be fixed rather easily, others may signal serious underlying problems and require closer attention and maybe even professional help. And trust me, fixing these BSODs can be pretty hard, especially when you don’t know the cause. 

But don’t worry, that’s what we’re here for, right? In this article, I’ll be showing you how to use the Event Viewer (and a couple of other ways) to find out the reason behind a BSOD.

How to Find Blue Screen Error Logs in the Event Viewer on Windows 10

Follow these steps:

PRO TIP
Download Auslogics BoostSpeed to diagnose and fix issues that cause Event Manager BSODs, ensuring a stable and error-free PC experience.
Download for Free Learn More

How to View a BSOD Error Log in the Event Viewer on Windows 11?

Alright, getting access to your Event Viewer BSOD error logs on Windows 10—check. Now, how do you do the same on Windows 11? After all, the new OS comes with a number of upgrades and changes.

For instance, Windows 11 comes with new designs for the Start menu and taskbar. As with most Windows upgrades, you also have fixes for some of the most commonly reported bugs and, therefore, a generally smoother performance.

However, when it comes to viewing BSOD error logs, the steps you will need to take on Windows 11 are not essentially different from what you need to do on Windows 10.

How to View a BSOD Error Log in the Event Viewer on Windows 11 1

But let’s recap and check out how to see the Event Viewer logs in Windows 11:

  • First, use the Win + S key combo on your PC to bring up the search feature.
  • Run a search for “Event Viewer” and select the first result.
  • In the Event Viewer, navigate to the left pane and go to Windows Logs.
  • Once here, click System.
  • Next, go to the right side of the window and select Create Custom View (you will find this option under System).
  • Make sure to stay in the Filter tab.
  • Next, head to the Logged drop-down menu and click Custom range.
  • Select the date and time range for which you want to see your Event Viewer BSOD logs.
  • When ready, press the OK button in the Custom Range dialog box.
  • In the Create Custom View dialog, head to Event level. Make sure to check the boxes for the following options: Critical, Warning, and Error.
  • Click OK.
  • Type in the name for the custom view you’ve just made.
  • Click OK.
  • Next, go back to the Event Viewer main window.
  • Here, you will see a full list of events that occurred during the specified period. They will be categorized into Warning, Critical, and Error events.
  • Double-click the event log and go to the Details tab to see more information.
How to View a BSOD Error Log in the Event Viewer on Windows 11 -2
These descriptions may be too technical. In this case, you can simply google the event ID to get a simpler explanation for what happened and what you can do to fix it.

By the way, we have a great article on startup and shutdown logs listing the most common reboot and shutdown event IDs.

What if Your System Is Always Restarting?

Some blue screen errors will throw your PC into an infinite loop of reboots. Your best course of action in this scenario is to check the reason for the BSOD in the Event Viewer in Safe Mode.

You have two ways to get into Safe Mode:

1. Go through the Automatic Repair environment

This method involves tricking your computer into believing that something has gone wrong with the boot process to trigger the Automatic Repair feature.

BSODs typically don’t affect the early boot process. So, Windows will likely not realize that anything is wrong until it’s time to load your startup applications.

Follow these steps to enter the Windows Recovery Environment (WinRE):

2. Use bootable media

Even the Automatic Repair feature can be broken. In such a case, you’ll have to use bootable media.

Bootable media allows you to load the Windows installation and repair environment even if your system isn’t booting. It could be a USB flash drive or DVD. If you don’t have a Windows 10/11 DVD, you can use another computer to create bootable media.

You can use a third-party tool—Rufus—or Microsoft’s Media Creation Tool. We’ll show you how to use both programs.

Creating a bootable Windows USB using Rufus

Rufus is a free third-party program for creating bootable media. All you need is your USB flash drive and the latest ISO image file of Windows 10 or Windows 11, which you can download from Microsoft’s website.

Follow these steps:

Using the Windows Media Creation Tool

Follow these steps to create the bootable media using the Media Creation Tool:

  • Head to Microsoft’s website and download the Media Creation Tool.
  • Run it on your computer.
  • Select the Create installation media for another PC radio button when the Windows Setup window opens, and then click Next.
  • On the next page, choose your language, Windows edition (Home, Pro, or Enterprise), and operating system architecture (64-bit or 32-bit).
  • Select the USB flash drive option under Choose which media to use, and then click Next.
  • Allow the tool to complete the process.

After creating the bootable USB, insert it into your system and reboot. Make sure you change your boot order accordingly. Once your computer comes up, press any key if you’re prompted.

When the Windows Setup screen appears, click on Repair your computer in the lower-left corner.

The Choose an option screen should now open. Click on Troubleshoot. Once the Troubleshoot screen appears, click on the Advanced options tile.

Now, click on Startup Settings once the Advanced options screen opens. Click on Restart. After your computer boots into the Startup Settings screen, tap the number beside Safe Mode and wait for your PC to reboot into Safe Mode.

You can now check the cause of the BSOD in the Event Viewer in Safe Mode.

Other Ways to Check the Causes of Blue Screen Errors

Did you know that using the Event Viewer for BSOD log checking is not the only way to find the reasons why your system crashes? You can also use the Windows Reliability Monitor or read a dump file with a built-in or a third-party app. Let’s briefly go over your options:

1. Using the Reliability Monitor

The Windows Reliability Monitor is a built-in app that tracks software issues and keeps a detailed log of events, especially when a crash occurs. The interface is user-friendly and works quite well on both Windows 10 and 11.

Your computer must boot up normally if you’re going to use the program. If it doesn’t, you can try opening it in Safe Mode.

You can learn more about using the Reliability Monitor from our article on how to view reliability history. We also have a detailed guide on how to check for BSOD causes, where the peculiarities of using this tool to pinpoint these causes are laid out comprehensively.

2. Reading a dump file

If your system crashes, Windows creates a dump file in the system memory where you can find apps that were running before the crash occurred. There are two main ways to analyze the dump file to check for causes of blue screen errors: using the WinDbg tool and using a third-party, free-to-use program such as BlueScreenView.

We have a great article on how to open and read .dmp files after a BSOD that covers both methods, so make sure to check it out. The information you find there could help you troubleshoot the blue screen without the Event Viewer, especially if a program is triggering it.

PRO TIP
Prevent System Crashes Now! Get Auslogics BoostSpeed to identify and resolve the root causes of Blue Screen errors, keeping your computer running smoothly and efficiently.
Download for Free Learn More

Checking Causes of BSODs Using the Event Viewer: Explained

And there you have it—a step-by-step guide on how to find out the cause of a BSOD in the Event Viewer (and even a little bit more). Now go out there and conquer, be it getting Event Viewer BSOD error logs, checking out the info in the Reliability Monitor, or reading a dump file.

Did you like this article? Think it might be useful for someone else? Then do not spare a thumbs up and share it! Cheers!

FAQ

What should I look for in Event Viewer logs to identify a BSOD cause?
When going through Event Viewer BSOD error logs, focus on events marked as Critical, Error, or Warning, and those related to system crashes or unexpected shutdowns. Mark the event ID in the log; it can help you out. For BSODs, pay attention to event ID 41 (Kernel-Power), event ID 1001 (BugCheck), or any disk, driver, or memory-related errors.
Are there tools that simplify BSOD analysis?
Yes. There are other utilities apart from the Event Viewer that allow you to find out blue screen causes. The Windows Reliability Monitor has a more user-friendly interface, and tools like BlueScreenView and WinDbg analyze crash dump files, making it easier for you to find the exact cause of a BSOD without the Event Viewer.
What is a BugCheck event, and how do I find it?
A BugCheck event (which is also called event ID 1001) is a log entry with detailed information about a BSOD that includes error codes and parameters that can help you understand why it happened. To find it in the Event Viewer, you need to create a custom view filtering for Critical, Error, and Warning events (check out this article to learn how) and look for event ID 1001.
How can I interpret error codes in the Event Viewer?
You need to note the event ID and associated error codes. Next, go to your browser and google these codes to find tech forums and articles that have the info on these codes and provide troubleshooting steps. As a tip, you can go to Microsoft’s support page and search there, as it’s a great resource with a vast knowledge base.
What should I do if the Event Viewer doesn’t show any clear BSOD cause?
First, breathe normally and try not to panic. You can use the Windows Reliability Monitor to get an overview of recent crashes (take a look a bit higher in this article). You can analyze the memory dump files using tools like WinDbg or BlueScreenView (we’ve got info on this in the article as well). If it doesn’t work out, check your hardware, especially your RAM and storage drives, as BSODs are generally triggered when there’s something wrong with them.
How can I save or export Event Viewer logs for further analysis?
Once you’ve filtered the logs to show relevant events in the Event Viewer, right-click on the custom view or individual event, then select Save All Events As… Choose a name, select a format (usually .evtx), and save it to where you prefer. Done! You can now share these logs with a technician or upload them to forums if you need help deciphering them.