What wil cause a CTD in Level flight after1/2 hour of flying?

Please tag your post with either msfs-2020 or msfs-2024 if you would like to discuss a specific sim.

In MSFS2024, I can successfully load in any airport ad take off. During level flight about 1.2 hour in I get a CTD. The demand is not high on my PC ad Temps are all good. Community folder and addons have no play as I am level an in middle of an Ocean for instance. Why the constant CTD??

Are you approaching a large city when it happens?

My CTDs (FS2020) seem to mostly be related to hardware. Unsure about FS2024, but a power-hungry USB device like a StreamDeck can cause havoc unless I use a powered USB hub.

Also make sure your USB devices aren’t going to sleep on you.

No idea if these are your issues, but worth a look.

1 Like

No idea if it might be part of the issue but are people making sure their RAM is working ok without errors?

Even good memory can go bad over time. A test run with Memtest86 can help make sure it’s not just a dying memory cell causing an issue. Most PCs don’t use ECC RAM so errors may not be detected until it crashes a program.

1 Like

I can be flying over the ocean, or just sitting on the runway not moving and I’ll get a CTD over time. The FP are incredible, and smooth, but it just crashes. NVidia 4090 card and 13900K cpu. I have MSFS2020 on ssme computer with 100 addons on it and it NEVER crashes. Why does MSFSS024 crash daily and MSFS2020 NEVER crash???

Generally that kind of errors would give a BSOD, not a CTD.

Moved to User Support Hub > Crashes (CTDs) as OP is requesting community assistance.

I have a better solution to my problem:
Give up on MSFS2024 - It is seriously lawed. I’ll fly my MSG2020 on the same computer with 100 addons and scenery maxed out - I still get >100 fps.
Wake me up when MSFS2024 is fixed by Asobo.

What hardware? I’m able to fly for hours upon hours on end in MSFS 2024 maxed out.

Had the exact thing happen in 2024 but not 2020. For me it was due to the last windows update last month.
Everything was fine until then.
Just out of interest have you updated either bios or Windows Update?
I updated my asus z690 to the newest bios. 4301 and my whole PC started crashing randomly. Seems it is quite a common issue so reverted.
The other was a day or so later Windows applied 2025-06 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5063060)
Now crashes exactly as you describe. Only in MSFS2024.
Again removed and barred this update and all is good again. After some research online it seems quite a few people are having the same issue in quite a few games and not just MSFS2024. Even Microsoft have acknowledged it.

1 Like

In my case was DDR memory speeds. I can run FS2020 on full EXPO (XMP for AMD) ram settings but not FS2024. I had to underclock my ram 200mhz to get it stable and never had any CTDs again.

1 Like

I had seemingly random CTD’s and a few BSOD shortly after 2024 came out(2020 was always stable). Sometimes it would be on the world map, sometimes on the ground sometimes on descent after a 3 hour flight.

I disabled XMP
Reduced my active cores from 32 to 30
Reduce my P Core ratio from iirc 55 to 53.

I’ve now had 1 CTD since early this year and that was caused by an addon. Overall my system is WY more stable.

1 Like

OK - the problem was solved (I am the one who started this thread). Apparently my computer ingested a great amount of dust and dog hair and completely blocked the fans. After that was removed, the computer operated without CTD. Still a mystery why only MS2024 crashed while MSFS2020 ran perfectly.

I was getting tons of CTDs in May and June, both in MSFS 2020 and 2024 (Live version and SU3 Beta), which forced me to stop flying completely.

Last week, I did a full reinstall of my PC, and since then, everything has been running smoothly—no more crashes so far.

I’ve noticed that VRAM usage is quite high: around 10–11 GB out of 12 GB on my RTX 5070, even in default scenarios.

My system specs:

  • CPU: Ryzen 7 9800x3D
  • GPU: NVIDIA RTX 5070 12 GB
  • RAM: 64GB DDR5 6000Mhz
  • Monitor: MPG 491CQPX

I’m leaning toward a few possible causes:

  1. A bad or buggy NVIDIA driver version
  2. Something on my system that was conflicting with MSFS (and also with some other game)