1 hour ago, fra147 said:

Same here, 2 CTD today (PC shutdown) after SU13. No FSTL, yes Fenix + PSXT/Real Traffic .

1st ctd approaching Mykonos, 2nd ctd approaching Dublin. Not a great day for my MSFS.

As well as here. Overflying Pairs in the Fenix A320 from EDDK to LPFR and on the return flight (LPRF-EDDK) as well CTD over Paris.

 

1 hour ago, hvw said:

As well as here. Overflying Pairs in the Fenix A320 from EDDK to LPFR and on the return flight (LPRF-EDDK) as well CTD over Paris.

There seem to be quite a few reports of CTD's coming in after this update, including my own.  Do you by any chance have the new rex accuseason advanced installed? 

I did a third flight but without CTD yesterday night. EDDM-EDDB...

Just as an attempt, I would like next days to momentarily disable GAIST because the CTD I had where always over the sea...

12 hours ago, Pilot53 said:

 

There seem to be quite a few reports of CTD's coming in after this update, including my own.  Do you by any chance have the new rex accuseason advanced installed? 

No, I haven't got that Rex app. 

i dint have any ctd before this sim update but now every flight with ai traffic from fslt or fs Hud atc injected i get ctd, with fslt sometimes just 30 seconds after start injecting aircraft suddenly crash  i think is something related with Sim connect cause sometimes happens with little nav map alone also 

8 hours ago, hvw said:

No, I haven't got that Rex app. 

I guess we can probably rule that out then

On 10/1/2023 at 4:43 AM, SquadronLeader said:

Having just returned from holiday, I updated to SU13 yesterday and set up a flight in the Fenix A320 yesterday from KLGA to KDCA. The only add-on I was using was the updated FSLTL. Not sure exactly when, but about half an hour in to the flight I had a CTD - not had one of these for many months. So, thought I would try a different flight, and again with the Fenix A320, I set up a flight from KDCA to KORD, and again used FSLTL. The same thing happened - a CTD after half an hour or so in to the flight.

In checking with this forum, I saw a similar type of thread, in which there was a reply that suggested that FSLTL may be injecting too many objects - which could be the cause of the CTD.

So today, I set up a new flight with the Fenix A320 form KDCA to KORD - but this time WITHOUT FSLTL, and the flight was absolutely fine, and thankfully no CTD - so I assume that I can safely say that FSLTL is the cause of my CTDs - can I?

I recall that there are some settings in FSLTL, which allow you to determine the number of airplanes that are injected - not sure why the parameters may have changed (if indeed this is the cause of my CTDs) from pre SU13 to post SU13. Any thoughts or suggestions - maybe someone could advise me of the changes that I need to make to the settings with reference to the number of airplanes injected.

or - any other thoughts.

 

Hi George,

As others have mentioned make sure you have the latest version of FSLTL installed. After SU13 the main Sim files were updated I could not install the Eastern Europe update and the sim kept crashing. I did try later and the updates processed successfully but I did also do the following which I do after each major update. The commands below might help with your situation.

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

 

Edited October 2, 20232 yr by RJC68

On 10/1/2023 at 7:46 PM, fra147 said:

2 CTD today (PC shutdown) after SU13. No FSTL, yes Fenix

exactly my issue as well.  Completely shutted down my PC and I´m not using FSTL but AIGAIM and Limited at 60% Traffic usage in AIGAIM/AIGTC

I had struggled with CTD over a month and found the solution is to slightly limit the performance of 4090. Using MSI Afterburner to under clock core/memory by -200MHz/-50MHz and set a power limit of 80% seems to completely get rid of the CTD for me in VR.

MSI AB is super easy and worth to give it a try. That is the only thing I did to solve the CTD issue. 

 

@FlyIce MSI afterburner is the cause of some CTDs and is one of the first things MSFS support will tell you to uninstall.

 

I use a etc 3090 and haven't installed MSI Afterburner, no Nvidia experience filters in use neither. 

The PC SHUTDOWN issues started after su13. 

28 minutes ago, Phantoms said:

@FlyIce MSI afterburner is the cause of some CTDs and is one of the first things MSFS support will tell you to uninstall.

 

Have always been using it (not for overclocking) and never had a CTD.

 

6 hours ago, Phantoms said:

@FlyIce MSI afterburner is the cause of some CTDs and is one of the first things MSFS support will tell you to uninstall.

I believe this is due to that MSFS believes, rightly so, that most people use MSI Afterburner to overclock their GPU therefore increase the chance of CTD. What I'm doing is the opposite: I use MSI Afterburner to underclock the GPU and apparently that helps me to get rid of the CTD.

Edited October 7, 20232 yr by FlyIce

FeelThere's KBNA does not seem to like FSLTL on my system.

Clean Community folder, except for Feelthere KBNA and the two FSLTL folders.  Insta-crash when loading a flight to north cargo gate 24.

Without FSLTL, loads up no problem.

I'm thinking AFCAD-type issue in Feelthere KBNA possibly, that isn't playing nice with FSLTL.

8 hours ago, Alvega said:

Have always been using it (not for overclocking) and never had a CTD.

That's great for you, but it's a known problem with many CTDs and was likely cause of a big CTD saga I had for a long time.

 

When I did finally go through the trouble of making a zendesk bug report, they had me send in a a msinfo file and a dxdiag file from my computer (instructions on how to generate them were also sent. Once I did that, the first thing they replied was:

Quote

We can see that you are getting exception code 0xc0000005 crash with your Sim. First, we recommend uninstalling MSI Afterburner and removing any overclock you might have on your CPU or GPU.

I didn't have any overclock and I wasn't actively using MSI afterburner anymore, but it was still installed on the system. I did a complete uninstall of it through Add/Remove programs. I also reset nVidia, etc. I had one single CTD a month later (probably a one off) after nearly a year of having them everytime I tried to fly and haven't had anymore since.

I can't say 100% it was MSI Afterburner ( I changed a couple other things then too), but given the fact that no more CTDs and the fact that it was the first thing MSFS support said leads me to believe it was a probability it was the cause.

2 hours ago, FlyIce said:

I believe this is due to that MSFS believes, rightly so, that most people use MSI Afterburner to overclock their GPU therefore increase the chance of CTD. What I'm doing is the opposite: I use MSI Afterburner to underclock the GPU and apparently that helps me to get rid of the CTD.

I'm not really sure that's why. I believe there are conflicts and that's why it's one of the first things suggested.

As I said, i wasn't even actively using it but it was still installed on the system. Undervolting itself could be the cause but you won't know until you stop and uninstall Afterburner to check. I didn't use Afterburner to undervolt, instead I used X1 precision for that. But during my trial of trying to find the culprit I had stopped undervolting and also uninstalled X1. However, since I wasn't actively using Afterburner I never thought to uninstall it. But even if you're not actively using it, it still loads up some stuff when you boot.

I no longer worry about undervolting (haven't about overclocking for years) which I did simply to not use as much electricity. I'm of the mind now that the more you mess with, the more chances you can cause problems.

 

Edit: BTW, if you want to file a bug report with MSFS zendesk they've made it real hard to find. Here's a direct link to it - https://flightsimulator.zendesk.com/hc/en-us/requests/new

Edited October 7, 20232 yr by Phantoms