Dmp file how to open

Открываем дампы памяти DMP

Варианты открытия DMP

Расширение DMP зарезервировано за файлами дампов памяти: снимков состояния RAM в определённый момент работы системы или отдельного приложения, которые нужны разработчикам для последующей отладки. Такой формат используют сотни видов ПО, и рассмотреть их все в объёмах данной статьи невозможно. Наиболее же часто встречающийся тип DMP-документа – так называемый малый дамп памяти, где записаны подробности сбоя системы, который привёл к появлению синего экрана смерти, потому на нём и сосредоточимся.

Способ 1: BlueScreenView

Небольшая бесплатная утилита от разработчика-энтузиаста, основной функцией которой является предоставление возможности просмотра DMP-файлов. Не нуждается в установке на компьютер – достаточно распаковать архив в любое подходящее место.

Утилита BlueScreenView рассчитана на продвинутых пользователей, потому её интерфейс может показаться сложным для новичка. Кроме того, доступна она только на английском языке.

Способ 2: Microsoft Debugging Tools for Windows

В составе среды разработки Windows SDK распространяется инструмент для отладки, который называется Debugging Tools for Windows. Приложение, рассчитанное на разработчиков, способно открывать в том числе и DMP-файлы.

Для запуска программы используйте ярлык «WinDbg».

Внимание! Для открытия DMP-файлов используйте только x64- или x86-версии дебаггера!

Утилита Debugging Tools for Windows ещё более сложная, чем BlueScreenView, и тоже не имеет русской локализации, однако предоставляет более подробную и точную информацию.

Заключение

Как видим, основную сложность при открытии DMP-файлов составляют сами программы, рассчитанные больше на специалистов, чем на рядовых пользователей.

How to open DMP files in Windows 10 [EASY STEPS]

There’s a large portion of Windows system files that are not as easily accessed as some others. One of those Windows-exclusive extensions is known as DMP (.dmp) or Windows Memory Dump files.

Today, we made sure to explain the value of these files and, what is most important, the means to open them in Windows 10. If you want to access the DMP file in Windows 10, but you’re not sure how to, make sure to continue reading.

How can I access DMP files in Windows 10?

What DMP file extension stands for?

For obvious reasons, they are mostly named Memory.dmp or Crash.dmp, respectively. Size-wise, they might be small individually.

However, as they tend to pile up over time, DMP files can take a lot of storage space when bundled. So, you can clean them up with ease with the Disk Cleanup utility.

How to open DMP files in Windows 10?

Now, opening these files isn’t exactly simple as Windows 10 doesn’t offer a built-in tool. There’s a good reason for this as rarely a common user will want to access them in the first place.

However, there are a few third-party utility tools that should enable you to open and read DMP files. They might look outdated, but in this case, we prioritize efficiency over looks.

Expert Tip: Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken. We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.

The first application is WhoCrashed, a dump file analyzer. This tool requires installation, but it’s fairly usable and has all the features you’ll need. You can even simulate the system crash (do this with caution) with certain parameters.

Read more about this topic

The second application is BlueScreenView. An oldtimer that supports every Windows iteration to date. You should have an easy time using it.

It is a portable small-sized application so it doesn’t require installation. Once you get it, just extract it and run the EXE file. However, we’re rushing. Firstly, you need to let the system create the dump files readable by the third-party software.

Bonus: DMP file viewers

As mentioned, Windows keeps tabs on the dump files your system creates and stores them all in a default location. This is generally %SystemRoot%memory.dmp.

Now, you can also find minidump files which are basically small-sized memory dump files that reside in the same location, but under the Minidump folder: %SystemRoot%\Minidump folder.

The latest Windows packages are equipped with debugging tools that often include a DMP file viewer. The most popular ones are WinDbg.exe (the Windows Debugger), KD.exe, CDB, and NTSD and they are also part of the WDK (Windows Driver Kit).

Here’s how to open a DMP file with WinDbg.exe:

