New patch 1.14.6.0. Would not download, quite possibly because of some problem with MS Store, so I had to resort to a Windows reinstall
MSFS reinstall as well obviously, took half a day to download those 155GB
Latest WHQL AMD drivers released a few days ago
First launch resulted in “Display driver amdkmdag stopped responding and has successfully recovered.” and the entire PC froze, I had to physically reboot it. First time this happens
Everything else works perfectly fine out of the box, all games included and in ultra settings.
It’s not PSU, it’s not BIOS, it’s not RAM, it’s not GPU, it’s definitely MSFS clashing with something else (AMD drivers or whatever).
Go figure. Bad programming, bad product, bad results. Blame me for being grumpy because I’ve paid literally thousands of euros for PC upgrade, peripherals and software and I still can’t play this thing since the latest update in early March.
Yes, I understand the fact that yesterday’s patch was exclusively addressing the known performance issues and nothing else. CTDs will still be there for the foreseeable future and I sincerely hope Asobo do something to address them because there are many of us who have heavily invested in MSFS and it’s super frustrating to not be able to play. We’ve been even called “trolls” by certain lovely people here in these very helpful forums, but they can’t even begin to imagine what it would be like for them (who are able to play) to be in our place. I just pity them and I’ll stop there.
However I may have done a huge breakthrough for the first time in a week or so.
After a few more dozen workarounds which amounted to nothing, I finally got the sim to load 3 (THREE) times consecutively without crashing in the main menu. This is unheard of. I did a couple of very short flights and it didn’t crash when I returned to the lobby and it even let me download all 30GB of in-game marketplace updates and was stable for several hours in the main menu.
So the absolute last workaround I did was to disable Xbox Game Bar. 99.9% sure that did the trick to some extent. It can be done like this:
Just before that I had also disabled AMD Adrenaline overlays but MSFS still crashed, so it’s probably Xbox Game Bar that did the trick. I’m not using any other workaround, no overclocks/underclocks, undervolts or disabled XMPs, nothing at all. Just a disabled Xbox Game Bar (running on its latest version anyway).
Unfortunately the 4th time around I got a VCRUNTIME140.dll CTD as soon as main menu appeared and the only different thing I did was to keep MSFS loading in the background while I was on the browser replying here in another topic. The 5th time I had the game load in the foreground and it’s still working fine half an hour later, I’ve left the aircraft flying circles while I’m switching between Windows, writing this post and so on, with no CTDs so far.
I pray to dear almighty God and all that’s holy and sacred and I pray to mankind’s welfare and to Asobo’s prosperity and to our childrens’ happiness, that disabling Xbox Game Bar was the trick that does it for me and I won’t have to use any other workaround.
… which is not to say the CTDs have stopped, as they are still happening all the time. The game will crash if it’s not loading in the foreground, it’ll crash if it returns to main menu after a flight and so on. It’s just that it usually works when a few hours ago it didn’t work at all (for a whole week).
edit: more never ending curiosities as even with Xbox Game Bar disabled the game will crash 100% of the time within 5 seconds being in the main menu if it’s in windowed mode. As soon as I switch it back to fullscreen (actually that’s borderless fullscreen, enabled via “C:\Users\asmod\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt”), then it becomes more or less stable again and I can now launch a landing challenge. Will this never end…
After the 1.14.6.0 update, I started to once again have the odd CTD. I got a hint though and so far running smoothly again. Reading back through this thread I noticed others have had similar behavior. I would get fps “stutters” during ATC audio events. And when I did CTD I would get some audio “stutters” right beforehand. I’ve got a Reverb G2 on the way so I’m not in the accepting mood. I noticed while watching Netflix, the odd time, I would get audio “stutters”. Well, I’ve been recording music professionally for some years. Those aren’t stutters. They are Buffer Underruns. I have been using my Mainboards soundcard which uses a Realtek driver. Ok I have the ability to test, So I did. I ran the game with my studio soundcard… what a difference. So far, no CTD. I’ll report back but its looking so far that the soundcard is the culprit. It has the latest driver too as one released after the recent windows update. MSFS seems a lot more responsive. It’s for sure a lot smoother visually, and ATC’s audio has no more effects on my FPS. My honeycomb controllers are also a lot snappier. As well I can reply to ATC the instant his/her audio stops, used to have to wait a seconds to reply
EDIT: Its not at all a cheap mainboard and the onboard DAC is “supposed” to be debcent
I haven’t experienced CTD’s since the game launched (which were caused by my old bluetooth keyboard that I have since replaced), but I’m getting them now after 1.14.6.0. I haven’t flown much since WU3, but prior to that I never had CTD’s after switching keyboards.
Mainly caused by VCRUNTIME140.dll, as others in this thread have reported. I did recently install some software that installed additional C++ libraries, but I have uninstalled those to no effect. Running Just Flight’s new Piper as well, but I don’t really feel like uninstalling a bunch of stuff. Will just stick the sim back on the shelf for now…
Bluetooth keyboard? Hadn’t heard that one before. Seriously, the number of different ways that MSFS can CTD knows no bounds apparently.
I’ve managed to crash it twice myself in the past 10 minutes by simply pressing Windows key while in the middle of the flight (again this is new as I hadn’t seen it before). I’m pondering the idea of raising a separate ticket with Asobo every time the game crashes in a different way.
3024 comments and counting. Still waiting for a fix that will make the game stable.
Thanks for the tip, but it didnt help. Screen froze just as I was starting to taxi. will ctd in a while when it has finished sending the dump file. Which of course I send to Zendesk who just ignore them.
I believe they made the bluetooth peripheral issue better, but the sim used to CTD when low power bluetooth devices went into power save mode and were woken up again.
I was undervolting my 3090 via MSI Afterburner. Went back to stock and flew for 2 hours without a CTD. Re-enabled my undervolt profile and flew around for another hour with no issue. Not sure if that was actually causing a problem or if I just got lucky… I’ll continue to fiddle with MSI Afterburner if I CTD again.
It sucks now. Time wasted again. Four flights on the same IFR route from LEMD to EDDF and each time a CTD, after a usage time of around 1h 30 minutes. In the case of commercial software, lawyers would write.
edit: on the route - PINAR UN870 SEGRE UN871 DITON T163 EMPAX
It’s a bit of a pain I’ve never had a CTD now since I set up flight on world map press fly immediately ctd this after patch only.
So did a clear out and full reinstall of sim and end up with same result.
No changes made to system.
So disappointed as before patch no problems.
yes.. I seen this long ago, but also with it I still not sure how this should avoid a CTD if the Fl..exe is shifted to another core or limited to run not at all cores. If this would be an issue, then we all must have a CTD and need to change the affinitiy
My only idea was, that CPU Turbo modes comes in steps at the cores and the user system have an thermo issue. But was also not sure about…
Example: in my case (i7-8700k) the cpu11 is the one which msfs use in 100% . I can simple shift it with the affinity to another core, but it makes not different and this in special because I use kind of overclocking “Sync All Cores” : so all my cores run in 100% Turbo Frequency.
But of course: users can try that. But for a “Try” they can also simple use the Taskmanager
The reason why a custom CPU affinity mask might prevent a CTD is, that when Windows is low on resources, it is forced to free some in order to prevent a system crash or BOD. Thus, it shuts down all resource intensive processes in order to save the system from crashing.
So any CPU core that is left over for anything other than FS2020, allows the system processes to utilize this free core alongside the demanding tasks of the sim. This however makes only sense for CPUs with more than 4 cores, as DX11 uses 4 cores and anything lower than that would lower the overall performance.
And of course people can try this via the task manager directly. That’s how I described it in my performance forum thread
..