I am having my rolling cache on another drive than I have installed the sim on. Could this be an issue? Or maybe have something to do with swap-file-location?
If the memory-consumtion trigger it and the pagefile can´t deal with it? In the first place you would hope for your RAM to handle it, but what if the consumption all over is very high up and those that does not crash are those with a working page-file?
Just figuring…
I think the sim is causing some kind of memory-leak. But why is really hard to pinpoint as it is as you say. I can happen in most odd stages on startup. In my case mostly randomly when flying. But for some days it occurs in main menu before I have even chosen plane and where to fly from.
Not sure, but for me I can reproduce the issue consistently and when enabling Debug Mode, the issue goes away.
I’m not convinced on high memory consumption personally, but thats just my opinion.
Many graphic card makers overclock their gpus but these are not guaranteed to work with every app and if they had to be it would likely mean reduced performance for everyone… MSFS does not like overclocks so anyone unsure of their Nvidia chip’s default frequencies can check here
NVidia Graphics Card Specification Chart - Studio 1 Productions and David Knarr
I abandoned MSFS a few weeks ago but after the last updatd have had two flights in the PMDG Boeing 737. Last night, however, I wasted 2 hours of my time LOWW - EGLL. Got within 70nm and AGAIN the dreaded graphic message and crash.
I don’t believe there is any commitment to solve this problem and am unimpressed with Asobo/Microsoft while they continue to expand this product with the sole reason to get new players and tberefore more cash. After all, this has been Microsoft’s attitude throughout the history of Windows.
It’s a shame that due to no serious competition as far as gaming is concerned that this dreadful company has managed to continue to frustrate players for so many years.
In the army we always secured our current position before advancing further. Replace secure with abandon and you have Microsoft.
EDIT: What made me so angry was when this thread was reported to have being SOLVED !
I think it’s unlikely that it’s the drivers, GPU memory clock speeds, or system memory fault in general. I myself am using a 3090 (FE w/o OC), 10900k with 32GB. Neither the GPU nor the system RAM overflows the memory - the utilization of both never reached 50%. It is also impossible for temperatures to be the cause, since these are also far below their max GPU/RAM values. Also not unimportant, the problem (for me) only occurs since update 10. In short - as others had already noticed using the latest hardware, e.g. 4090, etc., the problem also exists. In addition, it can be assumed that after the first appearance of the supposed OC-error message, everyone reflexively first rolled back any OC. I think this information should be the core that Asobo/Microsoft should start with.
Try the steps on the post here: Warning: Your graphics device has encountered a problem - #1981 by Donga120
It’s not a proper fix, but does allow me to actually play the game rather than wasting hours into a flight and then getting the CTD
Is anyone getting this issue in VR? I only get this in VR mode. When I’m in 2D it’s fine - no error. Tried all the fixes that have been suggested. Interested to hear from other VR users.
Regarding my machine, I had this error message one or two time only, at the beginning of S10 deployment. Never saw it again.
At that time I didn’t have any OC on CPU, and a GPU OC of +100MHz Clock and +500MHz memory.
Right before SU11 land, I decided to set the CPU OC of 5Ghz I had put aside months ago, only when running MSFS, and raised permanently the OC on my GPU +125 / +900.
I still not have this error message.
So it seems MSFS don’t have any issue with both my OC. I guess I’m lucky 
(for now)…
Me neither nor overtemp but for me overclocking is the only way to get these errors … IMO it’s probably a sync issue due to the uncapped nature of MSFS… and personally I don’t want any performance capping as for short(ish) flights my overclocks don’t CTD. It’s easy enough to turn them off for longer journeys.
Note: Asobo have not said this issue is neccesarily caused by overrunning total vram but only the expected amount for the gpu and data involved.
My guess is you have fps capped and/or your gpu is rarely at 100% usage. Also cpu overclocks are not relevant to this particular issue.
You’re right, the sim is capped 60fps as I have vsync ON, and my MSFS settings are made to always give me around 10% to 25% GPU headroom (so 66fps+ without vsync).
In my case, it absurdly never happened in VR, only in 2D and often on main sim screen. Absurd. GPU temp is nothing as well as Vram usage in those moments. While during VR session, GPU stresset at top NEVER happens.
Tried to roll back GPU drivers of 1 version, better. But not solved.
Anyway, before SU11, in my case, nothing in Community, it simply NEVER happened, same settings, same everything else.
100% is sim issue and not at all a GPU issue.
Just my 2 cents…
I will add something strange here just in case it helps somebody.
The way this bug works in my system is: Sim freezes for about 1-2 seconds sound goes (brrrrr) then the error pops out and the sim crashes to desktop.
Now something curious: Once it crashed my desktop doesn’t look exactly as before, colors are now washed out, so it seems it leaves the Nvidia driver in some kind of different state?
If I now use the sim in this state the error does not happen, I get the 1-2 seconds freeze from time to time but the sim survives, no CTD.
I would say that with the Nvidia driver in a “fresh” state, for example after a reboot the error happens in 50% of the freezes while after it happened once it only happens in 5% of the freezes or even less.
I get these freezes about once every 1 or 2 hours of flying, sometimes less.
I have no conclusions about this, only sharing in case somebody can figure out what is going on.
When an rtx Nvidia driver crashes it always tries to recover (and does otherwise you’d BSOD), this sounds like only a partial recovery. The brrrr is often a sign of memory crashing, in this case vram as ram would normally BSOD aswell.
Thanks! I know nothing about GPU drivers but what you say makes sense. My conclusion from what you tell me is that after a partial recovery the bug is less likely to happen (by a huge difference). No idea why, but maybe a hint about what is going on.
So different it is that If I have recently rebooted and I need to make a long haul flight, I randomly fly before until I get the error and then launch the long haul knowing it will likely be completed without problems. It makes no sense, except that it works for me.
The best I can suggest is to visit your mainboard manufacturers site and look for any updated drivers … bios too if you feel you’re competent enough (it’s not so difficult but follow instructions carefully).
Unlikely this has any effect as the bug-problem only happens in MSFS, it is clearly a sim bug not something in the user’s end, it happens to a lot of different users with different systems.
While the bug is not fixed we just try to find ways to mitigate it or make it less likely to happen but it seems we don’t have a clear conclusion.
MSFS is a non sandboxed MIMO title trying to sync several data sources from many combinations of hardware at variable speeds all in vram, to describe this as a bug is IMO pretty unfair because the only real cure is likely to be downclocking everyone to a safe limit whether they suffer from this issue or not.
It may be wrong to call it a bug but to me if it only happens in MSFS then it is a bug in MSFS. I’m not overclocking or doing anything strange, and all the other things I run on the same PC work perfectly without ever seeing this bug. I think there’s something that needs to be fixed but I might be wrong about that.