Repeated CTD's 1.18.14.0 & 1.18.15.0

Gday buddy…I’m not sure how much you have in your Community Folder and I like you have had CTD heaps of times since the sims first release…I came from FSX is I feel your pain. I have separate master folder which I place all my extras B787 mod, B777 mod, Airfields etc and as the sim gets its update I copy and paste my master to my community. Cheers Tricky

Yes - I moved everything out before the update and only put back in mods that have SU5 compatible. I wonder if there is a vpilot issue - many of my CTDs happen flying Vatsim, which of course makes them even more aggravating!

The curse of this sim is NOT CTD it is however ASOBO.

1 Like

Can’t do this anymore. I’ll have to wait, sim is broken to a point it is useless. We made a poll and 95% of our users reported regular CTDs (at least once every hour).

5 Likes

I feel your pain.

I just don’t understand how many users like myself do not
have CTDs and FS2020 is okay.

Someone at ASOBO should be able to determine this easily and quickly.

It would not take a Rocket Scientist.

1 Like

I had zero issues with CDTs until yesterday. I played for about four hours (PC), took a break, and tried to log back in and now I cannot get past the loading screen for a flight. I’ve tried every fix found in the forums, clean install, etc. and still no change.

Stumped…

2 Likes

Because bugs don’t work like the many people that automatically go around saying it’s user error and their machines are a mess, believe. There are too many variables that your PC can be fine but bugs can hit one system but not another. The fault is in the software, Asobo broke many things, AGAIN, and seems like they are trying to beat each previous update on how many issues they can add, it’s just some people have been lucky that not everything lined up to cause the bugs to activate, or some are too oblivious to the issues or don’t use said features. Can’t blame users and their PC’s though when the thing is crashing on console too.

1 Like

Not that it’s mods causing these CTD’s, but do you really copy and paste the files back and forth every update? If so I highly recommend Addons Linker on Flightsim.to. No need to move files with that, you put and organise your mods in folders anywhere you like and it adds links to them in your Community folder. Saves time and wear and tear on your drives and easier to narrow down a problematic mod.

2 Likes

Been getting repeated CTD since SU5 and it’s ■■■■■■■ me off, I spent $160 AUD on this game I didn’t pay for it to be a beta version

1 Like

Well , seems using Full screen mode instead of Windowed make it stable for me.
Fying since more than 15minutes now in full screen, while less then 5 minutes in windowed mode.

Hope the tip will work for you as well.

Edit : now more than one hour flight time …still no CTD :slight_smile:

Iv been having the same issue for 2 days… I removed my OC (MSI Afterburner) and reinstalled the sim and it seems to be fixed… it looks like to me the update has a bug relating to over clocking

LOL… the bug is the overclocking. It is not called without any reason “OVER …”

Even with the clock set to vanilla the crashes still happened… I uninstalled msi and reinstalled the sim and it works fine

yes… some version of MSI A… ( more exact the containing Riva ) cause also issues.

Take this with a pinch of salt and file it under ‘old wives tales’ if you will but after reading this post

and enabling this option I’ve not had a single CTD in two days of heavy sim usage.

wasm

FWIW, I had some anomalies and multiple CTDs after SimUpdate 5, but hotfix 1.18.14.0 cured most. As I’ve posted elsewhere, I have a very mid-range system (i5-9600, GTX 1060, 32GB RAM), and am frankly thrilled with the current performance level.

Now if someone could send me a profile for the old MS Force Feedback 2 Joystick, that would be great!

CTD when selecting FBW A320.

FlightSimulator.exe
0.0.0.0
00000000
FlightSimulator.exe
0.0.0.0
00000000
c0000005
00000000009dd838
f30
01d78abc9a47fae0
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
6e0a8ede-de46-4aa6-a08f-c2298989c5e0
Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
App

Hasn’t worked for me unfortunately

Toepassing: FlightSimulator.exe
Framework-versie: v4.0.30319
Beschrijving: het proces is beëindigd als gevolg van een onverwerkte uitzondering.
Uitzonderingsinformatie: uitzonderingscode c0000005, uitzonderingsadres 00007FF6B7B330B6

Naam van toepassing met fout: FlightSimulator.exe, versie: 1.18.14.0, tijdstempel: 0x00000000
Naam van module met fout: FlightSimulator.exe, versie: 1.18.14.0, tijdstempel: 0x00000000
Uitzonderingscode: 0xc0000005
Foutmarge: 0x00000000014b30b6
Id van proces met fout: 0x1314
Starttijd van toepassing met fout: 0x01d78ac5b3d6971d
Pad naar toepassing met fout: H:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pad naar module met fout: H:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Rapport-id: f9f4db11-cee3-4f51-9b3c-7e1941c91003
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:

Foutbucket 1942666105418415411, type 4
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: FlightSimulator.exe
P2: 1.18.14.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.18.14.0
P6: 00000000
P7: c0000005
P8: 00000000014b30b6
P9:
P10:

Toegevoegde bestanden:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA783.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAB2E.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAB4E.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAB5C.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAB8C.tmp.txt

Deze bestanden zijn mogelijk hier beschikbaar:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FlightSimulator._9791c5a82beb06ce0b7e985a49eb176140b8e7_1c286526_e44b7548-2954-4f0a-a8d7-d5de17a5249c

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: f9f4db11-cee3-4f51-9b3c-7e1941c91003
Rapportstatus: 268435456
Opgedeelde bucket: 2b6fdf5bcfca5def3af5bc87baa7fd33
GUID van CAB-bestand: 0

Funny thing… I just logged in and went to full screen (I had already tried this) and it loaded two flights. Great news-first access in a flight in two days!

To test it, I shut the FS2020, restarted, and now it crashes again.

Partial win!