

Stack and backing store memory written to the minidump file should be filtered to remove all but the pointer values necessary to reconstruct a stack trace. Include high-level information about the OS handles that are active when the minidump is created Include all accessible memory in the process. This results in the inclusion of global variables which can make the minidump significantly larger Include the data sections from all loaded modules. Include only the information necessary to capture stack traces for all existing threads in a process If you want to specify multiple dump types, you would need to set the corresponding bit in the DWORD value: Each dump type represents 1 bit of the 32-bit DWORD value. The table below shows the different dump types that you can specify for theĭWORD value.

This value is used when DumpType=0Īs indicated above, you can get very granular with the type of dump file to create. Type of dump to create (see the table below for the different dump types)Ĭustom dump options to be used. Maximum number of dump files to store in the folder HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps

By default, this feature is not enabled - an administrator needs to turn it on by modifying the registry values in
#MICROSOFT ERROR REPORTING VD650 FULL#
Starting with Windows Server 2008 and Windows Vista SP1, Windows Error Reporting (WER) can be configured to collect full user-mode dump files and store them locally after a user-mode application crashes. On the menu today - Windows Error Reporting. only twenty-two more days to go till Launch Day. First published on TECHNET on Feb 05, 2008ĭay Five.
