I've reached the end of my tether with the SU5 CTDs. I've tried everything I can think of, including a full reinstall. I've stripped out all of my addons from the community folder, marketplace purchases and even the MS/Asobo content updates. The straw that broke the camel's back for me was encountering repeated CTDs while trying to install the World Updates from the content manager into my fresh new installation of version 1.18.14.0.

If the software is too unstable to download and install its own updates, I'm not wasting any more of my time trying to get it to work. It runs the Just Flight Warrior on a clean installation, and even seems to handle a pre-SU5 freeware addon airport, but I've had enough of random CTDs and unlogged freezes. This is a game, I want to play it to have fun. Not to fire it up wondering if it's going to dump me back to my desktop just when I've settled into a flight.

Windows Event Viewer captures the CTDs, surprisingly, and all of them cite exception code 0xc0000005 and fault offset 0x000000000180bda9. The 005 exception seems to be a memory access violation, I can't tell from a quick search what the bda9 offset means.

For you lucky people whose MSFS SU5 installs are stable and playable, enjoy yourselves. I'll probably come back if there's a proper hotfix in the next couple of weeks or if SU6 gets us back to SU4 levels of stability. Until then I'm going to see what DCS is all about.

0xc0000005 is caused by RAM. Try disabling the XMP profile or increase RAM voltage in BIOS.

MSFS is very sensitive to minimal instability and even if other games run just fine, it can crash.

I never had CTD with SU5 except when I used FBW A32NX (which was then removed from the marketplace due to its incompatibility).

If you want to perform a full check, please follow this guide: 

 

I get CTD every time I try to install or uninstall from content manager.