The most difficult technical cases may require the acquisition of Full Dump Type crash dumps; these are logs generated by your system when an application crashes (un)expectedly, and may prove to be a challenging task to go through.
Before continuing, please keep in mind that editing wrong registry keys can cause unintended effects, and caution is advised. The procedure below is safe to follow.
- From Start, search for RegEdit
- From the folder tree found on the left side of the window, navigate to the following path:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps
- Right click on the LocalDumps folder, press New, and create the following keys:
- -> Expandable String Value, named DumpFolder
- Give it the value of %LOCALAPPDATA%\CrashDumps
- -> DWORD (32-bit) Value, named DumpCount
- Give it a value of 10
- -> DWORD (32-bit) Value, named DumpType
- Give it a value of 2
- To give the key a value, simply click on it's name from the list found on the right side of the window.
Once this is done, future unexpected crashes will logged on the following path:
This path can quickly be accessed by searching for %LOCALAPPDATA% in the Start menu. As the files generated on a Full Dump Type will be above the maximum upload limit on ticket attachments, it is suggested to use a cloud file sharing service such as Google Drive.
To learn more about full type Crash Dumps, you can check out this article.