Just did a short flight from EDDL to EDDF without any problems. Flying this route without debug mode was impossible.
Debug Mode on, Cap off and ingame Vsync to 60 FPS. GPU workload was around 93-97% but never reached 100% (or I did not see it).
Seems to work, but I will monitor further.
Additionally, the loading times from game start up and loading into the airport were much faster…maybe theres a coherence between loading times and debug mode or it is just random.
I think it’s random. I saw someone else say that Vsync increased load times, but my sim actually loaded 1 second slower with no fps cap.
this point I noticed too, also in other topics.
But if your system works fine if you reduce the OC ( and factory OC is still OC ) then its not application related. I also not need to revert the factory OC of my asus 2080TI OC.
What I would accept is a may be a nvidia driver issue related to 2080S , or realy stuff like for the 308xx user where many of these are faulty… A game / application can not overstress a stable system.
Hey Grzybciu, thanks for your suggestion. I tryed it now in a 90 min flight from Berlin to Munich and i had no Problems at this flight. (After SU9 i have problems with this “memory could not read” error. but this flight was fine)
i will test some more flights in the debug mode and watch if this CTD without error message dissapear.
it looks like something with the driver could be wrong as you mentioned bcs. i did not had that problem in the first year of the release from msfs.
i also tryed the 60 hz vsync but i do not reach that FPS maybe i will deactivate it for the next flight.
my pgu usage is often between 70 and 99% and the clock rates are 1935 MHZ GPU and 1937 Memory. without debug mode and active OC it goes over 2000 mhz.
This thread is about another error quinti. Its about a CTD without any error message. This memory crash is another thing 
(i got that too sometimes after sim update 9)
please see (may be vote) here…
currently we try to find out why some users get this and others not.
Today I’ve tried a full clean reinstall of nvidia drivers. Unfortunately that didn’t help the issue and I still get random CTDs if I run the sim without the debug mode enabled. Honestly, I’m starting to run out of ideas at this point.
I guess I’ll have to run MSFS with the debug mode enabled as long as it’s stable that way. I can’t really wrap my head around how just the factory OC on the gpu could make the simulator unstable.
Interesting - I’m using a 2080S (OC) and have exactly the same issue. Game will crash even in the menu with uncapped frames. Will also try the Debug Mode option and see if that alleviates the issue. Do you think its a driver issue that can be solved by NVidia or MSFS (which seems to be the only program that crashes under load!)?
Even after the Hotfix from today?
Also here memory crashes all the time can’t even take off it just crash with the memory error pop up.
Never had those before and it just unbelievable in SU9 after so much updates it just crashed without any reason.
These should be fixed ASAP!
(Also after the hotfix today)
Unfortunately, after two flights (uncapped with debug mode on, 2080 Super) without problems, I got a CTD while being on the gate in EDDL.
Didn’t realise there was one - but assuming it updated, it still crashes. Seemed fine in Debug Mode however (not that i want to leave it there)
I can’t really tell. I’ve done a full clean driver sweep and reinstall using Display Driver Uninstaller, but that didn’t change anything.
So far only enabling the debug mode or underclocking the gpu core clock via msi afterburner works (at least I didn’t get a ctd with it yet). But then again - @Housefrau3355 just had a CTD in debug mode (hopefully there was some other reason behind it 
).
It seems really odd to me that we all have exactly the same GPU and the only unstable app on our systems is MSFS. Is there any way we can bring Asobo’s attention to it?
Hey, i did yesterday 2 Flights with the PMDG 737. I forgott to activate the Debug mode and had no issues at all.
Now, a question for you. Do you activated the “Always High Performance” option in the Control Panel?
I set the default setting a few weeks ago. Maybe you should try that too?
I used to have it set like you did, but now I’m using the default setting as well.
I also have noticed that when using the PMDG 737 the sim seems more stable overall without the debug mode enabled, but then will crash randomly when I go back to menus. It’s kind of hit or miss.
Hey guys,
So glad I found this thread. I’ve got a MSI 2080S too. The Gaming Trio X one.
I’ve been getting CTDs on the Concorde in Singapore, Dubai and random places. And additionally, I hopped into the PMDG 737 yesterday. No crash on the first flight (Renton to KPDX). Second flight, crashed on landing (EBBR to KPCH).
And I just updated to the newest driver yesterday. I was thinking it’s a driver issue but I was getting CTDs in the Concorde in the previous driver as well.
Going to try the Debug mode and change the power management from “Always high performance” to whatever the default is.
If enough of us are having the issue, isn’t there a way to escalate this to Asobo and/or Nvidia?
Hopefully they will notice eventually. Please report how the debug mode workaround works for you. As an alternative you can also underclock the core clock via the MSI Afterburner (since you also use the Gaming X Trio, that should be about -30MHz). That’s what I use now so that I don’t have to enable the debug mode each time manually.
Did another flight yesterday an no CTD then. Maybe my last CTD at the EDDL gate was another reason…
I‘ll give it a try with -50MHz (just to be sure) via Afterburner on my 2080S Gaming X Trio
Underclocked on MSI Afterburner. Got a CTD again. Trying to fly from EBBR to ESSA.
Faulting application name: FlightSimulator.exe, version: 1.25.9.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.25.9.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001c0ce38
Faulting process id: 0x5438
Faulting application start time: 0x01d866d0a49a812e
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 1a91a0c9-9c10-4b0f-924d-58db35f9ab22
Faulting package full name:
Faulting package-relative application ID:
