Blue Screen of Death (BSOD) error is one of the common bugs you may encounter for several reasons. It may lead your system from malfunction to a complete crash, and you may end up losing access to your system and stored data. Sometimes, the error may go after rebooting your system. But what if it keeps occurring, and you don’t find any bugcheck for this error?
It would understandably be a frustrating situation. Don’t worry, though!
You can figure out the cause of the error with the help of the BSOD log file. Fortunately, Windows 10 stores such information in a sophisticated way, i.e., by creating a BSOD log file. But it doesn’t get stored in document or text form, which you can open and access directly. Accessing this file is a bit tricky. However, the solutions we’ve provided in this blog can help you locate the file and read it.
How to Find Windows 10 BSOD Logs?
A few DIY methods are shared here to help you check the BSOD logs Windows 10. Follow the steps mentioned against the methods.
Method 1: Use the Event Viewer
Using Event Viewer, you can view the content of event log files, and search & read the BSOD logs to diagnose issues related to the system and functions. It accesses the memory dumps and gathers logs stored on the PC. Event Viewer also provides crucial data on troubleshooting a problem when the system encounters a Blue Screen error.
- Type Event Viewer in Windows Search Box to open it.
- Go to Actions given on the top-left menu.
- Click Actions > Create Custom View.
- Select a time range against the ‘Logged’ option.
- Mark Error in Event Level and then mark Windows Logs in Event logs. Finally, click OK.
- Rename the ‘Custom View’ and click OK.
You’ll be able to see all the error logs on the screen. Locate the error events at the time of the last BSOD.
You can also click Details to see a log of apps and system messages, including errors, warnings, and information messages. It also helps in fixing other Windows problems.
Method 2: Use Windows 10 Monitor
Windows 10 Reliability Monitor is a built-in tool, allowing users to know the system’s stability. It lets you analyze if the application is crashing or not responding to issues and builds a PC stability chart. The Reliability Monitor checks out the stability on a scale of 1-10. The larger the scale, the better the system’s stability. You can access this tool through the control panel:
- Open Control Panel and navigate to System and Security.
- Next, go to Security and Maintenance.
- Navigate to Maintenance > View reliability history.
You will see the reliability data, displaying as a graph, where the cross (x) icons in red show errors and (i) icons in blue show a warning or notable event in the system.
When you click on Error or Warning icons, it will display the problem details. You can expand the details to locate BSOD errors or crashes.
Method 3: Use Registry Editor
You can also use the Registry Editor to check for the Windows 10 BSOD files. Follow the given instructions:
- Open the Run dialog box by pressing Windows + R. Type in regedit, and press Enter.
- Click ‘Yes’ if it asks for your permission to run the utility.
- Then follow HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control.
- Go to the right panel of Registry Editor, click New > QWORD (64 bit) Value.
- Rename it as Display Parameters, set the Value data to 1, and then click OK.
- Now, close the Registry Editor and reboot your PC.
I still can’t find where the BSOD logs Windows 10 are located. How would I fix it, and what about my data? Is it possible to recover data from a PC affected by a BSOD error? Don’t worry about your data, as you can recover it with the help of a powerful data recovery tool, such as Stellar Data Recovery Professional. It is a DIY data recovery software, which supports recovery from unbootable, crashed, or BSOD-affected Windows PCs and laptops. You can download its trial version to check its functionality and data recovery success rates.
Locating and accessing the Windows 10 BSOD logs is not always child’s play. However, you can refer to the methods given in this blog. Also, don’t forget to check the BSOD fixes. Finally, if you want to get back any lost data from the BSOD-affected system, use reliable data recovery software. The software can help you retrieve data even from non-booting or crashed Windows systems.
Was this article helpful?
YES0
NO
Did you recently face the Blue Screen of Death error? But couldn’t understand why the error occurs? Don’t worry, Windows saves the BSOD log file in a specific location. In this guide, you will find where is the BSOD log file located in Windows 10 and how to access & read the log file.
A Blue Screen Of Death (BSOD) is a splash screen that displays information about a system crash for a short while and proceeds to restart your computer. In the process, it saves the crash log files in the system before performing the restart. The BSOD happens due to a variety of factors, including incompatible software interfering with operating system processes, memory overflow, overheating of hardware, and failed system modifications.
The BSOD captures essential information regarding the crash and stores it on your computer so that it can be retrieved and sent back to Microsoft to analyze the cause of the crash. It has detailed codes and information that allows the user to diagnose issues with their computer. These files cannot be retrieved in a human-readable format, but it can be read using specific software that is present within the system.
Most of them might not be aware of the BSOD log files since you might not get enough time to read the text that appears during a crash. We can solve this issue by finding the location of the BSOD logs and viewing them to find problems and the time when it occurred.
Table of Contents
To find the location of Blue Screen of Death, BSOD error log file on Windows 10, follow the below method:
Access the BSOD log files using the Event Viewer Log
The Event Viewer Log is used to view the content of event logs – files that store information about the start and stop of services. It can be used to diagnose issues related to the system and functions, just like the BSOD log. We can use the Event Viewer Log to search and read the BSOD log files. It accesses the memory dumps and collects all the logs stored on your computer.
Event Viewer Log also provides vital information regarding troubleshooting any issues that happen when the system encounters a Blue Screen of Death. Let’s see how to access the BSOD log files using the Event Viewer Log:
1. Type Event viewer and click on it from the search results to open it.
2. Now, click on the Action tab. Select “Create custom view” from the dropdown menu.
3. Now you will be presented with a screen to filter the event logs according to different attributes.
4. In the Logged field, choose the time range from which you need to get the logs. Select the Event level as Error.
5. Choose Windows Logs from the Event log type dropdown and click OK.
6. Rename your view to anything you like and click OK.
7. Now you can see the Error events listed in the Event Viewer.
8. Select the most recent event to see the BSOD log details. Once selected, go to the Details tab to get more information regarding the BSOD error logs.
Use Windows 10 Reliability monitor
Windows 10 Reliability Monitor is a tool that enables users to know their computer’s stability. It analyzes the application crashing or not responding issues to create a chart about the stability of the system. The Reliability Monitor rates the stability from 1 to 10, and the higher the number – the better the stability. Let us see how to access this tool from the Control Panel:
1. Press Windows key + S to open Windows Search Bar. Type Control Panel in the search box and open it.
2. Now click on System and Security then click on the Security and Maintenance option.
3. Expand the maintenance section and click on the option “View reliability history.”
4. You can see that the reliability information is displayed as a graph with the instabilities and errors marked on the graph as points. The red circle represents an error, and the “i” represents a warning or notable event that occurred in the system.
5. Clicking on the error or warning symbols displays detailed information regarding the problem along with a summary and the exact time when the error occurred. You can expand the details to get more details about the BSOD crash.
Disable or Enable Memory Dump Logs in Windows 10
In Windows, you can disable or enable memory dump and kernel dump logs. It is possible to change the storage space allocated to these dumps to store logs reading system crashes. By default, the memory dump is located at “C:\Windows\memory.dmp”. You can easily change the default location of the memory dump files and enable or disable the memory dump logs:
1. Press Windows + R to bring up the Run window. Type “sysdm.cpl” in the window and hit Enter.
2. Go to the Advanced tab and click on the Settings button under Startup and Recovery.
3. Now in the Write Debugging information, select the appropriate option from Complete memory dump, Kernel memory dump, Automatic memory dump.
4. You can also disable the dump by selecting None from the dropdown. Note that you will not be able to report errors as the logs will not be stored during a system crash.
5. It is possible to change the location of the dump files. First, select the appropriate memory dump then under the “Dump file” field then type in the new location.
6. Click OK and then Restart your computer to save changes.
Memory dumps and BSOD log files help the user fix different issues on the Windows-based computer. You can also check the error using the QR code displayed during the BSOD crash on Windows 10 computer. Microsoft has a Bug check page that lists such error codes and their possible meanings. Try these methods and check whether you can find the solution for the system instability.
Recommended:
- Fix Ntoskrnl.exe BSOD Blue Screen error
- Using Driver Verifier to fix Blue Screen of Death (BSOD) errors
- Fix Black Desktop Background In Windows 10
We hope this article was helpful and you were able to find the BSOD log file location in Windows 10. If you still have any questions or confusion regarding this topic then feel free to ask them in the comment section below.
Все способы:
- Способ 1: Журнал событий
- Способ 2: Сторонние приложения
- WinDbg
- BlueScreenView
- Вопросы и ответы: 1
Способ 1: Журнал событий
Простой, но не самый удобный способ определения кода синего экрана, так как он предполагает выполнение дополнительных действий.
- Откройте системный «Журнал событий» командой
eventvwr.msc, выполненной в вызванном нажатием клавиш Win + R диалоговом окошке быстрого запуска. - Нажмите в правой колонке ссылку «Фильтр текущего журнала».
- В открывшемся окне отметьте флажком пункт «Критическое» и нажмите «ОК», чтобы отфильтровать события.
- Выберите последнюю запись об ошибке и откройте ее свойства двойным по ней кликом.
- Переключитесь на вкладку «Подробности», отыщите в списке параметр «BugCheckCode» и посмотрите его значение. Это и будет код ошибки в десятичном счислении.
- Переведите его в шестнадцатеричную систему счисления, воспользовавшись штатным «Калькулятором» Windows, переключив его в режим «Программист» (через меню, вызванное нажатием по кнопке меню слева вверху). Результат будет указан в строке «HEX» без нулей, которые понадобится добавить. Например, EF = 0x000000EF.
Теперь можно выполнить поиск решения проблемы в интернете, указав полученный шестнадцатеричный код ошибки BSOD.
Способ 2: Сторонние приложения
Удобнее определять ошибку через специальные приложения, работающие с файлом дампа. По умолчанию его создание включено в Windows, но если вы отключали его создание вручную, то просмотреть стоп-код таким образом не получится из-за отсутствия файла для анализа сбоя.
WinDbg
Синий экран со стоп-ошибками в Windows 10 не отличается информативностью и нередко содержит только название ошибки, но не ее код. Чтобы определить ее код, необходимо проанализировать файл минидампа. Сделать это можно средствами фирменной утилиты Microsoft WinDbg.
Скачать WinDbg с официального сайта
- Скачайте приложение для анализа дампов с Microsoft Store или официальной страницы разработчика и установите.
- Запустите программу от имени администратора и нажмите в левом верхнем углу кнопку «Файл».
- Выберите в меню опцию «Open dump file», нажмите кнопку «Browse», укажите путь к анализируемому файлу дампа в папке
C:\Windows\Minidumpи нажмите «Open». Папка Minidump может содержать несколько файлов c расширением DMP, из них следует выбирать тот, который имеет название, соответствующее дате и времени ошибки синего экрана. - Прокрутите содержимое блока «Command» вниз, найдите ссылку «!analyze -v» и кликните по ней. Вместо этого можно вставить команду
!analyze -vв поле под блоком «Command» и нажать клавишу ввода. - Отладчик выполнит анализ файла дампа и выведет в блок «Command» подробные сведения об ошибке. Ищите ее название – код будет указан напротив него в полном или сокращенном виде, например 139, 0x139 или 0x00000139.
Кроме кода WinDbg позволяет получать множество других полезных сведений об ошибке, в частности аргументы и имя исполняемого файла, вызвавшего критический сбой.
BlueScreenView
Для получения кода ошибки экрана BSOD также можно использовать стороннюю утилиту BlueScreenView. Она не настолько функциональна как WinDbg, но намного проще и меньше инструмента от Microsoft.
Скачать BlueScreenView с официального сайта
- Скачайте архив с утилитой с сайта разработчика, распакуйте его и запустите исполняемый файл. Там можно скачать и языковой файл — для русификации интерфейса поместите языковой файл в папку с исполняемым файлом «BlueScreenView.exe».
- По умолчанию утилита автоматически считывает все файлы дампов в папке
C:\Windows\Minidump, но если в вашем случае файл дампа находится в другом месте, откройте дополнительные параметры утилиты комбинацией клавиш Ctrl + 0. - В открывшемся окошке выберите пункт «Загрузить один файл МиниДампа» и укажите путь к файлу DMP.
- Просмотрите содержимое колонки «Код ошибки» — в нем будет указан искомый код в шестнадцатеричном формате.
Помимо кода ошибки синего экрана, утилита BlueScreenView показывает сбойный драйвер, список связанных файлов, параметры, стеки адресов и другие отладочные сведения.
Наша группа в TelegramПолезные советы и помощь
When your computer crashes and you face a Blue Screen of Death (BSOD), your system saves the details of the crash as a BSOD log, in a pre-defined location in Windows. This information gives you details about when the crash happened, what caused it, and sometimes even what to do to fix the problem.
In this guide, we will first discuss where are the BSOD files located in Windows and then how to identify them. Once you have located a BSOD file, we will show you how to read it properly to understand the potential causes of the error and resolve the problem.
Where Are the BSOD Log Files Located in Windows?
You can find the BSOD log files in the Event Viewer, Control Panel, and Registry Editor in Windows. Below, we have listed the detailed steps for finding these files in all three of these utilities.
1. Find and Read the BSOD Log Files in the Event Viewer
The Event Viewer is a tool developed by Microsoft for users to view system and program-related events in Windows. These events can include system errors, warnings, informational messages, and more. In other words, every issue you encounter (whether a minor glitch or a major crash) will be logged in the Event Viewer for later investigation and sharing with Microsoft.
You can check out our detailed guide on what the Event Viewer is and how it can be useful if you are unfamiliar with it.
Here is how you can find the BSOD log files in the Event Viewer:
-
Right-click on the Windows icon in the taskbar and choose Event Viewer from the context menu.
-
Head over to the Action menu located at the top, and choose Create Custom View from the context menu.
-
In the following dialog, expand the dropdown for Logged and choose the time when you encountered the issue.
-
Now, move to the Event Level section and choose Error.
-
Expand the dropdown for Event Logs and checkmark the box for Windows Logs.
- Click OK to proceed.
-
You will now be prompted to enter a name and description for the custom view you just created. Enter these details and click OK.
-
Once the view is created, you will be presented with a list of errors that occurred during the time frame you selected earlier. You can sort this information further in the Date and time section.
- Next, locate the BSOD using details like the date and time again.
- Once you find the targeted log, click on it.
- Check both the General and Details tabs to get information about this error.
Once you find the error code associated with the crash and the cause, you can look for solutions online, or head over to our guide that discusses how to fix blue screen errors in Windows if it’s a bsod.
2. Find and Read the BSOD Log Files in the Registry Editor
In case using the Event Viewer does not work for you for some reason, you can use another Windows utility to locate and study the BSOD log files—the Registry Editor.
Windows Registry Editor is an administrative-level utility that lets you control how Windows operates and interacts with hardware and software. The Registry stores information related to the hardware and software components of your system. This information in the Registry is stored in the form of keys and values, and by modifying these with the dedicated Registry Editor, you can customize the operations of your system.
Listed below are the steps for finding the BSOD log files in the Registry Editor. Make sure you are logged into your system as an administrator before you proceed.
- Press the Win + R keys to open Run.
- Type «regedit» in Run and press Ctrl + Shift + Enter to launch the Registry Editor as an administrator.
- Now, select Yes in the User Account Prompt.
-
Once you are inside the Registry Editor, navigate to the following location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl - Next, move to the right pane and right-click on an empty space anywhere.
-
Choose New > DWORD (32-bit) Value.
- Name this value as DisplayParameters and double-click on it.
-
Under Value data, type 1 and click OK.
- Once done, restart your PC.
Upon reboot, you should be able to view the log files without any problems.
3. Find and Read the BSOD Log Files in the Control Panel
The third way of finding and reading the BSOD log files is via the Control Panel. This approach offers a graphical representation of the log files using the Windows Reliability Monitor, unlike the methods we have explored previously.
The Reliability Monitor, which is different than the Performance Monitor (see Reliability Monitor vs. Performance Monitor) will show you a timeline of important system events that occurred on your computer including BSOD occurrences, software installations, application crashes, and other relevant events.
Here is how you can use it to identify and fix problems that may affect your system:
- Type Control Panel in the search area of the taskbar and click Open.
-
In the following window, choose System and Security > Security and Maintenance.
-
Click on Maintenance and then select View reliability history.
-
You should now see a graph showing the reliability data. Look for red cross icons and blue (i) icons in the graph, as they show problematic events.
- Click on each of the icons to view its details. Keep repeating the process to locate the event you are looking for.
You will be presented with information like the faulting application path, its name, fault module timestamp, exception code, etc. If this app caused a BSOD crash, then you can try ending its process via the Task Manager or uninstalling the app if it is not necessary.
It is also a good idea to copy this information and send it to Microsoft for review if you cannot find a solution online.
Learn How to Read Your BSOD Log Files and Resolve Your Crashes
Windows blue screen errors are nothing new, but since they only display messages like «Your PC encountered a problem» without describing the cause, it can be difficult to find a fix. Understanding how to read BSOD log files can not only help you identify the exact cause of the problem but also help you find the right solution.
Whenever a component causes your system to crash, you can disable it and switch to a better alternative to avoid the problem.
@titov_andrei
All my life I learn — and die a fool!
Комп перезагружается внезапно, даже иногда без нагрузки на память, проц и диск. Выходит сообщение на синем фоне о сборе данных об ошибке и дальнейшей перезагрузке. Где посмотреть эти данные?
-
Вопрос задан
-
57357 просмотров
C:\Windows\MEMORY.DMP C:\Windows\Minidump + Event viewer
Перед загрузкой системы нажмите F8 и выберете опцию «Отключить автоматическую перезагрузку при отказе системы». После этого при возникновении синего экрана можно посмотреть об ошибке подробнее. Проблема либо аппаратная, либо в драйверах.
Пригласить эксперта
Чтобы быстро просмотреть логи именно от синих экранов смерти BSOD, гораздо удобнее воспользоваться бесплатной программой BlueScreenView
-
Показать ещё
Загружается…