MSFS2024 - CTD 5 out of 5 attempts today

I suppose there must be at least some people in the air whenever the devs make changes to the server-side code. I suppose the only way to avoid any issues that might bring, would be to retain the old code as well as the new and use some form of time stamp to decide which to download, after comparing with the time of the start of the flight.

It looks like they’re not doing that however and perhaps that would produce more issues than it would solve?

However, some form of notification of the time of day when such changes might be applied, would not be a bad idea. I remember Eve Online had, and maybe still does, an hour or so every day where the system was maintained and wasn’t available. Downtime wouldn’t be absolutely necessary, but anyone that flies then, might need to accept that something might change during their flight. If it only takes a few minutes to apply the changes, at a published time, people could always just delay their flight, I suppose.

2 Likes

Is there evidence of this anywhere, there has to be some sort of log to determine the causes and fixes. Is it that they just don’t reveal this and never give a heads up to what’s being done behind the scenes. I’m all for fixes, but for the people that walk away and wait months to return, it would benefit them to see the tweaks and give the game another attempt.

1 Like

Sorry no hard evidence, just my opinion based on what I’ve experienced and read in the forum

1 Like

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:

It IS a problem with the servers.

What software is that?

It’s a cap from the game itself. You can see your balance on career mode.

1 Like

Ohhhh, thank you.
Haven’t got that far myself, this week it’s been crashing on career mode every single time, as soon as I was ready to land after two hours missions.

I feel compelled to share this one here.
I’ve been emailing back and forth with Zendesk about these Crash issues.
Nice people, but look at the state of our conversation:

Hello again.

Just a follow-up because I can’t shake this part of your answer out of my head:

Zendesk> Our servers would not make your app crash. It just does not function that way. We can stop trying to troubleshoot the matter for you if you would like. I do not think that this is something that a patch will resolve for you. T

Over the past month, I’ve experienced numerous random crashes despite thorough troubleshooting on my end. Reinstalling, deleting files, or clearing the cache has provided only temporary relief. After deleting the locally stored cache files, the sim runs smoother initially, but it eventually crashes again. This pattern strongly suggests server-side issues or potential problems with corrupted data being retrieved.

Remember, once again, I even bought new RAM modules and upgraded to 64 GB of RAM as suggested.

Moreover, I’ve noted a stark difference in stability between Microsoft Flight Simulator 2020 and 2024. The former, running on DX11, is smoother and stable, while 2024 with DX12 exhibits frequent crashes, stuttering, and performance issues. This suggests the root cause could be tied to the new DirectX 12 implementation.

Your previous response suggesting discontinuing support was disheartening. As a paying customer who has spent €135 on this game—the most expensive one I’ve ever purchased—I expect a higher level of service. Since November 20, I’ve barely enjoyed the sim. Every time I launch it, it’s not to enjoy flying but to test the software, expecting crashes or bugs. At this point, I feel like an unpaid (Alpha) beta tester.

I understand it can be frustrating to address repeated issues, but as a user, I’m equally frustrated being told to repeat the same ineffective troubleshooting steps. Please acknowledge that the issue likely resides in the software or servers and escalate this to the appropriate teams. It’s your job to investigate and resolve these issues—not mine.

You swear that “Our servers would not make your app crash”. Bold statement, if you ask me.

For context, here are examples of industry precedents where server-side issues led to significant crashes:

Blizzard Entertainment (World of Warcraft): Server-side issues during major updates caused widespread instability.

Electronic Arts (SimCity 2013): Persistent crashes traced to overloaded servers.

Asobo Studio (Microsoft Flight Simulator 2020): Initial releases faced similar server-side performance problems.

Oh look! Asobo Studio! MSFS 2020! What a coincidence, right?

I urge you to take this matter seriously. It’s unacceptable for me to dedicate over a month to testing your product without any meaningful resolution. Acknowledge the problem, investigate the server-side or DirectX 12 implementation, and improve communication with users who are actively trying to help.

Please take a look at the forums, I’m not the only one waiting for that patch that will not solve the issue for me (and thousands of other users).

Regards,

g

Zendesk> Updates will help with some of these issues. You will just need to wait for the dev team to work on the updates and release them though. The curent plan for 2025 is at least four big sim updates, then some smaller world and city updates in between.

