No crashes here.

Edited September 19, 20214 yr by Tuskin38

I've had 1 ctd since the hotfix after installing updating content manager and trying to exit the sim. Checking event viewer said it was kernel based. Restarted my system and no more ctd. 

Been flying the tbm with the mod and FBW experimental version. Just landed in Vancouver from Miami. No issues at all. 

Make sure you guys are checking to make sure no other suspect files are being loaded with the FlightSimulator.exe file like the capture one program. That was what was causing my crashes 

12 minutes ago, devgrp said:

Make sure you guys are checking to make sure no other suspect files are being loaded with the FlightSimulator.exe file like the capture one program. That was what was causing my crashes 

That is a point I thought about too. For my next flights I will probably not use Aivlasoft EFB which needs to run FSUIPC7 additionally.

Patric

2 hours ago, bobcat999 said:

I wouldn't be surprised if a lot of the recent CTD fixes have been lost again since the Friday 'hotfix'.  They lose control of their own code quite frequently.  Evidence = history and the latest batch of regressions.  

I wouldn't be surprised either. I see that the long pauses are back since last HF at my end. Maybe my connection, maybe not...

15 minutes ago, Dominique_K said:

I wouldn't be surprised either. I see that the long pauses are back since last HF at my end. Maybe my connection, maybe not...

The servers do seem to suffer a heavy workload at the weekends.  I get the little box popping up saying connection lost quite a lot now.  It tends to  come back on after a few seconds, but it can do it again at random throughout the flight.

3 hours ago, rayharris108 said:

Just wondering if CTDs are still related to overclocked graphics cards? I can't run MSFS anymore without running the GTX1080ti in debug mode - and no add-ons enabled. That's the case for me anyway even since WU6 HF1.

Mad!

 

 

None of my hardware is overclocked. 

Zero CTD's here w/ all flights thusfar (I guess this is about 4~) in the default 787 and Cit Longitude.

Edited September 19, 20214 yr by Noel

I will do a series of flights today with stock aircraft, no add-ons enabled. So far the 787 looks stable. 

I just had three consecutive CTDs.  Today was my first activity since the most recent HF.  I had experienced zero CTDs since a total reinstall after SU5 and it's subsequent HF.  That spanned 24 flights for a combined 43 hours.

My first difficulty today came with the world map.  Wish I had taken a photo.  There was a broad bright red arc from N to S  against the left edge of the world map.  When I started my flight I got an immediate CTD.  I was starting from a fresh system reboot.   Next  I rebooted my system again and attempted to start.  Received the Safe start dialog.  Ignored it and continued normally.  Never got to the checking for updates phase.  MSFS not only produced a CTD.  It caused my computer system to reboot.

I started MSFS once again, proceeded past the Safe mode dialog.  MSFS otherwise started normally.  Turned off AI Traffic.  Started my flight and got about 40 minutes into my flight.  Everything seemed well.  I performed a screen capture.  MSFS froze with the exception of audio, which continued.  I decided to wait it out.  Eventually MSFS went from frozen to CTD.

Rebooted.  Proceeded once again past the Safe mode dialog.  MSFS seemed to load just fine.  Started my flight again.  Got halfway down the runway, CTD again.

I was flying the Robt Young enhanced Turbo Bonanza with no change in loaded scenery or other mods since before the HF.  My previous 38 hours had been in the Turbo Bonanza.

WE BADLY NEED A ROLLBACK PROVISION ON UPDATES AND HF.  Much similar to rolling back a Windows Update.

😡

 

Edited September 19, 20214 yr by fppilot

This thread imho clearly shows the randomness of CTD's, lots of them introduced with SU5. While my WT CJ4 is prone to CTD since SU5 ( as the OP also indicates), the same route is perfectly flyable with the modded TBM and WT G3000 - yet other users suffer from CTD with the TBM. And while a lot of tips may be benfecial for one or the other user, the majority don't seem to change the situation. Which seems pretty logical to me: ASOBO has dramtically changed the sim core with SU5. Pre-Su5 I had 1 (one!) CTD in all the months since release, probably due to a faulty addon. Since SU5 the CJ4 suffers from CTD randomly, meaning it can be on taxi to the active, in flight, on approach and after landing. I thought I solved the problem with deleting the usercfg.opt file (one of the 1998 tips and tricks out there) as I completeted a 2:30hrs flight without issues - only to have a CTD after only 10 minutes the next day.

Matt Nischann has stated on the WT Discord that their CJ4 can not cause a CTD, they think it is underlying bugs in the sim itself what causes them. Zendesk however says it's the third party that is responsible to solve the issue. Perfect!

