Possibly because flag physics aren’t high on the priority list of things to fix for a flight simulator.
1 Like
Hello @Gryper3379,
The message you are seeing is not an error at all but rather a warning that you should update your GPU driver. In some older versions of Nvidia’s GeForce driver, there was an issue that could cause a crash when using Microsoft Flight Simulator. Nvidia fixed this crash with their 536.23 driver. For this reason, we are recommended all PC simmers who have an Nvidia GPU to upgrade to either the 536.23 driver or newer.
Thanks,
MSFS Team
You’re awesome! Thanks! I’ll try that as soon as possible. 
1 Like
I hadn’t upgraded from 526.37 until that new message. But after upgrading to 536.23 I haven’t gotten the dreaded message.
2 Likes
I got this message even on my very high end PC. Had to lower the lod a tad.
Also, Dx11 works much better than dx12. More frames
Hey, I’ve encountered this issue pretty often after AAU2. The sim could not run even 10 minutes after hitting the fly button. It seems that I’ve solved this issue by following this setting for the NVIDIA control panel. I have GTX 1070 with the driver 536.40. Link: https://channellfd.com/msfs-nvidia-control-panel-settings/ .
Maybe it will help somebody else.
2 Likes
Well said. Not investing anymore time and money when its clearly the coding at fault.
Remember folks its not your rig, its not your gpu or cpu and why should we be rolling back to old drivers!
Its the sim and these are legacy error messages in one form or another that have never gone away. So why should we buy another product ?
3 Likes
Hi guys. No more messages for several days
Does that mean the problem is solved from driver 536 26 or 536 40?
2 Likes
Suddenly getting this error today . Never encountered before until now . Using 536.40 , DX12. Weirdly I have been using nvidea filters without issue even tho others say it caused an issue, as of today this now causes an instant CTD if applied.
1 Like
I’ve tried everything that was mentioned by Asobo in this forum without help.
- vanilla reinstall
- empty community folder
- empty cloud save (great, AGAIN all achievements and settings incl. key bindings are gone)
- latest GPU driver 536.40 causes overheating warning in the menu already
- recommended driver 531.29 causes overheating warning in the menu which didn’t happen when this driver was the latest one
- previous driver 536.23, which was also working fine when actual, causes the same warning
- if driver is older than 535.79 MSFS shows an additional warning about an outdated GPU driver before crashing with overheating warning again
- went back from DX12 to DX11 even though DX12 was running fine for months
If this problem was related to the GPU driver why aren’t the old drivers solving the problem? They used to work fine before!
To me it seems way more logic the problem is within the sim. No other application is having any issues with any Nvidia driver on my system. And I haven’t touched any settings in the sim or the Nvidia menus when this fault killed my sim from one day to the other. For me problems started during the updates during FS Expo week:
19-JUN-2023 City Update II: France
22-JUN-2023 Aircraft & Avionics Update
23-JUN-2023 Famous Flyers Ford Tri-Motor
29-JUN-2023 City Update III: Texas
30-JUN-2023 Local Legends 10: Boeing Stratoliner
Reviews on the Microsoft market place show the 3 versions of MSFS which still cost 60 to 120 USD with 2.7 to 2.9 out of 5 stars. That tells a lot. Reviews on steam and Google are way better though. However, the latest pinned messages in this forum about GPU related crashes give an idea about the seriousness of this problem. I assume most of the users are on Nvidia cards. So, the majority is affected. Besides the sim itself I have purchased some addons but most of all a new PC beforehands. I write this to explain the high level of frustration. To me it’s not just a one dollar problem because the sim comes for free with the Microsoft game pass. I have invested way more not to mention a lot of time to get this thing running.
Even though the problem has been around for a while the number of affected users quickly increased in the past weeks while MSFS2024 was announced. This by far is the worst time to disappoint customers. First the impression arises that MSFS2020 gets neglected after 3 instead of 10 years in favor of developing MSFS2024 and while Asobo and Microsoft are trying to calm down customers MSFS2020 becomes unusable for so many clients.
I for myself will not buy MSFS2024 or upgrade from MSFS2020 (if this will be possible after all for existing owners of MSFS2020) until USER REVIEWS on YouTube, etc. show:
- improvement of stability: frame rates, download rates, download size, streaming of photogrammetry, updates for the better instead of the worse
- fixture of ever existing faults: horizon visible through terrain (rectification marked as “not planned” despite it has been voted third place in the bug list!); lights hovering above ground, insufficient texture resolution on airports, wrong navaids even though current navdata cycles from NavBlue were announced when this product was released, clipping ground tiles, release of unchecked new content such as scenery and aircraft,
- implementation of features that were standard from day one in older versions of the franchise and that have been promised ever since MSFS2020 was released as “Alpha version” and still haven’t been added in its current “Beta state” after three years: Instant replay, tower camera, seasons, good ATC, smooth weather changes, etc.
- enabeling customers to skip updates/roll back in case of problems
- proving (not just promising) that MSFS2020 addons actually do work in MSFS2024 (I don’t trust Asobo on this one as 3rd party developers already had to modify their products in MSFS2020 to keep them running after updates from Asobo)
I really wonder why Microsoft hasn’t pulled out for the 2024 version to save its reputation or has at least asked to get MSFS2020 right before financing MSFS2024. Quality over quantity is the way to go. All aircraft models look awesome. But functionality equals zero before other developers such as Working Title or FlyByWire put their hands on them. Why not get one thing right before throwing dozens of “good looking but empty 3D models” on paying customers? And what about hot fixes when something so serious happens right after announcing a successor?
Also, I assume that third party developers are getting mad because nobody will buy addons for a sim that isn’t running. That also affects Microsoft as they (want to) earn provision on products sold on their in-sim market place.
While I write these lines a message to the right shows "This topic has been solved. Only reply if you have additional details.” Good joke. Nothing has been resolved. See the number of views and votes on this topic. You really have to break things quite good to get a topic out of nowhere to the very top of the bug list within no time.
I will monitor this forum and customer feedbacks (not the fancy previews from Asobo) throughout the internet. But for this summer break I’ll enjoy the awesome clouds in DCS and spend some money on dedicated addons there. And boy is this sim loading fast.
6 Likes
Speak to me from the heart.. in terms of content! But the CTD problem has been since last year. It’s very bad, I’ve been through everything. I don’t understand why they don’t do anything. and say nothing about it. It’s not because of the Nvidia driver, that’s what I think now too. I buy myself a new graphics card RTX 4070 TI and a new CPU Ryzen 7 5800x3d. So I spent a lot of money. And immediately under DX12 CTD Boom. I have a very thick neck !!!
4 Likes
Gave this a go today again. Am not able to play for more than 5 minutes before the (new) message arrives. Asobo declared in some comment some month ago that the message could be clearer. So they fixed that part.
But the bug is still there. But comes and goes in a somewhat timely manner. I would not be surprised if I could fly without a problem after my summer vaction is over due to the fact that there are less updates performed within next coulple of weeks.
The solid silence from Asobo and MS about this problem is not the way this shouldnt have been handled. I guess I try to play within a week or so again.
One thing is for sure, and that is, if they dont solve this problem, or at least speak up about it, I will not go for MS 2024. Risking to buy another game that couldnt be played. But I assume they might just want to deliver this “for free” in xbox gamepass, and then they don´t need to bother that much about it.
Currently using 536.40. I’m pretty much maxed out using DX 12 and Frame Generation with zero issues. I can fly for hours upon hours back to back. I haven’t had this message pop-up in months.
5 Likes
CTD remain with latest NVidia drivers GeForce GRD 536.67 …
And not listed in the opened issues since 536.40, as if it was fixed …
3 Likes
I’m getting this error and ctd from quite some time now, happens a lot out of the blue even when the performance are not getting hit in terms of fps
did try a lot of nvidia driver builds now and honestly it did not change anything or anything sensible
2 Likes
It, just took my 5 mins to work out how to log into this forum to write this, since when clicking the login button at the top right, it simply threw me to a new user without actually allowing me to log in with an existing account, had to make a new account under another email, says it all really.
Started getting the error reported above, after multiple crashes i am now remembering why i lost interest in MSFS, shame really, nothing but problems and frustrations, as usual, everything else runs fine on my computer, its just MSFS. I like how they updated the fault to provide people with “information” as to the source of the fault. We all know the source of the fault is MSFS so stop blaming peoples computers!
For me it seems to have started after the most recent update (as i had not updated any other drivers) prior to this, system had been running error free for a good 1-2 months and then i went away for a couple of weeks. When i came back and loaded the sim, i was faced with the update.
After updating and after the crashes started, I then checked to see if there was an updated driver for my GPU, there was so i installed that hoping it would solve the problem but it didn’t…I have a RTX 3090 and a 5800X3D
I was also running DX12, i changed to DX11 on the advice of the error messages but it still crashed OFC!
I log my flights through a tracker and a VA so its a real pain when it crashes. The crashes are completely random, sometimes i can do the full flight without a crash (that includes return flights without restarting over 4 hours).
I have had it crash after landing when turning into the gate, i have had it crash after 4 hours of flying. The most recent crash was yesterday during descent after a 5 hour flight.
Initially i thought my GPU was getting too hot but i carefully monitored the temps to find them not getting above 70…
I would go back to another sim such as Xplane but its just too much like hard work at this stage as i deleted my gbs of add-ons etc, plus i really do like the looks and simplicity of msfs when its not crashing.
I have 1000’s of hours across all sims, i did find FSX to be the most stable personally but i used to run into the out of available memory errors due to the RAM limitations of 32bit software!
Guess ill just have to sit and wait for another update from msfs to see if that fixes it, not going to keep wasting my time doing medium/long flights for it to crash. I have yet to pull out the long haul aircraft as i wanted to make sure the sim was 100% stable before wasting more time.
On a final side note but it might have some value…i tried to load back into the sim after it crashed (auto save) and it was having none of it (i also tried this on previous crashes with the same effect). When i click load (after getting into the sim/go fly) screen goes black then it crashes back to desktop without any error, it doesn’t even attempt to load into the saved flight.
Yesterday i couldn’t even load a flight back up at all (i can always get into the sim/menu) but when it had crashed on other occasions, i was able to at least load up again at an airport, i just could never load a saved flight. But when it crashed yesterday i couldn’t even do this, it would just go to a black screen and crash to desktop without error.
In the end i needed to restart my computer to get back on FS and it worked again oddly enough, as in i was able to load back up at a gate etc, i was also able to successfully load the saved flight which failed to load after the crash so it seems what ever this crash is, the system needs a restart to sort the sim back out again (sometimes). I read something similar in another post about running windows updates and doing the restart etc but this only gets you back into the sim after a crash…it doesn’t stop the crash from repeating.
I can live with the crashes running an auto save etc but since i cannot load a save after a crash without first restarting the computer my tracking system looses all the data and i am back to square one again with hours wasted and needed to start the flight from the start. It just feels like such a waste of time. I am nearly ready to buy a VR headset but i will continue holding off, last thing i want is to be stuck with a £500 headset that i cannot use, i have no other purpose for a VR headset.
1 Like
I haven’t had that error message in months until I switched to dx12 and enabled dev mod to fix the texture pop up bug. Sticking with DX11.
1 Like
Got my sim back running by again switching back to DX11 and putting the global rendering quality to low. I did this several times before but the sim crashed too quickly to save these settings. Now that I installed all additional contents of the sim with 2.5MB/s on a 500MB/s line for 24hrs I can enjoy low end graphics, white boxes around the displays and all the nasty bugs in their full glory again. I remember the displays got blurry after switching to DX12. Now they’re even blurry on DX11. But they’ve got that fancy white box to make things more interesting.
In case you don’t want to type the link from the failure message manually here’s a C&P:
https://flightsimulator.zendesk.com/hc/en-us/articles/6422969348508
1 Like
I rolled back the driver yesterday, i will update later when i get chance to test but likely need to do a few flights since it can survive one to two without a crash. As mentioned though, i was already running a slightly newer driver and for me it seems to be the MS update that triggered this as a pose to the NVIDIA at that time. I guess the new update has turned very flakey against more than one NVIDIA driver. I hope the above works, ill likely have to step away from it otherwise as i find it demotivating when you waste all your time setting up for a flight for it to go and crash later down the line.
UPDATE
So far so good, 6 hour flight complete with no crash, i took the driver back and i decided to stay on DX11 for now just in case. Either its the driver or DX11 but my sim does seem a bit smoother than it was before too.
Might try DX12 again but only after i know it is once again fully stable!
Cheers all
1 Like