I also had the CTD without even thinking of opening the VFR-map. I deleted my manual cache insinde installation directory and deactivated rolling cache via ingame menu. I just flought several flights without CTD with live traffic and live weather.
2 Likes
having ctd even in the game menu…how?Tell me how can a ctd occur in the main menu with this error:
Nome dell’applicazione che ha generato l’errore: FlightSimulator.exe, versione: 1.9.3.0, timestamp: 0x5f6cd7d4
Nome del modulo che ha generato l’errore: FlightSimulator.exe, versione: 1.9.3.0, timestamp: 0x5f6cd7d4
Codice eccezione: 0xc0000005
Offset errore 0x000000000142e642
ID processo che ha generato l’errore: 0x3050
Ora di avvio dell’applicazione che ha generato l’errore: 0x01d69a696d643cea
Percorso dell’applicazione che ha generato l’errore: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Percorso del modulo che ha generato l’errore: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
ID segnalazione: 4a236f24-6125-4b90-b8e6-0eb3359a4e9c
Nome completo pacchetto che ha generato l’errore:
ID applicazione relativo al pacchetto che ha generato l’errore:
As the GPU tends to run flat out in the menus, maybe reverse out any overclocks you might have applied and try again.
Community staff will most likely be handling the bug reports. They will provide basic steps that will fix most issues as is all they can do not being developers. They cannot say when something will be fixed, it is the nature of software dev.
They will also accumulate data to try to find the most pressing issues, it seems this will be one of them with the replies. I can guarantee some users here are experiencing hardware failure signs. I can also guarantee there are software bugs that can be caught and fixed (nullptr for example).
In the end, most of the crashes will not be related, and will need to be investigated. It will take time for sure. I refunded the €119.99 package due to crash to desktop myself and will wait maybe 6 months to see if it is any better. I hope it is, it was fun while it didn’t crash.
EDIT: Workaround that has worked for me was turning off all AI and other player planes as well as AI vehicles. Have not had a CTD flying multiple hour trips since switching these off. Not ideal, but fine until patched.
Original Post:
Having the same issue as most above. Have tried the same flight 6 times between the last two days (KHVN to KIAD). I doubt it matters, but I’m using the G58. On first couple flights, I experience the AP/MFD shutting off multiple times per flight, requiring restarting the avionics. I fixed this by changing both AI and Multiplayer planes to generic, and did not see this issue past flight #2.
However, on all these those flights, my game crashed after the camera began drifting around the same spot, just after I get into Washington airspace between KEWR and KPHL. The camera moving around just prior to crash, what I would describe as a slow drift, happens both in cockpit or external viewpoints. I’ve tried these at different altitudes, which resulted in different flight times, so the CTD has happened between 30-60 minutes in. I have not gotten a CTD just after takeoff. Flying IFR, I do not have the VFR map open. On the last flight, I set my graphics to medium (run fullscreen 1080p), and still had a crash.
Prior to this, I had only experienced CTDs when I had my computer case monitor overlay open, but I have not seen one in about 3-4 weeks. Prior to this weekend, I have done multiple multi-hour flights with no CTD, including into busy airspace (mostly in DC area)
Willing to provide any further details to help advance trouble shooting on this issue.
Relevant Computer Specs (most parts less than a month old):
I7-10700k
32GB RAM
Separate SSD specifically for page file
1060 gtx (awaiting 3080 availability)
1 Like
How many of you have the Windows Store version? If so- the file protection and directory structure are absolutely awful. I got the Steam version installed and finished my first flight in weeks.
I’ll ask for a refund on the Microsoft Store version, but I’d stray away from it if you’re getting access violations in the error messages. Didn’t have anything to do with Azure, OC settings, affinity, etc. I just switched to the Steam version.
2 Likes
Before the patch… no CTD at all. After the Japan “Patch” I’ve had a CTD every flight along with the annoying camera issue. With no indication why. Then my last flight I got this. Any ideas?
if you hadn’t ctd before, and use msfs intensive, so this is obviously problem of msfs, i guess new software/hardware conflict, where thay fix something and broke something another, all be ok, nobody want the problem stay, not the end user, not the developer
probably we have something like system overload, when one process can eat some source from other, and both are critical important, this is conflict i think, net with rendering, rendering with memory/videomemory transfer, idk, but some modules need more room, and my another guess it’s can be not only about hardware or software problem, it’s can be something in the windows settings, libraries, delay of tdr or something similar, bad version of .net library or other runtime, this simulator very complicated, and with this complex stuff we have not very best windows situation, i think asobo/msfs make one big mistake - they workaround with updated windows, but if they will works with different windows versions from 1809 or even from 1803(not very good idea, but) they can found more flexible subsystem, that will stone’s stable, instead of this i gues they debug it at only two windows updated versions, with standard settings, but people use very different os, then we have this mess, i hope they will think about make it more simple, it will more complex for them to create more simple library msfs directory, but it will give us all base kernel, what will work ander water and in the fire, and after all we’ll got minimum problems with all windows updates and new addons, it’s will good for 3rd party guys, who will work with more universal sdk, and all will happy, like you are, who finish read this abracadabra, and no need to read more lol
This is still not acknowledged under known issues, what a disaster.
2hr flight scrapped today on approach with another CTD.
Getting beyond annoying now.
2 Likes
Agree, windows store path is just awful. With the admin privileges, I still dont have any control, cant even view files and everything is so opaque. I concur, and can guesstimate most issues arise out of access violation, likely because of this unnecessarily complicated structure-permission combination.
Let us know if they refund store purchase, will also switch to steam.
2 Likes
I’m about to lose patience with all these random crashes. It happens randomly (taxi, takeoff, cruise, descent… and sometimes I can do a 4 hour flight with no CTD). It’s unpredictable.
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, timestamp: 0x5f6cce4b
Faulty module name: FlightSimulator.exe, version: 0.0.0.0, timestamp: 0x5f6cce4b
Exception code: 0xc0000005
Fault deviation: 0x00000000014267e2
Failed process ID: 0x1454
Failed application start time: 0x01d69b16b4f37f9d
Faulting application path: C: \ Program Files \ WindowsApps \ Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe \ FlightSimulator.exe
Faulty module path: C: \ Program Files \ WindowsApps \ Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe \ FlightSimulator.exe
Report ID: 09b5a521-f061-48de-a3d1-49be8c6f9a43
Failed full package name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe
Failed package application ID: App
1 Like
Well, it definitely seems to be live traffic related. Turning off live traffic turns off the CTD “feature” in my case!
Give it a go…
P.S. This is a shame, because part of the pull of the Live Event is having other live players flying with you!
1 Like
Also count me in with this CTD… really frustrating.
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x5f6cce4b
Name des fehlerhaften Moduls: RenoirCore.WindowsDesktop.dll, Version: 0.0.0.0, Zeitstempel: 0x5f6b4c44
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000005189f
ID des fehlerhaften Prozesses: 0x4d3c
Startzeit der fehlerhaften Anwendung: 0x01d69b1e0ebd2c33
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe\RenoirCore.WindowsDesktop.dll
Berichtskennung: c9ec3ac1-25d6-43c8-a3b0-f81d51785f6d
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
1 Like
Just had another CTD. I really wish a dev would jump in and acknowledge this widespread issue.
1 Like
Another crash… Tried to desactivate live traffic and in the first flight it crashed during taxi. Frustating
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, timestamp: 0x5f6cce4b
Faulty module name: VCRUNTIME140.dll, version: 14.28.29231.0, timestamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault deviation: 0x00000000000012de
Failed process ID: 0x508
Failed application start time: 0x01d69b41754005da
Faulting application path: C: \ Program Files \ WindowsApps \ Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe \ FlightSimulator.exe
Faulting module path: C: \ Program Files \ WindowsApps \ Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe \ VCRUNTIME140.dll
Report ID: 779655d3-bff1-4864-8d9f-f904e180b79c
Failed full package name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe
Failed package application ID: App
same type of crash i had in crysis remastered and more aggressively than in msfs, it’s not only msfs problem it’s common collective ms problem
Yep CTDs here to even just setting up a flight, loading screen or in-flight. Before the patch I had absolutely no CTDs
1 Like
Had no ctd since day one … today 3 in flights on exact the same spot. Looks like a mem leak in a scenery object or something …
4th flight deviated from the route just 10 miles … no crash and could complete the flight.
Luckely i flew with a map on my ipad that frooze on crash … so could show location in zendesk ticket ( not that those tickets help much 
)