4 minutes ago, Alpine Scenery said:

You can respectfully disagree, and not to sound arrogant, but my experience goes back across thousands of PC's from years and years of seeing issues...
So your basing things on a few instances of problems, and I am basing it on having seen thousands of problems.

There are too many variables for me to say "ABSOLUTE" without actually examining and testing the issue.
I am just telling you which steps may help your issue.

The bus controller chips overheat on some boards, almost more than half the motherboards report the incorrect temps. Memory can run too hot.
Memory has QC variances and it's especially apparent when you are OC'n the CPU.
The threshholds are tiny tiny variances.
 

 

So WHY does this ONLY happen with MSFS 2020? I understand that MSFS 2020 pushes the heck out of components like no other but then it means that MSFS 2020 is not stable and doesn't interact properly with components. It's just like if I tell you that you have a Porsche but it has bad tires, of course the Porsche is going to crash and not handle the road well...

Edited January 6, 20215 yr by Clem116

30 minutes ago, Clem116 said:

So WHY does this ONLY happen with MSFS 2020? I understand that MSFS 2020 pushes the heck out of components like no other but then it means that MSFS 2020 is not stable and doesn't interact properly with components. It's just like if I tell you that you have a Porsche but it has bad tires, of course the Porsche is going to crash and not handle the road well...

Well, it's impossible to say without too much speculating because I don't know what the inside of your PC looks like exactly.
Do your memory DIMMS have heatsinks and is there enough air circulating in there?

Generally I'd pull out an Infrared thermometer gun and start taking memory temps and bus controller temp measurements. I'd also run a test that heats up the GPU to 82 constant and see if I can cause a general exception error while running other apps while the GPU is 80 - 82. I don't really recommend doing this stuff though as a consumer because you may damage something accidentally, though most things do throttle these days but the bus controller chip on the MB can overheat sometimes.

I was once running a huge corporate web site at a data center (we're talking really huge, like NASDAQ size), and the DC kept having outages. The techs were super smart and kept trying to diagnose and re-route around the issues using complex BGP settings, and what not. It was really frustrating and I eventually demanded they just swap their edge router and try a different one. These techs were at the top of their game and highest paid in their field, and all heavily degreed and certified. This went on for like 3 months, they kept having 5-10 minute outages. The problem wasn't the routes like they thought, it was a memory chip overheating in the million dollar edge router. It doesn't matter how smart you are, some things can only be found by POE (process of elimination).

It's impossible to really diagnose a problem without process of elimination and you only know after problem resolution, everything else is speculation. I don't necessarily go in order of MOST likely to LEAST likely, I just go in order of easiest to not-as-easy, unless it's like critical then I'll replace it all at once.

Edited January 6, 20215 yr by Alpine Scenery

Sounds like a VRAM issue!

Not all systems are the same and hitting your cards VRAM limits may cause your MSFS program to CTD while only causing mine to stuffer and lag!

 

 

Edited January 8, 20215 yr by Kilo60

If VRAM then possibly when settings are too ambitious in msfs. I have not had any CTDs anymore on my meager system (i5-2500, 8GB RAM, 1660s) since I disabled what I wrote further above. Yes, skies are sometimes lonely without at least AI or live traffic but I can live with that until MS finds a fix

On 1/1/2021 at 3:25 PM, vonmar said:

"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."

 

 

 

Nonsense.

I am currently having over 500 hours playing this game. Due to other commitments, I have not played since October. I mean, I have not touched MSFS. A couple of days ago I decided to check out what is new. Crashed to desktop from the menu on the same error message. Tried again. Same. Again. Same. About 25 times, 100% of the time. From the menu. From the world map. From the aircraft selection. Within 5 minutes.

Don't tell me that I just happen to be using MSFS at the time. 

It is annoying when people claim utter nonsense. If you cannot contribute, skip the topic. 

There might be some sort of incompatibility, sure. Since the game worked flawlessly before, it is obvious the system is up to the task. I never had any issues when it comes to performance. All settings nearly maxed out, excellent frames, it was rock stable until I last played. I have not replaced any hardware, did not mess with my configuration, have not installed any mods to the game itself, it is vanilla MSFS. Thus, I'd assume it has to do with a Windows or some sort of driver update or a conflict introduced by one of the recent game updates. Or it can be a failing piece of hardware perhaps, but since way too many people are involved, I'd rule it out. 
 

Are your runtime libraries up to date?

3 hours ago, kityatyi said:

I have not played since October. I mean, I have not touched MSFS. A couple of days ago I decided to check out what is new. Crashed to desktop from the menu

If you did not clear out your Community folder before doing a flight after the update, I would expect the sim to crash. Since October there have been at least two major sim updates and mods etc have had to be updated to be compatible.

Might try clearing your caches (rolling and manual). Some people state that it solved their CTDs. Not sure if it'll work for you, but there's no harm in trying.

What we would normally do at work if a system has continual CTD in particular software on particular hardware is drop in a new SSD and install a clean up to date Win10/Server or Ubuntu/Redhat  with minimal drivers and only the software causing issues and nothing else and go from there.

We generally only do that for servers though (which for us are about $US40K) as it is not worth the time/money on a desktop/laptop to do extensive troubleshooting,  For desktops and laptops we had one like that last week (i7 laptop) and the boss basically said drop it in the dumpster and buy them a new one it had cost us enough in lost time already.  We also avoid AMD GPUs at work because of past issues of occasional issues of  AMD drivers conflicting with some software and causing bluescreens.  The AMD drivers are not necessarily at fault but the boss prefers to avoid them  regardless as Nvidia do not have near as many driver issues.

Edited February 3, 20215 yr by Glenn Fitzpatrick