Hey guys, I get the crash right when I come in for landing, and it happens randomly.. It happened on Memphis, and Denver when Im on final…I monitor my graphics card and its been a steady 60 C so its not the temperate. I wasn’t doing this until they patch the game..Something is wrong here.,.
Oh sure, now I’ve fixed it. I did two things;
- I ran repair app. MSFS started but I got the BSOD trying to run it.
- Then I noticed everything was running slow on my PC. It turns out I skyped a friend about five days ago and apparently I didn’t completely shut it down. Once I shut it down, everything is running again. Make sure Skype is completely off! It’s a freaking resource hog.
This game has been in development for years and needed to be brought to market as soon as possible.
This is the problem.
Im still figuring it out what did they actually do in alpha and closed beta phase.
Tested MSFS and reported faults via Zendesk. Not much different to now, but with a smaller reporting base.
Then they ignored the reporting and went ahead too soon anyway?
I’m still having fun with it, so I’m not really griping (just a bit)… but this whole testing phase is mystifying if you see the number of bugs that made it in.
Exactly, we waited 10 years we couldve wait 1 year more, just to get the proper product. i used to be the MS fanboy but things and feelings has been changed since the release. Now i just dream of a single bug and CTD free flight. 0 flight so far.
I’ve just received an answer from MS on my Zendesk CTD issue. Nothing else, but a generic troubleshooting (install XBox app, try safe mode, uninstall VC++ redistributables) AND they asked me to attach MSInfo and DXdiag files which I attached in the request initially! Do they read these issues at all?!
Of course the issue was closed…
How does it look like in your case?
That’s the frustrating help desk approach we’ve all gotten used to. Usually they start off by not helping. Bit like your doctor telling you to come back in two weeks. Then only after the third message - when you’re really frustrated and it starts showing - they begin to move. Slowly.
But on the upside: I do suspect by now they’ve gotten wind of all the crashes. So I wouldn’t bother too much anymore.
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: 0x000000000191e0a5
Faulting process id: 0x22ac
Faulting application start time: 0x01d6878580778839
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: 8c4e9ab1-5d6b-4dd7-94ea-86c1b6c4c9ad
Faulting package full name: Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
it’s looks like software command !@$holles
I bought a brand new system just for FS2020, I do nothing else with that system and still, I’m having the same problems.. I do remember now why I decided to switch to Macs a long time ago..
I found a temp fix. https://forums.flightsimulator.com/t/ctds-temporary-fix-awaiting-patch/265544
I had been experiencing recurring CTDs and even BSODs in mid-flight, and after lots of troubleshooting the following combination of workarounds seems to do the trick for me:
- Increase page file size to 14 GB: this fixes CTDs when flying in large cities that require lots of RAM. Depending on how much RAM you have, you may have to set it to even larger sizes. Even with 16 GB RAM and a 14 GB page file, I run out of memory when flying over Tokyo, for example.
- Manually increase GPU fan speed and open PC casing to keep the GPU temperature below 75° (limiting FPS or reducing graphics quality may also help but in the end the temperature is probably what matters): this fixes the BSODs/CTDs
- (Switch audio output device from my HDMI monitor to my main sound card: this fixes an issue where the audio would go silent after some time mid-flight). EDIT: I think this issue was also caused by the GPU temps.
The GPU temperature issue seems particularly strange as I do not overclock and never had stability/temperature issues in any other game but it really does fix the BSODs and some of the CTDs for me.
Same here, I7 7700 with a 1080. Exactly as another member said, first it crashes after 3-4 hours, then after 5-10 minutes
Guys, I do think Zixxstar’s idea is great, before this I tried almost all ideas from this forum but never works, his idea that killing ‘explorer.exe’ process makes me the first time to play more than 2 hours without crash, and the whole day no crash.
Try it if you are still struggling on CTD.
Well I was overclocking graphics card a little with msi afterburner and turned it off and also been running flight sim in administer mode and it stop the crashes for now. I would always get a random crash right on final into certain airports. So far so good!
Thanks for solution, but it worked to me only 1 time. I changed language to Russian (I’m from Russia), exit game, delete directory, start the game… Crash on middle of blue loading bar. Tried this one more time, crash again. Restart PC- nothing works. I don’t know what to do. Maybe change language to English again?
CTD with no error message too. Sometime from the home menu, hangar, runway, mid-air tutorials… MSFS simply won’t run for more than 5 to 10 minutes.
Tried offline, online, very low settings, Ultra, tried all recommanded troobleshooting steps, no overclock, stable fibre connexion, everything up to date, clean reinstall of the game 3 times. Completely unplayable no matter what I do.
Ryzen 2700X, GTX 1080ti, 32Gb DDR4, NVMe SSD.
I launched the FS, after 30 seconds I was able to choose Airport and Aircraft, another 20 seconds later I was airborne. Take off, after 3 minutes I decided to switch the plane, another 20 seconds later I was flying another a plane. Great. A masterpiece of software.
Then i woke up, had breakfast and launched the FS. After 2 minutes I was asked to hit the anykey. 5 minutes later without any fancy happenings it CTD.
Tried id again, after 10 minutes I was on the option-screen. 8 minutes later I was on the runway. CTD.