MSFS2024 - CTD 5 out of 5 attempts today

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

Provide extra information to complete the original description of the issue:
• CTD happens when trying to change aircraft or livery in free flight. This applies to all streamed aircraft. I’d estimate 8 out of 10 times the sim does CTD.

Removing community content does not make a difference. In fact the Fenix A320 is the only aircraft where changing the livery has never resulted in a crash.

Contrary to some reports above I have never experienced a CTD once a flight was successfully loaded.

I’m having issues too.

All five of my MSFS 2024 sessions last night ended in CTD.
Only one of them I even got off the ground in a PC-12 in non-VR mode
Three times it happened just trying to load in with the Vision Jet.
And if it didn’t crash then it did every time I tried to activate VR mode while in flight.

What do you use to produce error reports/logs?

I would not take the Votes too literally.

If you can document a reproducible crash the Asobo development team will probably jump on it immediately as top priority.

Before I retired from C++ development if a crash was reproducible, we stopped current work and fixed it immediately, It becomes a matter of team pride and it avoids other customers suffering the same crash. Streaming means the (tested) fix can be downloaded automatically the next day. But a weekly patch might be prudent.

the game is also crashing overnight since yesterday

I can launch msfs 24 but I have the same error in the Asobo error report present in the game folder

I updated nvidia
I reinstalled twice, I even tried on a new hard drive
sometimes I manage to click on FLY and sometimes it crashes first

I specify that I did not modify anything, I quit by clicking on the button after several hours of flights without problem, I turned off the PC, turning it back on and launching msfs 24, I had this bug CTD either once I click on FLY or directly before being able to click on FLY, I have done several tests, by launching a flight in the open sea or on land, it is always the same result

here is the content of the generated AsoboReport-crash file

/!/ CRASH /!/TOML
[OnCrash]
Msg=“_handleSEH”
Type=“SEH”
Code=0xC0000005
[Engine]
ReportVersion=10
ExitApp=false
TimeUTC=2024-12-07T06:45:18Z
BuildVersion=“1.1.10.0”
UnscaledDeltaTimeMs=24.991899
TimeSpentRunningMs=236592.394912
TimeSpentPauseOffMs=236592.394912
TimeSpentTurnedOnMs=236592.394912
ContextUID=0x7EC2542BD12CE634
MemInfoUID=0x4FE68B335E15F102
DebuggerAllowed=false
AllocatedMem=23691509760
FrameCount=57127
IsMSIXVC=true
Purpose=“[default purpose]”

1 Like

Seriously? ah, yeah…

I’m trying hard to love this sim, honestly I am but it’s just so hard to not get annoyed when you have limited time and your PC either hard crashes or at the very least CTD 2nm from touchdown and so you have to abandon things.

CTD appears completely random and has been much, much worse since the update last week Beforehand I had good stability after fixing a driver issue and yet afterwards on an update supposed to help with stability it CTDs about 90% of the time for no reason whatsoever. Sometimes when loading in scenery. sometimes mid cruise with zero input.

No idea if this is actually of any use:

/!/ CRASH /!/TOML
[OnCrash]
Msg=“_handleSEH”
Type=“SEH”
Code=0xC0000005
[Engine]
ReportVersion=10
ExitApp=false
TimeUTC=2024-12-09T21:26:18Z
BuildVersion=“1.1.10.0”
UnscaledDeltaTimeMs=24.713399
TimeSpentRunningMs=7342732.249342
TimeSpentPauseOffMs=7342732.249342
TimeSpentTurnedOnMs=7342732.249342
ContextUID=-6198677981398489781 #0xA9F9DF37C9B5254B
MemInfoUID=-5698029006307295362 #0xB0EC88CEE72E7F7E
DebuggerAllowed=false
AllocatedMem=27402997760
FrameCount=374272
IsMSIXVC=false
Purpose=“[default purpose]”

7800X3D, 64Gb RAM, 4070 Super

2 Likes

I am also getting CTD every time I hit start flight.

Details including several Asobo Crash reports, DxDiag, MSinfo have been provided via support ticket, all recommended fixes have been applied:
Request #234628 CTD - Error Code 0x0000005

So sorry to hear that, I’m in the same club as you.

I’m currently at for every 10 attempts to start a flight, 1 of them completes. It either crashes when main menu loads or when I select the world map and it starts to zoom in then crashes.

Surely there is a log file being created of the CTD’s that can be shared

I keep saying I’m going to stop trying but I can’t help it!!

1 Like

Thx an sorry to hear that you are also still struggling.
I got this via my support ticket

Microsoft Flight Simulator uses the English (United States) Language Package for the ATC and other essential features. The simulator can’t run correctly when this pack is missing or corrupted, resulting in a CTD.
Here is how to install a language pack for Speech. If the pack is already installed, we suggest you remove it and install it again.

