Defrag Tools: #10 - ProcDump - Triggers

In this 3 part episode of Defrag Tools, Andrew Richards and Larry Larsen walk you through Sysinternals ProcDump. ProcDump allows you to capture the memory of a process running on the computer. The dump file can be of varying size and can be taken with varying outage durations. Dumps can be triggered immediately or can be triggered by a variety of events including CPU utilization, Memory utilization, a Performance Counter, a Hung Window and/or Native/Managed exceptions.
Part 1 covers what the tool captures and the outage durations that can be expected.
Part 2 goes through the wide variety of triggering options; in particular 1st and 2nd chance exceptions.
Part 3 (this week) goes through Windows 8 Modern Application support and Process Monitor logging support.
Resources:
Sysinternals ProcDump
Timeline:
[00:00] - Overview of Windows 8 Modern Applications
[01:09] - ProcDump v5.0 vs. PLMDebug
[01:38] - Registry - Package and Application Names (AppUserModeId)
[02:00] - Activation and Monitoring (-x <folder> <appusermodeid>)
[04:42] - User created ProcDump
[05:21] - Registry changes - DebugInformation
[05:40] - PLM created ProcDump
[06:53] - Process Monitor - Debug Output Profile events
[09:50] - PLM behaviour for Attach vs. Launch
[11:17] - And that's it for ProcDump!
[Update: 2012-10-26: This is fixed in ProcDump v5.1]
Due to a bug in ProcDump v5.0, when using -x <folder> <appusermodeid>, some applications get "RPC server not available" exceptions and then fail. The workaround is to debug the package (not the app) and manually activate the application.
e.g.
procdump.exe -ma -e 1 -f "" -x c:\dumps <packagename>
You guys forgot to update the Part 1 and Part 2 notes with links to Part 3 (the "Part 3" text below Part 1 and Part 2 links).
Procdump 5.1 is now finally online:
@MagicAndre1981: Took a long time but we finally made it. Thanks for your patience everyone.