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.

The secrets of your Windows 10 log files: how to find crash logs, error logs on Windows 10 the easy way

Should your PC run into trouble, here is how to find Windows 10 crash logs on your PC. It is quick and easy if you know where to start.

(If you are using Windows 8 or 8.1, here is an article tailor-cut for you on how to find crash logs on Windows 8.)

Find Windows 10 crash logs and error logs the easy way

…and you won’t ever need to dig for them the hard way.

Using this method, you can find crash logs and error logs—in fact, any type of logs that were written by the operating system and also any of your applications’ logs—in one place.

Step 1. Click on the search icon and type „Event Viewer“

Click on the Search icon located in the task bar. As soon as it pops up the search field, you can immediately start typing. Enter “Event Viewer” and watch the results unfold.

Click on the Search icon or press the key combination Windows-S

(Search in Windows 10 will behave differently depending on whether you have enabled or disabled web search. Here is a tip on how to disable web search from the task bar so that it no longer interferes with your desktop searches.)

Step 2. Type in “Event Viewer” and watch the results roll in

Wait for the list of search results to quit reshuffling, then right-click on the entry Event Viewer: Desktop app and select the command Run as Administrator.

How to find crash logs on Windows 10: press the key combination Windows-S, enter the search string “Event Viewer” and wait for the Search to display its icon in the results

Step 3. Create a custom view

In the Event Viewer, navigate through the various categories (called Views) in the left-hand navigation pane in order to inspect the various events in the main section of the screen. You can adjust your filter criteria until you find what you were looking for.

For quicker access to particular types of logs, click or tap on Create Custom View. Enter your criteria and confirm.

Windows 10 crash logs are best found in the Event Viewer: Inspecting logs this way is a breeze

Step 4. Export the logs you need for diagnostics

In order to export some of the logs for external diagnostics, make your selection in the list, then hit Save selected events….

If your computer is giving you a hard time with persistent crashes and the like, you may need to perform some repairs. Start by repairing the file system (see below). If that fails to resolve the issue, you can try and restore the boot directory. Here is how to do this: How to Repair Windows 10 to a State of Sparkling Awesomeness: Recover from Crashes, Restore, and Reboot.

Step 5. How to find the cause of persistent crashes using log files

A major cause of persistent crashes, BSoD incidents and other malfunctions comes down to hardware defects due to faulty manufacturing, overheating or rough handling. For clues, look at the Applications and Services Logs section of the Event Viewer.

Hardware components such as the CPU, RAM chips, video cards or the motherboard are extremely sensitive to heat. The system or its individual components may overheat during prolonged use, particularly when overclocking. Before the iron melts on you, adding or replacing case fans and coolers can save you real money. The most sensitive components include the video card(s), CPU(s), RAM chips and the motherboard. Adding fans to cool memory banks or fitting the system with liquid cooling can not only prevent damage—it can also improve performance. Hardware damage due to overheating tends to be pretty irreversible so that no amount of passive or active cooling will make the crashes go away. The quicker you can react to early signs of hardware malfunctions, the higher your chances at preventing damage to components in your PC or gaming console. Log files can give you invaluable insights into the real causes of persistent system crashes. We hope that helps. Feel free to post your questions in the comments below.

One last tidbit of rather obvious advice: file system errors tend to propagate. If you start experiencing system freezes or crashes, repair your file system to prevent further damage. The simplest way to do it is by running this command:

on each one of your drives (c: d: e: and so forth) in the Windows PowerShell as an Administrator. If Windows complains about a disk partition being in use, allow the system to reboot (do NOT force a dismount!).

Как посмотреть логи Windows?

Логи — это системные события, который происходят в любой операционной системе. С помощью логов можно легко отследить кто, что и когда делал. Читать логи могут не только системные администраторы, поэтому в данной инструкции рассмотрим, как смотреть логи ОС windows.

Ищете сервер с Windows? Выбирайте наши Windows VDS

Просмотр событий для проверки логов.

После нажатия комбинации “ Win+R и введите eventvwr.msc ” в любой системе Виндовс вы попадаете в просмотр событий. У вас откроется окно, где нужно развернуть Журналы Windows. В данном окне можно просмотреть все программы, которые открывались на ОС и, если была допущена ошибка, она также отобразится.

Аудит журнал поможет понять, что и кто и когда делал. Также отображается информация по запросам получения доступов.

В пункте Установка можно посмотреть логи ОС Виндовс, например, программы и обновления системы.

Система — наиболее важный журнал. С его помощью можно определить большинство ошибок ОС. К примеру, у вас появлялся синий экран. В данном журнале можно определить причину его появления.

Логи windows — для более специфических служб. Это могут быть DHCP или DNS.

Фильтрация событий.

С помощью Фильтра текущего журнала (раздел Действия) можно отфильтровать информацию, которую вы хотите просмотреть.

Обязательно нужно указать уровень Событий:

• Критическое
• Ошибка
• Предупреждение
• Сведения
• Подробности

Для сужения поиска можно отфильтровать источник событий и код.

Просмотр PowerShell логов.

Открываем PowerShell и вставляем следующую команду Get-EventLog -Logname ‘System’

В результате вы получите логи Системы

Для журнала Приложения используйте эту команду Get-EventLog -Logname ‘Application

Также обязательно ознакомьтесь с перечнем аббревиатур:

• Код события — EventID
• Компьютер — MachineName
• Порядковый номер события — Data, Index
• Категория задач — Category
• Код категории — CategoryNumber
• Уровень — EntryType
• Сообщение события — Message
• Источник — Source
• Дата генерации события — ReplacementString, InstanceID, TimeGenerated
• Дата записи события — TimeWritten
• Пользователь — UserName
• Сайт — Site
• Подразделение — Conteiner

Для выведения событий в командной оболочке только со столбцами «Уровень», «Дата записи события», «Источник», «Код события», «Категория» и «Сообщение события» для журнала «Система» используйте:

Get-EventLog –LogName ‘System’ | Format-Table EntryType, TimeWritten, Source, EventID, Category, Message

Если нужна подробная информация, замените Format-Table на Format-List на

Get-EventLog –LogName ‘System’ | Format-List EntryType, TimeWritten, Source, EventID, Category, Message

Формат информации станет более легким

Для фильтрации журнала, например, для фильтрации последних 20 сообщений, используйте команду

Get-EventLog –Logname ‘System’ –Newest 20

Если нужен список, позднее даты 1 января 2018 года, команда

Get-EventLog –LogName ‘System’ –After ‘1 января 2018’

Надеемся, данная статья поможет вам быстро и просто читать логи ОС Windows.

Желаем приятной работы!

Как установить свой образ на ВДС сервер с Виндовс, читайте в предыдущей статье.