I think the CTD is solved. I turned the graphics settings back to high on 2560x1440 res. Set the rolling cache from 8 to 20GB. No overclocking CPU. Set a flight from London Heathrow to London City Airport, but flying around the density of London between 500 to 1000ft, eventually landing at the Orbx updated London City Airport. No problems, and seems fairly smooth, and shut down FS normally. It must have been the overclocked CPU causing the problem, and the low rolling cache didn’t help. Thank you ALL for the comments and help.
Your welcome enjoy!
Please mark the topic as solved so others will look here to fix their own issue. Thanks!
Since when is stable overclocking evil? only since msfs.
K processors are now evil and wrong says msfs.
Same goes for all mods, airliner aircraft, real weather, live traffic, a modem, a network, a brand new stable PC, etc. etc. All of these things are, at one time or another, a problem for msfs.
Its never msfs, its every and any thing else!
Are we sure this is not pre-alpha???
STABLE overclocking is not evil. But how many users on this forum are capable of achieving true, stable overclocks on the equipment we see here? And how can we even tell that an overclock is at fault considering all the other issues caused by third party software like LNM and Navigraph using SimConnect? Asobo constantly breaking add-ons with every update so that they cause CTDs? Conflicts between add-ons causing CTDs? Liveries causing CTDs? Modifying official aircraft files and causing CTDs and update issues? Incomplete updates causing CTDs?
Do you want to eliminate variables or continue to defy the guidelines of good troubleshooting? Do you want to keep your complex, unstable environment with its CTDs, or do you want to solve it and fly? Do you even want to fly and temporarily accept the cost of that, or are you just here to repeatedly whine and complain about things that others have fixed?
To all reading this thread – the OP found his issue and solved it. It was overclocking in his case. I’m not saying a stable overclock is an issue, but OP went through a LOT of agony for months having CTDs. He fixed it by removing the overclock.
My suggestion is that if you have continual, seemingly random CTDs, and if you have already tried removing mods and all those other things – doesn’t it seem reasonable to try removing the variable of overclocking? It’s not hard, and just like in OP’s case, it may solve your problem and allow you to enjoy flying!
1 Like
Removing the overclock as a solution is fine and dandy. But why do so many other applications do fine? Or the better question, why does msfs not accommodate stable overclocks? Its not like people all over the world have had so many overclock issues only to come to this forum to complain about CTD’s. I have never seen so many overclock issues in the flight sim realm and I have been flight simming 35+ years. Overclocked K processors have been the norm for flight simulation for many years, but now its evil to have a fast system…all designed to frustrate. Very few other software packages require more speed than an advanced full featured flight sim.
When or if the advanced aircraft add-ons arrive them overclocks will be necessary, but will they remain evil? A true make or break. This msfs will either remain in an unconventional and unstable pre-alpha state, or cut out the excuses and function on a broad range of (overclocked or not) systems like software needs to do, right?
1 Like
Head over to Pete Dawson’s FSUIPC forum.
Some really nice info there in the MSFS section which may be what is happening here.
And in those 35+ years, have you ever seen a sim of this complexity and graphical beauty? It’s a beast and imposes limits on even the highest of high end computers. You cannot compare this to other software.
This sim was written to push the limits of modern computer systems. The new Xbox probably has better specs than many PCs in this forum, and it is not going to be affected by OS tweaks, user mods, overclocking, running multiple applications, and all the other things that plague us. It will be a restricted, factory-stable, known good environment running the default sim and authorized add-ons.
Rather than push our PCs and add-ons to the raw limits, why not take a different approach for right now. Eons ago, posters on this and other forums were advocating dialing EVERYTHING back to the minimums, then slowly ramping up while absolutely positive to keep a stable environment. That includes no overclocking, because you can get way more performance boost by using fewer mods, lower graphics, decreasing CPU load through not running anything but the sim and turning off AI traffic, weather, etc. The objective is to get a stable environment as MS/Asobo intended.
That is awful, I know, but it’s just for right now. The future will bring more optimizations and better hardware. Think of the sim as fine wine – not you guys under 18! – and decant it. Let it breathe. Give it just one more year!
Then sip it – don’t gulp it!! It’s fine wine!!! 
the game runs for me at around 40fps on cruise and at small airports and I’m using msfs afterburner, the game randomly crashes, I’ve played many other games that I run at the same fps and it doesn’t crash like this, its definitely the game.
In those 35 years I have been able to run the sim without the worry that the autopilot would not work. Common and frequent CTDs were also fixed before release. CTD’s used to be THE huge deal to developers, with msfs its just another normal day. Stated features were also fully included on release, not so with msfs. A product that requires a plethora of workarounds and customer sacrifices/compromises…its not right. If this was early access at a reduced price, it would be an educated, fair, and moral choice on the purchase, or choice to be on a “journey”.
Graphical beauty is meaningless when I cant fly to/from MPTO, or rely on the AI to behave at least somewhat normally, or have an ATC that makes just a little common sense, or have the real weather function consistently,…and on and on. Graphical beauty here is only good for screenshots…this products main focus at this juncture; fooled tons of people, who mostly would like to get a refund but most cannot.
This thread and likely thousands of others just like it, along with the mostly 1 star reviews on the Windows Store are proof that msfs falls way too short for something that has been released. Never in 35 years of computing has anything that should have had promise (according to the hype), been such a blunder, and it continues to be a blunder. Perhaps in 5-10 years it may have hope, but a possible WW III could smash that hope and make covid look like fun. So who cares about a journey until its finished; we have no control over anything at all anyway. This journey should have been completed on Aug 18 2020…the CTD’s continue…its always the customers fault…its just not right.
1 Like
Again, the creator of this topic (the OP) has said he SOLVED his problem and no longer has CTDs. In his specific case, the problem was OVERCLOCKING.
It is illogical then, to state that it’s “definitely the game” when in fact there is proof that it was not the “game”, it was overclocking.
When you make an absolute statement like that, then if there is ONE proven case that contradicts it, your statement is false.
You guys get so mad when someone posts, “It runs fine on my rig.” I happen to agree with you if that person is saying that since it runs okay for him, it can’t be the sim. In most cases, I don’t think that’s what they mean. I think they’re saying that it must be something specific to your environment and use of the sim.
Right now, there is a known, acknowledged bug with Little Nav Map and any other external application / tool that uses the sim’s SimConnect interface to get AI traffic data. It will cause a CTD. That IS a problem with the sim and Asobo is aware of it, acknowledges it, and is fixing it as we speak.
That means that the sim might be the cause of a CTD for anyone using LNM, FSUIPC, Navigraph, and other tools. No one can logically say that the sim cannot be the cause of a CTD. And no one is.
By the same token, you cannot say that overclocking cannot be the cause of a sim crash. Look up “CTD” and read the many threads that say they solved the CTD by getting rid of overclocking. In one interesting case, it was flicker caused by a portable heater periodically turning on, causing the power to drop too low for just a millisecond. This had the equivalent effect of an unstable overclock for that millisecond. CTD.
Why did removing the overclock fix it? Because it brought the system back down into a range of power and timing where it had the headroom to withstand the brief oscillation.
Conclusion? Overclocks are ONE variable that MIGHT cause a CTD. Since that is a proven fact, and someone has already eliminated all the sim-related variables such as mods and external tools and so on, overclocking is the last variable and should be eliminated. What have you got to lose?
Back on topic. This creator of thread has posted that his CTD issue was solved by removing overclocking. In this particular case, it cannot be argued that overclocking was the culprit, and therefore MIGHT be the culprit for others.
The Sherlock Holmes character famously said, "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth.”
If we eliminate all other factors other than overclocking, then overclocking – no matter how much you claim that it’s impossible – problems with overclocking must be the truth.
1 Like
oh ok, I am using fsupc, I found it gave me some frame drops so that makes sense.
There used to be a SimConnect bug after first release where ANY third party tool or application caused a HUGE frame rate drop. That got fixed and we didn’t have any CTDs or other major problems until the December update. The FSUIPC forum – and I think it was John Dowson himself – figured out it was AI traffic queries that might be the CTD culprit, so he posted an INI file entry to disable that.
If you search this forum for Little Nav Map, you will find posts by the author himself saying not to connect LNM to the sim because that same SimConnect issue will cause a CTD. He says you can still use LNM – just don’t connect to the sim.
I found the same issue with Navigraph and its SimLink component. You can use Navigraph, but don’t ask it to should you the AI or live traffic.
Interestingly, LNM says it uses the old FSX version of the SimConnect DLL to maintain compatibility with other sims. Eventually, they are going to have to convert to using the official SDK because SimConnect.dll has been discontinued. SimConnect now refers to the interface as supported by the SDK.
I wish you all the best luck as you hunt down this werewolf thing we call CTD.
1 Like
Back on topic:
The truth is, this msfs is famous for CTD’s no matter what the cause. I say, for overclocking to be a “cause” of CTD’s in msfs remains to be a truth that could eliminate a bright future for msfs. Processors are likely going to get slower once again, just like they did in 2008. They will soften the blow with something like 2 CPU sockets (!!?? 
),“ultra-threading”, or some new cache feature, but slow is slow. The turbo feature will not likely be able to cope/keep up with all the add-ons needed to workaround all the shortcomings of msfs either. There are always excuses about cooling not being adequate enough. The same old useless bla bla.
So instead of blaming/burdening customers, just fix msfs; this should not be a novel concept. Too much emphasis on screenshots will continue to hinder worthwhile progress and the customers will continue to be frustrated.
okay, so I notice a number of people are saying remove overclocks and other externals that communicate with the sim. What if I said my pc is not overclocked and I don’t have anything connected to the sim? This just so happens to be the situation I’m in. Before someone says its your hardware, its not as this sim ran perfectly fine at launch and has just got worse and worse in regards to CTD. Surly this should be the devs top priority right now. Making sure we have a game that we spent hard earned money on to be playable?
Anyway, rant over.
Your rant is completely understood, this sim can indeed be frustrating.
This is a quote from a post a few above this.
It explains what is probably happening in your case.
I have this as well.
“Right now, there is a known, acknowledged bug with Little Nav Map and any other external application / tool that uses the sim’s SimConnect interface to get AI traffic data. It will cause a CTD. That IS a problem with the sim and Asobo is aware of it, acknowledges it, and is fixing it as we speak.”
That means that the sim might be the cause of a CTD for anyone using LNM, FSUIPC, Navigraph, and other tools."
Not connecting these apps to the sim helps prevent this.
AI aircraft affect this. Dialing the amount back if not using live traffic, or turning live traffic off should help.
If you have FSUIPC, there is a command you can put in that app’s cfg. file to remedy this.
That is what I did, with no CTD’s since (yet anway!!)
It may not be the best solution, but until this gets fixed (and it IS being worked on, they have a good handle on what is causing it) it is a work-around.
1 Like
Hello,
Thank you ExceededBull193 for this thread and setting what worked for you (and most likely others) as a solution.
I’ll move this topic to ‘Resolved Bugs’ section.
Quick note regarding posts that followed. We also understand how frustrating it is to experience CTDs while flying in MSFS. CTDs can be the cause of various reasons, we always invite the community to check our articles. In that case: https://flightsimulator.zendesk.com/hc/en-us/articles/360015893879-How-to-troubleshoot-crashes-CTDs (The overclock is mentionned there)
Our objective is the same and team is willing to enhance your experience.
If the overclock didn’t change anything about CTDs (or doesn’t concern you), please follow instructions given in the article, you may find a solution that corresponds to your CTD issue.
1 Like