CTD after SU2 update every time clicking on start

User Support Hub Crashes (CTDs)
, ,
1

ISSUE DESCRIPTION

Description of the issue:

CTD upon clicking on Start after automatic (MS Store) SU2 update.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

Removed and yes.

FREQUENCY OF ISSUE

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

Every time, can’t enter game anymore.

REPRODUCTION STEPS

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

  1. Launch game
  2. Wait for Start button to appear
  3. Click on “start” or “continue” via accessibility menu

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:

No peripherals connected

[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?

2024, so DX12

[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 2080ti (old card but SU1 was running and 2020 does)

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

Amd Ryzen 7950X 64 Gb DDR5

My Tries without success:

Reinstall game. (2 times)
Installed Nvidia driver was the last one as required, reverted to 566.36, uninstalled nvida app.
Erasing Comunity folder, userCFG.opt, Content.xml
Deleting caches, DX, Nvidia etc…
Checked health of ntdll.dll (ok), Sfc Scanned the pc.
Uninstall W10 last (may) updates.

Event report:

Nom du journal :Application
Source : Application Error
Date : 19/05/2025 15:56:17
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur : DESKTOP-4HKP4PU
Description :
Nom de l’application défaillante FlightSimulator2024.exe, version : 1.4.20.0, horodatage : 0x00000000
Nom du module défaillant : ntdll.dll, version : 10.0.19041.5438, horodatage : 0xab0dece3
Code d’exception : 0xc0000374
Décalage d’erreur : 0x00000000000ff3c9
ID du processus défaillant : 0x3658
Heure de début de l’application défaillante : 0x01dbc8c5943fba23
Chemin d’accès de l’application défaillante : C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Chemin d’accès du module défaillant: C:\Windows\SYSTEM32\ntdll.dll
ID de rapport : b351e242-a753-4f94-b168-349157ee8245
Nom complet du package défaillant : Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe
ID de l’application relative au package défaillant : App
XML de l’événement :



1000
0
2
100
0
0x80000000000000

71555


Application
DESKTOP-4HKP4PU



FlightSimulator2024.exe
1.4.20.0
00000000
ntdll.dll
10.0.19041.5438
ab0dece3
c0000374
00000000000ff3c9
3658
01dbc8c5943fba23
C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
C:\Windows\SYSTEM32\ntdll.dll
b351e242-a753-4f94-b168-349157ee8245
Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe
App

Nom du journal :Application
Source : Windows Error Reporting
Date : 19/05/2025 15:56:19
ID de l’événement :1001
Catégorie de la tâche :Aucun
Niveau : Information
Mots clés : Classique
Utilisateur : N/A
Ordinateur : DESKTOP-4HKP4PU
Description :
Détecteur d’erreurs 1382047177783210342, type 5
Nom d’événement : MoAppCrash
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe
P2 : praid:App
P3 : 1.4.20.0
P4 : 00000000
P5 : StackHash_c70f
P6 : 10.0.19041.5438
P7 : ab0dece3
P8 : c0000374
P9 : PCH_B4_FROM_ntdll+0x000000000009E044
P10 :

Fichiers joints :
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER996B.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8F.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9BB0.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9BAE.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9BBE.tmp.txt

Ces fichiers sont peut-être disponibles ici :
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_6a3c774d4ea07fb62d9a69a2452f159dd7d83e58_fea788ec_1129d67b-50c6-41d6-9a87-fbe75290e18c

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : b351e242-a753-4f94-b168-349157ee8245
Statut du rapport : 268435456
Récipient avec hachage : fe73e0518e21a9f9e32e0495f6997166
GUID CAB :0
XML de l’événement :



1001
0
4
0
0
0x80000000000000

71556


Application
DESKTOP-4HKP4PU



1382047177783210342
5
MoAppCrash
Non disponible
0
Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe
praid:App
1.4.20.0
00000000
StackHash_c70f
10.0.19041.5438
ab0dece3
c0000374
PCH_B4_FROM_ntdll+0x000000000009E044



\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER996B.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8F.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9BB0.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9BAE.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9BBE.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_6a3c774d4ea07fb62d9a69a2452f159dd7d83e58_fea788ec_1129d67b-50c6-41d6-9a87-fbe75290e18c


0
b351e242-a753-4f94-b168-349157ee8245
268435456
fe73e0518e21a9f9e32e0495f6997166
0

2

check out my post, same issue.

3

Done Firm Tuna, and I voted too.

It must be a server side bug, I’ve done so much crazy things PC side without any success.

The only server thing i found we can try is erasing our cloud save.

Hope you guys don’t have build a career!

I haven’t, so after having wiped the save, I had access to all the configuration menus:
Graphics, controllers, plane selection, etc…

But msfs wont let you really enter the game main menu (activity selection) if you don’t setup your avatar (there are two ways to get there)
Clicking continue after avatar selection or customization leads to the same CTD (Freeze, audio hick-ups and back to desk).
Same ntdll.dll report.

Lost all settings and still no access to game since SU2 release.

4

Same exact thing for me. Support says it’s an mvodia issue. I’ve tried every available driver and each had the same result. Ctd. This sucks.

5

They are not correct as this impacts Xbox users, too. It’s apparently due to the profile/cloud save…and the only solution is to deleter all your data everywhere and start with the game from a scratch.

6

Wait, hang on…so you’ve followed the guidance on deleting game data and you STILL can’t access the sim?

7

Hey Firm Tuna thanks, but where do i find the “it’s a nvidia thing” answer from support?

8

Deleted my cloud save following this procedure:

https://flightsimulator.zendesk.com/hc/en-us/articles/17060350083612-How-to-delete-a-cloud-save-to-fix-some-loading-or-crashing-issues-Crashing-on-the-identity-screen-spawning-inside-buildings

It’s not deleting all your profile (explained there).

It a least gave me the access to configure the sim at launch.
Tried a lot of things here but CTD’s after entering the same point in game witch is the main menu (at “start” or at “continue” after avatar settings)

Didn’t try to log in Ms store with a new blank profile but I guess it should lead to the loss of the purchase!

9

I’m not sure I fully understand. So…you’ve followed the delete profile instructions but you still can’t access the sim? I’m not sure what you mean about the purchase…?

10

So I deleted the profile as well per support’s request. I was able to get into configure but that was it. Still crashed after that. Here’s what they said about it being an nvidia issue after running all the troubleshooting with me.

They’re saying it’s Nvidia causing it and they’re working with them on resolving this and other issues. By the way I tried every driver. Still nothing. Also this only happened with the su2 beta and the su2 release candidate.

Support
Today, 1:07 AM

Hi

Thank you for contacting Microsoft Flight Simulator Support today.

From your latest log, the error is still with ntdll.dll. NVIDIA has been having some major issues with it’s drivers and when you are using RTX5000 series GPU, you cannot go too far back with the drivers because the GPU will not work with them at all.

We recommend testing each of the available drivers to see if one of them would work in your system. And do not install the Nvidia app when installing the GPU drivers, install just the driver and nothing else.

Drivers you can try with RTX5090:
• 572.16
• 572.42
• 572.47
• 572.60
• 572.70
• 572.83
• 576.02
• 576.28
• 576.40
• 576.52

We are in constant communication with NVIDIA to make sure they know the issues users are having with the simulator so we can work together to improve the driver stability with MSFS2024 (if the issue is only limited to MSFS2024).

12

Do us a favour and relay to them that this has nothing to do with Nvidia as it’s affected me and several other Xbox users on the forums…and that that an incorrect diagnosis may be the reason why the ‘solution’ hasn’t worked properly for you.

13

Linked to this post on my zendesk ticket.

2 Likes
14

Same ■■■■■■■ Problem. Clicking start cause CTD. Never been before.

With every Update fs getting worse and worse.

15

Followed the procedure so I lost my log but it did not solve the problem. After confirming my Avatar I had the usual CTD…

16

Thank you for keeping us informed on your ticket @FirmTuna

I doubt about the Nvidia culprit…

I Rolled back to Nvdia driver v 566.36 (Via DDU), no nvidia app installed => same CTD
Disalbed GPU scheduling => same CTD
Ran Gaming Repair Tool => same CTD
Some Xbox Users (AMD graphics) experience the same CTD

To sort between local and cloud issues, maybe one sould log with another MS account (Store & Xbox) on the same machine.
An account owning MSFS 2024 of course.

1 Like
17

Tried:

566.03, 566.14, 566.36
572.16, 572.42, 572.47, 572.60, 572.70, 572.83
576.02, 576.28, 576.40

Same CTD

18

They essentially washed their hands of my ticket. Said nothing else they can do and closed it.

19

Updated the NVidia driver from 576.40 to 576.52 but still no joy. The most worrying thing is that there seems to be absolutely 0 movement or even interest from the side of Asobo to investigate this issue.

2 Likes
20

Issue Fixed
I have had the same CTD multiple times. The AsoboReport - Crash-******.txt always has the line Msg=“GPU Device Removed”.

I have tried all the reinstalls of nVidea drivers, MSFS 2024 and Steam - Always broke.

I then decided to watch the temperature of my graphics card - ASUS ROG STRIX RTX 2080 Ti GAMING OC 11G.

Monitoring was done by installing HWiNFO - selected the Sensors display and then started MSFS 2024. The temperature just climbed, 70°C, 80°C, 87°C and CTD!!! This was repeatable.

So with confirmation that the graphics card was overheating, causing it to protect itself, it became obvious that the AsoboReport states “GPU Device Removed”.

Reading up on nVidea graphics card overheating it becomes obvious that 1) the fans are not running as fast as needed, 2) the card is full of dust, or 3) the thermal paste is possibly not sufficient.

So, my card is still dust free. Next the fans not running fast enough.

MSI Afterburner is often recommended to fine tune a graphics card, so I installed it, set it up and sure enough the cooling was now controlled. Watching HWiNFO the temperature stayed around 82°C, close but under the maximum. MSFS 2024 finally ran, and ran and ran.

Final step was to disassemble the graphics card. I am well out of warranty, so checked on line, did not fined my card but the general process of removing screws (6 on mine - 15 plus on some others) and disconnecting any cables.

This revealed that there was little thermal paste and it did not cover the entire chip. I cleaned off the remainder and as I had Arctic thermal paste to hand I ensured a full coverage on the chip.

Once back in the box, the temperatures were lower still, 70°C to 80°C. Today I ran MSFS for 4 hours with no hiccup.

Yippee!!

Oh, and Support are correct IMHO that it is an nVidea not MSFS issue. Other will find different solutions, but check your graphis card for overheating.

21

No offense, but this doesn’t make sense. Did you have the issue as described by other users here (when pressing the Start button)? Why would a GPU overheat when you’ re not even in the menu yet? When I am getting the CTD the GPU temperature is at 52.9 degrees Celsius. Are you sure you are posting in the right topic?