MSFS Application Error - memory could not be read

I have not been home to post a screen shot but this confirms my suggestion that this is caused by a misconfiguration of the audio output device – I think caused by either Windows Update OR an NVIDIA driver update that was a day or two after SU9. Will post a screen shot when I get home but you can set the Windows Audio Output device properly in Windows - Settings - Sound - Output - Choose Where to Play a Sound.

After setting it there, check in Audio settings of FS to make the SAME device is selected. Do NOT use System Audio Device.

This was probably corrected when you did full re-installs.

3 Likes

Sign me up with this problem, and PC freezes and CTDs, I never had such problems with an OS+Simulator+whatever it is, I am going to instal Windows XP again.

Some others say that reinstalling all OS did not solve nothing, maybe try it with a backup, install only FS2020 and other necessary stuff and try it, if not I think, restore the full backup.

I may have an idea about your issue here…

3 Likes

Of course! I did not notice, I will install Windows 98 then.

Edit: Of course I was joking, I have w11, just in case a misunderstood.

1 Like

Did more testing. Turning up the ground detail slider from 100 to 200 makes the CTD happen a little further away from the treshold at EKBI.

So there is definetely something going on with the ground objects. And again, with WU5 uninstalled, no CTD.

If anything, i’ll just run without WU5 for now, instead of reinstalling W10

made also more testing.
Flight EBBR/LSZH with all addons running (airport scenerys/Vatsim/SLC/FS2Crew/…) and graphic settings medium (terrain/Object details 50) → no error!
Graphic settings does the trick for me it seems

I am getting the same error I believe since SU8… Windows Store version

Yes I have many addons but my system specs (mentioned in my profile) can handle those I am very confident :slight_smile:

I was working in Dev Mode the other day and got it, not flying or anything, just panning around and adjusting some polygons… I reported it on the Dev Forum and I was asked to send the Dump file but that was a bit too late as I opened the sim afterward a couple of times…

I might send the dump file if it happens again but I will not reinstall Windows or the Sim as some suggested… I will just wait for SU10… And will see

I had the Error a few mins ago in the Main menue after starting the sim. It appears 10 min after sim launch. I talked with the person next to me so i did not do anything in the sim.

So in this case not much memory was in movement (i guess)

Looks like the hotfix is out and this isnt in the changelog. Will have to hope whatever changes might have had an indirect positive effect but not optimistic.

1 Like

Anybody notice a small MSFS update today? Does anyone know what it fixes? Hopefully this issue!

Lets hope for the best.

It is the SU9 Hotfix, 1.25.9.0

The crashes are continue to happen after the hot fix today.

Can’t even take off, it just crashes.

These should be fix ASAP!

2 Likes

Check your Windows audio output device.

It is get mashed by the May Cumulative Windows Update and getting set to the Asus Audio Mixer (in my case). Not sure why it makes FS nuts but it does. Completely corrected the problem for me—you’ll see I was posting about this early.

1 Like

EDIT: false hope, it is still happening! #Killmenow

I had this memory could not be error all the time on a fresh install of MSFS and Windows 10 is up to date.

It would crash again and again after 10 min: unplayable.

Every other games or 3d software would work without issue.

But, I followed the instruction from this post:

I think deleting the Realtek High Definition Audio Driver fixed the issue.

I ran MSFS for a hour and it did not crash.

Good luck to all.

I’m having this as well

Same

Im about to try this… I dont think enough people are listening. My settings in-sim were “System’s default device”, so I’m hoping you’re onto something.

Good Lord, i hope this works…

Well… still got a CTD, but no memory error.

Can’t start any flight after todays hotfix!