Processes and virtual memory including session space ( !vm 4).

Hidden (unhandled and handled) exceptions on thread raw stacks.

CLR threads? ( mscorwks or clr modules on stack traces) Yes: use.

Process heap stats and validation ( !heap -s, !heap -s -v).

Your components on the full raw stack of the main application thread.

Your components on the full raw stack of the problem thread.

Process threads ( ~*kv or !uniqstack) for multiple exceptions and blocking functions.

Component timestamps, duplication and paths.

Critical sections ( !cs -s -l -o, !locks) for both crashes and hangs.

Default analysis (!analyze -v or !analyze -v -hang for hangs).

List of loaded and unloaded modules ( lmv or !dlls).

Computer name ( dS srv!srvcomputername or !envvar COMPUTERNAME).

The tool used to save a dump (to flag false positive, incomplete or inconsistent dumps).

Sometimes a simple search immediately points to the fix on a vendor’s site

Google or Microsoft search for suspected components as this could be a known issue.

dmp.I am just copy and paste from my own reference: If you omit the dump file name, it defaults to. To just create a dump of a running process, omit the CPU threshold. Use the -accepteula command line option to automatically accept the Sysinternals license agreement. x Launch the specified image with optional arguments. u Treat CPU usage relative to a single core.

t Write a dump when the process terminates. s Consecutive seconds CPU threshold must be hit before dump is written (default is 10). r Reflect (clone) the process for the dump to minimize the time the process is suspended (Windows 7 and higher only). p Trigger on the specified performance counter when the threshold is exceeded. n Number of dumps to write before exiting. The default dump format includes thread and handle information. ma Write a dump file with all process memory. m Memory commit threshold in MB at which to create a dump of the process. h Write dump if process has a hung window (does not respond to e Write a dump when the process encounters an unhandled exception. c CPU threshold at which to create a dump of the process. This option overrides to create a 64-bit dump.

64 By default Procdump will capture a 32-bit dump of a 32-bit process when running on 64-bit Windows. One such option is to do so when the process terminates (specifically, -t ). It's a handy command line utility that you point to a running instance and specify the circumstances under which you want it to generate a dump file.

Unhandeld exception. save a crash dump