First crash of the new patch. No ATC interaction, just minding my own business, and no surprises its 0xc0000005.
may be this something relate with too fast memory/ssd when system can not get all cpu instructions? something unbalance in the ipc, something heavy bottleneck too fast system system, i sure is there systems without ctd and very different system, and same situation with ctd systems, i just take ctd as normal and live with it from p3d till now 
i had ctd all the time, and most of them in flight simulators p3d and msfs 2020, and far cry 4, i think this one champion of ctd lol
hardware can not be “too fast” . It can only be instable because of hardware failure, not good envionrment condtions (e.g. heat) or wrong settings (e.g. bios).
Of course the drivers ar also a big point and if they do not a good job with the system integration, issues comes also on top.
In special if you have crash in many different games, it points more to an issue with your system.
PS. of course is windows OS it self a big bug nest
It’s so random now. Since WU6 I have more CTDs after landing, when taxiing to the gate. Addon and default airports. Having finished my flight is good, but not getting the plane to parking and shut it down leaves me behind with a kind of unsatisfied feeling.
too fast unbalance i mean, when something out of range relate other component, so in that situation this broke something when write to ssd, or ram, or between gpu and ram, something, what interface can not handle right, even with all components set to good, this is just part of all possible crashes include causes, what you mention, i just now flight very long time about 1000nm with one landing for refuel, but some time it’s crashes after 20 minutes, so i don’t even talking about my situation, because i have a lot addons, and flight around the world here and there, btw looks like afterburner really can be cause, even if use only for change fans curvature… idk
I will post when every crash happend
Faulting application name: FlightSimulator.exe, version: 1.19.8.0, time stamp: 0x00000000
Faulting module name: VCRUNTIME140.dll, version: 14.29.30133.0, time stamp: 0x60ff28cc
Exception code: 0xc0000005
Fault offset: 0x0000000000001470
Faulting process id: 0x9d0
Faulting application start time: 0x01d7a6df69acef2e
Faulting application path: M:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Report Id: e445008b-5013-4154-8362-c3ecf930b18e
Faulting package full name:
Faulting package-relative application ID:
Just got 2 CTDs. One after 6 hours of flight (yay) and one after 15 min of flight. First was in the TBM and second in the Longitude.
Communityfolder is completely empty and I bought the Aermacci MB 339 on the 8.9. but have done multiple flights since then without an Error (5 flights, arounds 5 hours total). Both errorcodes are: : 0xc0000005. I’m running volanata next to MSFS to track my flights since february. (Never had any issues before, just felt like telling I run one addon).
Regards
I’m getting sick and tired. I had no issues with the Gamepass version (400 flight hours) and Steam version (300 flight hours) until SU5. Since then I get very frequent, but completely random CTDs, most of them are during taxi or take off with the C172. Of course I tried everything, empty community folder, reinstall, delete config files from steam folder, 0 OC on CPU and VGA (I even downclocked the factory OC to NV reference values), disable XMP, reinstall VC++, but no stable result. I even had a new Windows install, when I moved to my NVMe, but that was before SU5.
I upgraded my PC mainly for MSFS: bought a 3070 for good price in December, bought a 1TB NVMe SSD and additional 16GB of RAM in June and I was planning to go for a Ryzen instead of my 9600K this fall, but now I’m thinking about selling my Logitech Yoke+pedals+switch, because I simply can’t use it. Oh and of course my 120€ for the Premium Deluxe goes down the drain.
Please MS & Asobo, at least allow people with CTDs downgrade to a previous version, where we had worse FPS and CPU utilization, but at least it was playable.
I’ve had exactly the same problem since the last update, there are different parts that crash
WwiseLibPCx64P.dll
CoherentGTCore.dll
WTF.dll
FlightSimulator.exe
Faulting module name: unknown
FlightSimulator.exe, version: 1.19.8.0,
but always with the same CTD as a result,
my computer is equipped with Intel i9 9900k and an Asus RTX 3080, 32GIG of RAM,
I have 20 years of experience as a Microsoft technician and am incredibly frustrated by the nonchalance that Asobo seems to show us who put thousands of dollars on this …
In regards to the above post referencing the Windows 10 PAGE FILE, if I have 32GB RAM, what should I put in the INITIAL SIZE (MB) and MAXIMUM SIZE (MB) boxes? I have the Auto manage paging file box un-checked. and CUSTOM SIZE button checked.
I advise you to set to C: “Size Managed by the System”
How big is your C: drive and how much space is left?
Since last World Update I am getting CTDs while entering the main menu after finished flight. It is much better from CTDs occurred during flights, yet I thought that I will report it anyway
Have been lucky up until WU6.
Only ever had ctd with the old camera bug and no ctd’s since then.
Now with WU6, I have had 2 ctd’s in 2 separate flights about 5 minutes and 10 minutes into a flight. Restarting the sim and the flights then went fine.
I have two 2.0TB nVME drives and have MSFS on the C: drive. It has 1.2TB FREE right now. The 2nd D: drive is virtually empty.
I have 32GB DDR5 Corsair RAM as well.
Ok 
perfect so you can leave the parameters on C:
(the more space you have on your disk, the better the virtual memory settings will work) 
After getting constant CTD I kind of had enough. It was reproducible for me, by starting for example at LEMG malaga airport, the game would crash 99% of the time. Also approaches would often CTD for me. I tried multiple things, limiting FPS, different drivers, empty community folder, safe mode, etc. Nothing really helped.
I decided to re-install my whole machine, with a clean windows 10 installation. Just installed video drivers (without geforce experience), downloaded MSFS from the windows store, before running the installer I copied my previous MSFS directory over so I didn’t have to download anything.
And I’ve been flying without CTD the whole weekend… The same community mods, the same CPU overclock, etc. In the meantime I’ve installed a bunch of other software. So far so good. Not sure if this is useful to someone, might be worth trying as a last resort. I’m starting to think for me at least, something was messed up with my windows install.
I have resolved my issues. No CTDs and was able to download all updates with no issues.
Totally shut OFF AVG Antivirus.
Removed and reinstalled all C+++ Redistributable’s.
Opened TASK MANAGER and shut down anything that may possibly conflict with MSFS.
Emoty community folder can now be gradually repopulated one item at a time.
Increased PAGE FILE to 32000.
I hope this helps someone.
Just to share that formatting my SSD where the game was installed (Steam) from ExFAT to NFTS seemes to have solved all my CTD issues. Game was crashing every single time I hit fly. Sometimes also just randomly in the menu.
I also solved my CTDs, after many many unsuccessful tries. I did 2 things yesterday in the evening, but I was too tired to try them:
-uninstalled my latest Nidia driver (471.96) with DDU and installed 471.41 - found this suggestion in one of the CTD threads
-“reinstalled” the US english language in Win10: installed my native language, set it as default, removed US english, added US english again and switched back to it as I prefer all my stuff in English for easier troubleshooting
Today I could fly many hours without any issues in VFR on ultra settings with lens correction, motion blur, etc turned off (I don’t like those effects), I could even put all the stuff back into the community folder (livery megapack, pushback tool, nohandlebar, sceneries). Right now I’m flying KSAN-KSFO for testing high density areas and IFR with ILS approach, performance is stable and everything is fine so far, I just contacted Oakland center, will update later how it ended.
Edit: I could also set my previous UV/OC settings for my VGA and I’m using my XMP profile for my RAMs (4x8GB 3200MHz) and I want to restore my CPU OC settings after this flight as it seems my issues were not related to these.
Edit2: Landed at KSFO, 0 issues.
If you have Capture One installed on your system, check the thread here:
CTD caused by Capture One 20 codec - Bugs & Issues / CTDs - Microsoft Flight Simulator Forums