MSFS Application Error - memory could not be read

[ivica78]

Sorry, my mistake. Error is: Memory could not be read

[MichaMMA]

if you ever seen “… written”, don’t forget in each case to check pagefile. There is realy a slightly difference in both messages and possible reasons. But like all of these kind of message, hard to find the root cause.

[ivica78]

OK, THX!!!

What settings do I need to set for pagefile?

[MichaMMA]

normaly is System-Managed ok, BUT ( yep, there is allways a but ) … it depends on your amount of RAM and more important “free disc space” ( windows not increase pagefile if not enough exist, there is a rule about that ). I think a test-case with a manuall setting like following would be fine:
16GB : MIN 16GIG MAX 25GIG ( or more max )
32GB : MIN 8GIG MAX 25GIG ( or more max )
( dont forget the restart )
Important is to know: with the min-value you ensure that these amount is allways available, indep. of free-disc space rule.

If the manuall setting will not help, then set it back to System-Managed… should be fine, at least if you own 32GB. And If you own more than 32GIG ( e.g. 64 ), then ignore the pagefile hints

[ivica78]

OK, THX. I will try these settings.
Thx for your support!!!

[sehnsedahamses]

Having 32GB and 16GBmin - 32GBmax pagefile did not safe me from this crash.

[Piccoloflyer]

it was “memory could not be read” last week error and CTD, this week I am getting “memory could not bw written” and MSFS CTD without me clicking OK to terminated the program, should I lodge a new bug

[Timur6260]

The randomness of this error drives me nuts. Yesterday three flights in a row without any problem (nice!) und today, after I changed ABSOLUTELY NOTHING I get three inside of a few minutes before I can even take off from the very airport I arrived at yesterday without problems in the same aircraft.

[sehnsedahamses]

No reason to worry, you can now even crash msfs with an halo spacecraft!

[MichaMMA]

dont forget that we come with @ivica78 bit out of topic… it was about the “…not written”, and not “…not read”.

@Piccoloflyer

“memory could not bw written”… should I lodge a new bug

there are some existing … MSFS Application Error - memory could not be read - #749 by MichaMMA

May be, at the end we find out that both relates together … Currently reported reasons for “written” was XMP mode and Pagefile. At least disable the XMP mode helped also some users within this topic too.

[mrnice1111]

i can also join now this wonderful club

[airwego1701]

Third CTD in a week. I’m all signed up now and waiting for a fix.

[OrangeRu1es]

I mean they released a hotfix for a small issue this week, so we can just hope that they will be able to do the same for this when they realise it is affecting a major section of the community, because I imagine there are lots of people who haven’t commented on the forum knowing that all we have to do is wait.

[Stratus903D]

yes but the problem they fixed but also had amazing 2 votes and not 185 like this one

Some training modules appear to be broken in the 1.26.5.0 update

Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it. Are you using Developer Mode or made changes in it? NO Brief description of the issue: basic training: takeoffs. when aircraft is taxied into position, instructor never authorizes the takeoff… just keeps saying “Let’s position the plane for takeoff”, as if it were not on the centreline, or some such thing. But plane is in fact perfectly on …

sorry 3 Votes

[JGL574VRG2]

The RAM in auto in an ASUS Z690 MB does not solve the errors to me either, the same, after 6 hours of flight in the middle of the Atlantic a complete freeze of the PC, thanks anyway.

All the people with those problem do not forget to vote the thread.

[Silvera1657]

This issue will not be fixed until Sim update 10 obviously. Making XMP disabled does not solve the problem because it’s so random and/or you are not trying a flight long enough to reproduce the issue. This is not even hardware related, there is something wrong with the code of the sim which prevents proper data writing on ram which causes CTD as soon as you get the error. There is only one thing to do at the moment which is to wait until Asobo fixes it, or we can load up a flight and pray that we won’t get the error.

By the way, disabling XMP may seem to fix the issue for some as lower MHZs limits the speed of memory access but i am pretty sure you will get it somehow when you try to fly another destination or eventually in a flight. Lowering in game graphic settings would also help a bit but you’ll never know.

What i would recommend everyone also is to update BIOS. It might affect RAM’s memory access.

[JGL574VRG2]

Maybe like select in energy option max performance preferred and select in advance option to never “disable-shut off” HDisks, USBs and PCI-Es, and other workarounds like sound and pagefile, and from only minutes of flight you can flight hours.

[TRUMPERAIR]

All newbies welcome to the club. Thanks for hitting the vote button. This memory could not be read issue is now under investigation by MS/Asobo. FINALLY!! Feel free to look back 700 posts to see the work around we all have been trying. Many of us have been here since April 2022!

[stuarticus]

I agree. It’s remarkably unstable.

[OrangeRu1es]

Anyone have crashes using windows 11?