CTDs are back

Typical attitude from someone who obvisouly does not suffer from recurrent CTD.

1 Like


Si I uninstalled and claimed a refund. thanks MS.

Welcome back…

Simple give us some informations about your issue. Mention the windows event log message, Installed Mods, Sytem Specs… etc…

■■■■■■■■, I like this straight ahead post.

1 Like

I got one and have been getting repeated CTDs with the DC Designs Concorde in Singapore Changi.

Faulting application name: FlightSimulator.exe, version:, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version:, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b97b5a
Faulting process id: 0x1ed4
Faulting application start time: 0x01d85282a80ebd50
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 947a9805-a453-45e1-b86b-f98c681e1eac
Faulting package full name:
Faulting package-relative application ID:

Same with me. Latest after 10 mins flying I get a reproducible CTD. At all airports I usually use: EDDR, EDDF, Wick, EGLW, ELLX…
Vanilla fresh installation. The whole mess started with SU8. I would love to return to SU7 where everything ran fine.

The event viewer shows a “clr.dll” error.
Makes no sense to fly at current. I am hoping for SU9.

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version:, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: clr.dll, Version: 4.8.4470.0, Zeitstempel: 0x61b72dcc
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000669e40
ID des fehlerhaften Prozesses: 0x4890
Startzeit der fehlerhaften Anwendung: 0x01d853db90726c77
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Berichtskennung: 29dab0d6-5309-4b84-8be2-7ddb950f97b8
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

and you didn’t happen to have CaptureOne installed?

If so: see here [BUG LOGGED] CTD caused by Capture One 20 codec - #12 by MichaMMA

1 Like

Hi MichaMMA

that seems to work :stuck_out_tongue_winking_eye: :partying_face: :partying_face:.
Although I had to de-install Capture One 22 totally, just renaming that particular file had no effect.
So, I will install CO on a diferent computer to do my image processing.

I don’t know how I have not noticed this hint, but you have made my day!!


hmmm… I thought there is also a setting to disable the explorer extension

In preferences/general … “Windows explorer integration” check box

But,… for the moment cratulation and happy flight :slight_smile:

how can I run a log to see why mine crashed?

You can have a look at the Windows Event Log, but that’s about it. It doesn’t currently have anything that approaches what X-Plan has.

ive got exactly the same crash offset 0x0000000001b97b5a as you twice today.
have no clue what the cause is. Maybe i try disabling some addons.

yup same here. since the lase WU update.

I’ve been stable and all of a sudden crashing crashing crashing. I uninstalled it, pending the update for tomorrow.

1 Like

Unfortunately same for me. Had no issues whatsoever until SU8, then followed tons of CTDs, the bulk of them when I click FLY NOW on the world map. The loading bar gets to about a third or a little more and bam - I’m back to the desktop. No error messsge, no clear indication via Event Viewer.

Some days it’ll happen 10 times in a row, with the whole cursed loop of booting the sim up again, then suddenly it works and runs perfectly smooth for hours. Then the next day it’s back to CTD. It’s driving me absolutely nuts.

Safe mode works most of the time, but even a minimal load of well established 3rd party addons like PMDG, Aerosoft, etc. increases the risk for CTD by a metric ton and I am just baffled.

No idea how it can run so well and smooth once it gets past the first loading screen and the rest of the time it must act out one dramatic stage croak after another.

And Unfortunately SU9 did not bring any remedy. Welp… guess this will continue to be a straining hobby.


The only CTD I’ve had at all is with a mod, which hasn’t been updated/changed for SU9. Everything else is working fantastic.

The clouds are LEGIT, ps.

I am having the same, but after SU9.
Now checking the mods in my community floder.

1 Like

This game just ■■■■, I dont know how to say but after almost 2 years we still fight with thiss issues and ctd. This Sim is a mood killer! I dont play this game anymore I am out, no mods, new computer, all was good but after the update 5 and 7,8 and also now I get mostly ctd’s!


Well, I have found my culprit - it was the Taog44 UH-1D. Threw it out of the Community folder and no more CTDs, the sim is running perfectly fine now.

If you (like me) really like the UH-1D, though, keep an eye on Taog’s product page on flightsim.to. At the moment the file is unavailable, telling me he is already working on a fix. So I’ll be patiently waiting for an update to this otherwise very well made addon.

By the way: anybody have a link to Taog’s Discord? The link on the product page is expired unfortunately.

1 Like

So did you have crashes even if you weren’t actually flying the UH-1D?

Yes, that can & does happen.