Detail steps to reproduce the issue encountered:
I deselected cores “0” and “1” and “2” and “3” (I think I have 16 cores altogether), plus I assigned a PRIORITY of “LOW” to FLIGHTSIMULATOR.EXE in the DETAILS tab of Task Manager.
Before the flight i restored the default overclocking in BIOS.
All default settings in SETTINGS, with ULTRA mode on the graphics.
Hello,
Sorry to hear about your CTDs. In the future, please follow the template given in this section. I have modified your post to fit that template. Adding all the aircraft you see this in would also help.
Hi Bob,
Thanks for the question. I just meant that if anyone were to attempt to reproduce this, the more information they have, the better. So, is it only happening with one aircraft?
Here are some other things to consider:
Does it always happen on the same route?
f you took a flight of similar duration that was not a TATL flight, would it also crash?
If you spawned at the airport, turned the aircraft on, and sat on the apron for the same duration as your flights, would you also CTD?
Yes, it has always been happening on the same flight - from EGKK to KJFK. I flew the same route for the purpose of being able to keep track of factors involved.
It’s always the same plane - the FBW A320, although the last time I flew it, it was the FBW non Christmas livery; before that I had always used the Christmas livery.
I think that it would have crashed just sitting on the tarmac, since it did crash that way a few crashes back - still at the airport, although I was taxiing at the time.
I don’t know for sure, but I think the crash phenominon would have happened on a non TATL flight (“trans Atlantic”, right?).
For this flight, I’m using the non Christmas livery with the most recent FBW DEV mod.
I am not messing with the PRIORITY or the AFFINITY in task Manager either, leaving those at default.
What I DID do , though, was to END TASK a bunch of items in the PROCESSES tab of Task Manager. I do have a complete list.
I will let you know how this flight turns out.
(On a power note, I set the monitor and hard drive to NEVER go to sleep. I tried to accomplish this in the past by letting YouTube run in the background, but I decided that that might mess with sound files conflicting, so I’m not running YouTube this time.)
Here is a list of the TASK MANAGER Tasks that I stopped before the trans Atlantic flight:
LIVEDR.EXE
MIC OFFICE CLICK TO RUN
POWERCHUTE
TABLET/TOUCH
ORIGIN WEB HELP
ALL ADOBE
ONE DRIVE
iCLOUD
GOOGLE CRASH HANDLER
ALL CREATIVE CLOUD
BONJOUR
ALL APPLE
NOTE:
I also unplugged all USB from the front of my computer (still have some in back).
DEFAULT OVERCLOCKING
FLIGHT SIM HIGH GRAPHICS SETTINGS
ALL MSFLTSIM 2020 SETTINGS DEFAULT, INCLUDING AI TRAFFIC
64 GB RAM
INTEL i9 9900 CPU @3.6 GHz
WINDOWS 10 PRO
NVIDIA GFORCE GTX 1080 TI
I had this too on my last flight from KJFK to EDDF. Around approach I started Little NavMap for taxiing which resulted in a crash. Don’t know if this was coincidental.
Seems like navigational changes and computations can cause a crash. I crashed at one point at KJFK (at the end of a trans Atlantic flight) when I changed the approach in my nav. computer…
