1 hour ago, altenae said:

Wel 

Fresh install in 2 different hardware.
No overclock and community folder empty.
So maybe a "you" problem maybe not

Yes, ignore that cheap throw-away comment.  It is a bit insulting to users really to call it a 'you' problem. 
We all know we can have trouble with both DX11 and DX12, especially with the dreaded GPU errors.

2 hours ago, flightskyc said:

Of course they do.

Definitely sounds like a you problem, unstable overclock, add on issues etc. I use and have used MSFS in dx11 with very few problems.

dx12 causes ctd’s for me. Dx11 fine.

It might be a "you" problem but the TS isn't blaming someone, he just wants to fix the issue and wonders why there isn't better information to help troubleshoot it. I tend to agree most issues are caused by issues on our own systems but still these need to be resolved. Addons are relatively easy to troubleshoot although timeconsuming but hardware issues usually are not  and it is difficult when one has so little information to go on.

For several months all my flights ended in CTD's and I had only generic error code. Lots of people had that very same error in the event log but the causes varied between soft- and hardware, video issues, overclocks and ram issues.
Ultimately it was a fault in the USB device driver that needed to be fixed by AMD but even if there was nothing I could have done to solve it knowing about it would at least save me lots of time and I might have resorted to using workarounds instead of trying to find and fix the issue.

This is starting to become a rant but:
On the whole I think MSFS is very unstable and needs either luck or a very well thought out combination and hardware and still luck to have all the UEFI settings correct and the right version of device drivers installed.
A single driverupdate, bios setting or a change in the distance between Saturn and Venus could throw a perfectly working combination suddenly off course.

I have had months of bliss where everything worked perfectly and then have suddenly nothing but issues with MSFS without a good clue of what happened. In the meantime, Windows and dozens of other applications continue to work as if nothing really changed, but not for MSFS.

I had a rash of CTDs, every day for months, and it turned out my brand new PC had a GPU -PSU problem. They were replaced by the manufacturer, and since then I have almost 2 years of flying  for hours everyday, with no CTDs at all. MSFS is not unstable, until it gets loaded down with buggy add ons, or defective hardware, 

Edited April 20, 20233 yr by Bobsk8

2 hours ago, Bobsk8 said:

I had a rash of CTDs, every day for months, and it turned out my brand new PC had a GPU -PSU problem. They were replaced by the manufacturer, and since then I have almost 2 years of flying  for hours everyday, with no CTDs at all. MSFS is not unstable, until it gets loaded down with buggy add ons, or defective hardware, 

If it was stable it would not crash due to an add-on 😉

Edited April 20, 20233 yr by altenae

20 hours ago, altenae said:

Why is ASOBO not collecting CTD info automatically  ?

They actually do . Not all but some definitely

Check "Microsoft Flight Simulator" under "View all problem reports"

https://www.top-password.com/blog/view-or-clear-problem-reports-in-windows-10/

16 minutes ago, altenae said:

If it was stable it would not crash due to an add-on 😉

You feed garbage into any computer, and it will crash. 

17 minutes ago, Bobsk8 said:

You feed garbage into any computer, and it will crash. 

When I install an addin for an Office application and it leads to instability that addon is automatically disabled by the software. I also get a notification from the application that addon so-and-so has been disabled because of <insert reason>.
I agree that hardware issues are difficult to trap but for addon issues at least Asobo should have thought of a mechanism to prevent CTD's when they allowed third parties create addons; They could lead to blue grass and green skies but CTD's should be preventable, especially if they leave no clue as to what caused it.
Even marketplace addons can lead to CTD's, one would assume at least some quality control there.

 

4 hours ago, orchestra_nl said:

When I install an addin for an Office application and it leads to instability that addon is automatically disabled by the software. I also get a notification from the application that addon so-and-so has been disabled because of <insert reason>.

Except finding the reasons for CTDs in Office compared to a flight sim has an insurmountable level of differences. 

4 hours ago, orchestra_nl said:

I agree that hardware issues are difficult to trap but for addon issues at least Asobo should have thought of a mechanism to prevent CTD's when they allowed third parties create addons;

how would that work? You would need to create some kind of instability checker on every single modifiable aspect of the sim and create some arbitrary “danger zone” for each of these. not to mention having to do all these among various threads that MSFS spawns.
 

It’s very easy to say “thought of a mechanism” but in practice it’s not the slightest bit easy compared to a word processor.

4 hours ago, orchestra_nl said:

They could lead to blue grass and green skies but CTD's should be preventable, especially if they leave no clue as to what caused it.

So then how would you prevent it ?

4 hours ago, orchestra_nl said:

Even marketplace addons can lead to CTD's, one would assume at least some quality control there.

 

it’s like installing a new rim on my car and the car starts acting up and I blame the car for being unstable.

the marketplace might have its range of test suites to ensure QC but it’s downright impossible to cover every edge case in something like a flight sim.

 

This is comes off a little short-sighted without regard to different complexities between two applications. Just because X does it doesn’t mean Y suddenly can.