It is really weird. So far I had 1 CTD with GSX installed on Friday, but none thereafter in the next 5 flights with the Bonanza, Islander and Fenix. All with Live weather, SU10beta. Hope it stays like that, but it sure is a shame for those who suffer from this!
..and if you havenât already and you are getting the âmemory could not be readâ message, please vote on the thread where that CTD has been discussed at length.
I have taken a Flight from EDDB - EDDK with Live Weather, Live Traffic (AIG), Acars, and GSX, everything was fine and GSX had worked also fine. My Last Driver Update is 4 Weeks or more ago.
Also no Worldupdates etc. taken in the last Weeks.
Yesterday and this morning I also had a couple of CTDâs, with or without GSX (SU9). Yesterday came another update of the world UpdateVI, maybe this is the cause of the CTDâs,?
yep.. for me is that the only relevant NEW error which never happens for users before and which started some days ago.
May be one exception is the âmemory could not readâ, but here we are still collecting informations âwithin the responsible topic for that errorâ whether also âmore NEW occurancesâ ( starting with same day as the ntdll issue ).
CTD:
FBW A320NX (Experimental version)
ENCN - ENGM (just prior to pushback for the return sector - same session as the first leg)
Live weather on
No live traffic, but on VATSIM (with AIG model matching)
SU9
DX11
Nvidia 3090
W10
As the header says i encounter crashes at nighttime. Since i started flyin at night time recently i cannot say if it would have been better some months before. At daytime i have no problems actually.
I tested actual and old grafic driver from NVIDIA but the night crashes still occour. I found some information within Windows (10).
The ID is 1001 and the Source is Windows Error Reporting.
Fehlerbucket 2255942993912543198, Typ 5
Ereignisname: MoAppCrash
Antwort: Nicht verfĂźgbar
CAB-Datei-ID: 0
xml version=â1.0â encoding=âUTF-16â?>10.019043(0x30): Windows 10 ProProfessional19041.1889.amd64fre.vb_release.191206-14061889Multiprocessor FreeX641031MoAppCrashMicrosoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwepraid:App1.26.5.000000000StackHash_e74110.0.19041.18061000a5b9c0000374PCH_DD_FROM_ntdll+0x000000000009DA9410.0.19043.2.0.0.256.481031e741e7416f17cba8c0ab30fa39851c7eafcf2c3a2c3a61935d46a331d0e430dae9a0650eE258741F-4C8C-42B7-A875-890F26D65BCBSystem manufacturerSystem Product Name140716061574841601-01-02T22:07:04Z-01:000a4d1a758-7661-4cfa-a8d9-bf70306b90992022-08-21T12:30:26Z
General:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.26.5.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.1806, Zeitstempel: 0x1000a5b9
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000ff609
ID des fehlerhaften Prozesses: 0x1f10
Startzeit der fehlerhaften Anwendung: 0x01d8b546bbe2212a
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: 94ca1e25-37f6-4b6d-8a46-862308998dff
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App