The nightmare started with the WU3.
And since then, I have not found a solution to the CTDs that occur on each flight.
Everything starts well, then during the flight (generally after 30 minutes or so) MSFS crashes with the same 0xc0000005 code.

I have tried everything, among others:
1 / Reinstalling MSFS
2 / Emptying the Community folder except FBW A320.
3 / Set the CPU and RAM to their original values.
Needless to say, all the drivers are up to date and my PC passes OCCT and RealBench tests without any problem.
I will not be reinstalling W10 since I assembled my new PC less than 3 months ago.

There are many cases of CTDs code 0xc0000005 on the official MSFS forum, but none of the suggested solutions work for me. I love MSFS, but I come to regret uninstalling P3D, a "cheesy" but reliable simulator.

Any help would be much appreciated. Thank you!

Hi David,

I had this exact same error message due to a scenery filename clash. It was only when the third party scenery designer renamed his files to specifically relate to the airport he had designed did the error message go away.

I hope this points you in the right direction.

Cheers

Terry

 

Thanks, Terry but the CTD occurs without any 3P addon installed.

I feel your pain and am experiencing the exact same problem - generally after around 20mins of flying + around 20mins of preflight.

Just out of interest 'how' do your crashes occur ? With mine, I get a momentary loss of sound lasting around a second, then a quick return to sound, then the frozen screen and crash message.

This Avsim posting seems an interesting read, particularly the second page where this potential fix is mentioned a couple of times.

I haven't had a chance to try it yet, but it does seem to 'have legs'.

Personally, I'm of the opinion my CTDs are related to the injection of AI. I can't prove this yet, but this, coupled with the above will be my areas of focus.

Regards

Welcome to the CTD club, where you will be offered everything from empty your community folder! to "I have never had a ctd since launch"

Edited March 4, 20215 yr by Car147

Sorry to hear that David. I hope you manage to get a resolution to your CTD ASAP.

Cheers

 

Terry

41 minutes ago, David Roch said:

The nightmare started with the WU3.
And since then, I have not found a solution to the CTDs that occur on each flight.
Everything starts well, then during the flight (generally after 30 minutes or so) MSFS crashes with the same 0xc0000005 code.

I have tried everything, among others:
1 / Reinstalling MSFS
2 / Emptying the Community folder except FBW A320.
3 / Set the CPU and RAM to their original values.
Needless to say, all the drivers are up to date and my PC passes OCCT and RealBench tests without any problem.
I will not be reinstalling W10 since I assembled my new PC less than 3 months ago.

There are many cases of CTDs code 0xc0000005 on the official MSFS forum, but none of the suggested solutions work for me. I love MSFS, but I come to regret uninstalling P3D, a "cheesy" but reliable simulator.

Any help would be much appreciated. Thank you!

Try resetting Windows. 

33 minutes ago, garydpoole said:

I feel your pain and am experiencing the exact same problem - generally after around 20mins of flying + around 20mins of preflight.

Since the last update MSFS reboots my PC. Just like that. It doesn't even CTD, it simply goes black and restarts the PC in a split second. Checked temps and volts and what not but everything looks good, even up to the moment the PC reboots (I was making a video of my hardware monitor app to see if something quickly changed in the very last moment but nothing).

Now the 'funny' things is that I also seem to be getting these reboots after around 20 minutes of flying. However, once I did get a reboot, the next flight reboots almost instantly. As it is now I might consider myself lucky if I get to fly around 15 minutes a day... Anyway, the fact that the next reboot comes as soon as I start a flight makes it look like it is heat related on my PC but my temps are good, no problems there... I stilk think that the last update did something funny.

And btw I did reinstall W10 from scratch and MSFS too... I even PSID reverted my SSD's... nothing helps.

Windows 10 updates are enabled and you're up to date?

My technique for these CTDs with common fault codes is to search youtube for videos with a lot of "likes" and very few dislikes.

Example 

 

Make sure you haven't got CTD Enabled in Settings.

Logically this cannot come from MSFS, otherwise all users without exception would have this error code 0xc0000005.
Other than that it’s not a minority. So it’s something else you have to look for somewhere else.

Counting the seconds until someone tells you  your system is NG, because only those people get CTDs'''     🤣

Whenever I have had the occasional CTD in MSFS, it has always been that same 0xc0000005 code in event viewer.

It's hard to trace (as we know).  Sometimes I can go days without one, then get a chain of them. 
I have tried testing if it is where I am flying and if it could be the odd add-on in my community folder, but it is so time consuming and hard to replicate.

I know some of the third party scenery had the BGL name clash issue, but the developers are aware of that now, and I currently have no scenery with that issue.
MSFS just seems so fragile the way it falls over like this without much useful error reporting.  Once again, it is something they are working on apparently.
 

Edited March 4, 20215 yr by bobcat999

10 minutes ago, bobcat999 said:

Whenever I have had the occasional CTD in MSFS, it has always been that same 0xc0000005 code in event viewer.

It's hard to trace (as we know).  Sometimes I can go days without one, then get a chain of them. 
I have tried testing if it is where I am flying and if it could be the odd add-on in my community folder, but it is so time consuming and hard to replicate.

I know some of the third party scenery had the BGL name clash issue, but the developers are aware of that now, and I currently have no scenery with that issue.
MSFS just seems so fragile the way it falls over like this without much useful error reporting.  Once again, it is something they are working on apparently.
 

I posted a couple of times about my intermittent CTDs, and there are always a few people telling me my system must have an issue. A coworker and I were discussing  this yesterday, and he happens to be a software programmer at the company where I work part time. He got a $4,000 gaming rig that he assembled about 2 months ago. He is a avid gamer and plays these games that are supposed to be really taxing on one's system, and he gets these ridiculous FPS of 150-200 etc with nary a glitch. He installed MSFS 2020 just to see how it would run on his system.  The first half dozen times he ran it, he got 2 CTD's. I told him about the " It must be your system" comments I see, and he said " That's BS". 

I'm having CTDs now too, whereas prior to this I've only had one since release. It's the same scenario described above - a bit of stuttering, a brief freeze with no sound, then sound returns for a moment, and finally a CTD with no explanation. My community folder is empty and today it happened while flying the steam 172. No AI, no photo gram, etc. Its pretty frustrating and made worse by there being no fault to chase down.