CTD Always on Startup

Version Alpha - 1.0.77.0

Frequency: Consistently

Severity: Blocker

No Packages installed

Repro: Installed and launch the sim. After windows opens, CTD.
Repro: Always, just launch MSFS 2024.

Windows 11
32GB RAM
Updated Bios
Updated Nvidia Drivers
GPU Nvidia Geforce RTX 3050

Event Viewer

Faulting application name: FlightSimulator2024.exe, version: 1.0.77.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.0.77.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000003453a8b
Faulting process id: 0x0x13C4
Faulting application start time: 0x0x1DB2FBD45BBE1EA
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.0.77.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.0.77.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Report Id: 9958fe36-e3c3-45ab-8c0a-0c3bfce6a177
Faulting package full name: Microsoft.Limitless_1.0.77.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Attachments

@fs1ar,

It looks like you had a debugger attached when launching the build - were you trying to debug some WASM module or doing something else?

As a reminder, you can allow a debugger to be attached with the -AllowDebugger switch when launching the sim EXE.
https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/WASM/VS_WASM_Debugger_Extension.htm

As in MSFS 2020, encrypted content won’t be mounted into the VFS when the switch is used.

Best regards,

Eric / Asobo

@EPellissier thanks.

I attached the debugger just to generate the dump and I did this with the -AllowDebugger flag, that is the only purpose as I as not able to generate a dump file with the task manager as the CTD happens too quickly when the window opens. With the debugger it broke on the offset above Fault offset: 0x0000000003453a8b and could save the dump to file.

Regardless of this, the CTD happens consistently on that same offset without a debugger on every load, consistently:

Faulting application name: FlightSimulator2024.exe, version: 1.0.77.0
Fault offset: 0x0000000003453a8b

Thanks
Federico

@fs1ar,

Your crash dump seems to show that a debugger was attached while -AllowDebugger was not specified - this is what caused the crash.

You do not need to attach a debugger to have a crash dump created.
Please follow the steps highlighted here: How to report a bug or crash

More precisely the relevant part is here: Collecting User-Mode Dumps - Win32 apps | Microsoft Learn

Please let us know if you need help setting this up properly.

Best regards,

Eric / Asobo

@EPellissier Here is the dump with no debugger attached (generated with task manager). Same CTD: MS Store click Play, MSFS is launched (splash screen), main window opens and CTD. Thanks

Faulting application name: FlightSimulator2024.exe, version: 1.0.77.0, time stamp: 0x00000000 Faulting module name: FlightSimulator2024.exe, version: 1.0.77.0, time stamp: 0x00000000 Exception code: 0x80000003 Fault offset: 0x0000000003453a8b Faulting process id: 0x0x8418 Faulting application start time: 0x0x1DB304E76B81629 Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.0.77.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.0.77.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe Report Id: 163d6fd8-2629-432e-bb1b-662bb0296c72 Faulting package full name: Microsoft.Limitless_1.0.77.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

1 Like

Hi @EPellissier

Just updated the sim and same CTD.

Repro: MS Store click Play, MSFS is launched (splash screen), main window opens and CTD

Faulting application name: FlightSimulator2024.exe, version: 1.0.84.0, time stamp: 0x00000000 Faulting module name: FlightSimulator2024.exe, version: 1.0.84.0, time stamp: 0x00000000 Exception code: 0x80000003 Fault offset: 0x00000000035161fb Faulting process id: 0x0xB2D0 Faulting application start time: 0x0x1DB3116178FBD83 Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.0.84.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.0.84.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe Report Id: 94ecdeb6-d493-4d68-a25e-e70b32de6eaa Faulting package full name: Microsoft.Limitless_1.0.84.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

Hi @EPellissier do you have any update on this? The CTD happens always and I can’t start the sim in any way.

Thanks,
Federico

Did you try using devmode launcher ?

Yes, tried that and same CTD, at same offset. Thanks for the help!

Hi @fs1ar,

Unfortunately all the dump files you provided lead to the same issue that the sim thinks you have a debugger attached while the -AllowDebugger option has not been set.
I have forwarded your dumps to the Security Team for review but I haven’t heard from them yet.

Best regards,

Eric / Asobo

@EPellissier thanks. I am not attaching a debugger. I even launched the sim from the devmode sample. Thanks, Federico