5 easy steps for determining EXACTLY what caused your FSX to crash

[pirateinparadise]

1 - Download and install Debugging Tools for Windows. This tool set includes WinDbg and other debuggers. I used the 3rd option to install the only the "debugging tools"
https://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx

2- Add the path tp the Microsoft symbol servers to your environment variables
(control panel -> System -> Advanced System Settings -> 'Advanced' tab -> 'Enviroment Variables' button)

_NT_SYMBOL_PATH=srv*F:/MSDebugSymbols*http://msdl.microsoft.com/download/symbols

( I haven't been able to stop the forum SW from changing the command above to a link - do not click on it). Be sure to replace 'F:\MSDebugSymbols' with the name of a folder that exists on your system. Leave the asterisks in there. '_NT_SYMBOL_PATH' is the variable name

3 - Run WinDbg (x86) - Look in the start menu.

4 - Press Ctrl-D to 'Open Crash Dump'. Browse to your FSX folder, and select the most recent .mdmp file.

5- There is a place to enter commands at the bottom of the screen, just to the right of where it says '0:000>'. Type in !analyze -v
Must be typed exactly like that -> Exclamation point followed by lowercase analyze -v

Ignore any errors about "missing symbols". If Microsoft did not write the software, their servers do not have the symbols. All of your Orbx, ASN, Couatl, GSX, etc. will show up with missing symbols. That is fine.

All the information the developers need to know what was happening when your FSX crashed is in the output. If you open a support ticket, upload the output when you open the ticket. Give the development team a little information to work with.