Hi Guys/Gals,

I hope this helps someone, because I just spent the better part of a day trying to get 1.5.9.0 running on my older system. It is an i7-10700 Gen 10 CPU with a MSI GTX-1660Ti GPU. I "had" 96GB of Ram in it using two 16GB Corsair sticks and two 32GB Crucial sticks. This new beta started crashing the second I upgraded to it from the last beta version 1.5.8.0. It would crash at 5% and sometimes at 20% loading. If I went back to SU2 there were no problems loading and running the program.

After a day and a half of a dog chasing its tail with uninstalling and reinstalling a plethora of stuff, reverting to earlier BIOSes, wearing my fingers raw in the BIOS setup, and plugging and re-plugging RAM, I'm now down to one stick of the 32GB Crucial Ram in there and now the program starts all the way every time.

So my bet is a lot of the CTDs and issues people see with this program are due to its silly hypersensitivity to hardware issues or timings that don't affect other programs or Windows itself.

BTW, I ran a memory test program which booted from a USB stick to completion with the original setup and it completed without errors.

Jaxsimmer

2x16GB Corsair RAM sticks and 2x32GB Crucial RAM sticks? That is a very unusual combination.

5600x, 32GB RAM, 3060 ti 8GB GRAM... No issues, CTD s, degraded performance so dar, LOD both at 100.

56 minutes ago, Christopher Low said:

2x16GB Corsair RAM sticks and 2x32GB Crucial RAM sticks? That is a very unusual combination.

I was running with 96GB of RAM. The Mobo will go up to 128GB. Other than two different brands, the sticks are the same. DDR4-3200. I couldn't even run with a matched set installed, i.e. two 32GB sticks or two 16GB sticks. Only runs now with one stick in one slot, giving 32GB.

19 minutes ago, Jaxsimmer said:

I was running with 96GB of RAM. The Mobo will go up to 128GB. Other than two different brands, the sticks are the same. DDR4-3200. I couldn't even run with a matched set installed, i.e. two 32GB sticks or two 16GB sticks. Only runs now with one stick in one slot, giving 32GB.

Maybe 2024 don't like aggressive timings. Have you tried setting everything back to default?

1 minute ago, Bigmack said:

Maybe 2024 don't like aggressive timings. Have you tried setting everything back to default?

Yes. Total default. No OC on anything. SU2 I could OC 34%.

5 minutes ago, Jaxsimmer said:

Yes. Total default. No OC on anything. SU2 I could OC 34%.

What about your system temps?

2 hours ago, Jaxsimmer said:

 

So my bet is a lot of the CTDs and issues people see with this program are due to its silly hypersensitivity to hardware issues or timings that don't affect other programs or Windows itself.

BTW, I ran a memory test program which booted from a USB stick to completion with the original setup and it completed without errors.

MSFS 2024 will discover issues with your RAM that even MemTest doesn't pick up. Read my story here: 

 

Edited June 21, 2025Jun 21 by abrams_tank

10 minutes ago, Bigmack said:

What about your system temps?

They are fine, thanks for thinking of that though. My big point in all of this is I have never had an issue with MSFS2020 or MSFS2024 with any CTDs while running or startup issues of any significance up until SU3 1.5.9.0. I can count on the fingers of one hand issues I've had in terms of those areas since MSFS2020 was released. So it has to be something that has put this beta update on a knife's edge. Maybe its the added telemetry. Maybe its some tuning they did with CPU cores or the balance between CPU and GPU.

For best speed and reliability,  usually 2 sticks are better than 1, 1 stick is better than 4. 4 sticks better than 3.  Best to use 2 identical sticks.

Have you tried making a copy of your user.cfg file, then delete it from your system and l start 2024 and et FS build another one with default settings? Also start 2024 with a empty community folder.

Edited June 21, 2025Jun 21 by Bigmack

Your problem is using 2 set of dual channel rams from 2 different brands.

Regardless of your size combinations, it is recommend to use the same brand, type and timing for your ram.

I used to have 2x32 and 2x16 to make up 48GB, no issues as all, using Ripjaws, xmp 2.0, same timing for the 2 sets of dual channel ddr4.

When i decided to upgrade to all 64, I make sure I can buy the new set that is the same for my 32.

Your memory test is not going to really solve your obvious issue.

13 hours ago, Bigmack said:

Have you tried making a copy of your user.cfg file, then delete it from your system and l start 2024 and et FS build another one with default settings? Also start 2024 with an empty community folder.

Thanks for the idea, but already did that.

3 hours ago, Jaxsimmer said:

Thanks for the idea, but already did that.

Only other thing I can think of is getting the same memory type for all 4 slots or use same memory for 2 slots. and set dual channel in BIOs.

Generaly it is not recommended to use diferent RAM sticks in your system. For multiple channel ram (and you dont want to be just in single channel) you need identical 2 or 4 sticks. Sometimes it is not enaught to have same timeings and capacity, even the same manufacturer, you want exactly the same model.

Also, if you end up with only 2 sticks, be carefull in what slots you put them. Generaly its the slot 2 and 4. Never One next to other. Look in your MB manual what slots to use for dual channel memory.

It is not just MSFS sensitivity. Its system sensitivity.   

Edited June 22, 2025Jun 22 by Dankovic