Hello

After 220 hours of flight without CTD with a clean windows and a clean FS.

For a week I have randomly CTDs about every 3 flights without explanation.

Spoiler

Name of the failed application FlightSimulator.exe, version: 0.0.0.0, timestamp: 0x5fda32ba
Name of the faulty module: VCRUNTIME140.dll, version: 14.28.29231.0, timestamp: 0x5f4c66c9
Exception code: 0xc0000005
Error offset: 0x00000000000012de
Faulting process ID: 0xb8c
Start time of the faulty application: 0x01d6fde2c9468931
Faulting application path: C: \ Program Files \ WindowsApps \ Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe \ FlightSimulator.exe
Faulty module path: C: \ Program Files \ WindowsApps \ Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe \ VCRUNTIME140.dll
Report ID: 4b7393e4-e4c8-47bd-a29b-ef4c7dc75990
Full name of failing package: Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe
Application ID for the failed package: App

No overclock
No Anti Virus
Windows Defender disabled and firewalls also before each flight

Community file (A320FBW LFPO and IVAO)

I haven't touched anything else installed apart from SLC.

I heard that there was a problem with SimConnect / FSUIPC

So I uninstalled SLC and FSUIPC while waiting for the update

And the problem again just after the start of CRZ.

I know that I am not the only one having this problem but I would like to know why everything was good and suddenly nothing is right ....

So I uninstalled all Visual C ++

And I will test flights without Visual C ++

Can it make a difference?

So I can just stop using RTSS because it needs it but too bad ... I prefer to finish my flights.

FYI I sent a ticket to Zendesk.

I'll keep you posted if it helps other people ...

All I can say is, I use RTSS for every flight going back months (version 7.2.3), and I have never had a CTD.

I see this VCRUNTIME140.dll thing about quite a lot though, and I have never seen a definitive solution, so I hope they find it for you! 

Until last week I also had 0 CTDs with RTSS.
It's not RTSS the fault that's for sure.

But the goal is precisely to have 0 Visual C ++ install and fly to see if that avoids crashes with this DLL.

And suddenly I removed RTSS because it uses VCruntime ...

2 hours ago, Axis3600 said:

I haven't touched anything else installed apart from SLC

What is SLC?.

Cheers, Ed

A few days after the last Sim update, I also had a CTD on every flight.
I also have RTSS and FSUIPC at the start.
If I start the Sim without FSUIPC I had no CTD.
Everything the Sim needs is started as an administrator.
I did not start FSUIPC as an administrator.
I had the tip here from the forum.
So right click on FSUIPC7.exe - Properties - Activate compatibility and run the program as administrator.
Now I don't have a CTD with FSUIPC either.
Maybe that will help you.

This attitude solved the problem for me.
Windows 10 is like an open book to me and then another
the sim that is always online. Today everything is still OK and
Unfortunately, nothing works tomorrow.

3 hours ago, edpatino said:

What is SLC?

Self Loarding Cargo

Ah not stupid because me FSUIPC this launches automatically ...
I just did a test flight without any visual C ++ installed and no crash ... I will still test but FSUIPC's lead in admin can only be good.

The response I got from Zendesk this morning is to uninstall all Visual C ++ in windows programs and reinstall the new ones (2015,2017 and 2019)
X64 and X86

But I have already done this manipulation ...
I am therefore waiting for another solution ...

 

 

For the last month or so, after having a CTD once in a blue moon, the frequency of CTDs has accelerated for me, and in looking at these forums and the official one, it has for many others unfortunately. Many have simconnect issues and for me it looks like that may be the culprit along with using Little Nav Map. When I use LNM, I get random crashes. If I don’t use it, zero crashes. Hopefully this weeks update will help with this issue. 

The author of LittleNavMap released a version intended to mitigate the CTDs within the last week or two.

Some people have reported the going into "Add/Remove Programs' and looking for SimConnect client installs in the list and uninstalling them helps.  May break FSX or P3D setups if you still use those though.

Un autre CTD ce matin en croisière sans Visual C ++ installé mais j'ai toujours le même message avec la DLL VCRUNTIME140 ...

Je commence à désespérer, je n'utilise pas Little Nav Map.
Pas même FSUIPC pour le moment, je viens de faire installer le 320 et Orly pas d'autre MOD non plus ...
C'est vraiment courant maintenant tous les 3 vols environ.

Pourquoi mon jeu s'est-il soudainement planté alors qu'avant d'avoir 0 CTD, je pouvais voler 6 heures sans bug!

La seule chose que j'ai changé est mon câble pour l'écran je ne suis pas d'un câble HDMI vers DisplayPort ...

Cela ne peut pas venir du problème de toute façon je veux remplacer le câble et revenir en HDMI mais cela me surprend que le problème vienne du

Edited February 9, 20215 yr by Axis3600
RAS

Could they solve this problem? This is like groundhog day. I feel like in the days of FSX, nothing has changed.

Getting a new GPU LITERALLY solved my CTDs.

8 minutes ago, Clem116 said:

Getting a new GPU LITERALLY solved my CTDs.

Me too. My PC Company  switched my AMD to Nvidia GPU, and haven't had a crash since, and it has been weeks. Prior to that I was getting 1 a day at least.