Update 1.3/4/5
CTD with the A300 from KDEN to KPDX, after takeoff at about FL200
CTD with the PMDG 738, EGKK to LFSB, made it onto the runway at EGKK and CTD
CTD with the Fenix enroute MHTG to SKMD, somewhere over Panama
Update 1.3/4/5
CTD with the A300 from KDEN to KPDX, after takeoff at about FL200
CTD with the PMDG 738, EGKK to LFSB, made it onto the runway at EGKK and CTD
CTD with the Fenix enroute MHTG to SKMD, somewhere over Panama
I’m getting CTDs after SU14 in about every flight; even short haul flights from e.g. Heathrow to Schiphol. Sim seems to get more & more unstable after every update — any form of financial compensation would be nice as the sim is currently basically unplayable. As this CTD is number 350 in 200+ hours: thinking of saying goodbye to MS Unplayable Flight Bug and start playing an actual working Sim like X-Plane 12. Will file a complaint at MS for an unplayable game for a refund. Si is below any standard.
Every single flight I’ve tried today ending in a CTD, just fantastic, honestly. Well faölksdjföling done
Just to confirm I’m also experiencing this issues, usually after a flight lasting more than an hour, there is a stutter, the audio disappears and then boom, CTD.
I may try Nvidia driver 536.67 as suggested thanks. Bloody frustrating ![]()
I already tried that, didn’t work sadly, still CTD galore
Same issue after rolling back to 536.67.
Here’s my crash log
MSFSReport-Crash-691385916.txt (26.6 KB)
This may just be a coincidence.
I was having random ctd’s after varying amounts of time. A minute after takeoff, mid flight, right on touchdown. I usually set up a 40 minute to 1 hour flight.
I did an update on my bios which some how screwed up my wireless mouse and keyboard. They would start after booting then just stop responding after a few minutes.
I disabled power saving in device manager for the usb’s. Keyboard and mouse work normal now.
Today I did a 45 minute and a 1 hr 5 minute flight with out a CTD.
VR with G2 and fly the Carenado Cessna 337.
Nope just tried another flight of about 35 minutes CTD 2 miles from the destination.
Update: I’ve done 4 flights of 40 to 50 minutes since yesterday. No CTD’s.
I uninstalled MSI Afterburner because I will soon be getting A Pimax Crystal and there is a problem with afterburner and Crystal from what I’ve read.
Also lowered some settings. Grass, clouds,water,buildings etc. After watching a video comparing the low to ultra settings. Some don’t have that big of a difference. To me anyway. Gained 8-10 fps. I was usually around 30-33 now its 38-40.
Up to 5 1/2 hours with out a CTD. So either it was uninstalling Afterburner of turning things down a bit.
When the Crystal arrives I’ll have to experiment with turning up the settings little by little.
Thought I’d add some more experience to this discussion. Up until yesterday, MSFS was actually quite stable for me. Tons of bugs in specific features but CTD was very rare. Yesterday, I started experiencing sudden CTD at inconsistent times - during startup, during loading a flight from world map, after clicking Fly Now, at the end of a flight, clicking return to Main Menu after a flight. Sometimes after running for just a few minutes, sometimes after 30-40 min. Happened with a default DHC-2 and with FS Academy Jetliner tutorial.
These are new planes for me (DHC-2 and default A320) - I usually fly with one of a few payware planes from BKSQ, Milviz, JF. I’m assuming there should be less problems with default planes than with addons - not more.
I assumed it had to do with some new or updated addons, so I removed everything that had changed recently. That didn’t help, so then I removed almost all my addons, including ones that had been in place quite a long time. Down to a small core of addons that have not changed in a long time. (FSUIPC, payware planes.
So far that hasn’t helped. I never get an error message - the program just disappears and I’m back to desktop. I’ll probably try safe mode next.
I haven’t knowingly updated graphics driver but I suppose the OS or AMD software might have done so.
I’m not posting all my specs, as nothing has changed, but briefly Win 10 Pro, 32 GB dual channel RAM, 1 TB SSD dedicated to MSFS, Ryzen 5 5600G CPU, Radeon RX6600.
Actually - I realize there are three changes that could be significant. I added a third monitor plugged into the graphics card AND I started using spacedesk to use an android tablet as a fourth display. The second and third monitors are used for other programs (eg LNM, Navigraph Charts) and for MSFS toolbar windows (VFR, Navlog, etc). I’m not using the multiple display feature for the primary window. I also added Air Manager although I didn’t have any panels open yesterday (but the addin was still there). Clearly I should try going back to two monitors, no air manager and no spacedesk to rule those out.
I have been having CTD issues since May of 2023, which kept getting worse. It got to a point just recently, that I was going to literally give up on MSFS. I looked up any, and all information about fixes to the sim, and Windows 11. I tried for more than half the year. I just recently read a post about someone who stopped using the NVIDIA Game Ready Drivers, and used the NVIDIA Studio Driver. The Game Ready drivers are updated frequently to patch the latest games that come out. The Studio Drivers are supposedly geared to Content Creators.
The problem is that the GRD’s are not tested for absolute stability, whereas the SD’s are!. The SD’s absolutely HAVE to be stable, or content creators wouldn’t be able to produce much content. They generally make income from what they produce, so the drivers that they use, MUST be stable!
They are both essentially the same drivers, with little differences. I uninstalled the GRD using DDU, and installed the Studio Driver, and guess what?!
I have not had a SINGLE CTD yet!!
If you have an NVIDIA GPU, and are having crashes, try the NVIDIA Studio Driver!
That saved my browser crashes too!
Some data…removed Air Manager and Spacedesk. Completed an FS Academy tutorial returned to Activities menu with no problem. Went to start the next activity (Jetliner 2), hit the Fly button, there was a pause of several seconds and…CTD. No error messages.
So I guess I’ve ruled out both AM and spacedesk. I’m going to try with everything but FSUIPC and Better Bravo lights removed, see how that goes.
Update: I believe that the issue may have been due to Windows replacing the AMD driver. After reinstalling the AMD Adrenaline software and updating my graphics display driver (or rather, restoring the one I had previously updated), so far the CTDs are not recurring.
I’m well over 10hrs now without a CTD.
i9 12900 RTX3090
Got 2 hrs in the A2A Comanche that I was waiting to buy when the CTD’s were under control.
I’m only running Little Nav Map and FSLTL. And VR with a Reverb G2 until my Pimax Crystal arrives sometime today.
545.65 nvidia driver. The newer driver is downloading now, have to see what happens with that later.
Just had my CTD in a while, mid flight in the eastern US… No pause or stutter, or any other indication of a possible problem; the sim just shutdown… Restarted, no issues… These are so infrequent and perplexing, its just more of an inconvenience than anything else…
When I get a CTD I back out any changes I’ve made before the CTD happened. There are modules on the Marketplace that will cause CTDs. I have had stable play for months now.
Clean install, install one module at a time. Fly for awhile in the new module before adding anything new. If it CTDs, take it out. It you CTD on another module (not the last one installed), uninstall the last module you added. I hope this helps.
More than 24 flying hours before a CTD yesterday.
I believe it was caused by Little Navmap.
Before the crash the map was redrawing itself over and over then the CTD happened. On the screen it said Little Navmap experienced too many errors and had to shut down. Flew over 3 hrs without the Map running,no CTD. Last 8 hrs were with the Pimax Crystal.