This is a very useful & informative Crash Log display App, that will clearly show all your MSFS CTDs, in a accessible table form.
Very good for seeing recurring patterns, and what has changed from SU to SU etc etc.
Note: Not all MSFS CTD are a direct result of MSFS crashing – some MSFS crashes are caused by other Apps, crashing MSFS.
It is easy to spot those as well with this tool.
Typical LOG Screenshot
Unfortunately, none of these logs will actually tell us why it crashed. That’s a solvable problem, but Asobo hasn’t seemed interested in solving it.
TRUE, if it was that easy, these CTD issues would have been all fixed a long time ago.
But what it does do, is to provide some information on when and why MSFS crashed, and how your own CTD history has changed over developing SU levels.
Note ( at least in my case) A sharp drop off in CTD, with later SUs. Asobo are gradually getting it resolved.
It also show when other Apps, (Mainly Simconnect Apps), are the cause of the MSFS Crash. Its not all Asobo’s coding that may cause MSFS CTD issues !!
Thanks for this, I will see it can shed some light on my very persistent (and apparently unique) CTD issue.
Getting a crash every time I end a flight longer than about 20 minutes and try to return to the main menu. It’s been like this for months and nothing I do makes any difference whatsoever. Very frustrating.
Thanks for this, will grab it.
What Asobo REALLY needs to do is to copy an excellent feature from XPlane - the log file.
Why this has not been done escapes me. Will be so useful for troubleshooting.
why users need a additional tool which do the same as the normal windows event viewer ? 
PS: and to be clear I mean “it do semanticly the same”
Users do not NEED it – but it is a very different Tool to the windows event viewer — I assume you have not looked at it yet, or you would appreciate that 
therefore my “PS” … I noticed that these tool ( which is not mentioned to support win11 ) based on the .wer files, but in generally its exact same info as the windows event log and reliability history of windows. At least what I seen 
..
and again a PS: because I not have a crash-report from MSFS, I’cant deeply check somewhat 
