How to Analyze Memory Dump Files (.dmp) in Windows 10:
If your Windows PC suffers Blue Screen of Death (BSOD) error, There will be many things. The most obvious is that your PC is forced to restart, as BSOD is a result of Windows crashing completely. A less obvious result of a BSOD error, however, is the error log that is created that allows you to troubleshoot the problem later.
This is called a memory dump file, which is saved in the DMP file format. These files include various information about the problem, including your current Windows version, any running app at the time of BSOD, and the driver itself and the error. Here’s what you need to do to help you analyze memory dump files.
What are memory dump files on Windows 10?
A Blue Screen of Death is a significant and irreversible error on a Windows PC, but the cause of these errors may vary. For example, a Unexpected kernel mode trap BSOD Usually caused by incompatible or overclocked hardware, while A Critical process BSOD died There can be various reasons including corrupt system files.
To help you troubleshoot the problem, Windows automatically generates a memory dump file. It usually has a stop code name and value (such as a System service exception stop code), A list of any driving drivers at the time of the accident, and some additional technical information you can use to identify the cause.
These dump files (using the DMP file format) are automatically saved to either root C: _, C: minidump, or C: Windows minidump Folder. To help you analyze them, you can install Microsoft’s debugging app Windbg From Microsoft Store. It helps you analyze memory dump files and detect stop code information.
You can also use old tools like NirSoft BlueScreenView To quickly analyze dump files created on your PC. It will also help you identify stop code values and possible causes (such as a specific driver file).
Once you know the stop code value, you can search for additional information about the problem online. For example, if you have detected from your dump file that you have encountered memory management BSOD, you can check us BSOD Error Guide For additional advice on solving the problem.
Because a BSOD error may prevent your PC from working, you may need to try and Restart windows in safe mode. Running Windows in safe mode minimizes the number of active system processes and drivers, allowing you to investigate things further.
If you cannot boot into Windows at all, however, your options are limited. Currently, there are no standalone tools you can run if Windows itself is not working properly to analyze BSOD dump files. If it does, then you will need it Recover dump files using linux live cd Using a DVD or portable USB flash memory stick.
You can then analyze the file using WinDbg or NirSoft BlueScreenView on a working Windows PC or laptop by following the steps below.
Changing memory dump file settings in windows settings
Memory dump files are created automatically, but you can set the level of detail included in the memory dump file in Windows Settings. This will only work for the BSOD that occurs. After the Changing this setting, but if your PC is having problems, you can follow these steps to add additional information to the dump files.
- To start, right-click on the Start menu and select Adjustment.
- In Adjustment Menu, select system > About. In Related settings Panel, in system > About Menu, select advanced System Settings the option.
- In system properties Menu, select Adjustment Options listed in Startup and recovery Bottom section.
- To change the level of detail entered by memory dump files when BSOD occurs, select one of the available options Write debugging information In the drop-down menu Startup and recovery Window. Full information is available on what each memory dump contains. Microsoft documentation website. Choose Okay > Okay To save your choice.
You may need to restart your PC after making this change to apply the setting. Any future BSOD errors will generate a memory dump file containing the level of information you select.
How to analyze Windows memory dump files using WinDbg
If you are suffering from a BSOD error, you can use Windbg To analyze a memory dump file. This Microsoft built development tool is the best way to analyze your memory files, but you can also use the old NirSoft BlueScreenView as an option by following the steps below.
These steps assume that your PC is working sufficiently to install and use WinDbg. If it is not, then you will have to recover the dump files from your hard drive using Linux Live CD or USB to perform the analysis elsewhere. Live CD environments can be booted using most installation media Linux distribution, Including Ubuntu and Debian.
- To begin, you will need to Install windbg preview From Microsoft Store. On the WinDbg store page, select Received To begin the installation.
- After WinDbg is installed, select and launch it launch On the store page or by launching it from the Start menu. If you cannot access your dump files, you will need to locate WinDbg in the Start menu right click Choose more more > run as administrator To give it the necessary access.
- In Windbg Window, select The file > Start debugging > Open dump file. Use the built-in File Explorer menu to open your latest dump file, which is usually saved to the root C: Folder, C: minidump, or C: Windows minidump Folder.
- Opening the DMP file will cause WinDbg to run the debugger and load the file. This can take some time depending on the size of the file and the level of detail saved. Once this is done, type The Analysis -v In the command box at the bottom of Order Tab, then press Enter To run the command.
- The Analysis -v The command will take some time to load and analyze the log file created by the BSOD error – wait for this process to complete. Once this is completed, you can analyze the complete output Order Tab. Specifically, find the stop code name and value (for example) Driver IRQL is not less or equal And D1) Is listed under Bugcheck Analysis Section. Along with the stop code, a brief description (such as driver issues) giving the reason will be listed, allowing you to troubleshoot further.
- You can also view other relevant information (such as) listed in the WinDbg analysis Module Name Value) to identify the cause. In this example, running BSOD code was caused by NotMyFault System Testing Tool.
Once you have identified the stop code and possible cause of the BSOD error, you can do further research on the issue to determine the possible fix.
How to analyze Windows memory dump files using NirSoft BlueScreenView
While WinDbg is not included with Windows, it is designed by Microsoft to troubleshoot BSOD errors. If you wish, you can analyze the memory dump files from your PC (or from another PC if you have a copy of the old dump files). NirSoft BlueScreenView equipment.
The bluescreen view may look dated, but it provides all the relevant information about your BSOD dump files. This includes the stop code name and price (s) Driver IRQL is not less or equal) Which you can then use to identify the cause.
- to start, Download and install NirSoft BlueScreenView tool On your Windows PC. Once the tool is installed, launch it from the Start menu.
- The bluescreen view will automatically detect any memory dump files from known sources such as C:/ And C: / Windows / MiniDump. If you want to manually load a file, however, select the option > advanced options.
- In advanced options Menu, switch to the folder in which your dump files are selected Browse Posted next to the button Load from the following MiniDump folder Box. To return it to the default location, select Default. Choose Okay To save your choice and load your files.
- In the main bluescreen view window, a list of your saved memory dump files will appear. Select one of the listed files to see more information about it. Stop code name will appear Bug check string The column allows you to do further research on this issue.
- The complete list of active files and drivers will be listed below, along with the selected memory dump file. Files highlighted in red will have a direct link to the cause of the BSOD error. for example, myfault.sys While NotMyFault is related to system testing tool ntoskrnl.exe Windows is the system kernel process.
While BlueScreenView is a useful tool for quickly identifying the BSOD error name, it is not a complete debugging tool like WinDbg. If you cannot troubleshoot the problem using this tool, you will need to try WinDbg for a more detailed analysis.
Troubleshooting BSOD errors using memory dump files
By using the memory dump file information you retrieve, you can troubleshoot BSOD errors by searching for stopping codes or related BSOD error files. Error prevention codes, in particular, can help you find the reason behind BSOD, from A. Poor system To one Unexpected store exception error BSOD.
BSOD errors are caused by everything Faulty hardware For corrupt system files. To help stop them, you need Check your pc for malware Regularly and Use devices like sfc If it becomes corrupt then repair your Windows installation. If all else fails, you can always Reset or reinstall windows 10 To restore your PC to full working order.