MSFS Application Error - memory could not be read

I have the same type of error, after ca. 1 hour no matter which area of the world or which aircraft - CTD, memory could not be read.

For those wanting to help out tooā€¦

I have two CTD today with this message. Never happened to me before. Just add my two cents to the story.

1 Like

This error is also in the Beta right now?

You bet, same issues.

canā€™t believe if, theyā€™ll ever fix it?

this topic is for ā€œmemory could not be readā€ :slight_smile:

Related to ntdll.dll / 0xc0000374 is this the relevant topic: Constant CTD every flight now (ntdll.dll)

Pardon me wrong topic

But letā€™s hope the devs/server admins fixing one, will also fix the other. :slight_smile:

Would be fine, but the application errors are longer existing, than the permanent CTD.

Yup, but something, probably server-related, has led to them both increasing in incidence revently.

Hope springs eternal gor an early fix or fixes

I hope, but doubt thatā€¦ The memory issue is much older.

My hope was, that we can 100% correlated both issue, that the memory-issue also occurs because of the same reason as the new ā€œntdllā€ ( e.g. possible server, or what ever ) and we get a better glue about the reason of the memory-issue. But, the users which never before get the ā€œntdllā€ error or other CTD in general ( e.g. me ) geting only the ā€œntdllā€ and not the ā€œmemoryā€¦ā€ issue.

But I found your former post a good one, where you mentioned like " a missing pointer to a log ". Also because some users report, that the game not crash if they get the error-popup till they press the ā€œokā€ button.

( man, some times its realy hard for me to say in english what I want to say :rofl: )

1 Like

Youā€™re doing very well if English isnā€™t your first language. I hadnā€™t noticed.

Edit: 3 typing/grammatical errors corrected. LOL, you see, even native speakers can get it wrong. Iā€™m old and was on a small mobile is my excuse :slight_smile:

1 Like

Can confirm I have been having CTDā€™s related to memory being read the last two days also.

Just had another one, during my flight from EBBR to EGLL using the FBW A32nx.

Just had another one when launching the app. All weekendā€™s ctds were not memory related but had no error message at all.

I had another one right now during my flight from Auckland to Nelson somewhere over the sea at 11.000ft. Just for the record.

Guys, next level is getting the game crush without an error. See you at the other topic;

I did wonder whether this CTD might be causing the ntdll.dll file to become corrupt, but iā€™m sure the devs will get to a fix pretty quickly.

1 Like

Idk know anymore