you know,.. I’am allways here 
And let us know if you found the issue. Your case was/is interessting and seems very special 
May be.. I assume there exist a way of esacaltion over the support page.
I reported this twice with Zendesk already (latest ticket 116960) send them all info i could think of, and they recently asked for some additional info which i gladly provided. A friend of mine had a problem a little week earlier than i, my ticket number was about 3000 higher. I ask myself if they can handle all of that. But rest assured i will report back happily if some day MSFS works again.
At the same time i can’t and won’t hide my disappointment be it here or elsewhere.
I had been having constant CTD I couldn’t be in the sim for more than 15 mins without a crash. I tried loads of different things but reducing my core clock and memory clock slightly with MSI afterburner seems to have improved things for me. Was just able to complete a short flight from Stansted to Liverpool in the FBW A320. Reducing those settings didn’t seem to have any affect on the Sim performance. Hope this helps anyone else having issues. My MSI Afterburner settings can be seen below.
PC Specs:
Windows 10
|Processor|AMD Ryzen 5 3600 6-Core Processor 3.59 GHz|
|Installed RAM|32.0 GB|
GPU: RTX 2060
|System type|64-bit operating system, x64-based processor|
I’m still trying to just get in the air but having zero success. Nothing I do changes the CTD issue im having.
Error. 0xc0000005
Recently lowered my gpu clock and it did absolutely nothing. I don’t think it’s stressing my gpu one bit. I can see the usage while the CTD happens and it’s not straining. Every single step in the pinned post about how to fix CTD issues does nothing. Over a month of no flying this really blows
In the GPS ,Piper Arrow, EGNH to EGOS , live weather tried to Invert the Flight Plan which used to work OK but now CTD today
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: 0x00000000018a3bad
Faulting process ID: 0x268c
Faulting application start time: 0x01d7929ae8070514
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 7a3d4e4a-18a9-4a09-96a4-8e6869a3464e
Faulting package full name: Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Do you realize you are posting in over a year old thread? This problem existed long before SU5.
1 Like
It may be a year old but people still need help and they need to fix these issues
1 Like
Did i said otherwise?
Zendesk is just brilliant.
Hi Alex,
Thank you for sending in that file. I can see MSFS2020 is crashing due to a general fault:
Faulting module name: FlightSimulator.exe
And task status:
Status
Solved
Wow!!!))))
2 Likes
Have you found a fix for msfs causing this error? I get this error (gfx driver crashing) and MSFS going “not responding” every time selecting an airport.
Hello unfortunately have not yet found a solution to the problem I’m still waiting for a patch that solves it
1 Like
I’m still getting this error since Update 5. Never had it before. It usually happens when I move my camera, inside or outside of cockpit.
Faulting application name: FlightSimulator.exe, versão: 0.0.0.0, carimbo de data/hora: 0x00000000
Faulting module name: FlightSimulator.exe, versão: 0.0.0.0, carimbo de data/hora: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001a12757
Faulting process id: 0x740
Faulting application start time: 0x01d79359257e51cd
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 573ff3d5-4619-4fad-a705-e179727b3cc9
Faulting package full name: Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
1 Like
I also got multiple CTD and in general the game is more laggy and I got problem with the pause menu ( the game stuck there and I cannot remove pause, and I have to close the game)…
this is the file from event reader:
Nome dell’applicazione che ha generato l’errore: FlightSimulator.exe, versione: 0.0.0.0, timestamp: 0x00000000
Nome del modulo che ha generato l’errore: FlightSimulator.exe, versione: 0.0.0.0, timestamp: 0x00000000
Codice eccezione: 0xc0000005
Offset errore 0x0000000000ce6120
ID processo che ha generato l’errore: 0x3fd8
Ora di avvio dell’applicazione che ha generato l’errore: 0x01d793747ab51b4e
Percorso dell’applicazione che ha generato l’errore: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Percorso del modulo che ha generato l’errore: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
ID segnalazione: 9cf2b76c-8c03-486f-ac6b-790aff8004c8
Nome completo pacchetto che ha generato l’errore: Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
ID applicazione relativo al pacchetto che ha generato l’errore: App
an info about the meaning of the Ticket Statuses:
https://flightsimulator.zendesk.com/hc/en-us/articles/360014232420-Zendesk-Bug-Reporting-FAQ
Ahh … well, I see …
Simple as that…
WAR IS PEACE.
FREEDOM IS SLAVERY.
IGNORANCE IS STRENGTH.
The support geniuses added to the collection:
SOLVED IS UNSOLVED.
And after all, the cause of the failures was also found there …
It turns out the crashes are happening in the file:
FlightSimulator.Exe !!!
I say - excellent, just excellent!
5 Likes
Yep, can’t ignore this anymore myself. Never, had issues with CTDs prior to SUP5. Now at least 50% of my attempted sessions end with CTD. This can happen at any phase ranging from selecting an airport on the map to set up the flight all the way to CTDs on touchdown. Seems to be no common thread. With addons / without.
Yes!
Never experienced CTD until last update? Now this is occurring periodically?
Matter of fact I’m in flight and experienced one as I write this! Never happened prior to last update!
Im also up to date.
This is on there side!
64 Gig
4.2 clocked
RTX 3090
Got CTD for second consecutive day while descending after a long flight, different aircraft on both occasions.
I should not say it’s on their side. Could be the 3090 choked on graphics and I need to update my drivers. I can only say it started after latest update? Trying to satisfy low end to high end pc’s must be a challenge!
1 Like
Just going to let this topic know how I fixed the issue. Computer is a home brew gaming machine with AMD ROG Strix MoBo and Nvidia GE Force 1660TI. Figured that would have the necessary HP to handle FS.
I wasted a lot of time trying everything in the book and then some. Every time it CTD I got an event log pointing to the Nvidia graphics driver. And I clean installed the OS and d/l FS from scratch and made sure all drivers were the latest. Still crashed, and in fact it took several days to d/l the new update because it kept crashing. But without the driver error.
So finally I got tired and figured to get a bit more drastic, and replaced the 1660 with an AMD 580. The program invoked and just as the main menu appeared, ctd. Stubborn person that I am, I restarted. And I can now fly!!! It has not crashed using either the Cessna or the 787.
As always, of course, YMMV. But I’m able to fly again, and that’s all I want. It was worth the bucks.
1 Like