I would like to give my testimony unfortunately without solution to date:
the sim worked very well until the beginning of November 2022 with my GTX950 card (yes only) and a RAM of 16 GB… the fault appeared after SU11 at the beginning of November and the update of the various NVIDIA drivers or vice- versa.
I can currently make a complete flight until landing if I delete before launching the software all the files from the local cache except packages.
But the problem comes back either when I want to return to the main menu or when I launch a 2nd or 3rd free flight (your graphic card etc…)
I of course listened to the advices of all of you my friends by downgrading the NVIDIA driver to the 531-29 and downclocking the card speed by -100 (WIN 10 up to date, DX11, low or medium setting, any plane, any airport, no World trafic, no weather in line, no addons).
I am almost desperate to see that my favorite simulator of 30 years no longer works. Please MS, Asobo or NVIDIA do something for me.
You shouldn’t downgrade the card speed, the most important underclocking is the GPU memory speed. Make sure you use MSI afterburner and underclock your GPU memory speed by 300Mhz (aprox) make sure you apply the changes with the tick mark in Afterburner.
It might help you use the sim while the bug is still unfixed.
A lot has been said recently but this is a long issue not something new.
Point 1:
It is NOT an error in the latest Nvidia driver, this bug happens for ANY driver, but some drivers trigger the error in more users than others so it is a common thing to associate this with a specific driver or to think that rolling back solves the issue.
In other words: for ANY driver you have a number of users that suffer this bug.
Point 2:
While we can’t be 100% certain we suspect this is a MSFS bug mainly because it happens for all drivers and it happens only in MSFS for users that have other GPU intensive applications. So we hope it will be eventually fixed.
Point 3:
The only semi-consistent workaround we have found so far is to underclock GPU memory speed or GPU clock speed or both by some number of Mhz, depending on each system, lowering the sim graphic settings has also worked. This does not mean that the problem is over stressing the GPU capabilities because this happens for low end and high end GPU cards and it happens even in the menu or the content manager when the GPU use is minimal.
Something important: Please stop thinking that rolling back a driver fixes the issue, it only stops the bug from happening in your system and will confuse other users.
it fixes the issue coming with the driver release 513.41… so we still mention that for users which are affected by that so that they can play. I had can never reproduce the issue in that topic here on two different systems and I really tried so many things to find a trigger for that, also extra OC the GPU ( what I usually not do, because 1% more perf is the stress not worth ) , but no chance. It started in my case direct with the 531.41 . There is a chance that a specific new DX12(Beta) feature impl. introduced with su12 cause the driver crash , but thats unimportant - a driver not have to crash and it is the driver which crashs, not msfs. Msfs simple detect that crash and stop itself. In ages before the popup was introduced, msfs ctd with no specific info.
and a suppl. : what we should also not forget. There was windows updates in parallel. Some minutes ago I spotted the same nvidia-driver crash with the event 4101 in the log - and NO - I was in that case not in MSFS.
if you allways start system with afterburner, then try without. There are not less users which use an afterburner version which cause a crash. Of course I would also not wonder if an 8 years old GPU ( and that is a gtx950 ) can have its own problems with that game. But we discussed so many different points in meanwhile and its allways like a loop.
I want to add my stake in the ground on this topic as this is a consistent error I am encountering myself as well and have been for some time now. I hope this will be seen by Asobo and be addressed as it’s currently renders the sim unplayable.
I’m going to post one more time and shutup. I had NEVER had a driver error until SU12. I have had the exact same issue with at least 3 different Nvidia driver versions. I just had the game crash with the overclocking error message running version 531.29 just about 10 minutes ago. I would love it if rolling back to .29 was the answer but that doesn’t seem to be the case. Also, I’m using DX11.
Thanks for this! Couldn’t make it 10 mins into a flight with DX12 turned on before I tried the underclock. Currently nearly 3 hours into the flight with DX12 and all settings ultra no problems. Nice one!
Luis, could you explain why underclocking the GPU memory helps fix this issue? I’d like to understand the cause. I have an RTX 3080 Suprim X 10GB card and I’m also experiencing the error. The error itself doesn’t tell you alot.
Sorry I really don’t know why underclocking works, I only know it is usually what helps to deal with this bug besides reducing sim graphic settings. I wish I knew more but it seems even for Asobo this bug is difficult to deal with.
This is also happening to me. It usually happens when I’m on the 3rd person camera moving around or even on the cockpit view as well, although it’s more difficult to happen.
Can’t complete a single flight without it happening, it even happened while the game was still launching/loading.
It happened to me with my AMD card multiple times before SU12. But that may have been related to my graphic card getting quite hot (I’m a total newbie to graphic card fiddeling and my fan speed profile was optimized for noise and not GPU temperature.
Yesterday I had my first CTD with SU12, but the error message was different…
we spoke about appr. 1000…1500 posts ago ( therefore is this thread so long , compared with the votes on it ) about that.
Therories was faulty hardware ( in special most users check only the gpu (chip)temp, but not the gpu-ram temp ) , driver stuff, issues with race conditions, etc… we had so many guesses.
The most important point is:
this dialog comes on different reasons . That we can also see in different error messages. With introducing of these popup ( su 10, or 11 ) it catch some kind of errors and show you the popup.
Therefore it is important to distinct in error messages users get.
The insension behind that popup was, so far I remember, that the game “no longer crash without an error message”. But I’am not sure, whether the popup catch to much. As example may be with the “restore/restart of the crashes nvidia driver the game could may be furthermore run fine” ( of course, not sure ).
With MSFS there’s a hell of a lot of syncing going on in vram from multiple sources and overclocks can quickly become unstable. If you investigate your particular graphics card’s specs and it is running faster than the Nvidia/AMD default for that gpu then it’s been overclocked by it’s producers and comes with no guarantees it will work with every software/hardware combination.
we spoke already about that, often now: new was not only the su12, also the nvidia driver 513.41 and a fallback to .29 ( or use dx11 ) fixed it in meanwhile for a lot of users.
Whether the game itself trigger the driver crash, or the driver itself is faulty ( in my opinion a driver have never to crash! ), we cant sure.
User which get the error as a different reason than the driver crash, might still get the error also if they done the fallback with the driver. Then may be one of all the other given hints ( most important the underclock of the hardware ) helped the users. Also then same sentence is valid: we are not sure whether the game triggers the ‘other kind of errors’ , or whether it is a different problem ( for me personaly: if set a limit so that the hardware can not run at max will be help, it points to the hardware itself ).
One answer about AMD answered the user one post ago for you with a guess:
so again a point for may be hardware related.
We are all not sure about what exactly is the reason for that and so I think nobody of us here can speak about what :
