One other thing I have noticed is that whilst I have always used my PCs sleep mode with MSFS without any issues, since SU13 I always get a CTD after coming out of sleep mode or a few minutes into continuing my flight.  I don't know whether that has any significance.

7 minutes ago, cianpars said:

One other thing I have noticed is that whilst I have always used my PCs sleep mode with MSFS without any issues, since SU13 I always get a CTD after coming out of sleep mode or a few minutes into continuing my flight.  I don't know whether that has any significance.

That could certainly give additional credence to a network connection issue as well. Many other things as well, of course, but network connections are finicky when coming out of sleep.

I had two CTD's yesterday and one today. Others reported CTD's today too on Microsoft's forum. SU13 is garbage and Microsobo shamelessly didn't even attempt to hotfix it with anything. 

8 minutes ago, cianpars said:

I don't know whether that has any significance.

Not for me it does not. Since my flight sim PC is only on when I am gaming, I have sleep mode disabled. A good thought though. 

41 minutes ago, sniper31 said:

I am starting to agree and lean to the same thoughts with the cause and also the work around. I am on my 6th successful flight after the 100Mbps Half Duplex change, and no CTD's yet. My MSFS install is still in a vanilla state, and I am still flying default everything. Still need to knock out some more successful flights in default mode, then eventually start to add in some addons and see what happens. 

I think you'll find that even if you reload everything, the half Duplex solution works. I have a significant set off addons enabled currently, all world and city updates, and the half duplex solution works every time. I get more stutters than I did pre-SU13, but I don't know if that's a network speed issue (and suspected syncing issue) or an SU13 issue.

Removing the photogrammetry cities made no difference.

Edited November 19, 20232 yr by mmcmah

I'm having much more 0xxxxxx0005 CTDs since SU13. Before SU13 I had maybe one every 6 months. My setup is the same and temps are perfect. It's definitely the SU13 and/or some server-side stuff.

Just now, Fiorentoni said:

I'm having much more 0xxxxxx0005 CTDs since SU13. Before SU13 I had maybe one every 6 months. My setup is the same and temps are perfect. It's definitely the SU13 and/or some server-side stuff.

100% SU13 is hosed. I haven't had a single CTD since SU5 and all of the sudden I am showered with them. What irks me is the fact that they're not hotfixing it with anything. Ugh. It's like I'm back in the FSX praying that it doesn't crash on final after a 3h+ flight. 

4 minutes ago, Fiorentoni said:

I'm having much more 0xxxxxx0005 CTDs since SU13. Before SU13 I had maybe one every 6 months. My setup is the same and temps are perfect. It's definitely the SU13 and/or some server-side stuff.

This is the exact code I am getting when I have my CTD's. And it all started with SU13 for me. 

Just tried a couple flights... 3 CTD's all while setup on FP setup page page. Seems to happen a lot but runs fine once finally loaded.

NOT beta

11 hours ago, sniper31 said:

This is the exact code I am getting when I have my CTD's. And it all started with SU13 for me. 

Problem is that‘s a standard/default code, that can be basically triggered by anything. It‘s totally useless, they could just as much give a popup „MSFS crashed but we have no idea why because we didn‘t bother to differentiate the exception errors“. 

I've had 5 attempts trying to get from LOWI to EGGD and on my sixth I tried the NIC workaround ie 100MB and half duplex. I hadn't loaded an approach into my BlackSquare B38 with the TDS GTN 750 I did it by the ILS in my NAV 1 with the APR in my AP. I got to within 2 miles of touchdown (after a few hours of flying) and got stuffed with MY SIXTH CTD in a row ! When will I ever be able to land my plane again !!!

12 minutes ago, thecanarian said:

I've had 5 attempts trying to get from LOWI to EGGD and on my sixth I tried the NIC workaround ie 100MB and half duplex. I hadn't loaded an approach into my BlackSquare B38 with the TDS GTN 750 I did it by the ILS in my NAV 1 with the APR in my AP. I got to within 2 miles of touchdown (after a few hours of flying) and got stuffed with MY SIXTH CTD in a row ! When will I ever be able to land my plane again !!!

Dang.  I’ve been following this thread for a while now and it’s getting depressing.  

7 hours ago, Fiorentoni said:

Problem is that‘s a standard/default code, that can be basically triggered by anything. It‘s totally useless, they could just as much give a popup „MSFS crashed but we have no idea why because we didn‘t bother to differentiate the exception errors“. 

Yes, agreed, it is indeed a rather vague error code. From what I can surmise, and also based on all of my testing and research, it at least tells me it's a software error code of some sort(s). In my situation, I have ruled out hardware, which if you have followed this thread are more than aware, but you are right. Trying to nail down what software issue the code is pointing to has proven extremely difficult. Maybe if I climb on top of my PC desk and do a kabooki dance, burn some incense, and chant in basic programming language, the solution will present itself. 😁 It's getting to that level....geez, I need a vacation...lol.

2 minutes ago, sniper31 said:

Maybe if I climb on top of my PC desk and do a kabooki dance, burn some incense, and chant in basic programming language, the solution will present itself. 😁 It's getting to that level....geez, I need a vacation...lol.

 LAUGHING OUT LOUD!!!!  🤣

That was brilliant Landon, you just made my day.

10 minutes ago, sniper31 said:

 I need a vacation...lol.

I think after this week, you should.

Have you installed the rest of the World Updates yet and everything else (default)? I keep thinking that there is some sort of conflict especially if you ruled out the data issues.

Edited November 20, 20232 yr by Sonosusto