MSFS Application Error - memory could not be read

Oh interesting, my crash was upon landing too.

My last one was exactly at touchdown with the main wheels.

Exactly the same !

1 Like

This is beyond frustrating. The sim has been out for more than 2 years and these CTDs are still unresolved! I was 30 seconds from touchdown into TNCM!
I had such high hopes that SU10 would at least restore some stability, let alone performance. Oh well…

1 Like

Are you using DX12 and DLSS with new Nvidia Driver?

:wave: 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
Have you disabled/removed all your mods and addons?

Yes
Brief description of the issue:

Selecting next after completing a Bush adventure leg brings up a read error. Selecting the read error closes MSFS. This only occurs when Next after completing the bush adventure leg. Selecting any other option does not cause the error and the program performs as expected.
Provide Screenshot(s)/video(s) of the issue encountered:

Error after completing leg of Bush Trip

Detailed steps to reproduce the issue encountered:

This occurs with several Bush trips regardless of if I am in Safe or Standard mode.
Start a new or return to a partially completed Bush Adventure.
Complete any leg of the adventure
Select Next at the conclusion of the Adventure

PC specs and/or peripheral set up if relevant:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

No fault bucket with time stamp that coincides with error
Build Version # when you first started experiencing this issue:

1.27.21.0

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

No, I’m running DX11 with DLSS with the latest Nvidia driver released August 9th.

Again and again and again… Driving me crazy since SU10. Never had it before.

Any reasonable fixes or workarounds discovered so far? What’s keeping Asobo.

From about 2 weeks before SU10 dropped, and i wasn’t on the beta, I didn’t suffer any of these CTD, but I’ve just had another. Thankfully, it was just a short flight from NSTU to NDFA, in the Fenix A320. (I know that’s an awful lot of aircraft for a 100nm trip, but it is a leg of my tour of the world’s capital cities and i wanted to do it all in the airbus).

This CTD really is a pain, so i’m hoping that Asobo are close to a fix.

I had just recently bought the Standard + Deluxe DLC of MSFS Game of the Year addition, but downloading would only ever reach no more than 24%, and there would be and error message (See embedded), and the download would be terminated and I would have to start over only to the same result. Unlike the other players encountering this problem, it happens in the downloading launcher, and directly stops the download.

Software fixes I have tried include but are not limited to:

  1. Moving the game to a different drive
  2. Cleared cache
  3. Clean booting my pc
  4. Resetting, repairing, and reinstalling MSFS
  5. Disabling all programs in the startup tab
  6. Disabling Anti-virus
  7. Changed the proper windows services to “Automatic” in the Services App
  8. Reinstalled gaming services
  9. Used SFC tool to scan and repair Windows
  10. Preformed a clean-boot of my PC
  11. Changing language pack
  12. And even tried the fix of a person who had the exact same error as me, except they got it while flying, and me while downloading:

I suspect it may be a hardware error so here are my specs:
i5-12600K
GeForce RTX 2070 Super MSI GAMING X
DDR4-3000 2x8 GB Corsair Ram
500 GB SN850 + 2 TB 3.5’ HD

I’m hoping to fix this issue soon, as I’ve almost completely given up.

Screenshot 2022-09-23 010323

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

simecrash

Same here I’m fear to do any flight past 2hrs
today mine crashed just past 17 mins

Try turning off Hardware Accelerated GPU Scheduling. That fixed it (so far) for me. Satisfaction is not guaranteed. Google or Duck-Duck-Go for the procedure, its easy.

Dam just tried that but no luck.

Mine is off (always been). Still doesn’t help with CTDs.

It would appear that the devs have made no progress on this, if indeed they are still investigating it, as there is still no mention of it in the weekly development update and it is still happening.

Any chance of a status update on this one please Asobo?

1 Like

After weeks of 0 issues and perfectly smooth performance I had to reinstall the game due to an issue, just before that I updated to the latest Nvidia GRD from the latest Studio one, and also WU Canada installed, now this issue is back.

with me the same I had no problems for weeks with World Update Canada error occurred again

I was very active in this thread for a while. Tried pretty much “everything” to solve it, and suddenly at some point it disappeared almost completely. I’ve had it perhaps once in the last month and I’ve been simming a lot.

I hope for you that you no longer get it.
I am now back from the GAME READY DRIVER 517.48 back to the studio driver 517.40 the last time I changed in June from the GAME READY DRIVER to the studio driver 512.96 I had not seen this error message until yesterday and I had previously made long flights over 3 hours without error message . the only thing that changed yesterday is the World Update and that I installed the GAME READY DRIVER 517.48