sorry, it’s in german, but it should be obvious from the order of the options
I followed the recommendations of Aerosoft
1 Like
Since I disabled all traffic (AIG and Offline - live traffic) I didn’t had a single CTD anymore
1 Like
That’s some great update @ObjektHafen5513, thanks for sharing.
Yesterday I was lounging in KATL (Atlanta) for about an hour or two, leaving only AIG Traffic on and everything else disabled. I had also changed Generic AI models to off, so as to pick up AIG’s 3D models and liveries.
But I wasn’t doing anything at all, engines off and just having MSFS running in the background, watching random Youtube videos. From time to time I’d watch some departures and arrivals (fewer than what should have been , but that’s a different issue so we won’t linger on that here).
Happy to report no CTDs but it doesn’t really mean anything as I wasn’t approaching the airport as usual (where things often crash). However if it HAD CTD’ed at least I’d have known it’s not in-game Live/Offline traffic. Obviously the tests will continue.
I can also confirm that CTDs seem to be interconnected with AI traffic. Most probably there is some memory mismanagement leading to mem leaks or maybe some null pointer exceptions as AI traffic keeps disappearing and spawning randomly.
Anyways I just tried to turn off live ai traffic as some pointed out this may help. And indeed just did my first successful flight since one week. A320 VHHH > UBBB. 9 hours. stable 40 fps and most important NO CTD
Don’t know if this was coincidence, but as mentioned it was my first complete flight since one week.
2 Likes
This is not airplane specific, it happens on the default airbus tbm930. It just happens more on the airbus because I push more buttons on that plane.
Any chance of this ever getting fixed?
I have no traffic enabled, yet I’m still crashing at the end of long flights when turning on final. ALWAYS when turning on final
Faulting application name: FlightSimulator.exe, version: 1.23.11.0, time stamp: 0x00000000
Faulting module name: CoherentGTJS.dll, version: 0.0.0.0, time stamp: 0x619d19ff
Exception code: 0xc0000409
Fault offset: 0x0000000000804d1d
Faulting process ID: 0x4644
Faulting application start time: 0x01d828e15eb60284
Faulting application path: G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\CoherentGTJS.dll
Report ID: 81bcd6a3-025e-47a5-8296-340b60a55ee3
Faulting package full name:
Faulting package-relative application ID:
1 Like
ColinM99912, try other aircraft or other version of aircraft.
So it may not be AI traffic (or only AI traffic) after all. Got yet another 0x…05 CTD this time with AI traffic off, directly above the destination airport at the end of a 2-hour flight. So much for immersion. Had only multiplayer and VATSIM on. Had never visited that airport before and it wasn’t a modded version.
It must be something related to airports alone, so I’ll try to disable all airport-relevant addons (REX textures, flightsim addons for airport vehicles etc. The problem is it doesn’t always do this (perhaps about 30-50% of the time), and it only happens after a significant amount of time, e.g. 1-hour flights or longer. Anyway, if SU8 doesn’t fix this one way or another, I’m out. I’ve had enough.
Some folks have found using a preset weather condition instead of live weather, as well as disabling traffic has helped.
and still also no issues in bit longer flights ( beside of the fact that the DC-6 is a bit cpu demanding )…
( still ATC windows-offline text2speach setting )
Hello,
through many sim updates i have the problem, that the sim keeps crashing and crashing (with and without OC/mods/…).
My Systemspecs:
MSI MPG B550 Gaming Edge
Amd Ryzen 7 5800X (2.8.0.1937)
Geforce RTX 3060Ti (511.79)
32GB RAM
Its on its own NVME PCIe 3.0 SSD Drive (1TB) installed
Windows 11 (64bit) (KB5010414)
Temps are well undercontroll (55-65, in 0.1% of the time it hits the 70°C mark)
Either its this Failure im getting:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.23.12.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: clr.dll, Version: 4.8.4470.0, Zeitstempel: 0x61b72dcc
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000669e40
ID des fehlerhaften Prozesses: 0x19a0
Startzeit der fehlerhaften Anwendung: 0x01d82c27aff41bb3
Pfad der fehlerhaften Anwendung: E:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Berichtskennung: 99d07b86-f54f-49ee-8f02-ac564599342a
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
or this one:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.22.2.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.22000.469, Zeitstempel: 0x931cda92
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000358ce
ID des fehlerhaften Prozesses: 0x459c
Startzeit der fehlerhaften Anwendung: 0x01d82bfd74dd84e4
Pfad der fehlerhaften Anwendung: E:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: c4d29198-3978-42e0-85ca-89013e5c485f
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Im sorry that its in german. Does anyone has a solution? What i did so far: Disabled OC, Tried lower Settings, Disabled Live -Weather, -Traffic; did a clean install, started with a empty Community folder; disabling sound drivers; disabled HAGS and Game mode; disabled Rolling Cache; cleaned the rolling cache folder/files.
Nothing helped even updating to the SU8 Beta didnt brought any difference.
Have you capture one installed ? Then look here:
Otherwise you can search in forum for exact these two dll mentioned in error log: clr.dll and ntdll.dll
1 Like
thank you so much! the hint with Capture One did the trick!
1 Like
CTDs before or immediately after landing are even worse in SU8. Essentially every single 2+ hour flight I’ve tried with WT CJ4 has crashed, either during final or while taxiing to parking.
Yesterday it CTD’ed 2 miles before landing in LOWL with vcruntime140.dll error which I hadn’t seen for more than a year. What’s worse is that subsequent attempts to load a flight starting from LOWL would crash with the same error during loading. It happened 4 times in a row and I have never seen this before. I only managed to load a LOWL flight when I quit Simtoolkitpro (which hasn’t caused any other issues afaik). Might be a coincidence, might not.
Today I decided to not launch Simtoolkitpro at all and I landed in ESNZ after a 3-hour flight, but crashed a couple of minutes later while taxiing. AI traffic was off, as I had only enabled multiplayer.
Turning live weather off is out of the question.
I’ve gradually removed almost all addons and I’m doing some tests with the last few remaining. The problem is that MSFS will crash during/after landing only after long 2-hour flights but never for shorter ones. So this makes it difficult to replicate or conduct tests easily. I’ve grown past frustration, I’m just laughing at what else this thing has in store.
Of course 99% of these issues stem from the fact that CTD logging is non existent so you never know what exactly was it that crashed the game.
I think I’ll just switch to Elden Ring for now until Xplane 12 is out.
same issue for me… don’t know what the problem, It worked fine until last update 8.
You guys ever get audio popping/crackling? I see spikes in my CPU performance when I hear the pops. Starting to think this is an audio driver issue perhaps.
CTD (three times) soon after takeoff from YMMB (Moorabbin) to YMML (Melbourne Intl) using stock Bonanza G36, Few Clouds, Real Time, and empty Community folders. Total of five CTDs today, more than any time since installing on day 1. MSFS 1.23.12.0, North Europe server.
PC with Windows 10 64bit, DirectX 11, Intel i9-10900, RTX 3060, 32Gb RAM, 1TB NVMe (OS and MSFS) + 2TB 7200 rpm drive, primary MSFS monitor is 4K Samsung 43" TV, other monitors are 23" HD. Saitek Yoke, Throttle, Rudder Pedals.
I attempted the same flight with my Carenado M20R Ovation with identical results - MSFS crashes as soon as I acknowledge “frequency change”.
I set YMMB (Moorabbin) as my departure with no destination. After takeoff my Carenado M20R Ovation (purchased through Marketplace , up to date) was flying on a heading of 310 and MSFS crashed about the same point. No communication with ATC after takeoff. I flew the M20R, 172 (G1000) and others earlier today with no incident).
I installed Nvidia Driver 497.29 and repeated the flight with no issues. No guarantee, but hopeful.
Just yesterday again on final approach at EDDN ILS 28 Z with A320neo and CTD.
Smooth flight for 9 hours and then bam…
1 Like