I want to confirm, that rolling back my NVidia driver seems to have done the trick for me.
I rolled back (using DDU) to 516.79 and have not got an application error so far after having them on every single flight (or even on the ground) before.
So thank you for that advise @TFEV1909
Daydreaming at work today⌠what if this CTD had such an easy fix as the ntdll.dll crash⌠Quickly came back to reality, lol.
I think this says it all. â This is from another user
I think folks commonly have a misconception about what this bug is, and assume that it can be fixed atomically by finding a single root cause.
The reality is, the âmemory cannot be referencedâ error means that the program tried to access some variable in its code and found the variable was missing or overwritten. This can literally be any variable in any part of the code. Amongst literal millions of lines of code, you could be chasing down thousands of these that may happen almost never, or almost all the time, and they all depend on the conditions of the surrounding code and data. They may also be entirely out of your code, when something downstream in some driver brings bad wrong or bad data into a variable, and then your code tries to access it.
Itâs a super common and often crazy complex issue to diagnose and debug in modern size codebases, the proverbial needle in a haystack, except the needle moves when you start searching through the haystack, and may remove or add other needles as you go, some or all or none of which may be the needle youâre actually looking for.
-Matt
Yeah, he makes some very valid points. I read that a little while ago I think. Food for thought!
I have completed two 4 hours flights without the error, i have disabled all internet services except photogrammetry and bing maps, well no error at all, for wheather i have used weatherforce
Well, rolling back the GPU driver improved things, but did not solve the problem.
Just wanted to make a flight and even before pushbacl, the error message ruined my plans once moreâŚ
Maybe they should rewrite it all in Rust 
Thatâd prevent most if not all such errors, although it would probably royally upset the developers, whoâd probably not enjoy being told how to code properly.
I just had a recently very rare flight, albeit short, that i managed to avoid any of these CTD on.
I was flying a Fenix A320, with all online services enabled, from KBIS to KPIR.
Built a PC 3 weeks ago, so far Iâve gotten this error around 10 times. All at random intervals, scenarios, locationsâŚ
Iâm sorry to hear that, and that youâre a member of this âclubâ. This probably does not matter much, but what PC specs do you have?
i5-12400F
32 gigs ram running at 3600mhz
3060ti
We both have 12th generation Intel and Nvidia 3-series. Do you have DDR5? Iâm guessing you donât since DDR5 in XMP tend to run a bit higher.
Nah, Iâve got ddr4.
Nothing, I added that register line with some hopes, the same, a freeze this time after a pair of hours.
Check out the beginning of the thread⌠The âmemory canât be ready errorâ is related to a problem with the sound device configuration that gets caused by a couple of different Windows updates. Usually, it goes away if you properly set up the default sounds device in Windows-Settings-Sound. Make it sure it is an actual out out device like a monitor and not one of the motherboard mixers.
If that does not work, reinstall the video driver â yes the video driver â and check the sound devices again.
Some may suggest this is related to the Windows page file but that is not case.
No, state that like a dogma, is not correct, I have done all those sound tricks and nothing. Thanks anyway really.
I also have the âmemory could not be readâ-after just a couple of minutes in almost every flight now. First time I saw it was like a month ago when i was trying out the new Salty 747. Then nothing until now. Trying to sort it out with empty community folder, but no⌠not that easy. Changed my virtual memory page-file in windows, but it didn´t help. I also have a Reshader that opens Msfs from a .bat-file and that why I seem to get the error almost every time. Im not on SU10 Beta and my Nvidia driver is lacking a a few updates (512.95).
Sorry, but no. If it ever was that simple, this thread wouldnât have more than 1300 posts.
I also have ReShade but even without it and in 100% vanilla sim (safe mode) I get the CTDs. I think the sad although probably true truth is that this type of CTD often does not have a simple âquick fixâ, although some remedies might decrease the frequency. Unfortunately this CTD seems notoriously hard to troubleshoot, at least from the end-user standpoint.
if someone gets the error already when starting MSFS check your EXE.XML you can also remove it from the folder for a test.
I tried to customize my exe.xml for GSX today and got the error when starting MSFS.
I removed the exe.xml and the startup worked again without error message.
After rewriting the exe.xml now everything works again