MSFS Application Error - memory could not be read

If that is asking for help, you might have to give a little (LOT) more detail as to what you mean by “Cannot start any flight” –

I’ve just tried changing my in game audio devices to the one I’m using. Rather than leaving at system default. And that seems to have stopped this crash. I’ve only done a quick 20 min test flight. But previously, I could get the sim to crash within a few mins by looking around in the cockpit.

Not sure if this a fix without more testing. But it seems like a good start. And worth a shot.

2 Likes

Yeah, thats true.
I found the solution in my case. I checked the eventviewer and it says something about d3d11 error.
I reinstalled the driver clean, and now its working again.
Was working with the driver before the hotfix for su9

I will try this out.

But it looks like the problem still occurs after the fix.
So your approach could probably work.

I was able to reproduce the problem very quickly by switching from 2D to VR several times. Let’s see. I will report back.

Hello everyone. Sorry for my english. I had the problem until a week ago and was able to solve it stably for me. I changed the memory frequency of my RAM in the bios from automatic to a fixed clock below the highest possible. So instead of 3000 only 2666 MHZ. since then the problem has not recurred. maybe that will help you too. best regards

i tested this and sadly for me id does not work

I saw in my windows event viewer under general that at the same time with the application error was a nvidia display error.
So there where no blackscreen, artifacts or something like that before the memory message appears.

Maybe someone can check if he get this error too?

I did a new installation of the nvidia driver (no beta)

Right now iam in a 5 hour flight with the pmdg737. Iam now 2 hours in the air.

I get this errors mostly after 3 hours airtime or right in the sim menue ideling 30min.

Agree.. so we should bring the seemingly solution back on top:

1 Like

I get these fairly regularly now. Nearly always when very close to destination airport. I’ve made a habit of now saving the flight close to the desination. It’s not our rigs, I’m fairly certain. Never get it on any other application, be it game, dev tool, utility etc. So it’s unique to MSFS for me.

too bad it didn’t help.

I have to say i have the most stable sim since msfs2020 started and i fly in VR.
I have not had a CTD since weeks… guess the last one was with SU7.

I think the crashes also have to do with the graphics settings, combined with the system hardware config, combined with the software config :grimacing:

What i did to my system, and i had crashes over crashes for months!

- Pagefile:
1/4 your RAM size as minimum
3.5x your RAM size as maximum
pagefile.sys on an SSD (Windows on C:, MSFS2020 on D:, Pagefile on drive I:)
Turn the rest off.

  • Cleaned up my C++ installations, that means i always, and only install the latest C++ package from here:
    Releases · abbodi1406/vcredist · GitHub

  • Delete the Content.xml file.

  • delete everything inside the sceneryindexes folder.

  • under Advanced Graphics Settings remove → FlightSimulator.exe from the list

  • right click C: → Properties → Disk Cleanup → delete DirectX Shader Cache

My config:
ryzen 5950x
6900xt
64gb ddr4 3600mhz
hp reverb G2

…let me know if it helps you if you try some of these tweaks.

thats pretty unnessary..

I own 64GIG RAM too and following works well and pagefile is never increased over the min of 1Gig.

PS: hope you checked the sound-setting too :slight_smile:

1 Like

i said what works for me, there will be always people who say this and that is not needed. If you don’t try it out, you won’t find it out.

if a game need a 3.5 x 64GIG ( 224GIG ) pagefile , then we can not speak about that somewhat works :slight_smile:

And no recommendation to install a repack of original c++ library.. If that thing have a bug, we search the next “issue” which we here can never reproduce.

PS: and dont forget.. it is not a normal CTD topic.. it is special for that “error-memory-could-not-be-read”

Here is a solution from a German PC-Online Website, which is really working for. It is depending on the automatic distribution for the RAM. After widen up the storage manually in the advanced settings I got not one CTD (result after 7 longhair flights). Before the changing I got a CTD after three flights in average. Perhaps one of the German Pilots here in the forum can explain in english language, how to find the settings in a WIN-system with is running english wording.
https://www.heise.de/ratgeber/Abstuerze-im-Microsoft-Flugsimulator-2020-5074764.html

for all which can’t German:

what CT Magazin recommend is to set pagefile to “system managed” ( win default ) , because a lot of users disabled it or set a wrong manuall value. Thats same what we , and the FAQ already mentioned.

They also mention wrong things, e.g. that the pagefile should have same size as RAM exist.

What I did was change both sound options in MSFS to be identical to what I have set within Windows sound settings. is this correct? I had another crash last night, but with no error code. EventViewer did not catch anything crazy either.

so far I understand @mjchernis correct, it was important to check windows sound setting and that in-game the same device is selected. May be he can give additional hints.

Our @Semor76 reported back that windows reinstall helped , which also points to a strange issue with may be a windows update or other driver update ( unfort. all these updates are often in parallel delivered to a msfs updated ).

I have no idea why only some users are affected and whether the sound-device-solution is valid for all users, but at least its a hint users can try.

Pagefile is often mentioned, but should not matter for users with 64GIG RAM ( we mentioned that in this thread ).

Is realy strange why only some users are affected from this problem.. but.. if I remember.. we found already so many strange things ( e.g where Norton AntiVirus killed for some MS-Store users the installation , etc. )..

hmmm.. then you might have fixed the “memory cou…read” thind and run into different issue. But not message in log.. I remember not many cases in forum where this happens.. ah:that was latest CTD, clean install and nothing in Event Logs - #4 by MichaMMA ( but not sure whether relevant for you )

1 Like

Can we please stop with this page file nonsense …

2 Likes

I am dreading having to reinstall MSFS. It will take forever with my internet.

The weird part is that the first crash was the Memory issue, but the second one had no error message and happened in the exact same place in the flight (just after Top of Descent). The route was to KDCA (payware).

There are two options in the MSFS sound page with audio devices. I’m not in front of it now, so I can’t tell you exactly what they say. I have both of them set the same as the windows setting. Maybe I will try a different output source.

It is not just the MSFS sound page — it is the Windows Settings Sound page where you need to make sure the output device is correct. Then you set MSFS to be the same as Windows.

A recent Windows update is messing with the sound settings—-actually two updates because MS re-issued the first one to fix a different problem.

A new Windows install will initially fix the problem BUT then Windows update comes along and installs the update that incorrectly sets the sound output device. Really annoying. Granted MSFS should not crash because of this — Forza Horizon just plays no sound — but, it is not entirely Asobo’s issue here.

You don’t need to reinstall MSFS or Windows to correct this problem.