Please, its NOT physical memory error … and everyone should stop rushing out and buying new, expensive Ram, in the hope that it will fix the issue. Its a Coding BUG.
Having said that, I do not presume to tell anyone “what they should do, or not do”, it’s your money and time - YOUR choice , do as you want with both –
(but don’t come back complaining it made no difference, as I did warn you !!)
.
That’s why it should be tested and preferably not just on one machine. My comment was specifically because of the zero address.
I am in the lucky position that I have different ram available I have tested MSFS with all of them and also with different clock frequencies it definitely has no influence on the error. How could it? You can’t fix a software bug with a hardware swap. If we had a real crash log maybe they could disable the service or whatever is causing the crash. What they are trying to do now is fishing in the dark nothing else maybe they will get lucky and do the right thing who knows. What I do know for sure is you are wasting way too much precious time on this.
That’s if it’s a software bug … because I cured it for me by resetting my gpu overclock back to default
I hate to say but the fact we have to do stuff like this and dig THIS DEEP. Is pathetic on Asobos and MS end. Sure bugs are going to happen but we as customers should not be expected to dig this deep to fix stuff Asobo needs to have dealt with. I don’t get this memory issue with any other game accept MSFS. That included P3D and X-Plane that have literally hundreds of GB in mods on top of them.
Becouse its clearly a MSFS problem no a customer PC problem
Im also done spending my free time on this. I’ll continue to read this forum every morning but I’m done debugging someone elses software
Exactly and it’s sad folks can’t see that. If it was a hardware problem more people would be saying it’s happening to all games. But even other people I know having this issue only have it with MSFS. Every other game/sim runs perfect. So based off that it cannot be hardware related especially when everybody from budget pcs to top dog high end pcs are having the issue and have done everything to try to solve it only for it to work for a while and then come back or it doesn’t work at all. It’s absolutely mind blowing that they claim they can’t recreate the issue when so many people are having said issue. We dogged the devs of cyberpunk for releasing buggy ■■■■ so why are we allowing Asobo and MS to get a pass? “It’s a flight sim” sure it’s a flight sim but it still
Doesn’t deserve a pass when the main issues people are having a CORE related. When the foundation of the sim is so unstable that even a console can’t handle it. THAT is not okay.
If its a multitasking timing issue, ( or possibly a “ntdll!NtWaitForMultipleObjects” issue), that I see all the time when analyzing my CTD dump files , then it may well be affected by GPU speed.
Notice, it’s the ones with fast systems, that seem to have more than their fair share of issues,
lit I have to slow down my ox just to play this. Then I’d rather not. Some people can call it what they want. I shouldn’t have to dumb down my pc to my a game work that’s just as new as my ox 
You pays your money you takes your choice. I am quite sweet with the 4fps less I get now in exchange for smoooooth even with high LODs.
Been crashing with this error twice today flying into Dublin
I will turn off live traffic=negative
Little Nav Map caused mine-had it running in background.
After weeks trying, I could end and land my test flight of 10:30h with the BAE 146, all the described in last posts plus instead of high performance energy plan, I set the Ultimate Performance plan hidden in Windows and not touching nothing in it, maybe reboot to be sure it is enabled.
I’ve been so frustrated with this error and many other CTD. so recently I tried to simplify all the settings. I use HP reverb VR, so in Vr setting I set it to high and 100% for all, turn off live stuff dull down data of other aircraft vehicle staff on the ground and turn off things like bloom. just had the basics activated and at high or 100% then with the openxr toolkit where I play to find the sweet spot that doesn’t get the overload error we all see. you could say but I don’t want to dull down my PC why should I not be able to get the full potential of my kick-■■■ unit. well you can drive your car on the highway in first gear at 100km/h and something is going to break. so think of it as using gears you need to find the cruising gear that allows your PC to run without breaking. I tried all the tips and tricks and yes there are bugs in the software but at least now I can fly and I assume with more power there is going to be a higher-level setting that reflects better quality imaging.
Asus Z590 MB
15 11600k
GTX 1080TI
32Gb ram
Samsung SSD
Folks, if you are on the open beta and still encounter this bug, please report it to the open beta forums.
There’s a worryingly familiar screenshot at DX12/DX11-- Several CTDs on Several Planes While Spawning (Solved: 3rd Party Mods Causing CTD) - Sim Update 10 BETA / CTDs - Microsoft Flight Simulator Forums and unfortunately the thread has been closed.
I suspect the lack of a mention of this issue in the beta release notes would suggest that it has not been fixed and the above screenshot would appear to confirm that.
Sad to see that it is still not fixed , I am unable to play msfs for the last few days because of this issue every time I try to do a flight get this error out of no where randomly its so irritating 
, don’t know what to do … Asobo please fix this …
Hmm…there is a mention in the release notes:
“Ongoing performance optimization work including fixes for several memory leaks”
Whatever this may be but yes, I think they still didn’t fix it.
I’m not overly sure that the CTD in the current version are caused by what might be normally termed as a “memory leak”, as for me at least, i see no increase in the RAM usage leading up to the CTD.
However, it does look like the sort of error that might be caused by a process trying to access memory that it doesn’t have allocated for its use. Maybe an out of bounds issue or scope not being handled correctly?
Hopefully someone will find the cause and fix it, as what has become very regular CTD, particularly after a fair bit of flying time, are far from fun.
