NOTAM; 

For those pilots running OverClocked systems it is suggested to review whether this is advantageous to Frame Rates/ Simulation Smoothness/ etc.

For reference I started with a relatively old chip - Devil's Canyon 4790K - O/C'd to 4.6 and had problems with glitches/ stutters and freezes. (Graphics; 1080Ti, 16 Gig DDR3 RAM, SSD x3 )

On letting the ASUS simply TURBO the chip on requirement - Flights/ Frames and Scenery Loading have become far more stable and smooth. Zero CTD.

Pilots are advised to allow their Simulators to be at default - the old mentality of having to O/C and burn everything to single-core parity with smoke filling the gaming room (FSX/ P3D/ X-Plane) is over.

Enjoy the new.

NOTAM Ends.

Edited January 1, 20215 yr by Will Fly For Cheese

Count me into the group experiencing constant CTDs AFTER the latest December 22nd update. No over clocking no system changes. Rock solid stable before the update now it crashes all the time. Default or addon aircraft. 
 

My system is stable in any other games or situations. It’s clear something is wrong with this build of MSFS whether it affects everyone or not something was changed within MSFS to cause this and it needs to be fixed. 
 

edit: I disabled rolling cache and haven’t had one in about 4 hours. 

Edited January 1, 20215 yr by Azapata87

Clem, you are saying you are still having crashes, but I haven't read anywhere (and please excuse me if I'm incorrect) where you have said you tried anything suggested.  I made the suggestion of a fix from Microsoft that took care of that dll, then noticed someone else had said essentially the exact same thing fixed it for them.

What have you tried in your efforts to solve the issue?

14 minutes ago, andyjohnston.net said:

Clem, you are saying you are still having crashes, but I haven't read anywhere (and please excuse me if I'm incorrect) where you have said you tried anything suggested.  I made the suggestion of a fix from Microsoft that took care of that dll, then noticed someone else had said essentially the exact same thing fixed it for them.

What have you tried in your efforts to solve the issue?

Yes, I have tried everything, including the DLL and Visual Libraries. I did mess with my CPU OC setting a while back and I have reverted back to default to see if this helps. 

And nope just had another one....

Faulting application name: FlightSimulator.exe, version: 1.12.13.0, time stamp: 0x5fda3fe4
Faulting module name: VCRUNTIME140.dll, version: 14.28.29325.2, time stamp: 0x5f6d82df
Exception code: 0xc0000005
Fault offset: 0x00000000000012de
Faulting process id: 0x4988
Faulting application start time: 0x01d6e0831b23cdc4
Faulting application path: D:\Program Files\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 69c2f732-8820-4649-924f-3d308875ef7f
Faulting package full name: 
Faulting package-relative application ID: 

On 12/31/2020 at 10:41 AM, sd_flyer said:

Also note I did had CTD often in alpha. So opted to replace my GTX1080 to RTX2080 Super. It helped with CTD back then

if we need better graphics cards then Asobo/Microsoft needs to put that in the recommended requirements.  My gtx1070ti is above the recommended as well.

LOTS of people having the same issue as well.

https://forums.flightsimulator.com/t/constant-ctd-after-update-1-12-13-0/340419/133

16 hours ago, Clem116 said:

And nope just had another one....

Faulting application name: FlightSimulator.exe, version: 1.12.13.0, time stamp: 0x5fda3fe4
Faulting module name: VCRUNTIME140.dll, version: 14.28.29325.2, time stamp: 0x5f6d82df
Exception code: 0xc0000005
Fault offset: 0x00000000000012de
Faulting process id: 0x4988
Faulting application start time: 0x01d6e0831b23cdc4
Faulting application path: D:\Program Files\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 69c2f732-8820-4649-924f-3d308875ef7f
Faulting package full name: 
Faulting package-relative application ID: 

Were you sitting in the lobby like your previous post? :

"Just got one from just sitting in the lobby for 20mins.... "

So, you do not have to be on a flight (in the Lobby?)

The reason is:

Exception code: 0xc0000005

Faulting application name: VCRUNTIME140.dll

Some running program / App on your PC caused it.

You just happen to be using MSFS at the time.

See:

c0000005 in event viewer:
Originally posted by  EllipticCurve here:
https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=136869&start=30

"Learn this code...MEMORY ACCESS VIOLATION.
A program is doing something bad with memory it does not own."

5 minutes ago, vonmar said:

Were you sitting in the lobby like your previous post? :

"Just got one from just sitting in the lobby for 20mins.... "

So, you do not have to be on a flight (in the Lobby?)

The reason is:

Exception code: 0xc0000005

Faulting application name: VCRUNTIME140.dll

Some running program / App on your PC caused it.

You just happen to be using MSFS at the time.

See:

c0000005 in event viewer:
Originally posted by  EllipticCurve here:
https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=136869&start=30

"Learn this code...MEMORY ACCESS VIOLATION.
A program is doing something bad with memory it does not own."

This is only true for maybe 5% of all causes which can lead to this error code. It can also be:

