How to View Windows 10 Crash Logs and Error Logs (2021 Updated) [Partition Magic]

By Irene | Follow | Last Updated January 05, 2021

Summary :

When you computer crashes, a crash log will be generated, which can help you analyze the causes of the crash. But, do you know how to view Windows 10 crash logs and error logs? If you don’t know, don’t worry. This article from MiniTool will show you how to view Windows 10 crash log with two methods.

Quick Navigation :

Method 1. View Windows 10 Crash Logs with Event Viewer

To view Windows 10 crash logs, you can make use of the built-in tool Event Viewer, which keeps a log of application and system messages, errors, warnings, etc. You can follow the steps below to check Windows crash logs Windows 10 with Event Viewer.

Step 1. Type Event Viewer in the Windows 10 Cortana search box. Then right click the best match Event Viewer and choose Run as Administrator.

Step 2. Here is the main interface of Event Viewer. On the left side of the window, you can view all the Logs according to the category. To view Windows 10 crash logs such as the logs of blue screen error, just click on Windows Logs.

Step 3. Then choose System under Windows Logs.

Step 4. Find and click Error on the event list. Then you can view the detailed crash log information shown up in the bottom of the window.

You can also create a custom view so you can view the crash logs more quickly. Here are steps on how to create a custom view.

Step 1. Click on Create a Custom View on the right window. As you click on Create Custom View, a new window will pop up.

Step 2. Choose a time period you want to view. Then check the boxes next Critical, Warning and Error in the Event levels section.

Step 3. Select the By log option. Then click the drop-down menu next to Event logs, and then select Application, Security and System.

Step 4. Then click OK to save the settings.

Step 5. Name this custom view and then click OK to start to view the Windows 10 crash log.

Step 6. Then you can view all the Windows 10 crash logs during the tome period you select.

Windows Reliability Monitor also enables you to view recent system and application crashes. Here’s how to check Windows 10 crash logs with Reliability Monitor.

As a game lover, you may run into computer crashes when playing games. This article offers some solutions to this issue.

Method 2. View Windows 10 Crash Log with Reliability Monitor

Step 1. Type reliability in the Windows 10 Cortana search box. Then click the best match View reliability history.

Step 2. From the main interface, you can see that the Reliability Monitor window is arranged by dates. If Windows crashes or freezes, you will see a red circle with an «X» representing the failure, as shown below.

Step 3. If you want to view a certain day’s crash log, just click that day’s column and more detailed information will be displayed at the bottom. You can also double click one of the listed events to open a new window with more information.

Conclusion

Event viewer and Reliability Monitor are all good for you to check Windows 10 crash logs. Choose a tool you like and you can get all the Windows crash log information.

Windows event viewer crashes

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Trying to access the Event Viewer in my W7 Ulitimate x64 machine. MMC starts fine, and other MMC apps work.

I get same result if I run eventvwr.exe or if I run MMC and then open the event viewer. Each time, I get the following message:

Problem signature:
Problem Event Name: APPCRASH
Application Name: mmc.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc808
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdfe0
Exception Code: c000041d
Exception Offset: 000000000000aa7d
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 46b5
Additional Information 2: 46b58121c9f2560689e145b4dc343836
Additional Information 3: 38d3
Additional Information 4: 38d36bc51ff6dc4d689c937359098f1a

I was finally able to run the event viewer by double clicking on the eventvwr.msc file in SysWOW64.

In the event log I could open, I found this:

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

These files may be available here:

Rechecking for solution: 0

Report Id: b922e400-a022-11df-872c-005056c00008

Report Status: 0

Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808

Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0

Exception code: 0xc000041d

Fault offset: 0x000000000000aa7d

Faulting process id: 0xa60

Faulting application start time: 0x01cb342f77edcea0

Faulting application path: C:\Windows\SysWOW64\mmc.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: b922e400-a022-11df-872c-005056c00008

Event Viewer crashes when you open a large event log file and sort log entries by one column on a Windows Vista-based or Windows Server 2008-based computer

Symptoms

Consider the following scenario:

You open a saved event log file in Event Viewer on a computer that runs Windows Vista or Windows Server 2008.

The log file size is more than 2 megabytes.

You sort log entries by clicking the header of a column.

In this scenario, an exception occurs and Event Viewer crashes. This problem is more likely to occur when you click a column header multiple times in a quick succession.

Resolution

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix on a Windows Vista-based computer, you must have Windows Vista Service Pack 1 or a later service pack installed on the computer.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service pack

No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.