Airbus A310: ~75% risk of of MSFS2024 process crash to desktop

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue:

I usually fly the A320 Neo (v.2), but recently I wanted to reacquaint myself with the lovely A310.

But that turned out not to be a particularly pleasant experience.

My first attempt ended abruptly while still on the ground preparing the aircraft. The MSFS process crashed. You know, the sound temporarily goes away for a second, then comes back for a fraction of a second, and then goes away permanently, a few seconds before the MSFS windows (yes, Win32 windows) are removed and the MSFS process dies.

My second attempt suffered the same faith.

On my third attempt, I was more successful. I has just reached my cruising altitude when MSFS crashed.

My fourth attempt was much more successful. I flew from ESSA26 to ESSL19.

My fifth attempt the day after, however, resulted in an early MSFS crash on the ground.

So it seems like the A310 simply has a high risk of crashing the process. Memory corruption? (Time to upgrade to C++26 with its “hardened” STL?)

FREQUENCY OF ISSUE

Apparently very often, maybe 75% risk of a MSFS process crash within an hour when flying (or attempting to fly) the A310 from ESSA to ESSL (haven’t tried any other route – I don’t get paid to investigate MSFS bugs!).

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Start MSFS.

  2. Plan a trip from ESSA26 to ESSL19 in the default A310.

  3. Set up the avionics and take off.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it?

No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

DX12 (I think?)

[PC Only] What GPU (Graphics Card) do you use?

RTX 5070 Ti

[PC Only] What other relevant PC specs can you share?

13 gen i7, 64 GB RAM, 3×2 TB SSD, Windows 11 Pro, no “no-name” hardware, no “strange” software.

MEDIA

Please add a screenshot or video of the issue occurring.

Made a new attempt today, didn’t even get airborne.

But this time the log contains more information:

Fel-bucket 1887126327945804966, typ 5
Händelsenamn: MoAppCrash
Svar: Inte tillgänglig
Kabinett-ID: 0

Problemsignatur:
P1: Microsoft.Limitless_1.5.27.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.5.27.0
P4: 00000000
P5: FlightSimulator2024.exe
P6: 1.5.27.0
P7: 00000000
P8: c0000005
P9: 0000000001568ed9
P10:

Bifogade filer:
\?\C:\Users\kvadr\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\AsoboReport-Crash.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e2a51ec9-e006-4a14-81ed-8fad0ce8ab6d.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0ec01b7a-9d9f-4538-a100-ba74ba292839.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20250923_1_EC_0_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.fe05bf13-a70c-45e7-a10a-fd168380fce3.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c51a89fd-5b26-430e-9929-08187a260f11.tmp.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.39e6abca-9cec-45a2-9cfb-dfaeeee663fd.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b768644e-9e9e-442c-b21a-d82906478a6b.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c7cad7bc-f1b2-49a4-a752-2fb30c385349.tmp.xml

Filerna kan vara tillgängliga här:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_ec279c46a960e082a221a41e2b153ac838c9cd1_5130d36f_cf63d5a9-7c97-4bc9-b830-624e606166c7

Analyssymbol:
Kontrollerar lösning igen: 0
Rapport-ID: f1e5afdd-2dc6-44db-81d3-d0bb54ad5dba
Rapportstatus: 268435456
Hash-bucket: 19917b3b63bba3e78a306b65977f3ca6
Cab-GUID: 0

Let me know if you want to see any of the generated files.

AsoboReport-Crash.txt (36.8 KB)

Maybe some clues here?

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

No success today either in the ATR.

AsoboReport-Crash.txt (39.3 KB)

Fel-bucket 1887126327945804966, typ 5
Händelsenamn: MoAppCrash
Svar: Inte tillgänglig
Kabinett-ID: 0

Problemsignatur:
P1: Microsoft.Limitless_1.5.27.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.5.27.0
P4: 00000000
P5: FlightSimulator2024.exe
P6: 1.5.27.0
P7: 00000000
P8: c0000005
P9: 0000000001568ed9
P10:

Bifogade filer:
\?\C:\Users\kvadr\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\AsoboReport-Crash.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d6630dc2-d456-4804-a824-c5d8578e3fca.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2007315d-42a5-4414-a83a-535952634618.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e4c7ea85-c1ed-4634-a04d-b0d71e2329e1.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6e58c843-6e4d-4ccf-81cd-93ec94b77c88.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.414145fd-c58a-4199-97df-7a3304da1287.tmp.xml

Filerna kan vara tillgängliga här:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_ec279c46a960e082a221a41e2b153ac838c9cd1_5130d36f_e6e1908c-440b-45c4-82b3-184dc54c2176

Analyssymbol:
Kontrollerar lösning igen: 0
Rapport-ID: d15510be-8bf9-4557-b503-b75fa7170d90
Rapportstatus: 2147487744
Hash-bucket: 19917b3b63bba3e78a306b65977f3ca6
Cab-GUID: 0

FWIW, I don’t experience any crashes if I stay away from the A310 and the ATRs.

I assume that senior Asobo software engineers are actually investigating reports like this?

Seriously, at least in Sweden it is customary for companies selling products and services to offer guarantees and support if the product is broken, malfunctions etc. There are even laws regarding this.

If a Win32 application crashes due to access violations, there’s a bug somewhere. Sure, it could be in the graphics driver, but since only MSFS crashes on my system, that seems unlikely.

I’m a 20+ years software developer myself and if I learn that one of my apps suffered an AV, I make that my 100% top priority.