Ok I have an update; worked for a day and then went back to having problems after an update
On Friday evening 9th. I launched the app after being way for one week, got a message to update (patch) which I did and after the update I did a short free flight KJFK NY for about 30 mins only add on was PMDG 737 with no CTD.
Did a subsequent flight later that evening with FSLTL (traffic) and Pro-ATC with a flight plan from CYYZ to KLGA 45 mins and “viola”, what do you know a smooth flight and no CTD from departure to landing with clouds and rain. Nothing was touched on my system from a week ago and no pc updates (windows).
On Sunday 11th. decided to do another flight (longer this time) to do some more testing and to my surprise got another request to update (a patch) which I did and guess what, the bloody CTD started happening again. All 3 times I tried couldn’t even get airborne which is exactly where I was one week ago. This is absurd something at MS end is causing this CTD. I am a software engineer by profession and have been racking my brains trying to determine when they say there are improving performances what are they doing; moving work away from the CPU and moving it to GPU, are they not managing resource allocation properly; I don’t know just trying to figure things out.
I did however notice that NVIDIA has a new driver update out about 5 days or so ago so I will just update it and see what happens. I always like to wait about 2 weeks before I update to a new driver just in the event there are problems. Another thing is; I have not updated my MSFS 2020 world scenery “US” from Content Manager and I am about 2 versions behind, not sure it that could be causing a problem, theoretically it shouldn’t.
Again, just wanted to provide an update on my problem. Still not solved.
Not having World Updates will not cause any issues.
That 005 exception code is extremely problematic to diagnose and cure.
The only time I had an issue was that exception and I could not fix it.
I ended up reinstalling windows, which cured it.
Having said that, there is this article on that exception code in our Tips and Troubleshooting section.
It is pretty generic, but it might be some help.
Hi,
after the small update last Friday, the MFS is working fine for me. There was no further update on Sunday for me, today I did some flights, everything worked okay (I have not changed any settings, it seems that the small update on Friday fixed the problems for me…hope so)
Thanks for your response and sharing the information. Yeah; I tried everything in the articles and still had issues. The only thing I haven’t done is reinstalling Windows which is something I am readily prepared to do at this time. If the application wasn’t loading at all or getting stuck on loading then maybe I will think about it. The problem is it works and then it doesn’t and every time it doesn’t it’s after an update.
That’s great, happy to hear that you are ok and I hope it stays that way.
Yes mine worked after the update on Friday like you. Very interesting you didn’t get an update on Sunday and I did, and it stopped working after. I am beginning to think that there might be a problem / glitch at the MS Servers, wouldn’t be the 1st time.
Will provide any updates once I get the time to trouble shoot and or find something useful that I haven’t tried as yet.
So, no good news so far. I did however see this post from SnarkyBottiburp
Not sure if anyone else tired this and if it worked for them. I will give it a try once I get a chance.
I also noticed that my in-game Library only shows that I have the MSFS 2020 Standard version installed, and I have always had the Premium -Deluxe version which it always showed. Not sure if that may have something to do with my CTD. I did open a ticket to got a clarification on that.
SOLVED - After a few hours scratching my head, trying different solutions to fix the problems that others had suggested - many of them on this forum, thank you for your help in that guys - I was contemplating deleting and reinstalling everything (Zendesk weren’t particularly helpful I have to say) but then I tried something in desperation and it worked. See below for the process I did.
I’m convinced that the mandatory update was corrupt somehow, so I looked for the files/folders that were updated by that update that was originally suggested by @ToniGsxr600 in the following folder path:
The 4 folders updated at the time of downloading the update were:
fs-base-genericairports
.fscontent
fs-base-ai-traffic
fs-base-nav
I moved these 4 folders to my desktop - DO NOT DELETE THEM! in case this solution doesn’t work for you and you can move them back again if needed!!!
I then tried to load MSFS again, and voila! - the mandatory update was again available and downloaded (much quicker than yesterday too), which placed new versions of those folders where they were. My simulator loaded without any further problem and is working perfectly again. Those files must have been corrupted somehow and that’s the reason that my simulator had multiple CTD’s when loading.
If you’re still having a problem, try this solution as it worked for me and it will hopefully work for you too.
Not Solved. Sorry that my post was misleading. I posted a post that SnarkyBottiburp ported stating what (he or she tried) to fix the problem on their side. However, I have not had a chance to try it as yet.
So, my problem is still not solved. Will reply back once I get a chance to try it.
My apologies for the confusion about it working for me but may work for others.
