Classic British Flight Sim

Just pushing back from the gate at EGCC in Pmdg 737 700, and CTD. Sim up and running 15mins or thereabouts

Log Name: Application
Source: Application Error
Date: 22/08/2022 16:24:15
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: FLIGHTSIM
Description:
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: 0x6bc
Faulting application start time: 0x01d8b6388e8863ba
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: adac3f0b-4038-4efa-9f39-699205a419a4
Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App


Will rollback graphics driver as first step
Dale

Just tried flying north from Brisbane again, this time in the default DA-60, and after about 40 minutes, another CTD. Waiting on Asobo to come up with something - they have acknowledged the problem, at least.

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.22000.832, time stamp: 0x3907dfbc
Exception code: 0xc0000374
Fault offset: 0x000000000010c9a9
Faulting process id: 0x4908
Faulting application start time: 0x01d8b6380d90533a
Faulting application path: G:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: 8f074a1f-3482-4b89-9894-08a076fab32a
Faulting package full name:
Faulting package-relative application ID:

Let me know how you get on Dale.

My flight today was reasonably short (under an hour) and I was able to ALT Tab between FS and LNM without issues.

I haven’t made any changes to my online settings and the AI etc was all working fine today, as was ATC.

I was using the 146-200.

Here was I thinking that I had tweaked MS2020 up a tad too much and all the time it may not have been me after all!!

Regards
Nigel.

Nigel H-J wrote: ↑

22 Aug 2022, 18:54

Here was I thinking that I had tweaked MS2020 up a tad too much and all the time it may not have been me after all!!

Regards
Nigel.

It's affecting a lot of people world-wide, Nigel. Even 737NG Driver mentioned it on Youtube. He had to turn all data services off for his live stream preview of the 737-800.

Well I rolled back the graphics driver back to 516.59, (easier said than done) and set off again Egcc to Venice Lipz in the 737 All setting as per normal no deleting of cache or anything all data services on real weather photogrammery etc
Perfect flight no issues Are there several things at play here? If its server related as many suspect how does that affect a graphics driver How does a driver cause ntdll.dll to crash
Dale

Glad you got a good flight in. I wonder if there is some Nvidia bloat interfering with a change thats been done server side?

Not sure Ben, but on installing the rollback I had the option to just install driver, or driver and experience. I opted for just driver. The install then removed nvidia experience and existing driver and installed just the driver. Still a bit bothered that defender was picking up a trojan within the 516.94 package. Nvidia report nothing wrong (false positive), but somethings amiss. I've let defender remove all trace of it.
Dale

Had a quick flight yesterday to check out the updated Islander without any problems, but it ctd'd today about 45 seconds after takeoff.
Hey ho, back to Blender I go.

Almost 2 hours there without issue.