If you’re interested in how to delete system error memory dump files in Windows 10, check out this awesome guide. Also, if you want to fix a corrupted memory dump effectively, follow the simple steps from this useful guide.

Yes, deleting these files will have no negative effect on your computer. They are mainly used for debugging purposes. You might want to keep them in case of errors or bugs. They will provide information as to who is responsible for a crash or an error message.

That should do it. In case you have alternative ways to open and read DMP files, make sure to tell us in the comment section below. We’ll be glad to hear from you.

Restoro has been downloaded by 0 readers this month.

How to read the small memory dump file that is created by Windows if a crash occurs

This article describes how to examine a small memory dump file. A small memory dump file can help you determine why your computer crashed.

If you are looking for debug information for Windows 8 or later, please check Debugging Tools for Windows (WinDbg, KD, CDB, NTSD). For more information about small memory dump, please check Small Memory Dump.

Small memory dump files

If your computer crashes, how can you find out what happened, fix the issue and it prevent it from happening again? You may find the small memory dump file useful in this situation. The small memory dump file contains the smallest amount of useful information that could help you identify why your computer crashed. The memory dump file contains the following information:

To create a memory dump file, Windows requires a paging file on the boot volume that is at least 2 megabytes (MB) in size. On computers that are running Microsoft Windows 2000, or a later version of Windows, a new memory dump file is created each time that a computer crash may occur. A history of these files is stored in a folder. If a second problem occurs and if Windows creates a second small memory dump file, Windows preserves the previous file. Windows gives each file a distinct, date-encoded file name. For example, Mini022900-01.dmp is the first memory dump file that was generated on February 29, 2000. Windows keeps a list of all the small memory dump files in the %SystemRoot%\Minidump folder.

The small memory dump file can be useful when hard disk space is limited. However, because of the limited information that is included, errors that were not directly caused by the thread that was running at the time of the problem may not be discovered by an analysis of this file.

Configure the dump type

To configure startup and recovery options to use the small memory dump file, follow these steps.

Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

Click Start, and then click Control Panel.

Double-click System, and then click Advanced system settings.

Click the Advanced tab, and then click Settings under Startup and Recovery.

In the Write debugging information list, click Small memory dump (256k).

To change the folder location for the small memory dump files, type a new path in the Dump File box or in the Small dump directory box, depending on your version of Windows).

Tools to read the small memory dump file

Use the Dump Check Utility (Dumpchk.exe) to read a memory dump file or verify that the file has been created correctly.

The Dump Check Utility does not require access to debugging symbols. Symbol files hold a variety of data which are not actually needed when running the binaries, but which could be very useful in the debugging process.

For more information about how to use Dump Check Utility in Windows NT, Windows 2000, Windows Server 2003 or Windows Server 2008, see Microsoft Knowledge Base article 156280: How to Use Dumpchk.exe to check a memory dump file.

For more information about how to use Dump Check Utility in Windows XP, Windows Vista or Windows 7, see Microsoft Knowledge Base article 315271: How to use Dumpchk.exe to check a Memory Dump file.

Or, you can use the Windows Debugger (WinDbg.exe) tool or the Kernel Debugger (KD.exe) tool to read small memory dump files. WinDbg and KD.exe are included with the latest version of the Debugging Tools for Windows package.

To install the debugging tools, see the Download and Install Debugging Tools for Windows webpage. Select the Typical installation. By default, the installer installs the debugging tools in the following folder:

C:\Program Files\Debugging Tools for Windows

This Web page also provides access to the downloadable symbol packages for Windows. For more information about Windows symbols, see Debugging with Symbols, and the Download Windows Symbol Packages webpage.

For more information about dump file options in Windows, see Overview of memory dump file options for Windows.

Open the dump file

To open the dump file after the installation is complete, follow these steps:

Change to the Debugging Tools for Windows folder. To do this, type the following at the command prompt, and then press ENTER:

To load the dump file into a debugger, type one of the following commands, and then press ENTER:

