Since I bought MFS, just the one CTD after pressing the “V” key a couple months back. 
From what I have read on here, having 32GB of RAM is the gamechanger.
That doesn’t surprise me at all. Yet another reason I’m glad I have 64GB lol…
I’ve found that people with “only” 16GB in their systems are for whatever reason, extremely protective of that choice. Even after having it pointed out that it’s cheap and easy, they still want to argue that their 16GB is not only enough, it’s actually more than enough, so how dare you dispute them and recommend that they change?? Why that is I have no idea, my only guess (and it is just that) is that we’re dealing with kids whose ability to upgrade their systems lies in their parent’s wallets, and if the parents aren’t open to yet another upgrade, they’re stuck, so they lash out. But who knows if that’s even close to being a correct guess or not.
Anyway, just throwing that out there for the sake of conversation.
Well I have 32GB of ram 12TB of SSD storage and 11GB of VRAM and I still have crashes, so maybe it’s not the amount of ram?
same here. very frustrating. Usually occurs when messing with the G1000 or FMC. trying to adjust the flight plan or change an arrival have ended poorly for me. Recently added the Thrustmaster throttle quadrant, not sure if/how much bearing that may have…
About 50/50 at the moment. Reinstalled Windows fresh, the sim from steam as well, and still crashes. Started happening with the 6800XT drivers: “driver timeout”.
Never had a problem with CTDs except the VFR map bug a few builds back. 32GB ram, no overclock.
Loading saved flight files multiple times gives me the CTD.
Just a remark on virtual memory on SSD devices is a very bad idea. SSD provide fast access to data that are changed rarely and NOT frequently. So none SDD hard drives should take care of virtual memory, SSD devices should have windows and program directories but only data with a long persistancy.
12 TG SDD? Really? 32GB RAM is perfect for MSFS, no more virtual memory required.
And I suggest to everyone who is unsuccessfully trying to solve CDTs - after following all the recommended solutions - remove all the MSFS components (app + msfspackages folder) and make a fresh new installation. I know what you are saying, waiting again for the pretty long download and installation work…low bandwidth…why should I…
Well I’m an IT specialist and have build my own computers, developed operating systems, did test management and software development for 30 years and know all windows versions since 2.11 Everything works better if you start with a fesh installation without history. And back to MSFS, I had some issues remaining after checking even the deepest settings in the internal XML file structure of the basic simobject behavior and they were all solved through a new installation. So give it a try to be sure you have tried everything. Good luck and best regards Guido
1 Like
Yes. Exactly my situation with RX 5700 XT. Have now reverted back to last WHQL driver (pre-6800 series) and so far CTD’s are gone.
Edit: When these AMD “driver timeout” error reports popped up after the CTD’s, I did fill in the details and send to AMD. The more people who do this the more likely AMD will address it quickly. This is a clear case where CTD’s are GPU driver related I believe.
Depends on the plane. Business jets I don’t CTD much these days, but frequently have system freezes when working with the Garmin’s during flight. I have given up on the commercial jets. The TPM seems the most stable so far. The rest I don’t have much interest in flying so can’t say.
I used to fly daily with FSX but since MSFS2020 maybe fly once a week. Hope to get back into it, but for now MFS2020 is just too frustrating even with a super spec’d out rig. Going back to FSX is also painful, after seeing what could be. Hopefully one day MFS2020 will be there but for now it’s DCS.
I have had only 4 CTD’s in 100 hrs. flight time. Each time I was flying the A320. No longer in my “stable” stable.
This is indeed a sound advice. Coming back to windows after years of working with MAC, i thought things would’ve improved, but nothing has changed over the years. This is the price consumers have to pay for open platform that has to work with million combinations of HW/SW.
Having said that, I did reinstall Windows 10 fresh, reinstalled the SIM. Days worth of labor. And the very first flight, I crashed to desktop. So at this point, I am really pinpointing the issue to either the sim or the AMD driver that messed this one up bad. Prior to 6800XT and VR, I did not have a single CTD since August.
Lol. Crazy Ivans. Totally relate to that. Happens a lot on the A32Nx as well
That’s so true.
Discounting the handful i’ve had due to an unstable GPU overclock, with stock GPU (3070) I’ve had 3 CTD in roughly 40 flights, all around the 1-2 hour mark. All my CTD’s happened when making approach flight plan changes in the vanilla TBM.
I’ve never had more than one CTD in a day, and as per the earlier post I always restart the PC after a CTD.
0
I was having CTDs with the FlybyWire A320. However it’s been fine for the last 3 weeks or so. I had one random CTD in the A320 near Aspen. Just pressed V to check out the flight Plan before the approach before the red top VOR.
570 hrs of flight as of today, flights from 1hr up to 8hr, 3 ctd since August 18th, two were my fault messing with drivers etc and one was just random but currently on a 340hr run with no issues or ctd’s. What’s my secret, I wish I knew but I keep a very tidy OS, don’t run other stuff in background, other tha skypark and such, nothing in my community folder. The other thing to note is I mainly fly GA, I do the airliners in X-Plane and p3d.