Same here! I tried everything to solve my CTD issue with no success…
The following video is me flying with very low settings in AP and all AI off (JFK to Dulles). I was able to see all green stats and 55-60fps avg… and with all that, it still crashes with no error. I haven’t been able to complete a successful flight.
https://video.nest.com/clip/de04cf415b7448f0a693a4cc1220f66f.mp4
Im running out of faith.
Do you have some CPU performance data that indicates that CPU0 is causing a problem? Tweaking CPU affinity or process priority is messing with the Windows core process scheduler and to some extent CPU hardware architecture.
Are you flying the same flight or a different flight after the CTD? And if you fly the same flight, does the CTD happen at the same place? Or is it all random?
I am doing the same flight every time while I keep testing… It happens Random… Sometimes 10 minutes after departure, so times mid flight… And just 5 minutes ago, while I was about to land… Very frustrating…
I have been having these crashes for a while now and finally solved for myself.
ATTENTION to the liveries you install. They are often applied to AI planes too and this crashes the game. Once I removed some liveries that weren’t compatible I solved everything.
Step Number ONE before Reporting a Issue: remove mods 
therefore I asked … in special for windows “older” ( or also in general ) sound drivers can be a pain and in special also realtek. If you only use usb sound, then you can also disable the onboard sound in bios.
may also be connected with this issue:
Origin Airport causes CTD
specs
msi m250b mb
i7 7700k
gtx msi 1060 6gb
kinston ram 32
samsung 870 1tb ssd
win update 20h2
after i upgraded ram 16 to 32 started crashing mins in to flight,turning on XMP in bios worked for me no ctd for 4 weeks now.
fps 15 to 20 , uninstalled nivida drivers complete then rebooted pc windows installed previous drivers
now installed newest nivida driver 560
did NOT install nivida EXPERIENCE and did NOT change anything in control panel.
just finnished flight over New York 900 feet over city and over the alps flying just over the peeks in cj4
at 31 to 35 fps.
just my journey in MSFS , hope someone can use this info if using nivida .
cant remember where on this site i found this tip but it worked for me and thats with 20h2.
graphic setting med. clouds ultra, might be sweet spot for this system.
still the same issue for me aswell, either with or without mods, third reinstall still on a m.2 pcie SSD, Win10 up to date aswell as the Mainboard and graphics driver.
I see the devs and CEO of MIcrosoft/Asobo sitting there in their next Q&A saying: “oh no really? Never heard of that problem, but we’ll look into it…”
2000 posts later stil the same issue.
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, timestamp: 0x5fc94fca
Faulting module name: CoherentUIGT.dll, version: 0.0.0.0, timestamp: 0x5f7613c5
Exception code: 0xc0000005
Error offset: 0x000000000013f4e7
Faulting process id: 0x2110
Faulting application start time: 0x01d6d3bf1919e911
Faulting application path: C: \ Program Files \ WindowsApps \ Microsoft.FlightSimulator_1.11.7.0_x64__8wekyb3d8bbwe \ FlightSimulator.exe
Faulting module path: C: \ Program Files \ WindowsApps \ Microsoft.FlightSimulator_1.11.7.0_x64__8wekyb3d8bbwe \ CoherentUIGT.dll
Report identifier: ebfc772b-e1c2-4eb0-8fc6-92445242a898
Full name of the faulty package: Microsoft.FlightSimulator_1.11.7.0_x64__8wekyb3d8bbwe
Application ID relative to the failed package: App
Have been having many CTD events since the latest patch. Decided to try your suggestion : 1) Selected affinity and unchecked CPU0 and 2) Turned off Real Time Protection in Windows Defender. Flew from Boeing Field (KBFI) in Seattle to Tri-Cities (KPSC). Periodically saved the flight because I anticipated that it would CTD. However the flight went perfectly! I do not understand why it worked, and if both CPU0 needs to be unchecked and Real Time Protection needs to be off, but this is very encouraging. Thank you charlieqt888.
I have been having varying degrees of CTD , even after the AI Plane number limiting fix.
Tried various Version of Nvida Drivers, and saw no concrete pattern.
So yesterday, I complete uninstalled and remove all traces of Nvida, and then did a clean install of 460.89
Been rock stable ever since, no CTD, and although it is probably a Placebo effect, I am sure the graphics look considerably better, and I am sitting at a point where its alternates back and forth between CPU & GPU limiting.
At this point – If it ain’t broke, don’t fix / tweek it !!
Changing three things at the same time makes it impossible to determine what really stopped the CTDs. Reset everything back and fly again to see if the CTDs return. If so, make one and only one change and retest. If there are no CTDs, then stop. Otherwise make the next change and retest. And then make the 3rd change. And saving the flight during the flight is a change if you don’t normally do that.
After I was able to get the client stable enough to complete the new download, it appears to be pretty stable. With the completely fresh install I let a flight run for over an hour and it ran just fine with High graphics. I’m going to test it out a little more and then see if I can start adding mods without running into issues.
Since release I’m stuck with the ucrtbase.dll error. The only change has been after a patch a couple of weeks ago: now 5 identical error messages pop up before the crash, instead a straight CTD. Recently, support suggested I should reinstall windows. Well, since I need my computer for work and everything else runs fine, I gave up and just deleted FS for now. That being said, I’d be curious if anybody with this particular problem did a reinstall and got it resolved.
Glad to hear of your success, however let me remind you of the first rule of troubleshooting.
Change ONE thing and test.
If you can keep it stable without messing with affinity I strongly suggest you do as this could cause other issues. I expect the real time process blocker has more to do with it that anything.
Can’t hurt to try anyway.
I have never been a fan of UPDATING drivers. It seems there are always bits left behind that cause no end issues somewhere down the road. I try to make a point of always uninstalling the old driver first. Once in a while I’ll go thru and do a clean up, especially when I notice extended boot times or instability. One of the cleanups I will do is make sure no unused drivers are residing in the system.
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
What the above command does is force all the non-present or old and invisible drivers to show up in the Device Manager list. Once you have done this, you can proceed with the uninstallation.
The good thing about this feature is that all the old drivers are faded out, so you can easily identify the old or non-present drivers from current drivers.
no.. we already determined that possible the order of driver installing, whether you made restarts, etc.
seems to have an effect.
Also, if we speak about Deinstalling the nvidia drivers, the users should choose “completely driver reset” so that older configuration files also removed. In another thread it comes on top that lots of users made own nvidia control panel settings, which are NOT the nvidia defaults and which then causing lot of trouble. The complet reset ensure, that you work without any kind of manual “self tweaking” settings
Also lots of users re-installing drivers without an window restart. I highly recommend to made restart after deinstall and after new-install.
I used DDU .. seems to have done a good job …
another recommendation: use official installer 
no, real.. I not know what this Guru3D Driver installs, deinstalls, removes, what ever do…
Important to mention was just, that a compleltly Deinstall is necessary.. with all former created config-files, etc. … If these DDU correct do , then you can of course use that tool 