Flightsimulator.exe - Application Error

Bug Reporting Hub Crashes (CTDs)
, ,
1

Please tag your post with #pc and/or #xbox. PC

Are you on Xbox, Steam or Microsoft Store version? Steam

Are you using Developer Mode or made changes to it? No

Brief description of the issue: I have been getting the following error in the last 4-5 days. I have not installed anything new within the simulator during that time period that might be causing this. And ideas?

Provide Screenshot(s)/video(s) of the issue encountered:

msfs error
msfs error1503×1153 180 KB

Detailed steps to reproduce the issue encountered: Happens randomly.

PC specs and/or peripheral set up if relevant: Alienware 17 R4, Core i7, GTX 2070, simulator installed in an SSD

Build Version # when you first started experiencing this issue: The current build 1.22.2.0. February 2022

2

did you find hints in existing topics ?

Example Search:
https://forums.flightsimulator.com/search?q=memory%20could%20not%20be%20read

e.g.
check windows e.g. with sfc / scannow and dism
check windows virtual memory setting

A example discussion, where user at the end reset windows : CTD upon dev tools loaded during game startup

3

I checked everything but didn’t find any relevance.

4

I just got this same weird error ? Were you able to fix this an get FS2020 working again ? Can you tell me how ? thanks

5

The error in the initial post is a user-mode application (FlightSimulator.exe) trying to access a kernel mode memory address. Windows does not allow that. It’s either an application bug or bad memory/configuration, hard disk.

6

It happens sometimes without notice but since the latest simulator update, the occurrence has reduced by 90%.

7

I am on Sim Update 9. Luckily, on hard rebooting the PC, and emptying the AFC Bridge and a flightsimbuilder -WASM module from the community folder ,it seems to have resolved itself!

8

Had the same issue. The plan would fly for 10-15 minutes and then you would get the application error. It all started after the most recent update. I tried the app repair and I also ran it in Developer mode. First 3+hr flight was fine. Next step is to see if it functions ok in normal mode.

1 Like
10

I’m now having the same symptom’s with 1.34.18.0

11

Have you considered deleting the Rolling Cache?

How you should delete it:

  1. Delete the Rolling Cache

  2. Apply and Save

  3. Go back to the previous screen

  4. Again go to Data tab and assign a Rolling Cache of 8 GB

  5. Apply and Save

  6. Load a flight

12

I’m not using the rolling cache.

13

I saw this screen appear with a crash after this update once. And that has happened once in one year - now.

Can’t specify what causes that.

14

the 0xffffffffffffffff one is an interesting on (ie -1)
Just like the 0x000000000000C one

Bad Pointer, often a 0 or a -1. (when one looks at a dis-assembly of a full Crash Dump, and the code that caused the CTD, with an invalid pointer :scream:

Interesting returned numbers, 0 & -1.

Both are frequently used return of an error code, instead of the expected pointer value. implying that error message retrurn are not being detected and processed.

In just about every case I have looked up, there is NO looking to see if that returned value is in the range of being a ERROR Code, and taking the necessary action if it is.

This lack of detecting if the returned value is an error code or not, is typically in a library dll, and not code that Asobo has directly coded, so it could be argued its not basically an issue being cause by any defective Asobo Coding.

ie Asobo’s coded Flightsimulator.exe’s STABILITY is also dependent on the 3rd party libraries it is using !!
:woozy_face: