1 minute ago, Sonosusto said:

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.

I have not installed all the WU's yet. I have three WU's installed (both USA ones and a Europe one) and everything else still default. I am wanting more successful flights before I add anything else. When I do start adding stuff, it will either be one at a time or small groups of items (like scenery). But, I am nowhere near ready to start that yet. All that said, I pretty much ruled out addons being the cause way back when I had a brand new fresh install of MSFS during this process and still was getting the same CTD. So, think conflict all you want, but when I had a fresh new install of MSFS, there was nothing to conflict with, and I still would get the CTD. I am telling you, it is something within the SU13 code that is affecting some of us. There is nothing else it can be at this point.

19 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.

I'm tipping MS will offer this as a solution at some point... only to find that some of us randomly fall off our desk due to a mysterious conflict! COD - Crash Off Desktop! As Dr Zachary Smith used to say.. "oh, the pain..the pain!"

2 minutes ago, vonduck said:

due to a mysterious conflict! COD - Crash Off Desktop!

Haha!!!!!!! Good one! 😁

12 minutes ago, sniper31 said:

I have not installed all the WU's yet. I have three WU's installed (both USA ones and a Europe one) and everything else still default. I am wanting more successful flights before I add anything else. When I do start adding stuff, it will either be one at a time or small groups of items (like scenery). But, I am nowhere near ready to start that yet. All that said, I pretty much ruled out addons being the cause way back when I had a brand new fresh install of MSFS during this process and still was getting the same CTD. So, think conflict all you want, but when I had a fresh new install of MSFS, there was nothing to conflict with, and I still would get the CTD. I am telling you, it is something within the SU13 code that is affecting some of us. There is nothing else it can be at this point.

Interesting. Question: were there any windows updates recently you've installed that changed any settings? I see you don't have NVIDIA stuff but I assume that sometimes their drivers updates and/or windows updates can change settings. I realize you already checked for hardware issues.

Example: After one particular Nvidia and/or windows updates.....I had to reset my XMP profile in the BIOS settings. My nvidia control panel even changed several settings. I only ask because I also have been really trying to research some answers for you. Apparently, there are reports of AMD-relating issues and their version of a BIOS profile as well.

What was the fault bucket ID  and event ID's again?

I guess this version of the sim is also ridiculously more sensitive to any overclocking, underclock, ram freq etc etc.

 

Edited November 20, 20232 yr by Sonosusto

2 minutes ago, Sonosusto said:

Interesting. Question: were there any windows updates recently you've installed that changed any settings? I see you don't have NVIDIA stuff but I assume that sometimes their drivers updates and/or windows updates can change settings. I realize you already checked for hardware issues.

Example: After one particular Nvidia and/or windows updates.....I had to reset my XMP profile in the BIOS settings. My nvidia control panel even changed several settings.

What was the fault bucket ID  and event ID's again?

I do indeed have Nvidia "stuff"... I have an MSI RTC 4090 GPU (listed in my sig). But, no Windows updates anywhere around the time of SU13. Drivers, Windows updates, GeForce settings etc, those are all in the early stages of my troubleshooting and things I have checked off more than a few times already. Here is a copy of my Event Viewer notification when I get the CTD:

AppName FlightSimulator.exe 
  AppVersion 1.34.16.0 
  AppTimeStamp 00000000 
  ModuleName FlightSimulator.exe 
  ModuleVersion 1.34.16.0 
  ModuleTimeStamp 00000000 
  ExceptionCode c0000005 
  FaultingOffset 00000000023f9441 
  ProcessId 0x18d8 
  ProcessCreationTime 0x1da14d700431f8e 
  AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe 
  ModulePath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe 
  IntegratorReportId 37124043-c1b6-49d7-96b0-231872851dac 
  PackageFullName Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe 
  PackageRelativeAppId App 

The only thing that changes when I get this CTD is the Faulting Offset code...that one is different every time I get the CTD.

27 minutes ago, sniper31 said:

I do indeed have Nvidia "stuff"... I have an MSI RTC 4090 GPU (listed in my sig). But, no Windows updates anywhere around the time of SU13. Drivers, Windows updates, GeForce settings etc, those are all in the early stages of my troubleshooting and things I have checked off more than a few times already. Here is a copy of my Event Viewer notification when I get the CTD:

AppName FlightSimulator.exe 
  AppVersion 1.34.16.0 
  AppTimeStamp 00000000 
  ModuleName FlightSimulator.exe 
  ModuleVersion 1.34.16.0 
  ModuleTimeStamp 00000000 
  ExceptionCode c0000005 
  FaultingOffset 00000000023f9441 
  ProcessId 0x18d8 
  ProcessCreationTime 0x1da14d700431f8e 
  AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe 
  ModulePath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe 
  IntegratorReportId 37124043-c1b6-49d7-96b0-231872851dac 
  PackageFullName Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe 
  PackageRelativeAppId App 

