1 minute ago, OneOfMany said:

I understand that you are running the ram at 3600, however some amd motherboard chipsets have shown to exhibit latency issues with ram clocked this high. Intel as well. There are various chipset used in PCs that support your CPU, from value to performance oriented. Even though they will work fine in less demanding situations, higher throughput will exacerbate any internal timing issues. We see this often as a shop specializing in gaming rigs. My first recommendation would be to loosen up the timings. My second unfortunately is to swap to a better brand of RAM. Although g. Skill is popular, we have moved away from it over the years as the problems encountered, and number of kits requiring rma was the highest of all brands. It is popular because it is usually the least expensive available for its specs. 

The RAM works just fine, not switching that at all (memtest86 for 15-20hrs). I doubt MSFS is more demanding on the memory than, say, recompiling my Gentoo install (where most of the RAM is used during the crunching). Other games, such as thehunter:COTW, give me higher temps than MSFS and have never crashed during my 500hr grind. That MSFS somehow would be more efficient in discerning issues with my RAM where everything else fails feels quite far-fetched tbh. 

26 minutes ago, Swe_Richard said:

The RAM works just fine, not switching that at all (memtest86 for 15-20hrs). I doubt MSFS is more demanding on the memory than, say, recompiling my Gentoo install (where most of the RAM is used during the crunching). Other games, such as thehunter:COTW, give me higher temps than MSFS and have never crashed during my 500hr grind. That MSFS somehow would be more efficient in discerning issues with my RAM where everything else fails feels quite far-fetched tbh. 

More far fetched than the fact that lowering tree settings is the cure?  Your frequency of CTD is well above the norm to begin with, I’d suggest it wouldn’t hurt experimenting with things that seem far fetched at this point.  IMHO, getting expert advice from a PC gaming rig manufacturer about his/her experience with that particular RAM module makes the test slightly more worth doing as well.

From strictly public service standpoint, it could be very useful to the community if you did in fact discover that memory clock sync was an issue.  Worst case is that you confirm it’s not … which is also a useful data point actually.

Understand. Just basing it on my twenty five years of owning my business and seeing these issues hundreds of times over the years. I can't troubleshoot your system over the internet, only try to offer solutions. Since I am on mobile, I don't see your main board if you list your specs. 

Since for myself and others who do not experience any ctd, although there may be software issues, they should not cause the problems to the magnitude you are experiencing them. I have read your issues on multiple threads, and understand your frustration. 

A less invasive test would be to pickup a 500GB ssd (not even nVMe), install fresh OS, drivers, clean install the sim, attach basic peripherals only - mouse, keyboard and flight controller and test. No marketplace add-ons, no 3rd party, no external utilities. 

12 minutes ago, VFXSimmer said:

More far fetched than the fact that lowering tree settings is the cure?  

Absolutely. As the issue was introduced for me with SU5 it is not at all far fetched to assume a bug was introduced that triggers on certain combinations of hardware. This does in no way imply faults in the hardware itself (as it functions perfectly well in all the other use cases). 
 

On a second note, I’ve built all my computers going back the last 25 years (including the current one) so I am not new in this game either. 

Thinking about your case some more, here is something else to consider.

What were the changes from SU4 to SU5?  Most will be quick to point out the graphics engine, UI etc etc.  But another big change was the use of more CPU threads to run code in parallel.  It wouldn’t be hard to think that a memory clock issue would be sensitive to that.  
 

The majority of software isn’t tuned to be heavily multithreaded.  If it’s at all possible that this is a result of multi thread algorithms, your other software could run just fine and never see an issue.  Perhaps what you’ve discovered is actually poorly written code on Asobo’s part that is only triggered by an anomalous hardware event?  Since you’ve exhausted all of the more obvious ctd trigger cases, maybe it’s time to start eliminating the less obvious ones.

As some have suggested in other threads, do you have Sonic Studio on your computer? Apparently that causes CTDs for some. 

15 minutes ago, Swe_Richard said:

On a second note, I’ve built all my computers going back the last 25 years (including the current one) so I am not new in this game either

Don't get me wrong. I am not implying that you are not knowledgeable nor capable of working with hardware and software. It is a simple matter of numbers where you see and troubleshoot these problems on a daily basis. I have only owned about forty devices over my years, but have built thousands, and serviced even more. I and my staff run into quirky things every day, with any type of software, from business, OS, and games. 

1 hour ago, Republic3D said:

As some have suggested in other threads, do you have Sonic Studio on your computer? Apparently that causes CTDs for some. 

Nope! No sonic studio. 

What wattage is your PSU?

4 minutes ago, Bobsk8 said:

What wattage is your PSU?

Not at the computer right now, but I’m pretty sure it’s 860W. 

Man stop being stubborn and lower your ram timing like what some of the others suggested. What do you have to lose? It's either going to work or it's not. 

2 minutes ago, devgrp said:

Man stop being stubborn and lower your ram timing like what some of the others suggested. What do you have to lose? It's either going to work or it's not. 

It's really part of the low hanging fruit, a piece of cake to test and rule-in or out.  Absolutely, lower the ram timing it's not relavent at all in terms of frame rate or other anyway.

8 minutes ago, devgrp said:

Man stop being stubborn and lower your ram timing like what some of the others suggested. What do you have to lose? It's either going to work or it's not. 

Because it shouldn’t be needed..? Was that your intellectual contribution to the thread? 

What is model of mobo? 

Edited August 19, 20214 yr by OneOfMany
Never mind. I'm out

2 minutes ago, Swe_Richard said:

Because it shouldn’t be needed..? Was that your intellectual contribution to the thread? 

I fear that if you're criteria to judge whether something is worth trying or not is just based on "Programs X, Y & Z run fine so program K should run fine too" then you're probably doomed to be stuck with your understandably frustrating CTD situation.  You can't pick and choose what data points to use in your troubleshooting. Since most others are not currently suffering the same fate, ignoring the "potential" that there is something unique to your particular hardware/software situation is not a wise state of mind.

"When you have eliminated all other possibilities, whatever remains, however improbable must be the truth" - Sherlock Homes