PMDG DC-6 works fine and I’m currently using the FBW A32NX.
1 Like
I would love to report my sim CTDing after 10 mins but it won’t even make it past the loading screen…which a year after release is just now bordering ridiculous.
1 Like
This is a common problem with seasons or tree mods in your community folder, or even marketplace content. Should go check if you use some of them.
Same problem as everyone here. CTD while I haven’t had one before.
On the other hand, I may have a working track:
I noticed coherent GT errors in the debug window which did not exist before.
Which could explain the CDTs if there is a problem on Coherent.
I am trying to see with some person who has the simulation that works if they have these errors
Constant CTDs. Been playing since release, never had a single CTD before the update yesterday. Just after SU5, crashed almost every time on load screen. This morning managed to get to the menu and completed a 2h flight, then crashed when exiting runway. Since this afternoon, constant crashes in flight.
No identifiable pattern. Empty community folder. All marketplace 3rd party purchases uninstalled. AI Traffic disabled. All CTDs appear related to NET Framework with either 0xc0000005 exception or faulting module clr.dll.
Specs:
Windows 10 20H2 - Ryzen 5600X - Asus B550 TUF Gaming Plus - 16GB RAM - EVGA RTX 2060
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000009da4e8
Faulting process id: 0x29a0
Faulting application start time: 0x01d783c4b6987988
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 5f98901e-bfae-4d17-a86d-cf5de67e2426
Faulting package full name: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: clr.dll, version: 4.8.4390.0, time stamp: 0x609c45bd
Exception code: 0xc0000005
Fault offset: 0x0000000000669d70
Faulting process id: 0xb720
Faulting application start time: 0x01d783ea4a0fe540
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Windows\MicrosoftNET\Framework64\v4.0.30319\clr.dll
Report Id: 039dba18-1aa3-4ca9-ab89-f1bf48977907
Faulting package full name: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
1 Like
CTD since update, Windows Event Viewer shows same error every time:
Error:
Faulting application name: FlightSimulator.exe, version: 1.18.13.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.18.13.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001123df0
Faulting process id: 0x21e4
Faulting application start time: 0x01d783f9a88b847d
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: ee418bdc-ac57-4ad4-9d28-2e4352364669
Faulting package full name:
Faulting package-relative application ID:
Information 1:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.18.13.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.18.13.0
P6: 00000000
P7: c0000005
P8: 0000000001123df0
P9:
P10:
Information 1:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.18.13.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.18.13.0
P6: 00000000
P7: c0000005
P8: 0000000001123df0
P9:
P10:
Information 2:
Fault bucket 1222504558169143629, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.18.13.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.18.13.0
P6: 00000000
P7: c0000005
P8: 0000000001123df0
P9:
P10:
I had maybe 3-4 CTDs in the game since I started playing it back in August 2020 before SU5. And I already had 3 CTDs in a row since SU5, 100% of my attempts to fly so far. What the heck?
Just want to join the chorus here.
The sim is now unplayable for me - I get the CTD’s at every point from menu loading to in sim and everywhere in between - multiple locations, aircraft etc. incluing the discovery flights.
Nothing in community folder just bare bones install (other than Dev A320nx which definitely causes CTD’s but also tried several other aircraft).
Such a shame given the otherwise amazing improvments to performance - if it’s not fixed by time my PC Game Pass is due for renewal in 2 months goodbye subscription.
1 Like
After checking for updates, the 1.18.13.0 program “checks out” - just closes - I’ve tried 5 times, same result. Dead.
Well, I checked Known Issues and disabled AI traffic. No CTD anymore so far.
Joining the fray for cathartic reasons; experience had thus far been fine with 1.18.13. No problems getting going. Managed to finish two short flights with AI on, then the game window just disappeared suddenly midway in to a multi-hour cruise (at around 7k feet over rural terrain). No alert or crash messaging, no freeze, no stutter, it was just gone. Smooth sailing until then. The only in-game condition I can think of to coincide with the event is that I was very close to receiving a low fuel alert and having to switch tanks.
Found the 0xc0000005 exception in EventViewer as others have noted:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001a6fc09
Faulting process id: 0x684
Faulting application start time: 0x01d783eaaeefd4db
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: b2763305-b9ae-4f57-8bc8-08b5ba1add27
Faulting package full name: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
It looks like the Sim is crashing the video driver, at least in my case, which in turn seem to cause the FS2020 CTD. I took down the time the Sim crashed and went to Windows event viewer, System, and at that exact time I found: Event ID 4101 “Display driver nvlddmkm stopped responding and has successfully recovered.”. (one for each corresponding FS2020 CTD)
Before the first FS2020 CTD after a fresh restart, I can play any games installed on my PC with no problems, be them VR or not. If after the FS2020 crash I try to start any of the games that were previously working, they crash too and I am unable to play them until a fresh restart of Windows.
This seems to confirm that it’s FS2020 crashing the video driver and not the other way around.
My config:
Intel(R) Core™ i7-9700K CPU @ 3.60GHz 3.60 GHz, 32.0 GB RAM, EVGA RTX 2070 Super, Windows 10 Pro 20h2 build 19042.1110 installed on 2TB Intel SSD, NVidia Drivers 471.41
To be honest, I’ve been having crashes constantly since update 3. It seems to be getting worse and worse with each update. It crashes while idle, when I load onto the runway, as soon as I get to my cruising altitude. I don’t understand how Youtubers have no problems with CTD, but we do. Very weird.
I have a CTD when trying to use A32nx from flybywire and some other issues with the pmdg dc 6, really bad this update with this situation.
Were you getting CTD’s on the loading and Main Menu screens as well though ? Or only in Sim ?
I doubt disabling AI Traffic is going to affect CTD’s during loading and menu phases … and I am also getting CTD’s in the discovery flights which I don’t think have AI Traffic ?
Over 11 hours to download, started MSFS up, go to the map screen, when to Fly…CTD.
Application: FlightSimulator.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF74E1CA4E8
Event ID: 1026
Source: .NET Runtime
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000009da4e8
Faulting process id: 0x32dc
Faulting application start time: 0x01d7840e9ffbeccc
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: ce31d302-b72f-425f-aba0-f63f08dcb4fa
Faulting package full name: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event ID: 1000
Source: Application Error
I never had issues with CTDs until today after SU5.
Now I can’t get through more than about 5 minutes of a flight(really just taxiing because not enough time to get into the air). It happens every time.
updated Nvidia drivers. no luck.
it is crashing when loading Flight or after loading on cockpit
Since the update, most of my flights end with either CTD or a “not responding” game. In my first flight after disabling realtime traffic, the game went “not responding again” (where I’m sitting at now).
I’ve had the problem in both 2D and VR.
Not running any mods at the moment.
When loading actual flight, within first 3-5 minutes. The game worked fine otherwise. Seems like AI traffic was the only issue for me
First, the weird altitude modelling is utterly messed up. . .
But I thought I was in the clear after an ~1.5 hourish flight (including prep) from ■■■■ to KCOS. . .even on the DME arc approach. . .
Whelp. . .guess not. 
Edit: bummer that Rapid City’s ICAO code is frowned upon. 
Edit again: adding this. . .I guess I had 2 CTDs today.
