Crash to desktop without error message

Having the same issue, tried all of the workarounds but nothing has worked so far. The crashes seem to be happening at random, but only mid-flight (not in the menu) and usually after 15 mins to 1 hour. Really frustrating. This needs to be made a priority.

Faulting application name: FlightSimulator.exe, version: 1.7.14.0, time stamp: 0x5f467f35
Faulting module name: d3d11.dll, version: 10.0.19041.1, time stamp: 0x84d2d982
Exception code: 0xc0000005
Fault offset: 0x000000000012ebd0
Faulting process ID: 0x13d4
Faulting application start time: 0x01d684992fd8226d
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report ID: 3f25a1dc-7038-4e0e-bb77-dbab9e48f652
Faulting package full name:
Faulting package-relative application ID:

I generally leave the XBox app running, since it uses next to no system resources sitting in the taskbar tray, so it probably was running in the case of my prior crashes.

As it happens, I got an email notification of your reply while I was flying (night flight along the French coast from Nice to Monaco and back - lovely ) so when I quit for the evening I closed the Xbox app. So far no crash after about 30 minutes. fingers crossed

It sure is - I decided to try it today after seeing a Youtube video of someone else flying around there during the day. I have discovered a love of night-time flying around urban areas in this sim - either just before dawn, or just after sunset. The lighting of the sky, distant clouds, and cityscapes is amazing.

P.S. It’s been a hour and no system crash so you might well be onto something about the Xbox app. Thanks again!

I notice my chances of CTDing while in windowed mode are about 80-90%, while if I do it fullscreen it’ll only crash 30-40%

No they dont care. They focused on fixing ATC and stupid live weather instead fixing this major issue. This error is around here since day 1 and still no fix from microsoft or Asobo.

Hi all,
I came here from the Dreadful performance - #786 by BilingualHarp7 thread. I also experience CTDs every time I play. Filed a bug report in Zendesk and attached 4 crash reports already.

After reading your replies and some replies from a FB group I thought there could be 2 factors causing this: overheating or XBox app. I tried two things recently to fight both. Usually I had XBox Game bar on with performance graph meter. I switched it off and additionally I opened my PC case to allow better heat dissipation. I could play almost 3 hoours. I could never play that long before. I decided to try what happens when I open XBox Game bar again. And it crashed after ca 30 minutes. So I switched it off. Then I tried to close my PC case again and watch the temps. The CPU and GPU got warmer indeed as expected, although not too much: CPU temp gained 5 C and GPU more less the same. It crashed also after abut 30 minutes.
My CPU temp during gampeplay is about 70 C and GPU 65 C when the case is closed. When It’s open the CPU temp goes down to 65 C and GPU to 58-60 max.

I don’t think the temps cause this, but the fact is that I could play hours when I opened my case. Previously an hour was the maximum. After the first crash previously I could play for about 30-40 minutes and it crashed again more and more often.
So the evidence isn’t clear enough to say it’s the heat that cause this, although it may increase the chance of the crash. Same for the XBOx game bar.

However I also noticed that my PSU gets really warm and keeps its fan spinning at maximum when I play. Both with opened and closed case. Perhaps it has something to do with these crashes then. Perhaps the power becomes not stable enough to keep the gameplay running. Not sure, but I ordered a new PSU with a higher wattage (curently have 500W and ordered 650W). The current PSU should provide enough power without any problem as the whole PC consumes about 370W, so there’re still spare 130W, but it makes more noise than my PC case, CPU and 3 GPU fans altogether. So I decided to replace it to a much better one and also quieter one, which is Gold rating (the current one hasn’t got any rating).

Let’s see if the better PSU changes something. I’ll share my observations with you.

PS. I’ve got no OC enabled for anything, just the factory boost CPU clock (3.8 GHz for my i5-3670K). The CPU does not engage any thermal throttling

Level Date and Time Source Event ID Task Category
Error 8/20/2020 11:37:20 AM Application Error 1000 (100) “Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f2ed221
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f2ed221
Exception code: 0xc0000005
Fault offset: 0x00000000015d3154
Faulting process id: 0xfb4
Faulting application start time: 0x01d676c0bb1f3488
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 33c9d058-5ddf-41fc-83d6-69d1ede60a2e
Faulting package full name: Microsoft.FlightSimulator_1.7.12.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App”

