must have jinxed it, another CTD literally happened 2 minutes after me saying the CTDs were gone… first one in over 20hrs of flight tho. It happened when i clicked on my navigraph chart, AMD display driver error, not sure if related to FS2020…
Each attempt to create a flight with G36 at LOWL (Linz, Austria) ends in a CTD close to the end of the loading process. This is fun pure !!! Twice full download and installation of the software did not change anything.
But, same flight configuration worked earlier without ANY CTD.
Saved training flights load successfully. Trying most advises of the forum regarding settings did not help.
But I detected the following:
- Taking the default C152 at LOWL … flight loads successfully
- Shut down the flight and take G36 at LOWL and “Tataaah” the flight loads suddenly sucscessfully.
I have done this procedure more then 10 times and it worked to 100% !!!
Who has an explanation for this strange behaviour ?
What need I to do that any of the specialists looks at this ?
Bruno
Back to MSFS after 3+ weeks, nothing’s changed.
- New BIOS installed, check.
- New AMD chipset drivers installed, check.
- New 6800XT drivers installed, check.
- All Windows and MS Store updates installed, check.
- SU4 installed without any issues, check.
- All in-game content updates installed, check.
- Community folder emptied and rolling cache deleted, check.
- Latest VC runtime libraries 14.29.30037 installed, check.
- Frequent and repeated CTDs due to GPU driver timeout when loading main menu, check.
- Frequent CTDs when finishing a flight and returning back to the main menu, check.
- CTDs within 2 minutes when attempting to start up A5 Icon (replicated twice), check.
- No CTDs or any other issues at all when flying C152 500’ over London, check (as expected).
I guess I’ll stick to C152/172 and Piper Arrow, as these never CTD for whatever reason.
4000 comments into this thread and 1034 votes later, the issues are still here. So much for fixing CTDs “asap”.
4 Likes
New to MSFS after thousand hours in FSX, new computer, playing through gamepass but planned to buy premium soon.
CTD everytime i want to take off or approching a big city, (like KFJK, KLAX, Paris, etc etc)
Fly from Edwards to KLAX, CTD everytime ~10nm from KLAX for exemple
Tried everything in the CTD support topic, new install here, everything up to date, computer way above recommended config and no problem with any other recent game.
Traffic / IA / Multiplayer / Weather clear or storm => Crash
Community folder empty or not => Crash
Cache clear or not => Crash
Nothing else running on my computer or many programs running => Crash
Multiscreen or not => Crash
Night or day => Crash
Graphics low or ultra => Crash
The only strange thing i notice is : when i have a Twitch / YouTube stream running (it’s not always the case, i tried without obviously), google Chrome crash at the same time as MSFS does.
So for now, game is just unplayable near big cities, i’ll stick to my countryard and i’ll wait to buy premium edition, 120€ for not being able to flight liners between big cities is unacceptable.
And awaiting for a fix, if someone have an idea, i take it with pleasure.
AMD, Intel or Nvidia?
try these:
- Set Priority Below normal / Low (in task manager)
- Turn off rolling cache
- Try in different screen mode (Fullscreen/Windowed)
- Set your windows language to English
- Turn off photogrammetry
- Run as administrator
- use different joystick
- always keep your GPU below 70°
i also got CTD before, but with some of these tips, i can extend my play time up to 6 hour before CTD happen again
I assume you tested each of those individually, and therefore know exactly which one fixed your CTD’s?
1 Like
the first 3 is the one that caused early CTD (like below 30 minutes of flight)
and the other just some minor problem that sometime caused CTD to me
1 Like
It’s weird how it affects systems differently.
I’ve never had to do any of that, although my OS language was always English. My issues stemmed from the airways messaging in the 530 & 750 addons. With those turned off I get no more crashes.
Although I have found another source that I know how to avoid, for the most part. Supposedly fixed, but I don’t think it is, at least completely.
I had a crash for the first time in over a month, weeks back, and it was because I was on a livestream where almost everyone was flying a default plane that had been modified. It was the 152 Backcountry addon by “sjfly2”.
Oddly it didn’t hit me immediately, but after a few legs, and we had all landed. As I taxied over to the group I crashed.
I then downloaded the addon, and selected that plane to fly, and I was able to fly the rest of the 2+ hour session after without issues.
A similar thing happened the other day, Friday I think, where we were doing some bushflying. Most everyone was in a cub of some kind, typically the Savage Grravel, or Carbon. I had disabled all those planes in the addon linker software, so I only had the default planes.
Again, as I spawned in I crashed. I realised what might have happened so I re-linked all of tthe addon planes I had.
This time I could spawn in and we flew for a few hours without any issues.
I suspect the issue here is the variant of the plane you have, but the livery you don’t issue.
I had the 152, and the Savage Cub planes, but I did not have their custom liveries for the modified versions of those two planes installed. Add them, and the problem goes away.
In that last example I wasn’t even flying those planes, I was in the BN2 Islander, but I had the files accessible to display those that did have those planes, and I could see their custom liveries.
This makes live streams potentially tricky for me. Even if I don’t want to fly a plane that is being showcased, I at least have to have it installed. That’s fine if its a freeware mod, but if its payware…
there is(was?) a issue with languages like chinese. Otherwise its not necessary to change the system language to english, only installed Lang Pack US is necessary.
@DelTogi
please post the error message from windows event log
1 Like
Ever since May 16 I have not been able to launch the game. Keeps crashing to desktop right after the black copyright screen on launch. I tried to do a clean install of the game following this topic but the issue persists.
I feel like I have tried almost everything short of re-installing windows but I would like to avoid that if possible. I’ve updated windows, updated my graphics drivers, checked for Microsoft store updates… is there something else that people have tried?
Faulting application name: FlightSimulator.exe, version: 1.16.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.16.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001c8e6c7
Faulting process id: 0x1954
Faulting application start time: 0x01d75adc24105c7e
Faulting application path: Z:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: Z:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: c64f9374-e719-4582-a81c-3cf7942d4f75
Faulting package full name:
Faulting package-relative application ID:
1 Like
you can sarching a bit about “black screen” in forum where you should find more “better matching topics”.. e.g. tried already “-FastLaunch” ?
I have the same problem as everybody else, with black screen and blue circle for a few moments as MSFS 2020 fails to start since SimUpdate 4.
Like everybody else also I have tried all of the various ‘fix’ recommendations and again without any success.
It is clear from the threads that the fault stems from the update, and trust that Asobo are working on this.
It would be encouraging if Asobo could at least acknowledge the issue, and confirm that they are looking into it to enable a fix to follow.
1 Like
I have a CTD about 15 minutes into any flight. Been running without issue since Aug 20, but the last update has broke FS completely for me.
Ryzen 5600x 32gb ECC
RX6700XT
Latest version of windows
2 Likes
I hate to say this but with Directx 12 coming soon i don’t think Asobo is worrying one bit about these CTD issues. Why waste time fixing something that will soon be history
Sorry to hear that another fellow simmer joins the club. This shows how no one should feel safe from CTDs, even those who brag left and right in these forums that they never had a CTD and MSFS is the most stable software out there and that those with CTDs must be doing something wrong etc. MSFS can apparently crash (or stop crashing) because of so many reasons, that it’s very hard to perform any meaningful debugging that can be applied to all users.
I hear that DX12 may be out even before summer end? If that’s the case then I’m more than happy to wait and see if anything changes.
In my latest tests in Crash to desktop without error message - #4064 by Zeppos after having A5 Icon crash 1-2 minutes into the session (soon after I turn on the master switch and look around), I entered the usual CTD loop where the game crashes 100% of the time when main menu is about to load. After the initial A5 crash, I must have had 10-15 or more consecutive main menu CTDs and I couldn’t exit the loop no matter what I tried.
However this time I thought to go to Adrenalin software, to the Tuning tab, then I selected manual settings in tuning control and decreased Max Frequency to 80% and also decreased max Voltage to 90% or something. Didn’t change anything else, all other settings were left in factory defaults. Voila, next time I loaded MSFS it finally managed to reach the main menu.
Apparently this didn’t solve all my problems, as A5 CTD’ed again within a minute or so but at least by applying the above frequency/voltage change I was able to avoid the CTD loop and consistently reach the main menu. As usual when I later loaded a flight with Piper Arrow, I didn’t have any issues and was able to fly happily for an hour or so. Which proves it’s not a generic overclocking thing, otherwise I’d get CTDs with the Arrow as well. I’ll have to do more testing though as my latest “workaround” may have been pure luck. I’ve had similar workarounds in the past which I first thought did the trick (like disabling Xbox Game Bar), only to be disappointed in the end.
Also random CTDs (10-20min flight) since the last Update. 
Still crashing upon startup even with a Steam reinstall
I few for many weeks with no CTDs after turning off AI traffic. About a week ago I turned AI traffic back on but no voices. Still no CTDs. But as soon as I turned on voices I started getting CTDs again. I have a good system, no add-ons and have updated language packs. I think (at least for me) it’s something to do with AI traffic and ATC voices. I have turned AI traffic off again despite it being a critical component of game enjoyment because it sure beats a CTD 1 hour 40 minutes into an IFR flight from cold and dark. It’s time the issue of CTDs was addressed.
Because it is extremely bad for business.