Finding Train Simulator Crash Dump Files
Posted by DTG Support (Trains) on 16 June 2020 12:33 PM
What is a Crash Dump?
A crash dump is what is created when a computer application's process contents are written to a file. It contains everything that the core process was working on at the time it experienced a problem or special condition that stopped it from processing data in the normal way (called an exception).
Why is a Crash Dump required?
Train Simulator is set up to create a crash dump so that we can analyse what Train Simulator was trying to do when it ran into a problem. This can typically reveal lots of information about the nature of a crash and can sometimes tell us why it happened.
What is in a Crash Dump file?
A crash dump contains only anonymous information about what Train Simulator was attempting to do, in the form of computer code, at the time it experienced a crash. It is essentially a record of the instructions it was performing when it ran into the problem. A crash dump contains only details about what Train Simulator was doing and contains absolutely no information about you, your computer or that can be used to identify you.
Providing a Crash Dump
If you've been asked to provide crash dump files, these are saved to your hard disk when Train Simulator stops responding and displays the Crash Dump error message.
The location of the files is often displayed in the error message provided and you should navigate to the folder advised, and provide the entire contents of the folder.
We will often ask for details relating to your specific computer's configuration that can reveal more about how your computer is set up, called a DxDiag Report, and we may also need a record of the actions that Train Simulator was performing, in the realms of the content it is loading or any scripts it was using, called a LogMate report.
The LogMate report is slightly different to a crash dump as it is often related to objects you interact with in the software, such as a locomotive. A Crash Dump is specifically about programmed functions and the code that determine how Train Simulator works. However, a LogMate Report can often provide hints about what was going on in the core code and, when used in conjunction with the analysis of the crash dump, can tell us exactly what Train Simulator was trying to do when it ran into a problem.
We may also want to see the details of the add-ons installed and whether Steam has correctly installed Train Simulator and something important hasn't been disabled. We can usually get this information from an appmanifest file.