The following table explains the use of the placeholders that are used in these commands.

Sample commands

You can use the following sample commands to open the dump file. These commands assume the following:

Sample 2. If you prefer the graphical version of the debugger instead of the command-line version, type the following command instead:

Examine the dump file

There are several commands that you can use to gather information in the dump file, including the following commands:

For help with other commands and for complete command syntax, see the debugging tools Help documentation. The debugging tools Help documentation can be found in the following location:

C:\Program Files\Debugging Tools for Windows\Debugger.chm

If you have symbol-related issues, use the Symchk utility to verify that the correct symbols are loaded correctly. For more information about how to use Symchk, see Debugging with Symbols.

Simplify the commands by using a batch file

After you identify the command that you must have to load memory dumps, you can create a batch file to examine a dump file. For example, create a batch file and name it Dump.bat. Save it in the folder where the debugging tools are installed. Type the following text in the batch file:

When you want to examine a dump file, type the following command to pass the dump file path to the batch file:

How to open DMP files in Windows 7, 8.1 or 10? (2018 Update)

DMP files (dump files) are useful for debugging Windows, so you should know how to open and read DMP files in Windows 7 or 8.1 if you want to debug blue screens. It’s very easy to open DMP files, but the difficult part is locating the actual problem and analyzing the DMP file correctly.

In order to open and view DMP files in Windows, you first have to install a driver kit and set the symbol path correctly. This will then allow you to open DMP files using the debugging tool. DMP (dump files) are the most useful files for you to debug your system, so there’s no way around this.

This shouldn’t take longer than 10 minutes, but if you have a slow connection, downloading the 700MB ISO file (debugging tools) might take a while.

1. Download Windows Driver Kit

To open DMP files, you will need the Windows Debugging Tools (additional download). The Debugging Tools are included in the Windows Driver Kit Version 7.1.0. You have to download this

700MB large ISO file from Microsoft first.

2. Install Driver Kit

The Windows 10 setup is called wdksetup.exe, not setup.exe

Important: On Windows 7, select Custom installed and change the location to e.g. C:\Debug\ it will make things easier if you don’t like typing the full path.

On Windows 8, you can change the installation path by choosing the second option: Download the Windows Driver Kit for Windows 8.1 for installation on a separate computer

Don’t know how to open ISO files? Read this: How to open ISO files in Windows 7

3. Open WinDBG

Either go directly to C:\Debug (or wherever you installed the debugging tools to) and click on windbg.exe:

Or open WinDBG via the Start Menu:

Set Symbol File Path

1. Step Create a new folder on your main drive and call it “Symbols”, e.g. C:\Symbols

2. Step Click on “File” – “Symbol File Path …”:

3. Step Insert the following path:

SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols

Replace “C:\Symbols” with your own folder if you created it somewhere else in step 1.

Open DMP file via WinDBG (CTRL+D)

WinDBG still opened? Good, the quickest way to open DMP files now is the shortcut CTRL+D or go to “File” and click on “Open Crash Dump File..”:

Where are DMP files located?

DMP files are located in C:\Windows\Minidump!

You can change the location where they are stored.

Can’t open DMP files? Permission Error!

If you are receiving a permission error like the one below, you have to take ownership of the DMP files first.

Usually, the owner is not even set:

Important: If you still receive the error “you don’t have permission to open this file, contact the system administrator”, copy the DMP file that you want to open and copy it into a subfolder, then it will work.

Let’s analyze the DMP file!

When you’re asked if you want to save the workspace, click yes. WinDBG will now open the DMP file and process it. This will take some time! Have some patience.

Here’s the first Bugcheck Analysis:

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn’t turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002c03000, address which referenced memory

In this case I had some corrupt drivers that attempted to access a IRQL that is too high, so my conclusion was to check my drivers. Now that you know the concrete error (my case: DRIVER_CORRUPTED_EXPOOL), you can also do some research and possibly find people with the same problem.

