33 minutes ago, udidwht said:

Run the following commands…

Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return

and it will then run. Wait until each runs and finishes before you move on to the next one.

When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly

Dism.exe /online /Cleanup-Image /checkhealth

Dism.exe /online /Cleanup-Image /scanhealth

Dism.exe /online /Cleanup-Image /Restorehealth

sfc /scannow

Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTART your computer as the last step. Then go for a test flight.

Been there, done this, way back near the beginning of my troubleshooting. It did not solve my particular CTD unfortunately. 

1 hour ago, sniper31 said:

Been there, done this, way back near the beginning of my troubleshooting. It did not solve my particular CTD unfortunately. 

And this is because, based on considerable evidence, that the CTD problem has nothing to do with Windows or basic computer operations. It is a problem with MSFS2020, specifically in one or more updates, and it will not be fixed until Asobo fixes it.

OK guys I found my issue w the CTDs or system hangs w SU14. On ground  60FPs Cpu load and temps were low,  12ms cpu time and gpu 10 or less ms.  CPU temps like 55c/65c. Take off from Kdtw payware w either the fenix or pmdg (repeated w both) and about 10m into the flight the computer start to throttle and I mean biiiig time, Ive never seen this before , temps spike to 90C which is insane on the 7900x3d, but the weird thing is the thread and cpu loads were not any different then on ground.  I REALLY have no idea whats up w that but I repeated it twice and the same area over michigan the cpu went crazy hot throttled and turned off the system probably causing the hang and ctds. I went to bios and set the PBO to limit to 80c.  Tried again and had a couple spikes up to 80c but system did not stutter/hang or CTD.  There might be something wonky going on in the game threads. not sure but found my issue. I suggest you all monitor temps and make sure your cpu doesnt get some throttling. You wont know it by thread load as I said my thread load was low and still CPU got maxed out! peace

2 minutes ago, wiler said:

OK guys I found my issue w the CTDs or system hangs w SU14. On ground  60FPs Cpu load and temps were low,  12ms cpu time and gpu 10 or less ms.  CPU temps like 55c/65c. Take off from Kdtw payware w either the fenix or pmdg (repeated w both) and about 10m into the flight the computer start to throttle and I mean biiiig time, Ive never seen this before , temps spike to 90C which is insane on the 7900x3d, but the weird thing is the thread and cpu loads were not any different then on ground.  I REALLY have no idea whats up w that but I repeated it twice and the same area over michigan the cpu went crazy hot throttled and turned off the system probably causing the hang and ctds. I went to bios and set the PBO to limit to 80c.  Tried again and had a couple spikes up to 80c but system did not stutter/hang or CTD.  There might be something wonky going on in the game threads. not sure but found my issue. I suggest you all monitor temps and make sure your cpu doesnt get some throttling. You wont know it by thread load as I said my thread load was low and still CPU got maxed out! peace

Well, for me that is not my issue. One thing I do all the time is monitor my temps and they stay in the mid 60's during all phases of MSFS sim flying, and that is in the Fenix A320 even. I do have liquid cooling and lots of fans with air circulation though, so that helps. Anyhow, the CTD's I experience with the same error code always in Event Viewer are not temp related. 

Your info could help others though.

Is this issue generally solved now? I haven't had a 0005 crash in a couple of weeks now. I have changed anything on my system and even undid the network throttling workaround. Did Microsoft (quietly) fix server/data problem? I haven't been following this issue on any other forums, but it's notable that it seemed basically vanish.

1 hour ago, odourboy said:

Is this issue generally solved now? I haven't had a 0005 crash in a couple of weeks now. I have changed anything on my system and even undid the network throttling workaround. Did Microsoft (quietly) fix server/data problem? I haven't been following this issue on any other forums, but it's notable that it seemed basically vanish.

Strangely enough, ive not had one for ages too! Not sure what they did or if they did anything... but im happy as!

No CTD's anymore, just random freezing. 

I get freezing up if I plug or unplug anything on my usb. If I plug everything in before starting msfs no freezing up.

 

8 hours ago, odourboy said:

Is this issue generally solved now? I haven't had a 0005 crash in a couple of weeks now. I have changed anything on my system and even undid the network throttling workaround. Did Microsoft (quietly) fix server/data problem? I haven't been following this issue on any other forums, but it's notable that it seemed basically vanish.

Sorry to say that for some of us, the issue has not vanished -- far from it. For me, the error is not the 0005; it is always 0x887a0006. I recently bit the bullet and did a complete reinstall of MSFS2020, which did not solve the problem. Changing settings in the sim helps to lower the frequency of the CTDs, but does not eliminate them. On a good day I can fly for maybe 45 minutes or an hour, if I'm lucky -- then bam! -- a CTD with no warning.

Ar far as I'm concerned, there is no doubt that this issue was created by SU13, before which I never had any CTDs. That particular update had the effect of making the sim unstable, so that CDTs are triggered much more easily than before. For some MSFS users this is not a problem, evidently because their rigs are better able to handle the instability. For the rest of us, not so. This issue can be corrected only by Asobo, if and when they choose to do so.

get freezing up as well. Have to task manager kill process to exit and restart MSFS....

1 hour ago, cobalt said:

Sorry to say that for some of us, the issue has not vanished -- far from it. For me, the error is not the 0005; it is always 0x887a0006

Sorry for your pain, but this thread was specially about the 00005 error and network adapter workaround. 

16 minutes ago, odourboy said:

Sorry for your pain, but this thread was specially about the 00005 error and network adapter workaround. 

The thread is titled CTDs all the time now and the ensuing discussion is not restricted to one error code. Check it out. The problem is clearly larger than which error codes are triggered -- it is that SU13 rendered the sim unstable, as I (and many others) have noted. Which particular errors are triggered in any one system is less important than the instability that causes them. That is what really needs fixing.

Edited January 12, 20242 yr by cobalt

 

1 hour ago, cobalt said:

The thread is titled CTDs all the time now and the ensuing discussion is not restricted to one error code. Check it out. The problem is clearly larger than which error codes are triggered -- it is that SU13 rendered the sim unstable, as I (and many others) have noted. Which particular errors are triggered in any one system is less important than the instability that causes them. That is what really needs fixing.

I agree with you. What we had in the past was so much better than today.