Sure, when I get home I will post a full list.
I’m sure you’ve tried without any addons as well. The list I have will have been the same for most of this year. The only things that I have added would be the A2A Comanche, and the BBS Short. Things updated would probably only be Navigraph data I think.
MSFS without some Necessary Addons is not worth Launching 
Totally agree. Technically I could fly without addon planes, and scenery, but I couldn’t do without SPAD as it drives my hardware. If for whatever reason Asobo designed MSFS to block access from SPAD I’d go back to X-Plane. 
the guys who test Beta reported that they do not have CTD’s anymore (of this kind)…
the thing is: we have NO idea what triggers and what causes…
I have these CTD’s with similar error code and characteristics since March.
Believe me, I tried everything suggested.
the thing is also: you can run the sim without a CTD for 5-6 days and you THINK you found the issue and then BAAAM it comes again.
so - what do I hope? I hope that - like all the other issues since 2020 I was facing - it gets sorted out either by an update, by a community tip or a workaround.
Probably you are right. Im on beta and i dont have CTD so far. But who knows maybe they will return 
Last time i always have CTD on touchdown (example Geneve, Asobo Frankfurt, Zurich etc.) Only thing i do is GSX disabled jetways and services. Tested yesterday 3h flight no CTD. Im really hope this tweak with GSX fixed my CTD or maybe is placebo or is SU14 
hwho knows Tested with my favorite Fenix, and also with A310 and PMDG 738. My essential addons (fs realistic, GSX pro, volanta, Navigraph)
GSX (all versions) NEW: Added a new optional setting in the %APPDATA%\Virtuali\Couatladdons.INI file to disable GSX while cruising higher 10000 feet/faster than 250 kts, to prevent possible crashes due to problems receiving Navdata. To enable it, add disable_in_cruise=1 in the [GSX] section
What is needed is a Debug Console option to keep a trace, and produce a log when the CTD occurs, that will contain the trace BACK to where the CAUSE of the CTD occured … typically from bad code or bad data.
If the CTD is then found to be being cause by an addon, that addon should be identified, and then the User will have the option to take whatever measures they want - (or can) – – ie: either do not us the Addon, or corresponding with the addon developer.
What is not working, is the user having no idea what may be cause the CTD, and Asobo stating in Release notes that “Various CTD issue were fixed”, without any explanation or details as to what those CTD issue were.
We are automatically sending Crash reports to Asobo – the least they could do in return, is to tell us what, in some detail, they have claimed to have fixed.
It should be a 2 way exchange of information - (or maybe no exchange at all)
This is the list of my current Community addons:
a2a-aircraft-pa24
antsairplanes-tiger-moth_1.1.0
atsimulations-aircraft-piaggio_2.15
bagolu-c152-neoflybannertow
bigradials-goose_1.09
bksq-aircraft-analogbaron
bksq-aircraft-analogbonanza
bksq-aircraft-analogcaravan_0.1.4a
bksq-aircraft-analogkingair
blackbox-shorts-regional
blackboxsimulation-bn2-islander
flysimware-cessna-414aw_4.4.1
gotgravel-savage-grravel_2.1.2
justflight-aircraft-pa28-arrow-iii
justflight-aircraft-pa28-turboarrow
justflight-aircraft-pa28-warrior-ii
ke79-airport-ke79-sierra-sky-park-airport_V2.1
navigraph-navdata
navigraph-navdata-base
neofly-neofly-objects
neofly-neofly-smokes
orbx-aircraft-pac750_1.1.0
pmdg-aircraft-dc6
spad-bridge-module
sws-aircraft-kodiak-wheels
vbcorp-airport-ut25-monument-valley
wbsim-aircraft-c172sp-classic_1.0.6
ZZZ JD - Clean Glass Mod 1.33.3
z_750XSTOL_fm_mod
z_blackbox-shorts-regional_mod
z_BS_A36_fm_mod
z_BS_Baron_fm_mod
z_jf_warrior_fm_mod
Thanks … I notice: NO Carenado addon MS-Market planes
Do you run LNM at the same time as MSFS, and if so, have you determined if LNM can cause CTDs ?
Ah, those are only Community addons, no MS-Market items at all.
I do have some Carenado planes installed.
carenado-aircraft-c182rg
carenado-aircraft-ct182t-skylane-g1000
carenado-aircraft-m20r-ovation
carenado-aircraft-pa44-seminole
I’ve had plenty of crashes while tracking flights in LNM. On one occasion, after having a near three hour flight, at the very end, our last stop, I decided to turn on the flight tracking. I had a hunch it was a possible cause, and I forget the reason why I turned it on in the first place.
Knowing all this, I forgot to turn it off again. Within 5 minutes the sim crashed. I’m now very careful what I allow to communicate via Simconnect, and right now I excluded flight tracking.
That said, I did go through a period of using Volanta, and I don’t remember any crashes during that period.
All of those crashes matched this error code.
I can not fly from Sofia to Vienna 
it is so funny, I have to post it. I can not finish my tour.
I tried the PC12, the Hondajet, the Malibu.
Somewhere near the boarder for Bulgaria to Serbia I get our common CTD
Either at FL260 or 430 … or chose one.
I tried manual import of the flightplan, simbrief and msfs flightplan … I tried also to change sceneries below my flight route, deactivated all of them … nope.
CTD every time. Meanwhile I did dly some heli in Innsbruck, all add-ons turned on. no CTD - it is a really funny bug.
It could be a scenery cache issue, so try clearing or disabling that.
It could also be a autogen issue. Change the autogen quality to Low.
Also, please post the exact location this happens. You can use LNM to track your flight, and when it crashes again it will indicate the location.
Or if you know the closest GPS fix that would work too.
I admire your persistence
always caused issues, caching is always OFF for me
autogen issues at FL430?
Latitude=43.598406
Longitude=22.245893
Altitude=11308.668594
Latitude=43.917533
Longitude=22.384626
Altitude=12309.331634
Latitude=43.856318
Longitude=22.46824
Altitude=12173.402725
Latitude=43.143871
Longitude=23.327235
Altitude=7628.996734
Autogen can get generated to some degree at altitude, but it’s more about the data being loaded, rather than how it is presented. There was an issue a few years back where a very similar issue was observed, but there were specific pointers in the crash report that led to the Blackshark AI being the possible cause, which led to the discovery that turning autogen down to Low or Medium stopped the crashes.
I’ll try to fly to these areas over the weekend to see what happens.
I’ve built a flight plan for it, over what looks like some interesting scenery.
LBSF N0100A075 4309N02320E 4336N02215E 4351N02228E 4355N02223E LYBE
after 3 successful flights another crash…
flight ctd at cruise/fl360
KMCO RDSOX1 JFRYS DCT PATOY Q116 VLKNN DCT GETME J151 STL DCT IOW DCT MNOSO BLUEM4 KMSP
Fault bucket 1560424989613081798, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 1546319973224916426
Problem signature:
P1: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.34.16.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.34.16.0
P7: 00000000
P8: c0000005
P9: 00000000023f9441
P10:
*When a “instruction at referenced memory could not be read” error is clearly the result of a buggy piece of software, there may be only one course of action that will work – contacting the developers. *
*Bugs happen and if the game or software package is constantly crashing with this error, it might not be something that you can do anything about. So pop an email to customer support, hit up the official forums and get some advice on whether you’re missing something obvious or if it really is a glitch in the Matrix
tried to get info on this but after dealing with ctd’s for over a month and doing various troubleshooting i do suspect it is a msfs2020 issue.
well I did not think that you will monitor my problem thanks - no matter what will happen - delightful
well kick me, but I succeeded this time … after 7 attempts or so. this time I was flying with the VisionJet… same route, same add-ons activated … it would be so funny if it would not happen to me
moreover - I had to leave my home and the sim was running 5 hours in the main menu and when I came back I proceeded …
Hi,
and I just had a CTD while launching MSFS in Safe Mode. 
I flew the route this morning, at between 5500, and 6500 feet, with no issues.
CTD after selecting departure airport (kmco). was going to try and fly my flight again that ctd yesterday…the sim had other ideas.
Fault bucket 1560424989613081798, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.34.16.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.34.16.0
P7: 00000000
P8: c0000005
P9: 00000000023f9441
P10:
ok second attempt today:
loaded into different airport (kiah) successful all the way through ready to fly.
exited out to reattempt flight out of (kmco). successful through ready to fly. sat at gate for appx 35 min. taxi out good until I changed camera view to external and then freeze and CTD!!! so frustrating.
wish we would get some feedback here on what the devs could be working on or what they think the issue is.
trying my best to troubleshoot but it’s trying my patience, and this is no longer fun.
Fault bucket 1321017739356568306, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.34.16.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.34.16.0
P7: 00000000
P8: c0000005
P9: 0000000002405f75
P10:
