Count me also
SU9 + Fenix 320
Two CTD today. The first one after landing at EGSS when I turned on GSX and I was chasing the “follow me car” (that one could be GSX relatd).
Second one after around three hours, on descend phase, on the second flight after a turnaround. GSX app was not running.
I have had two or three more CTD in the last two days, though I blamed those on GSX (which may not be the culprit after all).
Before that, two months “clean”
No FS updates, no changes in software or hardware (at least that I know).
Nvidia GeForce driver 512.95
i7 11700 + RTX360Ti + HP Reverg G2
All those CTD left not trace in the Windows event viewer, but at least in one I got the infamous memory error dialog box.
Ok so my fix above does not fix things just had another one. Going to give up with this just now until the developers get back in tomorrow and try and fix things.
SU10 will be released soon, maybe this will be fixed (or server problem due to a pre-release maintenance…). That’s will be weird but i’ve didn’t tried spiritism yet.
I just had also CTD, never happened before in MSFS for me. No new airports, airplanes installed since last flight.
EDIT: no GSX installed.
EDIT2: event from event log:
Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.19041.1806, time stamp: 0x1000a5b9
Exception code: 0xc0000374
Fault offset: 0x00000000000ff609
Faulting process id: 0xc240
Faulting application start time: 0x01d8b596e6b77113
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5a3fe2d1-24c1-4980-ba53-2706b93e72df
Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
More info with bucket ID:
Fault bucket 1855134808529458861, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_4ae8285069b969f313456703cb5b6fa9cd6766_936bb001_79bfb717-4686-452a-a2d2-ce073d4ab488
Summarizing all the data I’ve collected from this thread so far:
This specific CTD is only affecting PC players (both MS Store and Steam). Xbox and Xbox Cloud Gaming players are NOT impacted.
Only some, not all, PC players are getting this CTD.
This specific CTD starting occurring on or about Friday, August 19.
It is affecting players with both Nvidia and AMD GPUs. Driver version does not seem to matter.
It is affecting players on both the SU9 live build and the SU10 beta build.
It is affecting players on both Windows 10 and Windows 11.
It is possibly (unconfirmed) related to online services such as Live Weather, Live Traffic, and Azure terrain caching.
Based on the above, my personal best guess at this time is that it is indeed a change unrelated to the MSFS code or servers (I’m not making a definitive statement here; I could very well be wrong about this). The suggestion that it could be caused by an update to Windows (and/or Windows Defender) makes a lot of sense to me. It’s a good working theory that when flightsimulator.exe requests online data (such as live weather, live traffic, etc.), Windows Defender is somehow interpreting this as a security threat and terminates the application. That would explain why @GeomitraLNG1987does not get a CTD when flying over the UK (that terrain is already cached locally) but does get a CTD when flying over Australia (non-cached terrain is being requested from Azure).
As I mentioned in an earlier post, I flew for over four hours yesterday trying to replicate this crash with and without live weather enabled, but my sim was perfectly stable the entire time. I noticed today that I have two pending Windows Updates (see screen capture below) that will be installed the next time I restart my PC. If I reboot and install these updates, will I start getting this CTD?
I don’t use WIndows Defender though, my firewall + other protection is handled by a different application.
I must say it was pretty violently scanning for heurs-virusses the past few days though. It treated GSX and ProATC-SR pretty suspicious, while I normally don’t see it fire up so much.
Could there be some global activity going on too, large-scale cyberattacks that are shutting down servers and pulling up firewalls?
