Frequently Asked Questions
Frequently Asked Questions
Creating a crash dump from a specific process (ProcDump)
Posted by Rami Taipale (M-Files) on 21 February 2019 03:08 PM

If there is a need to figure out why a certain program or a process crashes, you can use a utility called ProcDump. It is a command line debugger tool, which will dump the in-memory contents of the process of an application into a .dmp (dump) file. Dumps will contain the call stacks, registers and data of the application at the time the dump is taken. It is like a point-in-time snapshot of an application. You can also create a dump file with Task Manager, but it's not the most optimal tool in a crash situation.

More information about ProcDump with the download link can be found here:

Runs on:

  • Client: Windows Vista and higher.
  • Server: Windows Server 2008 and higher.


Download the app, open an elevated Command Prompt (as an Administrator), start ProcDump with the following parameters and repeat the problematic actions until the process crashes:
procdump -ma -e -w processname.exe
This will (try to) catch the crash event and generate a dump file with all process memory. The ProcDump process remains running until the crash happens or the monitored process exits normally.


When you have problems with e.g. Excel crashing, enter the following command in an elevated Command Prompt in the directory where the ProcDump.exe has been extracted:
procdump -ma -e -w excel.exe
Wait for Excel image
Open Excel and use it in a way it will most probably crash. If the crash happens, a crash dump should be generated in the same directory with the ProcDump.exe. If Excel does not crash, close Excel normally and enter the command again next time you are planning to generate the crash dump.
The dump file size could be quite large and you should get separate instructions on how to deliver it to the M-Files Technical Support.
(3 vote(s))
This article was helpful
This article was not helpful

Help Desk Software by Kayako case