Notices: This section not yet converted to new layout. Download stats are rolling back out.



Package test results are passing.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 1/18/2019.

ProcDump is a command-line utility whose primary purpose is monitoring an application for CPU spikes and generating crash dumps.

Command line usage

procdump [-a] [[-c|-cl CPU usage] [-u] [-s seconds]] [-n exceeds] [-e [1 [-b]] [-f <filter,...>] [-g] [-h] [-l] [-m|-ml commit usage] [-ma | -mp] [-o] [-p|-pl counter threshold] [-r] [-t] [-d <callback DLL>] [-64] <[-w] <process name | service name | PID> [dump file] | -i <dump file> | -u | -x <dump file> <image file> [arguments] >] [-? [ -e]

Avoid outage. Requires -r. If the trigger will cause the target to suspend for a prolonged time due to an exceeded concurrent dump limit, the trigger will be skipped

Treat debug breakpoints as exceptions (otherwise ignore them)

CPU threshold at which to create a dump of the process

CPU threshold below which to create a dump of the process

Invoke the minidump callback routine named MiniDumpCallbackRoutine of the specified DLL

Write a dump when the process encounters an unhandled exception. Include the 1 to create dump on first chance exceptions

Filter the first chance exceptions. Wildcards (*) are supported. To just display the names without dumping, use a blank ("") filter

Run as a native debugger in a managed process (no interop)

Write dump if process has a hung window (does not respond to window messages for at least 5 seconds)

Install ProcDump as the AeDebug postmortem debugger. Only -ma, -mp, -d and -r are supported as additional options

Display the debug logging of the process

Memory commit threshold in MB at which to create a dump

Write a dump file with all process memory. The default dump format only includes thread and handle information

Trigger when memory commit drops below specified MB value

Write a dump file with thread and handle information, and all read/write process memory. To minimize dump size, memory areas larger than 512MB are searched for, and if found, the largest area is excluded. A memory area is the collection of same sized memory allocation areas. The removal of this (cache) memory reduces Exchange and SQL Server dumps by over 90%

Number of dumps to write before exiting

Overwrite an existing dump file

Trigger on the specified performance counter when the threshold is exceeded. Note: to specify a process counter when there are multiple instances of the process running, use the process ID with the following syntax: "\Process(&lt;name&gt;_<pid>)\counter"`

Trigger when performance counter falls below the specified value

Dump using a clone. Concurrent limit is optional (default 1, max 5). CAUTION: a high concurrency value may impact system performance

  • Windows 7, 8 : Uses Reflection. OS doesn't support -e.
  • Windows 8.1+ : Uses PSS. All trigger types are supported.

Consecutive seconds before dump is written (default is 10)

Write a dump when the process terminates

Treat CPU usage relative to a single core (used with -c). As the only option, Uninstalls ProcDump as the postmortem debugger

Wait for the specified process to launch if it's not running

Launch the specified image with optional arguments. If it is a Store Application or Package, ProcDump will start on the next activation (only)

By default ProcDump will capture a 32-bit dump of a 32-bit process when running on 64-bit Windows. This option overrides to create a 64-bit dump. Only use for WOW64 subsystem debugging

Use -? -e to see example command lines

To install ProcDump, run the following command from the command line or from PowerShell:

C:\> choco install procdump

To upgrade ProcDump, run the following command from the command line or from PowerShell:

C:\> choco upgrade procdump


  • tools\chocolateyInstall.ps1 Show
    $packageName = 'procdump'
    $url = ''
    $checksum = '9e089b3f25a85c58f901094e4126412bbef480bd7baef2a9039bdef328bf5baa'
    $checksumType = 'sha256'
    $url64 = "$url"
    $checksum64 = "$checksum"
    $checksumType64 = "checksumType"
    $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    Install-ChocolateyZipPackage -PackageName "$packageName" `
                                 -Url "$url" `
                                 -UnzipLocation "$toolsDir" `
                                 -Url64bit "$url64" `
                                 -Checksum "$checksum" `
                                 -ChecksumType "$checksumType" `
                                 -Checksum64 "$checksum64" `
                                 -ChecksumType64 "$checksumType64"
    Write-Verbose "Accepting license..."
    $regRoot = 'HKCU:\Software\Sysinternals'
    $regPkg = 'ProcDump'
    $regPath = Join-Path $regRoot $regPkg
    if (!(Test-Path $regRoot)) {New-Item -Path "$regRoot"}
    if (!(Test-Path $regPath)) {New-Item -Path "$regRoot" -Name "$regPkg"}
    Set-ItemProperty -Path "$regPath" -Name EulaAccepted -Value 1
    if ((Get-ItemProperty -Path "$regPath").EulaAccepted -ne 1) {
      throw "Failed setting registry value."

Virus Scan Results

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.


This package has no dependencies.

Package Maintainer(s)

Software Author(s)

  • Mark Russinovich


© Mark Russinovich


Release Notes



  • Automatically built and uploaded by dtgm

Version History

Version Downloads Last updated Status
ProcDump 8.00 2263 Friday, April 29, 2016 approved
ProcDump 779 Wednesday, February 10, 2016 approved
ProcDump 7.01 1048 Wednesday, September 17, 2014  
ProcDump 7.0 370 Thursday, May 15, 2014  
ProcDump 6.0 316 Monday, November 18, 2013  
ProcDump 364 Monday, October 8, 2012  

Discussion for the ProcDump Package

Ground rules:

  • This discussion is only about ProcDump and the ProcDump package. If you have feedback for Chocolatey, please contact the google group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or ProcDump, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.

comments powered by Disqus uses cookies to enhance the user experience of the site.