1 minute ago, sniper31 said:

Well, so much for SU14 now. Out of two flights conducted, same friggin' SU13 CTD error code. I give up....all different hardware, complete reinstall, vanilla MSFS and same old CTD as SU13 and SU14. Argh.....

But Landon, did you try the half duplex fix? I mean I've now had dozens of good flights without one CTD since I did that.

It works with the half duplex, yes, but that is a work around, not a solution. I was hoping SU14 would fix the actual cause. 

2 minutes ago, sniper31 said:

It works with the half duplex, yes, but that is a work around, not a solution. I was hoping SU14 would fix the actual cause. 

Ok, good then, I know it ain't a fix nor is it perfect but at least I can fly without a CTD now.  I don't see any difference with this half duplex business.

1 minute ago, Jack_Sawyer said:

Ok, good then, I know it ain't a fix nor is it perfect but at least I can fly without a CTD now.  I don't see any difference with this half duplex business.

Well, no difference when flying, but when I want to play something else OR download an update for MSFS or something else, it's a big difference.

Just now, sniper31 said:

Well, no difference when flying, but when I want to play something else OR download an update for MSFS or something else, it's a big difference.

I see.  I don't use this PC for anything but MSFS, not even surfing or email.  I'm a Mac guy.  However, when SU14 came down the pipe it was as fast as always.  I have AT&T fiber almost right to the PC.

1 minute ago, Jack_Sawyer said:

I see.  I don't use this PC for anything but MSFS, not even surfing or email.  I'm a Mac guy.  However, when SU14 came down the pipe it was as fast as always.  I have AT&T fiber almost right to the PC.

Well, I have 1Gb fiber right to my flight PC too, but at half duplex downloading on it is very slow. But, oh well, it is what it is. If Asobo didn't fix it in SU14 then they probably are not going to. So, I can hope MS2024 does not cause the same CTD. Never ever in my years of using a PC for flight simming or gaming have I had to manage or lower my data speed. The ONLY time I have ever had to do that is with MSFS SU13 and now SU14. 

1 minute ago, sniper31 said:

Well, I have 1Gb fiber right to my flight PC too, but at half duplex downloading on it is very slow. But, oh well, it is what it is. If Asobo didn't fix it in SU14 then they probably are not going to. So, I can hope MS2024 does not cause the same CTD. Never ever in my years of using a PC for flight simming or gaming have I had to manage or lower my data speed. The ONLY time I have ever had to do that is with MSFS SU13 and now SU14. 

Sorry Landon.  I'm indifferent but I know it's important to a lot of people.

Just now, Jack_Sawyer said:

Sorry Landon.  I'm indifferent but I know it's important to a lot of people.

Certainly not your fault, but thanks 🙂 

 

43 minutes ago, sniper31 said:

The ONLY time I have ever had to do that is with MSFS SU13 and now SU14.

It’s a hunch, but your PSU has remained the same with all your recent ‘builds’,

& I can fathom why reducing bandwidth potentially reduces ‘spikes’,

only a suggestion - no CTDs with Seasonic 1300W Platinum here - with the PSU running at about 600W max (about 50% - right in the PSU maximum efficiency zone) with Strix 3090 OC & 12900KS…

1 minute ago, craigeaglefire said:

It’s a hunch, but your PSU has remained the same with all your recent ‘builds’,

& I can fathom why reducing bandwidth potentially reduces ‘spikes’,

only a suggestion - no CTDs with Seasonic 1300W Platinum here - with the PSU running at about 600W max (about 50% - right in the PSU maximum efficiency zone) with Strix 3090 OC & 12900KS…

I've already checked that issue. And, no my PSU has not stayed the same when I tried another build. I have a few extra PSU's. My main one is a Seasonic 1050W Platinum that works flawlessly despite MSFS. But, just to check the box, I did switch it out with an EVGA 1100W PSU I had extra. The error code, which is ALWAYS the same points to software, not hardware anyway. 

Still, a good suggestion. 

Here is a new twist on the CTD problem, at least for me -- nor have I seen any mention of this in any earlier post. I have found that I can fly for an indefinite period (up to two hours or more) without a CTD, as long as the plane is in external view, but when I switch to panel view there is a CTD within a few seconds! Annoying as this is, it might actually serve as a useful clue to what is going on here. Any ideas?

1 hour ago, cobalt said:

Here is a new twist on the CTD problem, at least for me -- nor have I seen any mention of this in any earlier post. I have found that I can fly for an indefinite period (up to two hours or more) without a CTD, as long as the plane is in external view, but when I switch to panel view there is a CTD within a few seconds! Annoying as this is, it might actually serve as a useful clue to what is going on here. Any ideas?

That's a new one on me. With the CTD's I have been experiencing since SU13 and SU14, all with the same error code, I am in and out of the cockpit all through the flight. Up until it crashes. When I adjust my network adapter speed to Half Duplex 100 Mbps then I can fly without CTD's and jump in and out of the cockpit (I do this frequently to capture screenshots) without any problems or CTD's. 

But,that is my experience. 

I’m irate as I type this.  I had dozens of good flights.  But today I went into the sim to the default KSTS to take some screenshots for a comic I’m working on and needed an in flight exterior view.  I got a CTD after panning around.  All that was new was a Windows 10 security update.  Checked the half duplex and it had not changed.  M$ infuriates me.

Not getting CTD's, however long stutters/pauses and when closing it often doesn't close properly. Having to go into task manger and manually close MSFS.

Run the following commands…

Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return

and it will then run. Wait until each runs and finishes before you move on to the next one.

When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly

Dism.exe /online /Cleanup-Image /checkhealth

Dism.exe /online /Cleanup-Image /scanhealth

Dism.exe /online /Cleanup-Image /Restorehealth

sfc /scannow

Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTART your computer as the last step. Then go for a test flight.