Let me quote your words here:

We have multiple teams working on the sim and some are working only on console issues and others are working with something else. VR is important in the sim but compared to the total number of players, the amount of VR users isn’t that much. And that is also reflected on how much resources can be allocated to a specific area in the sim. We are still working hard and doing our best to fix the issues users have been reporting.

There has been three updates already with ZERO fixes for FUNCTIONAL bugs VR being addressed. Yet, cosmetic ones for Xbox users are getting out of the door faster than fast.

I can’t believe they are producing a game for VR and have no interest in fixing problems there? What madness. Imagine a car manufacturer refusing to fix problems that occur in 3rd gear. To me, that sounds a bit like “yes, we have VR, but for financial reasons we can’t afford a headset… or unfortunately we can’t support it due to a lack of know-how”. It would be interesting to know how they solved the problems in 2020.
In my opinion VR is absolutely necessary for a game like this. It’s the only place where you really “sit in the cockpit”. Sorry, but a game that is also called a simulator without VR is pretty useless, I can go right back to playing free size.

And a happy new year to everyone.

1 Like

I have tried to play this game now three times since installing just before December 25th.

Each time it has crashed.

Today the ATC menu randomly popped up on the screen and I could not close it. All of the keys (ESC, SHIFT + C etc) stopped working as did the menu you can click on top centre of the screen when in flight.

I had no option but to kill the game from task manager.

I’m uninstalling it for now. Way to buggy and waste of time to try and play.

In my opinion this is the buggiest version of FS every and I have been playing since the very first version (no exaggeration).

2 Likes

Hi
2 CTD today

the last one
/!/ CRASH /!/TOML
[OnCrash]
Msg=“_handleSEH”
Type=“SEH”
Code=0xC0000005
[Engine]
ReportVersion=10
ExitApp=false
TimeUTC=2025-01-04T15:50:05Z
BuildVersion=“1.2.8.0”
UnscaledDeltaTimeMs=28.415
TimeSpentRunningMs=8512745.821676
TimeSpentPauseOffMs=8512745.821676
TimeSpentTurnedOnMs=8512745.821676
ContextUID=-9154056804916151200 #0x80F641D61139BC60
MemInfoUID=-8993757680751053521 #0x832FC10A52E4752F
DebuggerAllowed=false
AllocatedMem=27362816000
FrameCount=397765
IsMSIXVC=true
Purpose=“CGameGuiManager_G”

