6 minutes ago, Clem116 said:

Now THIS is helpful! Thanks 🙂

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

Than complete the other 20%. 😉 What have you left out then?

3 minutes ago, mpo910 said:

Than complete the other 20%. 😉 What have you left out then?

• 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

6 minutes ago, Clem116 said:

• 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

Start with the second and third point in that order. Right click on windows and than use windows powershell (admin).

Copy and paste 

sfc /scannow

hit Enter and wait. Does this find any integrity files? If not

than copy and paste the second command right after and just hit enter and let it run.

THIS you can do all the time if you think you have some issues within you OS! It does NOT harm at all. 

It just checks you windows installation if there are any "obvious" integrity issues AND repairs them if something is found. It is NOT a new windows installation.

Marcus

 

3 minutes ago, mpo910 said:

Start with the second and third point in that order. Right click on windows and than use windows powershell (admin).

Copy and paste 

sfc /scannow

hit Enter and wait. Does this find any integrity files? If not

than copy and paste the second command right after and just hit enter and let it run.

THIS you can do all the time if you think you have some issues within you OS! It does NOT harm at all. 

It just checks you windows installation if there are any "obvious" integrity issues AND repairs them if something is found. It is NOT a new windows installation.

Marcus

2 - Windows Resource Protection did not find any integrity violations.

3 - No component store corruption detected.

@ Clem116 ,

On your last error:
“Faulting module name: VCRUNTIME140.dll, version: 14.28.29325.2, time stamp: 0x5f6d82df
Exception code: 0xc0000005”


Were you just “sitting in the lobby”  like your previous post mentioned or was it a MSFS flight that crashed? 

2 minutes ago, Clem116 said:

 

2 - Windows Resource Protection did not find any integrity violations.

3 - No component store corruption detected.

Than I think you should at least uninstall and reinstall all hardware related drivers (joystick, etc.)

Uninstall MSFS and reinstall the MSFS app. 

Is MSFS the Steam or stand alone version?

If steam, uninstall and reinstall via steam. Also reinstalling steam could help (but I can not see how much work this will be for you)

Marcus

1 minute ago, vonmar said:

@ Clem116 ,

On your last error:
“Faulting module name: VCRUNTIME140.dll, version: 14.28.29325.2, time stamp: 0x5f6d82df
Exception code: 0xc0000005”


Were you just “sitting in the lobby”  like your previous post mentioned or was it a MSFS flight that crashed? 

I do not get you at all. What is your advice if he says "yes" and what if he says "no".

 

3 minutes ago, mpo910 said:

Than I think you should at least uninstall and reinstall all hardware related drivers (joystick, etc.)

Uninstall MSFS and reinstall the MSFS app. 

Is MSFS the Steam or stand alone version?

If steam, uninstall and reinstall via steam. Also reinstalling steam could help (but I can not see how much work this will be for you)

Marcus

I am in the process of re-installing MSFS 2020 via Steam. 

I'm confused I did a re-install of MSFS 2020 and it didn't download any content. Is that normal? I'm already in the lobby.

Edited January 2, 20215 yr by Clem116

4 minutes ago, Clem116 said:

I'm confused I did a re-install of MSFS 2020 and it didn't download any content. Is that normal? I'm already in the loby.

Yes. That should be normal. The content does not get deleted by the app uninstall process. You have to do this manually IF you want (you don´t want........I think. This would be one of your last steps you can try.).

I don´t want to give you much hope it is MSFS app related. But you have to try at least.

Most likely it is really NOT MSFS bound.

Reinstalling steam completely could also be an option!

Sometimes it helps doing things again and again BUT in some slight other way and order!

And if you are investigating more than 4 to 8 hours........

Reinstall Windows and all other things from scratch. It is much work, but it will speed up your system, nice and clean, less errors etc. BUT that is something you have to decide.

Marcus

Edited January 2, 20215 yr by mpo910

22 minutes ago, mpo910 said:

I do not get you at all. What is your advice if he says "yes" and what if he says "no".

 

That is understandable if you do not get it.

You have not read all the replies in this topic .

I was asking the OP a follow up question.

 

I had previously offered:

Set up a flight, fly it and note where you were and what you were doing when it crashes.

Screenshots or a video would be helpful.

Tell me about the flight setup and I (and possibly other pilots) will see if I can fly the same flight and see what happens.

 

I was just trying to be helpful.

Actually offering to do something. Additional testing.

 

I think you need to re-start with the whole rig. Your problems appear to be unique. Therefore, I diagnose a fundamental Hardware fault with the way you have your PC configured. Endless capering around the issue is not going to solve it - as these posts give testament to that.

Bin the whole thing. Start again from BIOS and re-build your rig with Win 10. Get that stable and go from there.

It really is sooo important that your Flight Sim Rig really does just that! If you have a load of other Games, Apps, Stuff loaded up, it's going to conflict. MSFS 2020 wants to be top of the tree in terms of System Utilisation. If it in't - it get's annoyed and sulks. This is what you are experiencing.

From reading your posts - you have a conflict - majorly in that your system is task-saturated.

Start again. Build a lean, mean, simming machine and don't fill it with a load of rubbish doing stuff in the background.

(I do this for a living - building Sims for Airlines - and if I've learned one thing over the years it's this; If it's a Sim - let it be a Sim and no other thing.)

 

Edited January 2, 20215 yr by Will Fly For Cheese

Formatting my PC, maybe it has something to do with old P3D files or something. See you in a bit!

After a FRESH OS install and VANILLA sim, I got a new different CTD 30mins into flight....

Faulting application name: FlightSimulator.exe, version: 1.12.13.0, time stamp: 0x5fda3fe4
Faulting module name: d3d11.dll, version: 10.0.19041.546, time stamp: 0xef86554b
Exception code: 0xc0000005
Fault offset: 0x000000000012e980
Faulting process id: 0x26a4
Faulting application start time: 0x01d6e1785081af91
Faulting application path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\d3d11.dll
Report Id: 24d12ef5-21b8-49d6-93a4-3614f141591c
Faulting package full name: 
Faulting package-relative application ID: 

Could be anything, but it's probably hardware related. Maybe heat, voltage related (PS), memory, or bad video card... You could also try to install the Gamepass version at least temporarily to see if that helps the issue. It could also be a bad memory dimm, and it only happens in the sim because nothing else hardly ever uses that much memory. HW settings, driver issue, bad memory, overheating, bad video card, or bad voltage from PS.

However, more than half the time, it's probably one of three things: a BIOS setting is incorrectly configured, a faulty memory Dimm, or a heat / video card fan issue. Review your temps carefully and try underclocking video card using MSI Afterburner. Underclock it about 5% and try again. Make sure you didn't change anything in your BIOS too much, try using default BIOS settings. If none of that works, try removing one of the memory DIMM's, consult your motherboard manual depending on how many DIMMS you have installed, and try to isolate the memory. If still nothing works, I'd RMA the video card and the memory at the same time, and maybe even the motherboard (if your not past RMA stage). It's easier to just RMA multiple things at once and try a fresh config.

https://forums.flightsimulator.com/t/how-i-fixed-my-exception-0xc0000005-crash-to-desktop/279205/3

 

Edited January 3, 20215 yr by Alpine Scenery