I am running VR with most items on Ultra. I’m going to turn everything down a notch and see if that helps. I am a programmer and believe they actually have an issue with the program itself. Aside from that Grand Canyon example, most of my CTD’s happen on approach. I see many people with a similar complaint. Nothing like flying a whole trip and getting CTD right at one of the funnest parts. Over…and over…and over. Something in the rendering I’d think OR maybe it just doesn’t play well with these latest gen of Nvidia cards or something. Not sure. I’ll resort back to X-Plane for a while until SU12 comes out and maybe they’ll have it resolved. The x-plane graphics are no comparison but at least it doesn’t CTD.
1 Like
Also after reading several people talking about audio glitch just before CTD, I’m guessing the audio drivers are unrelated. I specifically listened for that yesterday and they are right you do get an audio event just before the CTD but I’m thinking that’s just that the audio is the first to detect the CTD then the sim CTD. It’s literally not even a second between that audio glitch and CTD.
That’s how mine happen. It’s not so much audio glitch as it is stuff freezing up (audio included) right before crashing.
Anyway, my last CTD report (way above) is when I finally had enough and quit flying. I’m hoping that something gets fixed with the next SU and will try again after that.
1 Like
Do you have the same issue if you follow the OP’s steps to reproduce it?
No
Provide extra information to complete the original description of the issue:
Super stable until today 11900K 4090 32 GB 4000 mhz cl16 ram
If relevant, provide additional screenshots/video:
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
One reason I think this is actually a problem with the core program itself was refreshed to me the other day.I did try putting some of my settings down (turned TLOD down to 100) but still CTD about 10 miles away from my destination.
Yesterday I did a pretty small flight from KORD to KDAB. I few around Disney world for a bit, landed back at KORD then switched from the 737 back to a GA aircraft and went to Daytona Beach. Flight went fine. Landed. As soon as I ended the flight and hit the button to go to return to main menu, CTD. This has happened several times.
1 Like
I have CTD/Freeze when I try to reload Second Flight Plan on the CRJ 700 from Aerosoft. I had 4-5 Months no CTD or Freeze (PC)
Ok so I’ve waited patiently for SU12. Haven’t had a crash free day in months. I did my ut52 to Kgcn flight since it crashed to desktop (or whole system sometimes) 100% of the time. Got about 60mmiles in and crashed but this crash was something I saw talked about in beta forum with having a breakpoint. One person suggested letting windows automatically adjust page file. Mine was already set like that so I instead set it manually and fattened it up. Tried my flight and it successfully made the flight. Just to back it up, I did it again. Successful. Then I decided to fly back to UT52 and it CTD sitting on the runway. Progress I guess.
Funny thing is: this is a high end machine. I’ve got 64GB of ram. I would think the page file would never even be touched.
Taking off now for another flight that crashed last week. We’ll see how this goes. 291 miles. Wish me luck!
But it’s not just MSFS, Windows and probably Direct X also use it in the background. I have a fixed 15GB on C: with it disabled on all other drives, never a problem.
Well…just flew an hour and a half. Two flights. Zero problems. Skeptical…but happy so far! I definitely could not have done that 2 days ago without a CTD.
Just to add to this post. I too have been getting the same issues with CTD after 30 to 60 minutes into flights. It does seem to be worse since SU10 for me. I also found that a dump file is created upon these crashes, FlightSimulator.exe.19796.dmp, which I found in my AppData/Local/Packages/Microsoft.FlightSimulator_8wekyb3d8bbwe/ folder. Not sure if the same for everyone, but you should be able to just do a search for the .dmp file extension. I have submitted the dump to asobo via the crash report so hopefully they can interpret what may have happened.
3 things come to mind. Too high temperatures, unstable ram/vram or flaky internet/wifi however there are other possibilities such as bad addons, wrong time zones etc.
I haven’t flown since December because of the CTDs. I was waiting patiently for the SU12 update to come and when it did I updated. MSFS had forgotten my flightstick and rudder pedals so I had to move them to a new usb ports to get msfs to recognize them (basically just swapped their ports) and then reconfigure them.
Set up my same flight KTHA to KTBR. Spent nearly 3 hrs. on the ground at KTHA and flying to KTBR only to have a CTD on my approach about 2 miles before final. Same CTD, short quick stutter and then boom to desktop.
As you can see from all my post in this thread which I started, I’ve included a ton of info and testing. It’s not temps, ram, addons, etc. I don’t know what it is but it’s extremely frustrating. My machine can play other games that push it to it’s limit with no problems for hours on end, but it’s something about msfs that does this.
1 Like
For me the CTDs have reduced a lot on Xbox Series X after the AAU1 and SU12, but the Black Screens phenomenon has increased A LOT!
On my steam install, the crash dmp file is found at C:\Users\username\AppData\Local\CrashDumps\
They’ve made the crash and technical support form very hard to find, but you can go directly to it at https://flightsimulator.zendesk.com/hc/en-us/requests/new
Well….so I realized that in fact my temperatures have in fact slowly been creeping up over the last few months. In the last week or two I discovered my peaks were hitting 99-100c on my I9-11900K. I really attributed it to Flight Sim just gradually getting more taxing on the system. So I replaced my 240mm with a 360…and it cut my temps in half. It rarely taps out of the 50’s now under full load. I flew all over the place the last few days and got zero CTD. While temps were pretty hot over the last few weeks, the months prior weren’t hitting 100 they were like 70’s and 80’s under load which I would not think would be warm enough to cause a problem. So not sure why those temps would cause CTD every day but fact is with temps only peaking in the 50’s it’s been trouble free for two days now. I’ll push it some more over the next few days and see how it goes.
Confirmed problem free now. Flew fir a few hours today. Worked perfectly.
1 Like
About a week ago I switched to DX12 with DLSS. I have flown several 2 hr flights since then without a CTD. The other good thing is that my FPS went up from 25 to 30 to 45 to 60+. But the downside is Stuttering, it gets really bad over large cities at low altitude. Something to do with VRAM maxing out. Hoping for a fix in the next update. The stuttering is bad sometimes but not as bad as a CTD.
According to Task Manager I am not maxing out my VRAM. It says I am running about 80% usage even while the stuttering is going on. I also discovered that all I have to do to avoid stuttering is to climb to 3000 ft or so as I pass over these large cities. For the last week or so I have been flying in Australia and New Zealand. When I get back to the US or Europe I will try it with some much bigger cities and see if the plan holds. Still it’s going to be a big problem trying to land at one of the airports.
Same here… I stopped playing in December last year because i can’t complete a flight longer than 2 hours without getting a drop to 5ps. Good to see Asobo still haven’t fixed the problem 
I ended up doing a reset to MSFS 2020, and so far I’ve had no issues.