In this situation, we usually recommend that our users download procdump (which can be simply extracted from a zip file, no installation is required) and then we give them a batch file that contains something like this:
mkdir c:\dumps
procdump -e -c 10 -w myprocess.exe c:\dumps
When a process throws an unhandled exception, it will create a dump file in a directory c:\dumpsthat you can load into Visual Studio or Windbg (the command !analyze -vis your friend)
source
share