Quite a few when I first got it then made some changes setting the priority to low and the affinity unselecting CPU 0 all was good got an update yesterday and 2 times it CTD so no flying till this one is fixed. frustrating to say the least.
Only after buying KSLC from the MSFS2020 Steam store. It doesnt work and causes an immediate CTD on my system. And Steam gives no refunds.
There’s a thread about an issue with 3rd party airports that CTD, I did experience the same recently
If you are in this case with KSLC, then you could try the workaround proposed, it worked for me
@ExpiredSpy56910, third party addon makers are generally pretty quick to issue patches for such things, so I’d say disable it for now until that’s done, then you’ll be fine. I haven’t bought that one myself yet, even though I “hearted it”, but eventually I will, so I’ll keep an eye on it.
If anybody notices when it gets fixed, could you please let me know? Thanks very much!
I’m off to goof with my new CRJ (I keep saying that…), no CTDs from it so far! But I haven’t even had it for 24 hours, so knock on wood…
In the last 2 weeks out of 27 flights, I have had 21 CTD’s. Its seems to progressively getting worse.
Had 2 or 3 since launch maybe, well over 150 hours in now. And haven’t had a CTD in quite a while now.
For me it very much depends where I fly.
In Europe or Asia I have maybe 1 every 20-30 flights. That’s a tolerable level for me.
If I fly in the USA I have one very other flight which makes it so annoying that I can’t deal with it.
I don’t know why this is but that’s it.
PS: it’s a sad statistic to make for this sim
None. (and this answer must be more than 10 characters so…)
The same thing happens to me
@RedBaron423, you put this reply into a thread full of dozens upon dozens of people who have reported 0 or very close to 0 CTDs, it doesn’t occur to you that some how, some way, the problem might be you? Not you as a person, but I mean your setup.
There’s almost certainly something about your rig that’s causing this. Something that’s too overclocked, or trying to run settings your rig can’t handle, not enough RAM (I think this one is big, but nobody wants to hear that), an addon that’s broken, trying to run the app on subpar hardware, or something. That list is far from comprehensive of what it could be.
It could even be something completely off the wall, I remember reading on this very forum about one guy who was having CTDs, and it turned out to be a memory module that didn’t have enough heat compound on it, and even though it ran perfectly fine with literally everything else, MSFS was enough to push it over the edge. How in the hell he figured that out is beyond me, but he did, and replaced the offending memory module, and his problem went away.
You need to realize that you are a statistical anomaly, that what’s happening to you is not happening to most others, and look inward, instead of lashing out and blaming someone else.
Just some food for thought…
(Now watch as this post gets hidden… Sometimes the truth hurts, and whiners don’t want to hear it.)
I’d never had a CTD during the game before the last week. Now I’ve had two. Both in VR, the first time the game just closed and my Quest went back to standalone mode, the second time the game froze in VR with a timer showing but it never unfroze. I couldn’t control/alt/delete out of it and needed to restart the PC.
The only additional third party mod I’ve installed recently is the Weymouth and Portland photgrammetry on Flightsim.to. But although both my crashes have been since then neither of my crashes took place in Weymouth or Portland. First crash happened on the way to Weymouth, about 25 miles out, and the second happened as I was flying over Brownsea Island in Bournemouth, having just spent an hour flying over Weymouth and Portland for twenty minutes or so and then being 25 miles past Weymouth so don’t think it’s that mod?
EDIT - just saw the post below me about AI traffic. I’ve always had AI traffic enabled and not had any problems before. If I keep getting crashes I’ll try turning it off, but I like seeing other planes.
Normally I don’t have CTDs, playing since launch.
Last two weeks I saw multiple CTDs, but it was because I set (by accident) to use AI Traffic.
Turned off and it is all fine now.
Stay away from AI Traffic.
Never had any CTD since I turned off my CPU overclocking
I think there are CTDs once in a while even now. But they have dramatically increased. I had one with the FBWA32NX. However I have had more occasions where the screen freezes completely and then remains frozen and I have to go to the Task Manager to kill the Sim. There seems to be no way to recover from the Screen Freeze. Anyone else having the ‘Screen Freeze’ issue?
I’ve not had one since the latest fix, knock on wood…
Until the France update (140hrs logged) I had 0 CTD’s.
After that update and the “hotfix” patch I had CTD’s on at least 50% of flights.
Since 1.15.10 back to a completely stable sim again.
There are hundreds of things that can cause CTDs, and as we’ve seen from this thread, most people have few or even none. However, if you are having them, the first thing I would recommend is to remove your overclocks. They’re probably not helping your performance in MSFS anyway, though they might in other games, so you might just have to remember to turn them off or on depending on what you’re playing.
If you’re an Nvidia user, removing the overclock is so easy, even a caveman can do it. Just use afterburner to create a profile with no overclocks, and switch to that when you’re simming.
As for CPU overclocks, well, that depends entirely on what CPU you have, and what motherboard you have, so there is no universal answer. But on my ASUS board, it’s as easy as going into bios, and changing exactly ONE setting. But if you’re not running an Intel K processor on an ASUS board, well, I can’t help you because I haven’t got a clue how to do it.
But even though I can’t help you, you might be able to figure it out for yourself, or somebody else here might have some assistance for you.
But removing those overclocks will make the group with CTD problems even smaller than it already is, and if that describes you, give it a shot. I promise it won’t hurt, and if it doesn’t help you can always turn it back on. But as I said, it won’t affect your MSFS performance (or shouldn’t, anyway) at all to begin with.
So give it a shot, there’s nothing to lose, and potentially having no more CTDs to gain.
Like 6 CTDs in hundreds of flights, it was all caused by a failing video card and it only seemed to affect MSFS at first. It was devilishly difficult to troubleshoot and track down, I’m glad that’s over.
MY CTDs after months of trying to track down the problem, which was sometimes as many as two a day, turned out to be the aircraft I was flying, the JF Arrow 3. The moment I stopped flying it and moved to another aircraft, the CTDs stopped and have not reoccured.
I had the screen freezes off and on with CTDs. Same thing, task manager was the only way to shut the program down once I got a screen freeze.