Ensure you remove this key after the dump file has been captured. restart Windows to be sure WER will be using the new 'DumpType' configuration, and then reproduce the issue or wait for the crash to happen again, at which point a full process dump should now be captured by WER and sent to us.ģ. After establishing the 'DumpType' configuration. If the application isn’t 'running as a user' and crashes, then the full process dumps will be written to 'C:\Windows\System32\config\systemprofile\AppData\Local\CrashDumps\', which is the user profile area used by Windows system components.Ģ. So if a normal desktop application like XMetaL crashes, the full process dumps will be written to the 'C:\Users\AppData\Local\CrashDumps\' directory for the interactive user who was logged on. The full process dumps caused by the 'DumpType' configuration are written to a '%LOCALAPPDATA%\CrashDumps' directory, which is relative to the current user profile. Usually, the parameter 'Write debug information' is set to 'Automatic memory dump'. From here, select the System and Security section and then System, then click the Advanced System Settings tab and click Options under Startup and Recovery. This will cause future crashes captured by WER (Windows Error Reporting) to have full process dumps written. The parameter memory dump can be found through the Control Panel. Note: The 'LocalDumps' subkey does not typically exist by default, and must be created in addition to the actual 'DumpType' DWORD value within that subkey.
