Thankfully enough, Windows 10 comes with a neat way of storing all kinds of information, including the BSOD log file.
The only problem is that this type of log file isn’t like the ones you are used to. more specifically, it doesn’t come as a text document that you could open with Notepad.
So accessing the BSOD log file is a bit trickier, but it can be done, either using some of Windows 10’s own tools or with third-party software.
How do I check the BSoD log?
1. Use the Event Viewer
- Press Windows + X to open the Quick Links menu
- Click on Event Viewer
- Look over the Actions pane
- Click the Create Custom View link
- Select a time range
- This is where you should input the time range of when the BSOD happened
- Check the Error checkbox in the Event Level section
- Select the Event Logs menu
- Check the Windows Logs checkbox
- Click OK
- Give the custom view a name, and then press OK. (The Event Viewer will now show the information base don the filters you applied.)
- Sort the information by date using the Date and Time header
- Look at the error events at the time of your last BSOD
- For more details regarding the error, click on the Details tab
You’ll see that the Windows Event Viewer shows a log of application and system messages.
This includes errors, information messages, and warnings, and it is a useful tool for troubleshooting all kinds of different Windows problems.
2. Use a third-party BSoD viewer
If all of the steps mentioned above seem too complicated, then you could make use of a third-party event viewer. These apps will usually do the exact same thing as the Windows Event Viewer, but with fewer steps.
For a more details on how you can use a third-party BSOD viewer, check out this in-depth guide.
For this particular situation, we recommend using NirSoft’s BlueScreenView.
The tools scans your systems for the BSoD crash file and returns the information in one single table, so you can easily analyze it. This way, you’ll easily see the cause of the event and the location.
As a result, you’ll be able to go for the exact troubleshooting method.