Intel Xeon Extreme 3495X does crash too, you got to take it down to 32 cores.
Itās really a shame that a show stopping issue identified in the alpha and that affects so many users still hasnāt been fixed. I have had this issue with other games from indie producers who have fixed it literally within hours so I canāt understand why Asobo hasnāt fixed this yet.
This CPU only has 16 cores, so you cannot switch it down 
You mean you disabled HT?
AMD users/Threadripper users, even when I reduced core count, I was still getting a CTD until I turned off hyperthreading which then allowed the sim to load. Make sure you have this setting off if youāre still experiencing issues.
Such a shame, as people with high cores/threads could have really benefited with their current setups.
This has to be one of the worst game releases in history.
In the Fs2024 Beta Phase, IĀ“ve created a ticket regarding this issue, but it has been closed directly. And it looks like they havenĀ“t solved it yet.
IĀ“ve got the same system like @PixelHunter4664 but with an 3970X.
Also in my case with TR 3970X this solution works.
Number of cores limit 10.
One additional info, CTD appears on virgin windows 11 install 23H2with all the updates, just with latest Nvidia driver.
Made no difference for me.
AMD5950x, so 32 cores total (shouldnāt have happened already). Dropped to 30, then 20 - no difference at all, still hard shutdown whenever video starts to play during setup (no detectable spikes in temps/power in HWinfo at 100ms intervals)
Thanks ubahn, deactivating hyperthreading in the bios did the job for me also.
Seeing this issue: I have a AMD Ryzen Threadripper PRO 3975WX 32-Cores 3.50 GHz. I am sorry, but this is not solved. It has a workaround. Reducing the capability of my PC is putting the burden on the customer. Done SW / HW for years, and I would not accept this as anything but a workaround. I hope this gets solved.
Huge thanks to ubahnverleih for his post on this matter.
I have no idea how it works, but this has solved the problem for me (disabling HyperThreading).
After around 10 days of total failures to actually get into MSFS 2024, I can now do so consistently.
Thanks also to JamesGerlach465 - I have amended my workaround so that I do not need to worry about entering the BIOS again to change back.
This community really is wonderful!
I really hope Asobo sort this so that this āworkaroundā is not necessary any more.
Same as machtoo - i have the i9 10980xe and reduced the number of cores from 36 to 32 in msconfig and i have now finally got into the setup screen - fingers crossed all now workk ok.
I also have this issue. I have a TR 7960X, but for me disabling cores is absolutely not an option. I refunded it (again) for now, but i am hopeful for a solution.
Same issue running an i9 7980xe - reduced cores down to 32 and was able to play. I am hoping they fix this as this seems absolutely insane for a 2024 release.
the i9 10980xe only has 18 cores. something is wrong.
a āthreadā is not the same as a ācoreā - while a core is a physical processing unit within a CPU, a thread is a virtual construct that allows a single core to handle multiple tasks seemingly simultaneously, meaning you can have multiple threads running on a single core
Thereās a lot of use of total threads in this discussion. Iām in a similar position. I have 18 cores/36 threads. Once I reduced it to 16 cores/32 threads I can at least get into the sim. Obviously a true fix needs to be implemented, but I never would have even been able to get into the sim without this workaround.
Regards
Hyperthreading, 36 cores.
In case anyone is interested: The patch 1.1.10 does NOT fix the issue.
Ridiculous. I have had this issue with small, indie developers who fixed it within hours/days. Tell you just how poor their coders are.
Can we please tag this as a bug OP? I donāt feel like it should be marked as a work around.
1 Like
Well, without knowing the reason (which we never will), this is a little harsh. Though I understand that itās annoying to turn down the PC once you want to play MSFS2024 and donāt forget to turn it up again for all other programs in the world, it might well be that itās hard or even impossible to reproduce the error and trace it in the debugger. Thatās what Iāve often experienced with parallel threading in both C++ and C# as well.
This is definitely not an amateurish thing to do.