Today I upgraded from the stable beta version to the build version 1.21.18. changed. Now I only have CTD’s. These CTD’s are also in safe mode without community folders! As soon as I start my flight, there are CTD’s. Sometimes only when I’m in the cockpit. Sometimes after a minute, sometimes after 3 minutes … I have already slowed down the graphics card, reduced the settings, to no avail! The CTD’s keep coming back. I am at a loss … 
PC: i9 3.60 GHz / 32 GB Ram / Win10 Home
NVIDIA GeForce RTX 3090 / Driver: 497.29
Yep. 
Same here. . . .although I can’t even get the upgrade at this point.
Never had CTDs until the latest update…renamed community folder and still CTD.
Constant CTDs. I have used different planes. I have removed everything in Community folder. I have walked through all options ( it even crashed whilst I was checking options) to check there are no apparent anomalies. CTDs happen from checking options to after a flight has taken off but crashes within five minutes or so.
After trying all the usual things, the simulator has not crashed since updating the Nvidia driver. I was able to reinstall the community file and proceed normally.
I would move the Community Folder to the desktop and reinstall MSFS. This helped me greatly. The latest bug fix is working great. The best I have had it for a long time.
Same boat, impossible to play the game and quite frankly I spend more time looking at this forum for CTD solution rather than playing anything. We should be getting refunds for an unplayable game.
For the ones about to attack me, I’ve tried all the fixes individually and in combinations. High end pc (nvidia), all hardware drivers updates, no OC, back and forth through the past 3-4 nvidia drivers, removed features, folder, vanilla game etc. etc. just nothing, constant CTDs.
Also, this is not my problem, this is FS2020’s problem, nothing else crashes
1 Like
Same here after the 1.5gb update ctd within 45 seconds
I don’t know if I should rest assured that I’m not the only one with this problem. But hey, Microsoft / Asobo, that doesn’t work! Not only I have invested a lot of money in expensive graphics cards, expensive VR equipment and in the last few weeks I have only been busy tracking down errors and can hardly really fly! Guys, you have to get a grip on that! You do a great job with a great visionary idea, but don’t break it with inadequate controls! Please!!! (I am going to reinstall everything from scratch now and hope for my luck!) )
Hello all,
what I saw also previously as big problem was graphics driver problem, especially with new versions. This I see here from more posts. Guys, try only go back with driver version or lower bit to see what will happen. Are some Win Updates meanwhile proceeded? Check for sure…
… yes that can be. But a developer company like ausobo and even more microsoft has to keep an eye on that and react to it and offer solutions immediately and not leave something like that to the experiments of the community, sorry … Other developers have that under control too. I’ve never had so many massive problems with an app as with Microsoft’s flight simulator. Especially since there was no update of the graphics driver between the beta and the public version.
how they should do that ? they can not check each hardware driver… its a old and not very usefull discussion.
That drivers cause big issues is not new and all other applications run into same, also other flightsims. As example I remember last year that Prepare3D does no longer started with driver 466.11 and nvidia have to deliver a fix for here driver-version.
But in this case I not know about a new driver version these days… the 497.29 is since 20/Dec/2021 online. In case there are other updates on your system in meanwhile, who knows…
Because you report a CTD it would be allways a good idea to post the windows event log. Sometime we can see more details with that…
Obviously, I seem to have narrowed down and resolved the problem for now. The first flight in January and since the last update without a CTD. Thanks @ CuzDawg3! He had exactly the same problems as I had for a few days. In fact, deleting the Realtek sound driver (which has been running unchanged in the background for almost a year) ended the CTD … Unbelievable, you don’t think of that … Thanx CuzDawg3! Now I’m trying to rebuild the community folder bit by bit. With every extra thing I’m afraid that the CTD will come again … The jerking mouse in VR has still not been eliminated, but I can live with that!
today I noticed , beacuse we spoke in other topic about, that nahimic service was auto-reenabled and latest file chane was 11 / 2021… who knows how many users run into issues because there was again a change with that plaque ( I assume windows update installs this a-volute stuff… it match in my case with the windows update 20H2 ). In my case I have no longer issue in case the service is running, but we know this is a big trouble make for lots of systems.