Long story short: imho all the vodoo out there doesn't change the situation for most users. Only ASOBO can - and has to!

Before SU5 CTDs were very rare for me. maybe 5 or 6 in several months. Since SU5 I get much more CTDs and with WU6 and its Hotfixit is even worse.

For me it seems that the sim becomes more and more fragile. It also looks like the sim is meanwhile much more sensible about add-ons. There may also be some cross-incompatibilities, which means it is not a particular add-on causing the CTD but rather the combination of two or more.

2 hours ago, Dominique_K said:

I wouldn't be surprised either. I see that the long pauses are back since last HF at my end. Maybe my connection, maybe not...

I have notices small stutter since this new HF!!

2 hours ago, bobcat999 said:

The servers do seem to suffer a heavy workload at the weekends.  I get the little box popping up saying connection lost quite a lot now.  It tends to  come back on after a few seconds, but it can do it again at random throughout the flight.

IN the pass year I have never had it, since SU5 its a 50/50 in every flight to get it, sure it reconnects and on I go.....Great!!

37 minutes ago, Nemo said:

Before SU5 CTDs were very rare for me. maybe 5 or 6 in several months. Since SU5 I get much more CTDs and with WU6 and its Hotfixit is even worse.

For me it seems that the sim becomes more and more fragile. It also looks like the sim is meanwhile much more sensible about add-ons. There may also be some cross-incompatibilities, which means it is not a particular add-on causing the CTD but rather the combination of two or more.

Never had CTD untill SU5......Hhmmm seems to be a patten here?

When do people ever learn in a CTD topic that simply posting I dont have them, is....better not say. Sure add some think for people to look at or do but "Zero CTD's here w/ all flight" yer Noel as normal very helpful. 🙄 He will start a poll next " people with no CTD please post" Right....🙄

"No crashes here.!" Epic!!! realy helpfull...........

Edited September 19, 20214 yr by Nyxx

12 minutes ago, Nemo said:

Before SU5 CTDs were very rare for me. maybe 5 or 6 in several months. Since SU5 I get much more CTDs and with WU6 and its Hotfixit is even worse.

For me it seems that the sim becomes more and more fragile. It also looks like the sim is meanwhile much more sensible about add-ons. There may also be some cross-incompatibilities, which means it is not a particular add-on causing the CTD but rather the combination of two or more.

Same here but only a few before SU5, after SU5 every other flight resulted in a CTD! No change with WU6, its probably worse actually! I only have Navigraph and the Longitude mod installed and no overclocking!

All of my crashes have happened in flight, never a problem on departure or approach! 99% of my crashes have been the same error except one!

Log Name:      Application
Source:        Application Error
Date:          19/09/2021 15:11:40
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-Q2EK6FG
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001263e8d
Faulting process id: 0x4cd4
Faulting application start time: 0x01d7ad5c936be375
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: fbe17e99-b1f9-47f6-bd81-917d75b18ee3
Faulting package full name: Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-09-19T14:11:40.1721219Z" />
    <EventRecordID>8072</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-Q2EK6FG</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>0000000001263e8d</Data>
    <Data>4cd4</Data>
    <Data>01d7ad5c936be375</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>fbe17e99-b1f9-47f6-bd81-917d75b18ee3</Data>
    <Data>Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

I had this error last night for the first time!

Log Name:      Application
Source:        Application Error
Date:          18/09/2021 18:27:21
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-Q2EK6FG
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: CoherentGTJS.dll, version: 0.0.0.0, time stamp: 0x6102bea6
Exception code: 0xc0000409
Fault offset: 0x00000000008042a1
Faulting process id: 0x31e4
Faulting application start time: 0x01d7ac8f1a20f183
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\CoherentGTJS.dll
Report Id: a3bf3461-6d50-4d73-bff3-b45800bf0842
Faulting package full name: Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-09-18T17:27:21.1773008Z" />
    <EventRecordID>7839</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-Q2EK6FG</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>CoherentGTJS.dll</Data>
    <Data>0.0.0.0</Data>
    <Data>6102bea6</Data>
    <Data>c0000409</Data>
    <Data>00000000008042a1</Data>
    <Data>31e4</Data>
    <Data>01d7ac8f1a20f183</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\CoherentGTJS.dll</Data>
    <Data>a3bf3461-6d50-4d73-bff3-b45800bf0842</Data>
    <Data>Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

 

Stock TBM causes CTDs. Going to try the Caravan next.