And the other one
/!/ CRASH /!/TOML
[OnCrash]
Msg=“_handleSEH”
Type=“SEH”
Code=0xE06D7363
ThrowName=“gxzB|zX1dOQ\\U[Zyz@8yyK@i”
[Engine]
ReportVersion=10
ExitApp=false
TimeUTC=2025-01-04T13:27:35Z
BuildVersion=“1.2.8.0”
UnscaledDeltaTimeMs=5930.511718
TimeSpentRunningMs=1654979.283252
TimeSpentPauseOffMs=1654979.283252
TimeSpentTurnedOnMs=1654979.283252
ContextUID=-1001966259347431445 #0xF2184CFEEAAB5FEB
MemInfoUID=-2334718888154999308 #0xDF99698A852055F4
DebuggerAllowed=false
AllocatedMem=16766529536
FrameCount=261001
IsMSIXVC=true
Purpose=“CGlobalFlow_G”

There are 3 other reports with the same Purpose=“CGlobalFlow_G” from yesterday. Any Idea from what it comes?

1 Like

You could ask Zendesk about it, but they’re gonna tell you something like this:

The error messages are just generic, we know it’s crashing but we don’t know why.

That’s what they tole me at least. So all that info means nothing to them.
Please don’t shoot the messenger.

Cheers!

I am absolutely frustrated with the MS/ Asobo team who cant get their ■■■■ straight. One simmer mentioned a software/ coding issue which introduced a memory leak/ out of memory issue.

I also really agree with this memory leak theory . I feel this CTD started with the last upate in FS2020. I have played it for 4 yrs and never had as many random CTD’s as i did with FS2020 in the last few months on the year. To the point that FS2020 was un playable , and i was looking forward to the ’ Better’ sim, FS2024.

9/10 times the error code i 0cx000005 [ out of memory / memory cant be read]

Well, same horrible coding issue seems to have happened with FS2024 and 100% worse now, CTD;s every time, completely random, and inevitably its the 0xc00005 [ out of memory] code in event viewer.

I cannot explain enough my frustration/ anger and bitter dissappointment at Asobo. All they want to do is make amazing videos [like they did for 2024] / Over promise and under -deliver.

The only thing that works well in FS2024 is the opening video; thats it. after that, its a ■■■■ show. random CTD;s, within seconds of hitting FLY NOW. some just in the menu.

2 Likes

What is your system spec?

I’m having the exact same issue as DocAdnanA described. The sim constantly crashes to desktop (CTD), almost always with the same 0xc00005 error code. It’s completely random and makes the game unplayable. I’ve spent 3500 euros on this setup, including the PC, joystick set, and MSFS 2024 Aviator Edition, and for what? To maybe enjoy an hour of playtime, if I’m lucky, before another crash happens? This is utterly unacceptable.

My system specs: MSI MEG Z790 ACE MAX (MS-7D86) motherboard, Intel Core i7-14700K CPU, 32GB G.Skill RAM (7200 MHz), Samsung 990 PRO SSDs (1TB + 2TB), NVIDIA GeForce RTX 4080 SUPER, and Windows 11 with all the latest updates.
I’ve done everything possible: updated all drivers, reinstalled the GPU driver from scratch with a clean install, and I’m running the latest NVIDIA driver (566.45). The only thing left is reinstalling Windows, but I refuse to go that far.

How is it possible that users are being left to deal with these problems? I’m a software developer myself, and I can’t believe the solution here seems to be analyzing individual user configurations or relying on workarounds. This is not how you deliver a reliable product. We’re paying a premium for this, and it’s absurd that something as fundamental as stability isn’t even being properly addressed. This level of frustration is beyond words.

3 Likes

I did all this too. My fix was dropped my cpu back to 5.6ghz (14900k) all perfromance cores and dropped my 7200 ram back to 7000 still on xmp II. not had a single ctd since and performance is actually better in 2020 and 2024

With 32gb you can often run into to problems. check your ram usage using the developer mode fps

Windows 11, i9-13900K @ 3.00 Ghz, Asus RTX 4090, 128 GB RAM
latest Asus ROG mobo BIOS, latest Nvidia driver

Still worth a shot for anyone running i7 or i9 13th or 14th gen CPU’s

I solved my CTDs by turning Hyper-Threading Off on my 14900K. That said, I also solved it by using Windows “High Performance” Power Plan with HT On. BTW, I’m also running my 14900K at 6.1 Ghz on 2 P-Cores, 5.8 Ghz on all P-Cores, and 4.5 Ghz on all E-Cores. That’s the max overclock I’m able to get and remain stable. I also tried downclocking to solve the CTDs, but that didn’t help. If you really want to maintain the performance that the 13th and 14th gen processors have to offer, try using the Windows “High Performance” Power Plan to improve stability.

My OC mods in the BIOS include:

  1. Using the default Gigabyte Aorus Master X Z790 power setting of “Optimization” (not one that’s Intel approved)
  2. Limiting PL1 and PL2 to 320W
  3. Limiting ICCMAX to 400A
  4. Setting 2 P-Cores to run at 6.1 Ghz
  5. Setting 8 P-Cores to run at 5.8 Ghz
  6. Setting 16 E-Cores to run at 4.5 Ghz
  7. Using the TVB setting to reduce all P-Core clock speeds by 100 Mhz at 80 degrees C
  8. Using the TVB setting to reduce all P-Core clock speeds by another 100 Mhz at 90 degrees C
  9. Running the RAM on XMP1 with both “Low Latency” and “High Bandwidth” enabled

With these settings and coupled with my Corsair H170i AiO cooling solution, the processor consistently scores 66,500 on the current PassMark Benchmark test (Ver. 11.1, Build 1002) and remains perfectly stable. The PassMark average for the 14900K is 59,797 and the median is 60,690. Interestingly, the PassMark average for the 14900KS is 62,064 and the median is 62,510.

And “yes”, it can run MSFS 2024 with those OC settings without CTDs as long as the Windows Power Plan is set to “High Performance.” While I don’t see more than a 1-2 FPS improvement with my OC, I do see significantly more consistent and smoother frame times.

1 Like