Renaming, Deleting, Apply to All A/C causing CTD's

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.

2 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:
Since the Dec 2 update, anytime I try to either delete, or use the Apply to all aircraft in the controller settings, I get a CTD.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes. Tested with empty Community folder. Still crashed to desktop.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time

REPRODUCTION STEPS

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

  1. Created a profile (such as keyboard using Duplicate).
  2. Then try to apply “Assign to All Aircraft” or Delete the profile
  3. The screen sits there for a few seconds, then MSFS2024 disappears back to the desktop and has to be re-started again.

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:
Logitech keyboard; Honeycomb Bravo throttle quadrant; Thrustmaster Airbus throttle quadrant.

[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?
N/A Issue with MSFS2024 only

[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:
Nvidia driver 566.14

[PC Only] What other relevant PC specs can you share?
I9 processor, 64 Gb RAM, Windows 10 Home ver 22H2, Drive C: SSD 1 TB; Drive K: SSD 4 TB. Nvidia 4090 Graphics card.

MEDIA

Please add a screenshot or video of the issue occurring.
Unable. No message appears. Simulator simply quits.

[END OF FIRST USER REPORT]


: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:

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

Having the same issue. Got this error code from debug

This fixed the issue but you lose all profiles.

Not sure at this point I want to lose all the profiles I already created. I am hoping MS/Asobo fixes it soon. In the meantime, I’ll rename the unwanted profiles to “Delete Me” and get rid of them later.
Thanks for the suggestions though.

If MS or Asobo sees this, here is a copy of the error message I get when I try to delete a keyboard profile.

Has there been a response from MS/Asobo about this matter? I have the same exact issue. I am in the process of mapping all controllers apart from the keyboard to SPAD.next and would like to delete most of the profiles created to date, but this issue is preventing me from doing so. I’ve tried all the recommended workarounds in a similar thread to this, with no joy. I am vaguely hoping this might be fixed with this week’s patch, but I am tempering my expectation.

It would be very helpful if MS/Asobo provided some insight and a potential solution that does not involve reinstalling the sim or losing the progress made to date in career mode, challenges etc.

Unfortunately, it isn’t even tagged feedback-logged, so it’s hard to know if they are aware.

It ought (big emphasis on that) to be on their internal list, given its obviousness, but you know how that goes…

1 Like

I admit my hopes are low, based on the response given with respect to the video memory/lowFPS issue during the last dev stream.

You’d think that platform stability and CTDs would be high up on the agenda vs, say, dunno, populating the digital twin with zebras and koalas.

I don’t mean to be facetious, but I didn’t get the impression that this was high enough on the agenda, if on the agenda at all.

Yeah, I would expect that tagging a bug ctd or even putting the word “CTD” in a title would be on someone important’s watch list and would see immediate response from those in charge of bug tracking/management.

But here we are 6 days later.

It would be if I were managing the bugs here.

I wrote up a similar bug that is a subset of this one and it also didn’t get tagged:

Indeed. Hopefully Asobo will take note and that this feedback is taken seriously. I genuinely applaud the effort that went into building this simulator, but I am not convinced that they have their priorities in the right order.

1 Like

Not fixed in 1.2.7.0.

Thank you for the bug report.

We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged

I’m pretty bummed it took a week to get this tagged.

This seems like something they could/should have been working on to include in this patch since it was something they broke in the last patch.

I can confirm that updating to 1.2.7.0 did not resolved this issue for me either.

Thanks @Jummivana for logging this. A kind word of advice for the team is that CTDs and other stability/critical bugs should be picked up and dealt with with a bit more urgency. While this most definitely can be described as a first world problem, it would be great to see Microsoft/Asobo dedicate the lion’s share of the effort to eradicate CTDs, and then proceed to less critical bugs/omissions.

In the meantime I got a response from Zendesk, which while very quick, did not help resolve the issue. I was slightly annoyed that the ticket was marked as “solved” before I had confirmed if it had or had not. Below were the suggestions I received, which sadly did not work.

We apologize for the issue you’re experiencing after deleting the controller profile and encountering the ‘memory could not be read’ error. We understand how this can be inconvenient and impact your gaming experience. Please be assured that we are looking into it to find a resolution.

We are aware of this issue, and it is currently being investigated. In the meantime, you can try to resolve the issue by yourself by going through the steps listed in the article below.
Fix “Instruction at Referenced Memory Could Not Be Read” Errors

There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.


Moreover, we recommend checking if the Xbox services are set to run automatically. If not, please try changing the status to automatic. Otherwise, try disabling the Xbox services for testing purposes.

  1. Press Windows Key + R to open the Run dialog box.
  2. Type services.msc and press Enter.
  3. In the Services window, scroll down to find the services that start with Xbox.
  4. Check the status of the following services:
  • Xbox Accessory Management Service
  • Xbox Live Auth Manager
  • Xbox Live Game Save
  • Xbox Live Networking Service
  1. Ensure that the Status column for each of these services shows Running.
  2. If any of these services are not running, right-click on the service and select Start.
  3. Additionally, you can set the Startup Type to Automatic by right-clicking on the service, selecting Properties, and then choosing Automatic from the Startup type drop-down menu.

Note: There is an upcoming update for MSFS2024, so, please be aware and install the update.

@Jummivana, if it helps, occasionally, but not always, I also get pop-up error windows of this type:

FlightSimulator2024.exe – Application Error
The instruction at 0x00007FF6E8207990 referenced memory at 0x0000000000000010. The memory could not be read. Click on OK to terminate the program.

FlightSimulator2024.exe – Application Error
The instruction at 0x00007FF7E7C47990 referenced memory at 0x0000000000000010. The memory could not be read. Click on OK to terminate the program.

The respective Event Viewer outputs are:
Faulting application name: FlightSimulator2024.exe, version: 1.2.7.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.2.7.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000003201890
Faulting process id: 0x1718
Faulting application start time: 0x1DB4B589E4704E9
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.2.7.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.2.7.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Report Id: 9c378fd2-56b1-42ce-88c6-e7937ae507fb
Faulting package full name: Microsoft.Limitless_1.2.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Faulting application name: FlightSimulator2024.exe, version: 1.2.7.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.2.7.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000003201890
Faulting process id: 0x4E04
Faulting application start time: 0x1DB4B5A74E01AFD
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.2.7.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.2.7.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Report Id: a8d46224-31fb-4c24-828a-73597018e05d
Faulting package full name: Microsoft.Limitless_1.2.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

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:

Same problem on my system, to the letter. Have tried a different profile selection, but repeatedly get the CTD.

If relevant, provide additional screenshots/video:

Same problem.
Second time Tobiii is mentioned in changelog, second time its impossible to assign config to all airplanes. Instant CTD (Creating WER)
God preserve us of getting untested patches.

I don’t think the latest patch addressed this issue. Bug has been logged, so hopefully it can be addressed in the next patch or maybe a hotfix.

Since I first reported this issue, I fixed it myself by following the instructions labeled: “How to delete a cloud save to fix some loading or crashing issues…”
I have had no problem deleting unwanted profiles since, BUT it removes practically everything including profiles I did now want removed. Not the way I wanted to resolve this, so I am now rebuilding and reassigning aircraft to get back to where I was previously.

Does it delete the career progress?

Not worried about losing all hardware profiles as I shifted almost everything to SPAD.next and avoid any or most future chaos related to hardware bindings.