ProcDump is a command-line utility used to capture unhandled exceptions and unexpected crashes or failures. Based on the conditions you specify, ProcDump generates a dump file for a process, which our Technical Support team can use to identify the cause of an issue on your system.
Procedure
- Download ProcDump.
-
Extract the ProcDump.exe file and save it to your computer.
NOTE: If the folder exists on your system, it is a best practice to save the file to C:\Program Files (x86)\Windows Debugging Tools.
- Ensure that the process you want to dump is running.
-
If the process is running multiple times, do the following:
- Open Windows Task Manager click More details, and select the Details tab.
- Note the process ID (PID) of each repeated instance of the process.
-
Run Command Prompt as an administrator and use the
cd
command to navigate to where you saved ProcDumpe.exe. -
Generate a dump by modifying the following command line as needed:
ProcDump.exe -ma [Process Name] [Destination Folder]
NOTE: To make sure you get a full memory dump, always include-ma
in your ProcDump command.- To generate a dump immediately, enter the command as is. For example:
ProcDump.exe -ma GenetecDirectory.exe C:\Dumps
- To generate a dump for multiple instances of a process, replace
[ProcessName]
with one of the PIDs you noted, and repeat for each instance. For example:ProcDump.exe -ma 9192 C:\Dumps
- To generate a dump for a process that has a hung (unresponsive) window, add
-h
to your command line. For example:ProcDump.exe -ma -h GenetecDirectory.exe C:\Dumps
- To queue a dump to be generated when the process crashes or fails, add
-e
to your command line. For example:ProcDump.exe -ma -e GenetecDirectory.exe C:\Dumps
IMPORTANT: While the process is still running, do not close Command Prompt. Only close Command Prompt once the dump has been generated. - To generate a dump immediately, enter the command as is. For example:
-
When the dump is finished, retrieve copies of the following 32-bit files from
C:\Windows\Microsoft.NET\Framework\v4.0.XXX on the target
machine:
- sos.dll
- clr.dll
- mscordackws.dll
- Mscordbi.dll
- Retrieve the 64-bit versions of the same files from step 8 from C:\Windows\Microsoft.NET\Framework64\v4.0.XXX.
- Collect the dump files, the 32-bit .dll files, and the 64-bit .dll files, and send them to Technical Support.