Windows event viewer crash

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.

Читайте также:  Strict nat как исправить windows 10

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 10 Apps crash to desktop — Event Viewer shows lots of Errors «access is denied»

The Windows Event Viewer desktop application is filled with Error entries that show that a module cannot start because it does not have access rights. Could this have something to do with the fact that I’m using Windows with a main account which only has «normal» user rights instead of «administrator» user rights?

Event Viewer Error log entry example:

Log Name: Application
Source: Microsoft-Windows-Immersive-Shell
Date: 2015-10-20 19:53:43
Event ID: 5973
Task Category: (5973)
Level: Error
Keywords:
User: SURFACE\Johan
Computer: Surface
Description:
Activation of app Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy!App failed with error: Access is denied. See the Microsoft-Windows-TWinUI/Operational log for additional information.
Event Xml:

5973
0
2
5973
0
0x2000000000000000

86998

Application
Surface

Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy!App
-2147024891

And another one:

Log Name: Application
Source: Microsoft-Windows-Immersive-Shell
Date: 2015-10-20 19:53:39
Event ID: 5973
Task Category: (5973)
Level: Error
Keywords:
User: SURFACE\Johan
Computer: Surface
Description:
Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: Access is denied. See the Microsoft-Windows-TWinUI/Operational log for additional information.
Event Xml:

5973
0
2
5973
0
0x2000000000000000

86997

Application
Surface

Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI
-2147024891

Replies (3) 

Thank you for posting your in Microsoft Community.

It is unfortunate that you have ended up in this situation.

Run the App Troubleshooter and check the troubleshooter report:

The Apps Troubleshooter is an automated tool which we have developed to address a number of known issues that can prevent the Apps from running properly. This troubleshooter automatically fixes some issues, including suboptimal screen resolution, incorrect security or account settings etc. You can click on this link to download and run the Apps troubleshooter.

Читайте также:  Обновиться до 2004 как обновиться windows 10

“What to do if you have problems with an app

In future, if you have any issues related to Windows, do get back to us. We will be happy to assist you.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Rajesh, Namaste,

Thanks for the offer of running the Troubleshooter. Perhaps I should have stated that I already had executed the troubleshooter before posting my issue, without positive outcome.

The issue does no longer happen at the moment; I disabled Cortana by setting my country settings to Germany (country I am living in) and the OS language to English US; this is a combination not supported by Cortana and therefore the program won’t start.

A couple of hours later my apps were starting as they should. I can’t say for sure that disabling Cortana really stopped the error from happening, but that’s all I actually did. Unless of course there was a fix on the Microsoft’s side. But as has been the case lately, there is simply no clear way of knowing for sure what changed.

I feel like Microsoft is pushing off too many times the issue of apps crashing on to the users, or customers, as if we’re doing something wrong, by not running apps in an «container» system which will catch apps crashing like the OS treats regular desktop applications. The way the apps are just crashing and disappearing is honestly just really cheap and unstable. It does not give me any trust in Windows 10 as a productive platform, something Microsoft is so eager to sell in the advertisements.

I wish for Microsoft to enhance the «apps» systems, which it wants to push so dearly, to be much more user-centric friendly, as in creating a much more clearer way of starting, stopping, crashing etc. I wish for Microsoft to build in a way for us users to be more confident using the apps if it really wants us to invest in the platform.

I sincerely hope this will improve in the near future.

Windows event viewer crash

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.

Читайте также:  Где храниться контакты windows live

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

Windows event viewer crash

To evaluate the BSOD please post logs for troubleshooting.

Using administrative command prompt copy and paste this whole command.

Make sure the default language is English so that the logs can be scanned and read.

The command will automatically collect the computer files and place them on the desktop.

Then use 7zip to organize the files and one drive, drop box, or google drive to place share links into the thread for troubleshooting.

This command will automatically collect these files: msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

Open administrative command prompt and copy and paste the whole command:

copy %SystemRoot%\minidump\*.dmp «%USERPROFILE%\Desktop\»&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt «%USERPROFILE%\Desktop\SFdebugFiles\»&type %SystemRoot%\System32\drivers\etc\hosts >> «%USERPROFILE%\Desktop\hosts.txt»&systeminfo > «%USERPROFILE%\Desktop\systeminfo.txt»&driverquery /v > «%USERPROFILE%\Desktop\drivers.txt» &msinfo32 /nfo «%USERPROFILE%\Desktop\msinfo32.nfo»&wevtutil qe System /f:text > «%USERPROFILE%\Desktop\eventlog.txt»&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall «%USERPROFILE%\Desktop\uninstall.txt»&reg export «HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components» «%USERPROFILE%\Desktop\installed.txt»&net start > «%USERPROFILE%\Desktop\services.txt»&REM wmic startup list full /format:htable >»%USERPROFILE%\Desktop\startup.html»&wmic STARTUP GET Caption, Command, User >»%USERPROFILE%\Desktop\startup.txt»

There are two files for you to find manually:

Use file explorer > this PC > local C: drive > right upper corner search enter the above to find results.

In the left lower corner search type: dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread
.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.
.
.
.
.
.

Оцените статью