Driver Verifier Manager / Testing Drivers For System Interrupts

Sidenote: To run the driver verifier enter “verifier” into an elevated command prompt (how to open command prompt), you can then check the settings of currently loaded drivers for example. Keep in mind that this is advanced stuff, so you would have to do some research about it first.

If you like, you can read our detailed guide on finding and fixing system interrupts

I hope that this helped out some of you guys who wanted to open DMP files. Once you get used to reading DMP files, they can be handy for finding and solving problems in Windows 7 and Windows in general.

Oliver SK.

Thank you, very useful indeed. I needed to find an analysis for a series of blue screens on win 7. I have not seen anything so unstable for about 25 years.

Regards,
Andrew
Gotland Sweden

Any help on this would be much welcomed. I find this to be unnecessarily complex and fragile in the setup.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Glebe Health\Desktop70810-19546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e43e50
Debug session time: Thu Jul 8 11:32:21.228 2010 (UTC + 1:00)
System Uptime: 0 days 0:18:59.302
Loading Kernel Symbols
………………………………………………………
……………………………………………………….
…………………………
Loading User Symbols
Loading unloaded module list
……
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Do you have daemon tools or alcohol installed?

If so, you might want to try to uninstall them and see if you still get blue screens. Use this tool to uninstall it: http://www.duplexsecure.com/en/downloads

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump72510-19250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c54e50
Debug session time: Sun Jul 25 11:09:11.624 2010 (UTC + 9:00)
System Uptime: 0 days 0:00:11.732
Loading Kernel Symbols
…………………………………………..
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Probably caused by : hardware

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800652e8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

STACK_TEXT:
fffff880`0337e6f0 fffff800`02cd1a79 : fffffa80`0652e8d0 fffffa80`05521b60 fffff8a0`00000005 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0337ec10 fffff800`02bb35a7 : fffffa80`0652e8d0 fffff800`02c2c5f8 fffffa80`05521b60 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0337ec40 fffff800`02b1bb85 : fffff800`02c8e360 fffffa80`06548828 fffffa80`06548820 fffffa80`05521b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0337ec80 fffff800`02a94861 : fffff880`010f9e00 fffff800`02b1bb60 fffffa80`05521b60 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0337ecb0 fffff800`02d2ca86 : 61e461e4`1f661f66 fffffa80`05521b60 00000000`00000080 fffffa80`05509040 : nt!ExpWorkerThread+0x111
fffff880`0337ed40 fffff800`02a65b06 : fffff880`03186180 fffffa80`05521b60 fffff880`031910c0 26972697`edaeedae : nt!PspSystemThreadStartup+0x5a
fffff880`0337ed80 00000000`00000000 : fffff880`0337f000 fffff880`03379000 fffff880`03f2d540 00000000`00000000 : nt!KxStartSystemThread+0x16

DMP file extension

Table of Contents

We hope you find this page helpful and a valuable resource!

6 extension(s) and 0 alias(es) found in database

✅ Windows Memory Dump

✅ DB/TextWorks Exported Records File

✅ PDP-10 Core Dump

✅ Depiction Element Definition Data

✅ BYOND Dream Maker Map Data

✅ Steam Client Dump Data

Other types of files may also use the .dmp file extension.

According to the searches on our site, these misspellings were the most common in the past year:

Is it possible that the filename extension is misspelled?

We found the following similar file extensions in our database:

When you double-click a file to open it, Windows examines the filename extension. If Windows recognizes the filename extension, it opens the file in the program that is associated with that filename extension. When Windows does not recognize a filename extension, you receive the following message:

Windows cannot open this file:

To open this file, Windows needs to know what program you want to use to open it.

If you don’t know how to set the .dmp file association, check the FAQ.

🔴 Can I change the extension of files?

Changing the filename extension of a file is not a good idea. When you change a file’s extension, you change the way programs on your computer read the file. The problem is, changing the file extension does not change the file format.

If you have helpful information about the .dmp file extension, write to us!