Hardware related

Windows related

.dll related

App Start related

Registry related

....

You knowledge seem to be very high level and it is not helpful for any user at all.

Are you the same guy who posts this all the time over at LM support forum (yep, another platform but I am just curious)?

Marcus

22 minutes ago, mpo910 said:

This is only true for maybe 5% of all causes which can lead to this error code. It can also be:

Hardware related

Windows related

.dll related

App Start related

Registry related

....

You knowledge seem to be very high level and it is not helpful for any user at all.

Are you the same guy who posts this all the time over at LM support forum (yep, another platform but I am just curious)?

Marcus

Here the support is for the Op's problem and many are trying to help.

Are you?

Your additional information was already mentioned in a previous post.

Have you read all the posts in this topic?

You need not judge who is helpful and who is not.

Note:

In my post I had a follow up question for the OP.

Edited January 2, 20215 yr by vonmar

21 minutes ago, mpo910 said:

This is only true for maybe 5% of all causes which can lead to this error code. It can also be:

Hardware related

Windows related

.dll related

App Start related

Registry related

....

You knowledge seem to be very high level and it is not helpful for any user at all.

Are you the same guy who posts this all the time over at LM support forum (yep, another platform but I am just curious)?

Marcus

Thank you so much for the info, but how do I know which program is causing this then? And why does this ONLY happen with MSFS 2020?

Edited January 2, 20215 yr by Clem116

1 minute ago, vonmar said:

Here the support is for the Op's problem and many are trying to help.

Are you?

I was talking about you. Don´t switch the conversation.  I am sorry to say this, but it is really very shortcoming to point a user in a memory access violation direction where most of the time this is not the cause. Your behavior on LM did also irritated lots of other users and that´s why I posted and reacted with this to point the user in other directions where he should look at.

He should try:

• Checking device manager if any hardware issues occur (yellow triangles?)
• Reinstall all VC redists he can get from microsoft site
• reinstall the MSFS app, if he does not have it done already (only the app, not the whole MSFS directory)
• run sfc /scannow at powershell admin
• run dism /online /cleanup-image /scanhealth at powershell admin
• reinstall nvidia driver
• disable all msfs mods
• reinstall ALL hardware components (joysticks etc.)
• Disable, delete and if necessary reset!! all OC profiles for GPU cards

 

This is the way to approach. 

Marcus

 

5 minutes ago, Clem116 said:

Thank you so much for the info, but how do I know which program is causing this then? And why does this ONLY happen with MSFS 2020?

I would start here if I where you:

https://support.microsoft.com/de-de/help/2977003/the-latest-supported-visual-c-downloads

Install them all beginning from the oldest to the newest ones (2008, 2010, etc.).

AND

Install always the x86 and x64 variants. It does not matter if your windows is x86 or x64.

You can also reinstall your Mainboard Chipset driver (download this from your mainboard supplier site). This is important because if this driver has issues than a lot can go wrong!

Delete any GPU overclock tool like MSI Afterburner, RIVA Tuner, etc. They can cause trouble too.

After this reinstall NVIDIA driver. Delete the prior driver one with DDU tool, restart and install the newest!! one (google ddu driver uninstall)

If you use some ssd with seperate drivers, reinstall the drivers too. This is simple and does not lead to any data lost.

After you done this, reinstall the MSFS APP. DON`T delete your whole MSFS directory. JUST the APP.

Start MSFS and don´t use any MODS. If you want to use the famous flybywire one, take the stable version. I runs ok on my end.

Report back if you need further help.

Marcus

 

3 minutes ago, mpo910 said:

I would start here if I where you:

https://support.microsoft.com/de-de/help/2977003/the-latest-supported-visual-c-downloads

Install them all beginning from the oldest to the newest ones (2008, 2010, etc.).

AND

Install always the x86 and x64 variants. It does not matter if your windows is x86 or x64.

You can also reinstall your Mainboard Chipset driver (download this from your mainboard supplier site). This is important because if this driver has issues than a lot can go wrong!

Delete any GPU overclock tool like MSI Afterburner, RIVA Tuner, etc. They can cause trouble too.

After this reinstall NVIDIA driver. Delete the prior driver one with DDU tool, restart and install the newest!! one (google ddu driver uninstall)

If you use some ssd with seperate drivers, reinstall the drivers too. This is simple and does not lead to any data lost.

After you done this, reinstall the MSFS APP. DON`T delete your whole MSFS directory. JUST the APP.

Start MSFS and don´t use any MODS. If you want to use the famous flybywire one, take the stable version. I runs ok on my end.

Report back if you need further help.

Marcus

 

Now THIS is helpful! Thanks 🙂

I have done 80% of the above and still no luck 😞

Like I mentioned:

The additional information was already part of previous post by sd_Flyer which contained your current information.:

“Here is some interesting read regarding this error https://www.stellarinfo.com/blog/how-to-fix-error-code-0xc0000005-in-windows/

There is also similar error described on Nvidia forum. It could be related to system or hardware not necessarily to MSFS”