We can divide the sim’s gpu load into 3 levels based on the size:
The most high spot is within the Main Menu, there the gpu load is between 80 - 100%, even more than when being in game! however, the gpu vram usage would be 6 GB min @ Epic settings 4k resolution. this high gpu load while in menu can explain why so many are getting this error just in menus, despite the fact being the real trigger to this issue is still unknown.
While In Game, there the gpu load would be 60 - 75 % load as an average. performance optimization technologies can explain why the load here is not maxed out as in main menu. but here the vram usage would be @ the maximum; with the previously mentioned settings, the vram usage would be 9 GB as minimum, & can explain why the rest get the error while playing, & again, despite the fact being the real trigger to this issue is still unknown.
well, I still compare with my systems. In meanwhile two of them not run into that issue, never. And the first one was build with the exact same graphicscard as @BlueYello reported. At least I see a relation if so many users report like “it was helpfull to do a setting which limits the system load” ( gpu, ram, clock, voltage, what ever ).
That the error about vram-usage is missleading we know already, I’am pretty sure what users get have nothing to do with the amount of vram.
What I not understand.. if users expect , like @BlueYello , that the problem comes from the “factory OC”, why not run additional test-scenarios. Simple disable factory OC ( e.g easy within NCP and the Debug-Mode) - the 1% less performance will no human bean notice. And for me I can only repeat: if such a setting is helpfull, the issue is not the game.
My 2080TI was also in-game in 100% load , it depends on the settings/resolution/view/etc, so not only in menu ( where I use the low-power-mode ). Of course there are also other factors, like windows itself, a driver, a specific software, a specific mod, whats ever.. but still, “if the game not crash if users limit the max system load, then I would search the issue on the system”.
On other side I not know, why till now these error-report-dialog was not “improved” and give users more informations what exactly was catch’ed. That would made analyses much easier and users not “groping in the dark”..
The hot spot temperature is the hottest GPU die sensor out of numerous sensors on the die. Ideally you want the delta between the reported GPU temperature and hotspot temperature to be the lowest possible, but there is always some variation due to non-uniform heatsink contact or thin/cracked thermal paste. As long as your main reported GPU temperature is fine, there’s really nothing to worry about. It could just be that one corner sensor is hot, but the remaining is fine.
That may lead to that if we figured out the relation that triggers this issue, then it would be a combination of certain settings to apply, in other words, something specific we must avoid. that if it was not a coincidence for whom didn’t encountered the error.
for sure, stable performance will lead to a stable sim.
100% agree, that explains why some with 24 GB Vram has encountered the error.
true, but of course we are talking about a middle ground, an average.
this point can be tricky, because i always for example run my sim @ max settings, and i don’t get the error when this issue in (sleeping mode), when it appears (awakes), it wont really matter, because you can get it immediately, or even in installation process if you reinstall the sim & encountered it while the installation; as i did @ the first time. so i guess the sim can handle the max settings pretty well, so this error is due to some sort of conflict the least to say,
i guess they maybe waiting to locate the issue, so to differentiate between the contexts afterwards.
I have now been able to reproduce this error 3 times. Also hade some time flying as a preference when it doesnt crash.
Here are my steps performed while using TechPower-up GPU-Z.
Use 2 screens. Main-screen is for the game. I use fullscreen mode.
2.While in game-menus in-game. I open file explorer on my second screen. This will show very clear in the PerfCap Reason-measure that will go from mostly idle to capped by all possible measures (colors) at the same time:
Some weeks before my new findings I chooseD to shut down steam right after starting the game as it crashed with this message at the same time I saw Steam pushing out a sale. Felt like it was related already then, but it didnt help me all the way.
So, my thought is that it is related to the taskbar or windows menu that is “missbehaving” behind the game for some reason. Will start to find out how to disable the “taskbar-buttons” for a start:
Yes, this is me. Had this is menu just once or twice. I do fly more than sitting in the menu so that will be one explanation.
My latest post here shows how I can reproduce the error, again and again though… In the menus.
because if i switch while the sim is loading, to desktop, the sim wont continue loading.
but if i loaded the sim, then i can switch to other task on windows while the sim is running with no problems, this is useful while updating to new updates provided by MS\Asobo, so you can do multi-tasking on windows while downloading big downloads.
Upgraded to a 4080 and I’m getting these crashes from time to time. I’m using DLDSR running at 5160x2160 so my GPU is taking quite the pounding in terms of VRAM at airports but all my crashes have happened when my VRAM is lower, such as paused at the menu or cruising above the ocean. Temps are 60c so can’t be overheating. No real idea what’s going on here and the dump files give no real information of value.
Have you tried using the latest version of the nVidia Frame Generation .dll? The that comes with msfs is only version v1.0.1.0. The latest version is 1.0.7.0. With the old version I could cause the crash by simply resizing the sim window (100% of the time). With the newer version I have had 1 crash in about 3 weeks.
Test results on my end for the workaround suggested in this thread about resetting the cloud files for the sim, after 2 weeks, since the test started in 11\2\2023:
i Didn’t encountered the error in this period, the sim runs perfectly @ max settings.
i can confirm from my end, that deleting cloud save files themselves have no effect or relation to this error.
i can confirm from my end, that resetting the sim settings by deleting the cloud files, is vital, after every sim update:
it appears there was some conflicts between old saved settings, and new implementations were implemented in the sim, so resetting the settings after every sim update (not regular add-ons updates), can be very useful as this workaround suggests.
however, while this can reduce significantly this error, based on the fact that majority of the simmers are encountering this error immediately after every sim update,& being this error very random afterwards;still this error may appear due to other conflicts, due to the other fact that some simmers are still encountering the error after trying this workaround, as level 1, & others whom reinstalled the whole sim as level 2, & others whom reinstalled the whole windows as level 3.
Conclusion: not overclocking your gpu, & resetting the settings by deleting the cloud save files for whom is ready to do that, can significantly decrease the chances of encountering this error.
so the workaround is workingspecially after updating to an update that have new implementations to graphics.
For whom still encountering this error after all, you can bet its a temporary issue as the sim is getting more solid beside its growing content each month \ s.
Happy simming for all, & special THX for MSFS Team 4 their efforts & incredible content that they provide to the sim.
Amen to that.
I did step upon this bug today again.
This time it was the first time while updating.
The Worldupdate 12 threw me into windowed mode (Guess only Asobo and MS know the reason for this and that it is by dedault.).
"Happened " to move my cursor over the “show desktop” at the bottom right corner of the screen. Poof. CTD. No errors in the eventlog at all.
Tried continuing the update while in windows mode after that (from the MS store). I crashed 3 times within 1 minute. 4th time I entered fullscreen mode and updated. 5 GB took like 90 minutes but it didnt crash and here I am…
Stable, not really. Good communication from MS//Asobo to community. Not really? Not much transparency as it seems.
I will rest my wallet until this platform feels more stable…
Well, seems like this bug from hell is back with a bang.
Feeling in a good mood as sun is shining in Sweden I felt for a flying session on the coast. But this message keeps coming back.
As always (for me), it seems its way more frequent before and right after an update.
I am seriously thinking of stop playing this game and find a better(not broken) one.
It rarely crashes in the menu for me, and never when loading. If I provoke it to crash by letting the windows program-menu becom visible in front of MS while in menus it crashes all the time.
Actually this “Design” is helpful, cz when updating sim updates, no one will sit infront of the sim in the process, everyone will comeback, or do multitasking, & here the windowed mode help you track the downloading process easily, while you are multitasking.
when the big download is done, just a click to swtich back to fullscreen, to enjoy the downloaded update, LOL.
its not about the downloader, thats ok.. its about the game where you configured full-screen, then an update is installed where the installer is windowed and then the former in-game setting ( my setting ) ‘that I want full screen’ is ignored and the game starts windowed. So, for me still a bug, but not realy important
We should try to help each other because stopping using the sim because of this bug would be quite sad.
Do you use MSI afterburner? Did you try the workaround of underclocking your GPU memory speed about 200mhz (might depend on each system) and pressing “A” (apply) ?
With this remedy my system went from “it will always crash” to “it won’t crash”, I’ve done 13 hours long-hauls without problems.
If you have tried it and still got the bug maybe try underclocking a tad more. Only GPU memory should be enough according to our experiments.