The only thing that changes when I get this CTD is the Faulting Offset code...that one is different every time I get the CTD.

If I am not mistaken, that process ID looks familiar. I think that has something to do with Windows Office or Windows 365.

Good grief. The exception code is always useless.

Have you tried using the flight sims "improved" crash report and sent that to Asobo?

Do you use DX 11 or 12?

Have you reverted back to an older Nvidia driver? I realize this all changed after SU13 but it's worth a shot to test out a few previous versions since you're using the default sim right now anyway.

 

Edited November 20, 20232 yr by Sonosusto

1 hour 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 !!!

If you have World Update 6 installed, uninstall it and try again. I've seen people reporting World Update 6 causes them CTD's.

12 minutes ago, Sonosusto said:

If I am not mistaken, that process ID looks familiar. I think that has something to do with Windows Office or Windows 365.

Good grief. The exception code is always useless.

Have you tried using the flight sims "improved" crash report and sent that to Asobo?

Do you use DX 11 or 12?

Have you reverted back to an older Nvidia driver? I realize this all changed after SU13 but it's worth a shot to test out a few previous versions since you're using the default sim right now anyway.

I do not have any version of MS Office installed on my sim PC. 

Yes, I have sent the crash report to Asobo. No response at all.

I have tried both DX11 and DX12 (pretty sure you've already asked me that;) )

Tried all kinds of different GPU drivers, old, new, middle. 

2 minutes ago, Alvega said:

If you have World Update 6 installed, uninstall it and try again. I've seen people reporting World Update 6 causes them CTD's.

Not the cause of my CTD's because I get it even with a vanilla install of MSFS and no WU's installed. 

1 minute ago, sniper31 said:

Not the cause of my CTD's because I get it even with a vanilla install of MSFS and no WU's installed. 

I know, I was replying to @thecanarian.

4 minutes ago, Alvega said:

I know, I was replying to @thecanarian.

My bad...should have read your quoted text. Sorry.

 

Though, I would highly suggest installing all world updates at this point. The reason why I mention this (again) is because I did have an issue (my own fault) where I completely forgot to install WU10 and 11 altogether I was getting CTD's all the time. That was after 3+ days of testing out addons, hardware, settings just to find out I missing WU. On a whim, I downloaded and installed them and no more CTD's It's worth a shot at this point.

4 minutes ago, Sonosusto said:

Though, I would highly suggest installing all world updates at this point. The reason why I mention this (again) is because I did have an issue (my own fault) where I completely forgot to install WU10 and 11 altogether I was getting CTD's all the time. That was after 3+ days of testing out addons, hardware, settings just to find out I missing WU. On a whim, I downloaded and installed them and no more CTD's It's worth a shot at this point.

Yeah, I'll get them all installed eventually. But, I am a methodical troubleshooter, so I am not going to install them all in one big whop. Install, some test flights, rinse and repeat. I don't want to change the variables too much at once. 

At this point, the limiting my NIC data speed to 100Mbps Half Duplex workaround, and I stress, workaround-not solution, seems to be the answer right now. I can only hope that Asobo/MS fix the coding issue that they introduced with SU13, and I can put my NIC back on Auto-Negotiation and leave it there so I can enjoy my high data speeds that I am paying for. 

1 hour ago, sniper31 said:

Yeah, I'll get them all installed eventually. But, I am a methodical troubleshooter, so I am not going to install them all in one big whop. Install, some test flights, rinse and repeat. I don't want to change the variables too much at once. 

At this point, the limiting my NIC data speed to 100Mbps Half Duplex workaround, and I stress, workaround-not solution, seems to be the answer right now. I can only hope that Asobo/MS fix the coding issue that they introduced with SU13, and I can put my NIC back on Auto-Negotiation and leave it there so I can enjoy my high data speeds that I am paying for. 

Hi Landon, I know someone posted a link on how to do this but despite my reading it and re-reading it I’m not sure what or how to do what you describe.  Any advice for a neophyte like me?  I’m not even using my sim now because of the exact CTD’s you describe.

6 minutes ago, Jack_Sawyer said:

Hi Landon, I know someone posted a link on how to do this but despite my reading it and re-reading it I’m not sure what or how to do what you describe.  Any advice for a neophyte like me?  I’m not even using my sim now because of the exact CTD’s you describe.

This video covers it:

(1) 🚀⚙️ How to change Link Speed of Ethernet Adapter Windows 11 ✅ - YouTube