DMP File

[LJay24]

I found some files in crashdumps on games that randomly crash and I'd like to know why. Can anyone help me in opening the dmp files?

[Omega]

A .dmp file is a memory dump file. The game devs can use it to see what made the game crash. I don't think there is any way for you to open the file in a readable form.

[mtono]

u can just open it with notepad...if u can read anything well, u can see sth.
not to know better...the only way to see, if you cant open afile...in windows.

[LJay24]

the exploited님이 먼저 게시:

u can just open it with notepad...if u can read anything well, u can see sth.
not to know better...the only way to see, if you cant open afile...in windows.

Anything notepad can't open just crashes, so it's most likely that it can't read it.

[Omega]

LJay24님이 먼저 게시:

the exploited님이 먼저 게시:

u can just open it with notepad...if u can read anything well, u can see sth.
not to know better...the only way to see, if you cant open afile...in windows.

Anything notepad can't open just crashes, so it's most likely that it can't read it.

Notepad can open anything.

[LJay24]

Omega님이 먼저 게시:

LJay24님이 먼저 게시:

Anything notepad can't open just crashes, so it's most likely that it can't read it.

Notepad can open anything.

Why does it crash though?

[RGX12]

In a post like this, you need to at least be bothered to state which OS you're using. There are also different size dump files which a Windows system can output (essentially, it breaks down as small, medium, and large), which can be changed by the user. But in general you have at least 3 options, assuming your system is outputting "mini"-dumps (which is the default):

1) The "standard" procedure is to use the Microsoft debugger, WinDBG, to interpret the memory dump and find the root cause of the crashing. But this requires a bit of technical knowledge and would require a lot of effort to explain, so I found this for you:
- https://www.techrepublic.com/blog/windows-and-office/how-do-i-use-windbg-debugger-to-troubleshoot-a-blue-screen-of-death/

2) A much easier, but somewhat less conclusive, troubleshooting method is to use the very good free utility program "BlueScreenView" to examine the dump file and see the stop condition code and which drivers were "on the stack" (in memory) at the time of the crash. The one at the top is usually the culprit, and the program will show you this. This utility is often the first one I turn to.
- http://www.nirsoft.net/utils/blue_screen_view.html

3) If you don't understand the results, or the first 2 choices prove inconclusive, you can get expert help in the Windows forums. TenForums.com (assuming you have Win 10) has an ongoing BSOD troubleshooting thread where you can have people figure out the cause for you, by uploading the output of specific tools they mention. Search for it. EightForums.com and SevenForums.com have similar help threads for Win 8/8.1 and Win 7 users respectively).

[Bad 💀 Motha]

Notepad does have limits though. If something like a DMP file is very large in overall file size, something like Notepad generally will fail to open it.

Try Notepad++ https://notepad-plus-plus.org
Which is much better and actually supports various formatting styles and such too.