100% repeatable CTD. I’ve found, at least with my system, there is instability between the software and the Nvidia driver when my GPU gets to around 80c. I get a CTD with no faulting module other than the .exe, and my System crash log shows my display driver stopped responding and recovered after the CTD. I have both the Windows and Steam version and tested on both (completely uninstalled Windows version and installed Steam version) as well as tested on both older and new graphics drivers and the exact same thing happens every time. Doesn’t matter the weather, scenery, settings (low, medium, high), data settings (live or not). My case unfortunately, has poor cooling, so to mitigate the issue I’ve opened my front and both side panels and it keeps my temps from going over 75-76. I’ve yet to have a CTD since, but if I put the panels back on and get that temp up to around 80c, bam CTD. I’ve stress-tested my GPU multiple times (see results and scores below) with zero instability or performance issue with it pegged at 80c for 30min at a time. I can play other very intensive games and VR titles with no issues. This is the only piece of software causing my display driver to fail within a few minutes.

CTD (Display driver crashes at 80c GPU temp)

Furmark GPU Stresstesting (After 10min)

Furmark GPU Stresstesting (After 30min)

GPU Score - 2k

Exact Card Specs

Thank you for your report. I throttled back my GPU (gtx2080super) with MSI Afterburner so the temp is no higher as 75 C. Since then NO CTD’s anymore and a lot less fannoise from my computer. The simulator itself has the same performance.

No problem, I did submit a Zendesk ticket so I hope it and these other CTD issues get visibility.

#1 Top replies Thread. #2 Most viewed Thread. Yet no response from devs nor a fix.

To be fair they specifically state the forums are not where devs look for issues. I’m not saying they don’t take a peak, but if you are having this issue (it just started occuring for myself after the update) create a zendesk ticket so that they can see this problem is a big one.

The more people that create tickets, the more likely this will be investigated and included in one of the next updates.

The forums are for Self-Service, hence the name. Please make a ticket like I did.

Submitted the issue for like 6 times already. All we get an automated response, do this do that BS.

I did create a Zendesk ticket and posted that I did so, a few threads up. Self-Service is to help other people and get visibility onto issues, which I hope I’m doing as well.

Thank you so much for this suggestion. I just did the same in MSI afterburner. Set a 75C temp limit and custom fan curve (Radeon R9 Fury). Managed to complete a 1.5 hour flight with no CTD which is the best I’ve managed so far.

Yes, but if it’s the top issue on zendesk they’ll know about it. you mentioned no response from devs, i wouldn’t expect a response from them on here, thats all.

JJDAwg, didn’t mean to respond to you, looks like the forums responds to the wrong person sometimes.

I got the same module error, but only around Keflavik area

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Exception code: 0xc0000005
Fault offset: 0x0000000000f9de8b
Faulting process id: 0x1274
Faulting application start time: 0x01d68555744d1c4a
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 9845c998-ffac-4bb8-94d8-d24e1be14eca
Faulting package full name: Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Isn’t the Keflavik area a known spot to cause CTD?
The problem with issues like this (random CTD) is that it can be caused by such a large number of things. Not saying it doesn’t need to be addressed, but saying MS and Asobo are “Stupid” like some people are here, for fixing Live Weather, ATC, and other things that have clear and direct fixes, doesn’t mean they aren’t sorting through the myriad of things that may or may not be causing CTDs for different people.

Keflavik is certainly a known bug, and should be addressed. I don’t know if anyone can get near that place.

Some people have mentioned high GPU temps, in the past (before the patch i believe) peripherals being disconnected would cause CTDs. I guess my point is, when you guys get these crashes, follow the steps and file a ticket. The more info they have, the easier it will be to investigate. Thats why they ask if all else fails to send DXDIAG and MSINFO.

There’s clearly still issues with the software, that were not ironed out in testing phases. Whether or not they should have caught and fixed every potential issue ever prior to release is a whole other debate lol.

Same issue.

Ryzen 3700x, 32gb, 5700XT

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Exception code: 0xc0000005
Fault offset: 0x00000000003d16bc
Faulting process id: 0x2200
Faulting application start time: 0x01d685768f14e390
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: a0aae567-7177-40bd-b1d3-b73a84fd6170
Faulting package full name: Microsoft.FlightSimulator_1.7.12.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Will try the MSI afterburner trick, might work for AMD GPU’s as well.

Have the same issue
Crash to my desktop without any error codes
My pc
Gtx1080TIZotac
Core i7 4770K3.5
Cpu&gbu without any oc
Ram 16 gb 1600 mhz
Powersupply 600 w
Hdd 1TB
Running on medium settings
Only 40 m of flying after that frezzing & igot my crash message I tried everything but no luck
Really we need a sulotion as soon as possible :pensive_face: