Interesting, there appears to be quite a number of posts here of CTD’s on approach, I myself have had a number of these as well, but one of the “interesting” observations is that this happens prior to calling ATC message “on approach/final”, has anyone else seen this??
Nah they’ll probably never end. But, what can be done is reduce them in scale. Problem is, the latest update seems to have done the opposite of that.
1 Like
I encountered a reproducible problem on stable FBW A32NX when the route was changed in MCDU (return to departure airport) and CTD occurred at the last point of the route. Development version of A32NX does not have this problem.
Not using in-game ATC myself, these were all VATSIM flights with different aircraft and to different airports. I found a year-old thread about people having CTDs specifically on approach and the workaround for them was to turn on generic plane models. Because, yes, MSFS can apparently bloody crash if it doesn’t like a single livery. It’s that stable.
So in my case I’ve turned off multiplayer, stopped using AIG and only use Offline AI traffic until I figure out what’s going on. But I didn’t expect that some random quick panning in LNM’s map would crash MSFS as well.
For me it mostly happens when there is ATC talk, no matter on final or elsewhere, there seems to be a bug in their audio engine, resulting in a crash.
I just found another bug in my system, SAM - the AMD feature to increase fps using an AMD cpu with GPU in combination. Turning the feature OFF in bios makes the flights much more stable, but with less fps. I hate both now, on and off 
IIRC that “SAM” (Smart Access Memory) thing is also referenced as “Above 4G decoding” along with “re-size BAR support” in various BIOS versions. Both need to be enabled for SAM to work and I think that nowadays MSFS is making use of it to gain some extra performance. It’s a sad thing if some (or many/all) users need to disable it to make MSFS more stable (but run worse).
Mine has been on for ages, but I’ll do some tests with it disabled.
Good day all
I have a strong problem and i wish someone had this problem.
Since last SU7 HF update i have more ctd. I partially reolved them by setting personnal to medium settings.
Less ctd, but during a Flight today i would crank up terrain level and detail and object level of détail and After apply my desktop stop and restart.
I have a 12900k no oc, HT on, ddr4 and 3090 Fe.
Thanks for your help.
My game usually runs very stable. Today I was doing a flight from Amsterdam to Jakarta in the default 747-8. About half an hour into the flight, over Germany, the game crashed. Just a 0xc000005 error and nothing else.
I’m glad it happened so early and not 10 minutes before landing. But I was wondering, is there a reason for this CTD? And is there a way to save the state of the entire flight including all airplane switches?
Hello, this happened today when resizing the Navigraph panel with an approach chart loaded, I won’t be using in-game navigraph. (Flight was between VGHS to VGCB) Live WX and real time, some AI but no live traffic.
Faulting application name: FlightSimulator.exe, version: 1.21.18.0, time stamp: 0x00000000
Faulting module name: CoherentGTCore.dll, version: 0.0.0.0, time stamp: 0x61360811
Exception code: 0xc0000005
Fault offset: 0x000000000044a016
Faulting process id: 0x428
Faulting application start time: 0x01d81590ad0633d6
Faulting application path: C:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\CoherentGTCore.dll
Report Id: 6f71110b-e495-4201-80c8-6e515a008bcb
Faulting package full name:
Faulting package-relative application ID:
Steam version on root C M.2, 5900X, 3080 and 64gb ram, Win10 pro.
Yep! I got a CTD today too. Seems like a server issue as I have done nothing to the game! I hope they fix this issue! They need to know that this is mostly related to their servers and how overloaded the servers have gotten (or how slow they are)! This game is not worth playing with CTDs.
Seems that CTD reports are always on the rise just before a world or sim update.
My theory is they’re changing things on the server side in preparation for the updates or they’re already testing out some of them.
1 Like
Another CTD while taxiing to park in EDDP this time, thankfully towards the end of a 3-hour flight so the crash didn’t matter much. It still fit the pattern of CTDs immediately before/after landing in various airports.
AIG was off as I only had multiplayer, live traffic and VATSIM on. For good measure I removed AIG’s cached data from Community folder after the CTD. Let’s see what happens next time.
Another disappointment was the huge framerate hit as it gradually changed from 60 fps to 40 with lots of stuttering, possibly due to overcast and rain. It doesn’t seem to be directly related to my 6800XT’s performance as loading the airport from scratch with the same weather conditions works a little bit better than 40fps. It’s as if performance is gradually decreasing after X hours of flight.
AMD GPU DRIVERS 22.1.2
After Install of 22.1.2 started experiencing CTD in flight only.
Removed 22.1.2 and re-installed 21.12.1. = No CTD.
( 21.11.2 where stable also )
May be specific to my set up, but if your AMD GPU and suddenly experiencing CTD after 22.1.2, suggest you try this 1st.
1 Like
I’ll give it a go. I keep getting CTDs since version 22 of amd drivers but not sure if its the cause.
Faulting application name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b22bba
Faulting process id: 0x1350
Faulting application start time: 0x01d8187f7b3d1a4f
Faulting application path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 595f4f2c-873d-4f92-86f1-11a460ae8faa
Faulting package full name:
Faulting package-relative application ID:
Hi, I keep getting this error, I can’t even get into a flight lol.
Do you have an antivirus program running?
Hey I fixed my issue it has to do with a setting that reset in the options page within the dev mode for the a320nx been running fine since.
2 Likes
After doing some online searching I see this particular CTD without an error since August 2020.
From EventViewer, people have pointed out the Exception code: 0x0000005 which has indicated a whole range of fixes. Re-install Windows, MSFS2020, don’t overclock and the list goes on.
I have only recently been experiencing this CTD and tried re-installing MSFS2020 as a fix. After doing so, the crashes still occurred, happening between 5 and 20mins.
This is the only game I’m getting this CTD error which tells me it’s something Asobo needs to fix, not us!
A temporary workaround I have found that works is to reduce your FPS to 30.
I use MSI Afterburner (Specifically RivaTuner Statistics Server which is also installed with it) to limit my Framerates to 30.
I tried doing this in game by using the V-sync option and 30fps but it didn’t work.
Once you have MSI Afterburner installed, go to your taskbar right hand side and open up RivaTunerStatisticsServer (Click on the screen with the pink 60)
Once RTSS is open, set your Framerate limit to 30 (See pic below)
Since changing the FPS to 30, I have had MSFS2020 running for 2 hours without a crash.
Note for Nvidia users - I’m using the latest Nvidia drivers (511.65) which along with the previous (511.23) ones caused these CTDs. Others have said using driver 497.29 has helped them resolve this issue.
Hi Ex,
Check out my post below yours. I had exactly the same error message and fixed it by reducing my fps to 30 using MSI Afterburner.
Asobo need to get their act together!