I had it and I cured it by dropping back to 3600MHz. I’m not going to be a test bed for everyone else though. After the upgrade I will test it again at the higher speed.
1 Like
That’s your prerogative, but remember that position if you post about a bug, and want others to corroborate. The community works best if everyone helps.
1 Like
Alright you win! … half an hour with disabled cache is all I giving you and it wil be in a default aircraft with no add ons. 
1 Like
Well that didn’t take long, as soon as I switched to the Cessna Caravan I got kicked out whereas previously it has always been in flight. I wonder if Windows 11 has anything to do with it? … My rolling cache theory was only based on that none of my other apps use it. I could always be wrong.
Quite possibly. Windows 11 isn’t officially out yet, and thus not supported. If it works for you, that’s great, and useful testing, but if you go to MS/Asobo for support they will likely tell you to install Windows 10 before they help.
It may not be anything to do with Win11 at all, but that would likely be their first request.
I agree … and at least I know how to fix mine
1 Like
Uh huh! now GTA kicked me out of their benchmark precisely as the jet was flying towards the city which also possibly means cache flushing or loading problems. I am definitely pushing my ram to it’s limits but that didn’t happen under W10.
Think it’s back to safe territory and 3600 meg for me
1 Like
It does sound like you are hitting the limits of what you memory is happy with. It could also be voltage dependent. It’s also one of the reasons why the general advice is to remove any overclocks as part of an attempt to regain simulator stability.
For my crashes the vast majority have been down to some known issue, or at least heresay from many people. For me my crashes were predominantly GPS mod dependant. Turn off airway messages, and the problem goes away.
But it does leave a couple which as far as I am concerned are as yet unexplained.
If I fly the Arrow, and I have both the 530, and 750 mods active at the same time, even if the plane spawns with the 750 loaded, and I haven’t been shuffling through the GPS’s via the pad, the sim will most likely crash at some point. It’s not guaranteed, but it does happen enough for me to suspect it. The error messages in the event log seem unique also. If I ensure that only one of those mods are active then I don’t get crashes.
The other one, which Zendesk neatly closed down, and considered solved when I posted my workaround, was regarding crashes while on group flights with lots of other people flying a plane I did not have loaded. In that particular case the majority were flying the 152 backcountry modded plan. When I was anywhere near the pack, I got stuttering. When I landed at one stop, and taxied over to where the group was the sim crashed. It did this twice. On the second crash I downloaded the modded plane, and spawned in it. I had no stuttering, or crashes for the next two hours.
I think that last one seems to be a variant of the issue where planes you have minus a community livery caused a crash. In this case, it was a plane mod for a default aircraft. So in effect I had the 152 installed, but not the liveries the mod ships with. This was never acknowledged as an issue.
I think this is a unique scenario. If I fly with people that had a plane I haven’t bought it’s not an issue. But a modded plane, which appears as its own individual plane to be selected, plus its own liveries, is. An example of this might be a group flight of those with one of the GotGravel mods. If everyone was flying the Vertigo, but I didn’t have that mod installed, because I have the default aircraft installed on which the Vertigo is based, I would likely get the stuttering then crash. It only seems to occur when in the vicinity of a large number of them, though. Like errors are piling up in the SDK window, if you had it loaded, and you have no way of viewing or clearing them if you don’t.
independent of that we come really out of topic.. I can’t believe that there is any difference noticeable by human eyes in case 3600 → 3800 RAM speed 
2 or 3 fps at most however with a system like mine that is sink or swim territory. Makes the UI noticably snappier though, not that it’s ever been slow in the first place.
Just got another sim crash with no message. If they aren’t going to fix them, and god knows I hope they do, then they should at least…at least…have a “restart where you left off” option.
EDIT: Two CTDs this morning. Ugh!
3 Likes
I am sorry to hear,when msfs works it is great but it is very unstable, mine completely quit a month ago. No solution insight. Bad bargain! Poor aftersales.
1 Like
O boy are you serious, is this the way you deal with a paying customer 's legit frustration about a non working product, i paid about 700 euro’s for this game, in game store add-ons and add-ons from Aerosoft and Orbx, and that is only the software! That’s all gone now because the game does not work, thanks for your kind and understanding words Hester40MT!
Have you tried this?
thx for your reply, i tried all things zendesk advised, at the end even reinstalled my pc/win10 (losing my log’s)
Also tried on second desktop it simply wont go past castle pic (does not even install) only CTD.
So you have <32GB memory, and you have adjusted your virtual memory as advised? With respect, you said you tried everything that Zendesk asked you to do, but I asked if you tried that, not what Zendesk asked, and in my experience I would be surprised if they suggested that.
16GB users often have issues like this, effectively running out of memory.
Perhaps a list of your hardware components would help? Just the PC not the peripherals.
You may not want to hear this, but there will be something about your system that the sim doesn’t like. In the absence of fixing the sim to not do this, we have to tinker with the system so that it doesn’t crash any more. That might involve buying more physical RAM, or playing around with virtual memory, for example. Or it could mean flying without any community addons for while. I know in your case the sim crashes before you even get to fly, but I assume you tried emptying your Community folder as that is one of the things Zendesk will ask you to do.
1 Like
Thx again, it was working perfectly on my desktop since august 2020, all of a sudden it stopped.
MY PC i5 9600k
32gb
nvidia 1060I 6gb
win 10 fully updated
drivers updated
So it may not be the memory issue that some users have. It could be Nvidia driver related, though I don’t know off the the top of my head what error you get for that. The error you listed was definitely memory related.
If you have re-installed the OS, and you still can’t launch the sim, either there is something with your hardware causing this, or there is a piece of software that you are installing each time that is causing it.
Can you confirm you did try launching the sim without any community mods installed? None at all, not even ones you think aren’t the causes. Nothing can be ruled out at this time.
Given the error, my money might be on a faulty memory module, based purely on the error message. Does you motherboard offer a hardware memory tester in the BIOS? If not there are software solutions:
Also, are you running any overclocks? In this case, I would remove any XMP profiles you might have active, just for testing purposes.
if possible please make a screenshot of your windows virtual pagefile setting ( Crash to desktop without error message - #4335 by MichaMMA )
Also check your free amount of disc space.
And may be you can post the exact error message from windows event log ( 800xxx3 stand usually for memory , but who knows ) .
Let me detail the situation a bit,
I see msfs in the store, it says i own it.
i can download an install it from the store.
On first run msfs should go to download and install the content.
I never get there because shortly after the first scenery screen (the castle pic) appears i get CTD. on both of my desktop computers. The pc where i tried to install msfs first on was/and still is completely clean fresh installed/updated win 10. On which msfs ran since aug 2020.
I read about the memory and tested it it was fine.
As i cant install there is no community folder or any other leftovers from previous installations.
Naam van toepassing met fout: FlightSimulator.exe, versie: 0.0.0.0, tijdstempel: 0x60c0b1e3
Naam van module met fout: FlightSimulator.exe, versie: 0.0.0.0, tijdstempel: 0x60c0b1e3
Uitzonderingscode: 0x80000003
Foutmarge: 0x0000000000734619
Id van proces met fout: 0x2624
Starttijd van toepassing met fout: 0x01d77a717727e0e3
Pad naar toepassing met fout: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pad naar module met fout: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Rapport-id: 2ab71132-cef6-4215-9f6d-d88e060653c4
Volledige pakketnaam met fout: Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe
Relatieve toepassings-id van pakket met fout: App