On my 4th flight since the hotfix. First two were in the WT CJ4. No add-ons enabled except this and FB KDEN. One ended in CTD after 1 to 1.5 hours heading from JFK to Atlanta. Second flight same course ended in frozen sim maybe 45 minutes in. Third flight in stock 787 on same course did not lock up after an hour. Trying a longer flight in the 787 to confirm it was the CJ4. 

Edited September 18, 20214 yr by RobJC

Update: no CTDs with the stock 787 yet. 

Using Capture One?

The CJ4 is working perfectly well for me. 

Scratch that. Just had my first CTD since WU6 in the CJ4. Obviously don't know if the CJ4 is the cause but I suffered a CTD nonetheless. Fault was with MSFS .exe itself according to the logbook. 

Great.

EDIT: Maybe because I turned on AI-traffic for this flight...?

Edited September 18, 20214 yr by Swe_Richard

I have AI traffic on, hundreds of addons, and I'm getting no CTDs yet.

Okay did a flight from JFK to Hawaii in the 787 and no CTDs. Probably a 6 hour flight. But…my FPS was down to 20 when it started out at 60. So something is very wrong with long flights. 
 

 

2 minutes ago, RobJC said:

my FPS was down to 20 when it started out at 60. So something is very wrong with long flights. 

if you have air traffic turned on, turn it off and on again.

Just had one also.

Source
FlightSimulator.exe

Summary
Stopped working

Date
‎19/‎09/‎2021 10:10

Status
Report sent

Description
Faulting Application Path:    C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Problem signature
Problem Event Name:    MoAppCrash
Package Full Name:    Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe
Application Name:    praid:App
Application Version:    0.0.0.0
Application Timestamp:    00000000
Fault Module Name:    FlightSimulator.exe
Fault Module Version:    0.0.0.0
Fault Module Timestamp:    00000000
Exception Code:    c0000005
Exception Offset:    0000000001c6c7ca
OS Version:    10.0.19043.2.0.0.768.101
Locale ID:    2057
Additional Information 1:    e66f
Additional Information 2:    e66f8449f1bf36fb8ae1a3fac342e49e
Additional Information 3:    f7b7
Additional Information 4:    f7b7377c1e79aba5d94031a50d48a8ca

Extra information about the problem
Bucket ID:    37f22171b341b9baefdc4d65de7e0e5b (2295795009971949147)
 

 

Me also.  Mine was a proper lock-up after a few minutes of flying.  I got the blue screen with the smiley face!   I hope it is just a blip.

Quote

 

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!

 

 

I had a CTD on my flight from LOWW to GMAD too. I used the FBW A320NX (latest stable release). I was away from my PC for about 1,5 hours. As I came back to the desk, MSFS was closed.😐

At the event log there was a 0xc0000005 error to be seen.

Patric

 

Edited September 19, 20214 yr by pscharff

I am getting the same now. 1080ti. Was ok since the hot fix, but now crashing again.

0xc0000005

LFSB to EGPH FBWA320NX

Edited September 19, 20214 yr by ZKOKQ

I had two CTD, but both where when I stick in or stick out a USB-device.

I know that is better to do this with ESC tickt, but I think it was repaired.🤔

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.  

Yep me too.

TBM with latest mod and WT G3000 out of Orbx LOWI en route LIPB. CTD after 15 mins. (005c).

Regenerated Cache, running card in debug mode. Made no difference…