Same here, CTD on almost every flight feels like back in fsx again
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001d8ecde
ID des fehlerhaften Prozesses: 0x43d0
Startzeit der fehlerhaften Anwendung: 0x01d78e8da54082dd
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: e2a906fa-5e6c-4e4f-9729-cb21dd873716
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
I have no overclocking going on on the Ryzen5 system and I have the same exact architecture from July 20 as I do now. The only difference is that FS was updated.
I am guessing that some drivers are not aligned properly. But I have NO clue as to which it could be… BEcause the monitors literally lose signal I assume its the GPU reacting differently than a few weeks ago when all was fine.
I updated to the latest drivers as I said and no go.
In the meantime I also reformatted the drive it was on in NTFS and put it back on and that did nothing…
I do not have any idea where to even begin looking for a failure. I have never had a single issue with FS and now after the update it simply wont even load. If I get to the map screen which happens intermittently, it doesnt take long for the computer to hang again with black screens and no signal to the monitors. EVEN if I just sit there and do nothing.
If you disabled XMP and have no other overclocks, it’s either hardware, a bad use of storage systems or Windows itself depending on what changes have been made to your system (and that includes by any anti virus). Download and run Memtest86 to see that your ram is not misfireing.
Things you might still try
set a not too large rolling cache on the same drive as your install and let windows manage virtual memory also on that drive and if that’s not enough you will still need to have at least 30GB spare capacity just to keep windows from reorganising.
For now you should if possible have Community and Official on that drive but if you have moved them you should view the UserCfg.opt file to check that they are linked.
Bios update, motherboard resources updates, Windows update including optional and if you still have problems a full from scratch Windows install so any data will need backing up to a different drive and unplugged from the system to be safe (not forgetting to ‘write down’ any encryption keys you might need later (usb stick)).
Really that about all I can suggest that hasn’t been already.
After installing the NVidia 471.68 (2070Super) drivers, I was able to make a three-hour tour in the simulator (including flights and working with the editor). Which is much longer and better than the 50 flights of 1 minute in the previous two weeks.
Of course, there is always the possibility of a coincidence or a Placebo effect, but let’s hope for the best. (Just in case, I made a few more test flights before I wrote this message).
One day later: I was happy too soon. I was just about to fly another lap from Innsbruck over Mont Blanc to Nice. Less than 30 seconds on the world map and I have a CTD. The game is still unplayable.
Cuspidflyer, welcome to the forum. I understand your frustration not being able to start your simulator, I am sure this problem will be overcome for you so just ‘hang in there’ for the moment.
The latest Win10 update addresses a performance problem with ‘Game Mode’ and fixes it as well as addressing a problem that stops some games from starting. Here is a link to my posting about this…
I suggest you read this posting which is very good, I have linked to this before, but just in case you missed it…
BilingualHarp7 who has posted below your post, is one of many who are following this CTD problem in detail, watch his and others postings.
Keep up-to-date by following the posts and do not be afraid to ask asking questions, there is some great helpers in this forum. Enjoy your time in the forum.
But you and I can be understood - so I want to hope for a miracle after absolutely terrible torment in an attempt to solve the problem with the disgusting SU5.
If it’s a pattern, point 2 should not be there, at least not described as a pattern. Each CTD is a result of something for which you have to find the source and then describe the findings.
Just had another crash. I was redoing the flight above, and just as I landed at Megeve LFHM I crashed.
Application: FlightSimulator.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF668AB6120
I don’t know if it’s airports in general or just mods but even in Superspud’s relatively small EGNS I get a sudden 5-6 frame drop which is so unlike my system, over whole towns I lose 4 or 5 but that’s in about 0.2 increments as I approach them. And I can’t say I’ve noticed it in the default airport which is just pretty basic A.I.
Don‘t know if it helps anyone, but I was interested to see what happens if I purposely break an AI generic aircraft/use one that is not SU5 compatible (my settings use generic aircraft for multiplayer). First tried to load at the relatively large Paris airport where lots of planes should spawn. I had a CTD just before the final loading screen finished. Then I tried starting from a small airport and flying into a larger one. Had the CTD on final, when the faulty plane loaded in. The event viewer shows 0xc0…05 error. In conclusion MSFS seems relatively sensitive, resulting in direct CTDs instead of just not loading the problematic aircraft or giving an indication where the problem is located. In the end the results were kind of expected, but I was curious what kind of error the event viewer would show…
Yep… same experience here. Except that the CTD can occur any time between clicking ‘Fly’ and ‘Fly now’ (i.e. during the flight loading process). The CTD is also very intermittent, occurring perhaps 20%) of the time. In addition, I have not experienced a CTD once in the cockpit and flying. The issue only arose for me too following SU5. The apparent random nature of the problem makes me wonder whether it’s server related.
0000005 means nothing, I got one by deliberately running an increased vram clock on my gpu with Afterburner. Either it got too hot for which I got no alarms or my MB wasn’t instructed to supply enough voltage … which makes most sense as I didn’t increase it (can’t increase it).
0000005 is not tied to MSFS but your hardware with power supply being the most obvious.
Make sure your power settings are set to high performance.
