Thats a sure thing.
1 Like
Itâs a PC and you want to talk of logical? 
But honestly reading this even such mundane stuff like peripherals could have an impact even if ostensibly they have nothing to do with graphics
Based on this another research paper, this issue appears untroubleshootable on the userâs end, & is a programming issue on modern hardware designs.
link for the full file:
I wouldnât say this is an âissue on modern harware designsâ because it only happens in MSFS, it is a bug, we might try anything we can to mitigate it or reduce whatever it triggers the bug but in the end it has to be investigated and fixed by the devs.
2 Likes
100% Agree.
for whom likes to try different workarounds for the issue, this may help: renewing the dll file : GFSDK_Aftermath_Lib.x64
link:
gfsdk_aftermath_lib.x64.dll free download | DLLâfiles.com (dll-files.com)
file location to replace for whom is able to access the simâs files (steam users):
C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator
but I have often other applications opended in parallel. Usually the browser, which known use also gpu hardware, but also other applications⊠Of course we often recommended to test without other applications running in parallel, just to find out possible problematic ones, but I would assume much more users which report issues if that would be a general issue.
1 Like
iam too using multitasking while the sim is opened, never had a problem, the crash scenarios i encountered were different, but the research papers i posted a screenshots from, points to a possible effects on âgpu virtual addresses translationâ the cause of this gpu CTD, so i liked to share them as a basic knowledge not official examination to the simâs gpu addresses translation failure itself.
2 Likes
It happens to me yesterday - the error caused by typing mistake in Nvidia Profile Inspector so my fault 
2 Likes
Well exactly, itâs not going to affect everyone. Itâs almost but not quite funny how everyone thinks they have the most stable PC in the world but then a little bug like this can turn their world upside down. But the real good news is that this is likely to be remedied soonest because it really has gone on quite long enough.
3 Likes
I eventually cured this persistent and very annoying problem by biting the bullet and simply dialling back my overclocked GPU - 2080ti - by 100 Mhz or so, using MSI Afterburner (it was running at 1920, now at around 1800). Iâve noticed no difference in overall performance (although I run it at a fixed 30 fps, and if anything, it now runs smoother) and Iâve not had the error message for a couple of months now.
Why it only started back in September, I donât know, but as everyone says, it would be nice if Asobo found out the underlying cause and fixed it.
By all accounts the problem has been found (see above) so presumably a fix is being worked on.
Itâs not down to Asobo but more to do with MSFS not having strict safe performance caps which to be quite honest nobody wants. The time for that if ever would be before final release and thatâs a long way off yet.
1 Like
Where is the rference to the problem being found?
Thanks!
Ok a bit of presumption on my part but the two white papers a few posts up ⊠hopefully they provide enough information for a fix to be found
No, they are just papers, OP posted them in good faith but might be completely unrelated to this.
Maybe maybe not but we can all hope. I have long maintained video memory management/clockspeed is the main culprit and this seems to be right up that street. Even if itâs a windows/microsoft dll runtime error itâs vram where it actually hits us.
1 Like
The frustrating part is that after having the CTD for a few weeks, I did something and spent most of February CTD free, then NVIDA has an update to the driver, and WHAM back to CTD that happen about three minutes into taking offâŠ
i agree.
the thing is this is not totally a bug, or a programming error, its kind of conflict in the simâs performance behavior, since this CTD is happening only to MSFS, it means somewhere there in the sim can be tweaked to resolve this by the devs, hopefully.
as a small example, Hogwarts Legacy can hit 15 GB Vram usage @ max 4k settings with 100% gpu load with 70-90 c temp an average, without a single crash, & up tp 48 GB RAM with Virtual. however, experts from TechPowerUp revealed that some bad implementations leads to a performance issue in the game.
this is just a concept of how small things if tweaked right, the performance can always run right.
Link for reference:
Hogwarts Legacy: FSR 2.1 vs. XeSS vs. DLSS 3 Comparison Review | TechPowerUp
a game never implement a âperformance capâ , why ?
If the system crash in high load, then it is not the application which is possible faulty . It is the system : a piece of hardware, a wrong setting, whats ever. If that is ensured the reason for the popup, then it would also explain why only âsomeâ users get it and not all - the majority have a issue-free-system.
I have the exact same problem and reverted to Nvidia drivers 517.48 and so far no crashes anymore.
Yes thatâs one of their most stable although those following it are slightly quicker. Just donât try to hang on to it forever or future features wonât be supported etc.
1 Like