Description
An app crashes now and then, and by the time you notice, the scene is gone. CPU spikes briefly, then looks normal the moment you open Task Manager. ProcDump takes the opposite approach: set a trigger and it writes a dump file the moment something goes wrong, ready for debugging later.
It is a Sysinternals command-line tool and a single exe is enough. Triggers can be CPU above a threshold for a number of seconds, committed memory over a limit, a hung window, or a specific exception. Or let it launch the target itself with -x so it watches from the first instruction.
Conditional triggers: CPU, commit memory, hung windows and exceptions all work as triggers, so you do not have to sit and watch
Crash capture: saves a dump when the monitored process crashes, with -ma for full memory or -mp for a much smaller minidump
Launch and monitor: start a program with arguments under -x, ideal for problems that only appear during startup
Standard dumps: writes regular .dmp files that open directly in WinDbg or Visual Studio
It is a Sysinternals command-line tool and a single exe is enough. Triggers can be CPU above a threshold for a number of seconds, committed memory over a limit, a hung window, or a specific exception. Or let it launch the target itself with -x so it watches from the first instruction.
Features
Conditional triggers: CPU, commit memory, hung windows and exceptions all work as triggers, so you do not have to sit and watch
Crash capture: saves a dump when the monitored process crashes, with -ma for full memory or -mp for a much smaller minidump
Launch and monitor: start a program with arguments under -x, ideal for problems that only appear during startup
Standard dumps: writes regular .dmp files that open directly in WinDbg or Visual Studio
