Using ProcDump Quick Guide

Document ID : KB000047299
Last Modified Date : 14/02/2018
Show Technical Document Details


When a Service Desk process is crashing in a Windows Server Environment, you can use the ProcDump utility to monitor that process and generate a full user dump on that process at the next crash occurrence. This document is a Quick Guide for generating a crash dump using ProcDump. There are other tools available for generating crash dumps, but this document is specific for ProcDump.


ProcDump is a command-line utility provided by Microsoft whose primary purpose is monitoring an application for CPU spikes and generating crash dumps from such occurrences. With the dump available an administrator or developer can determine the cause of the spike. 


Service Desk 12.9

Service Desk 14.1


1) First download the ProcDump Utility here:

2) Locate the PID (Process ID) for the process that is crashing.  The best way to do this is to go to the processes tab in task manager on the server where the process is crashing, and get the current PID for the process.

For this document, let´s use domsrvr as an example:


In the domsrvr case, see there are tree processes: (1) domsrvr, (2) domsrvr:wsp and (3) domsrvr:hw. For this specific case, we have to generate a crash dump of the first domsrvr instance. You have to be sure what process exactly you have to generate a crash dump, because depending of the environment, there are a lot of process running for the same binary, but using different command line arguments.

Adding the "Command line" column to the Windows Task manager interface helps you identify what the correct process is.

3) If you are sure what process you need a crash dump and if you have the PID, run the command below:

procdump.exe -e -ma 4988

After running procdump, you will see the output below:


At this time, you have to wait for a crash.

After crashing, you will see the output below:


4) Find the dump file and send it to CA Support:


See the file with .dmp extension.

Additional Information:

If for any reason, Service Desk services were restarted, you need to execute the steps below again. After restarting Service Desk services, PID will be different and you need to attach ProcDump for the new PID.