Not sure if this might cause issues on your side, but I assume you might run on English (UK).
Under normal circumstances this should not make any difference anyhow we talk about MS/Asobo. :wink: Might be something to try as well.

Good luck, I had some successful flight yesterday as well. What I am not getting my head around most of the time it did work around 3pm until about 6pm during the week. Outside of this window I get almost 100% of the time CTD.
At the end this would indicate my system should not be the root cause.

PS: I did share several logfiles via the support ticket I mentiond above including DxDiag, MSinfo that provides them with a more deeper view into my system and its configuration.

I’m struggling to pinpoint what the issue is on my side as nothing else crashes on my system apart from MSFS24. I can be online in iRacing/Asseto Corsa for hours without the system missing a heartbeat but within minutes of MSFS24 loading it’s CTD and back to the start.

I like you don’t think it’s our systems which is the issue. As you’re aware I’ve been trying on both Windows 10 & 11 installed on NVME’s and SSD’s and this makes no difference.

Below is my system specs:
7800x3D
64GB DDR5 6000MHZ
4070Ti - 566.36 drivers (Also tried 566.03 and 566.14)

1 Like

Same here, I can run DCS, Assetto Corsa, Assetto Corsa Competitione, F1 23 / 24, iRacing, DayZ, Elite Dangerous, Star Citizen, Dirt5 and a bunch of other games.

System Specs:
Intel(R) Core™ i9-14900K, 3200 MHz, 24 core
ROG MAXIMUS Z790 HERO
(RAM) 64,0 GB dominator_titanium
NVIDIA GeForce RTX 4090 24GB
Microsoft Windows 11 Pro 64 bit

1 Like

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

Provide extra information to complete the original description of the issue:
• Also with large planes on my PC such as Airbus A330, A400M, 747-8, 787

If relevant, provide additional screenshots/video:

As it has recently come to light that during the big rush for installation, in the early days after release, and the severe demands on the CDN server, there might be corrupted files on your system, a reinstall might, and i did say might, address the issue.

If you haven’t already tried, what’s the worst that could happen. :wink:

Thank you for your suggestion. Personally I did this almost on a daily base over the last week or so.
Beside a ton of other suggestions from MSFS Support.
Did several times DDU with fresh installation for my nvidia driver, uninstalled the language pack and did a fresh install, checked windows system integrity, FlushDNS, deleted several times my online profile and many other suggestions from Support.

Today I got the following message from Support:

Thank you for contacting Microsoft Flight Simulator Support today.
If the issue still persists, we ask you to wait for the patch 3 to go live later tonight and trying again to see if the situation has improved. This is a big batch and will include a lot of fixes for issues users have been reporting.

Right now I would everybody recommend to wait until the patch arrives before performing another install.
Not sure how reliable the information from Support is and there might be some showstopper appearing during the day. But at least I would wait until the patch arrives.
And maybe do a fresh install after the patch arrived.

No need to try to troubleshot something that might be out of our control

2 Likes

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

Provide extra information to complete the original description of the issue:
• Random and consistent white and black screen crashes. Waiting for the big fix this week.

If relevant, provide additional screenshots/video:
•No problem with MSFS 2020

Sim continues to CTD after patch 3. Not able to start a flight. This is just hilarious.

60h of “play time” with 2h of actual flighttime. Since the sim seems to run sometimes only the majority of the time not I judge for myself it is not related to my system.

I guess I call this a mike drop. For all of you that are able to run the sim, have fun and enjoy it!
I am sure in a couple of month it will be really good.

Faulting application name: FlightSimulator2024.exe, version: 1.2.7.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000211a7203a20
Faulting process id: 0x0x1988
Faulting application start time: 0x0x1DB4B8B20A6AAF6
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.2.7.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: unknown
Report Id: f9e422b9-e42a-42a5-85c7-cbcd61fd9fef
Faulting package full name: Microsoft.Limitless_1.2.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Have you tried running the exe ‘as Admin’?

Apparently, exception code 5 is an access denied issue and running as admin is one of the suggested workarounds in the guide at Basic Troubleshooting: How to troubleshoot crashing/CTDs issues – Microsoft Flight Simulator Support

There might be another suggestion in there that sorts your issue permanently.

Thank you for your replay.

I did run as admin and not as admin

Started in save mode and normal

DDU – NVIDIA driver a few times

Just running vanilla without any addons

Sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

Changed my system language to English (US)

Ipconfig /flushDNS

Used different DNS Adress (Cloudflare)

New installation even after patch 3

Ripped out one of my RAM to go down to 32GB

Did reduce the number of cores down to 20

Did send the support several Dump files and System information

And a few other suggestions

I am running out of options here.

Might sound as a silly question, but have you any software like Afterburner running in the background? Or, like, have you an overclocked system?

No, and the strange thing is sometimes a day it does work. Primarly in the afternoon local time.
This would indicate to me it is not related to my system.