Just had a CTD 1 hour into a flight.

Anyone else had it?

 

Karl

I just started geting that one.  I did a repair on the Microsoft Visual C ++runtime to see if that fixes it.

Yep. Got it yesterday for the first time with HF1. Don't even remember what caused it. I've had CTDs from changing display settings and also plugging joystick in.

Edited May 4, 20206 yr by NightOfDreams

Hi

Don't know if this will help; I had VCRuntime140.dll CTDs. Mostly related to a non compatible airport or other add-on. V5 is strange, some older addons appear to work fine, others cause CTDs.

What addons are you using? With few native v5 add ons out there right now most of us are using v4 installs pointing at v5. My guess would be it's likely to be something to do with that. Even Orbx has some airports that need work in v5 apparently - although they have already been released. I had a VCruntime140.dll CTD when approaching one of their airports. Orbx were able to replicate it.

It's unlikely to be your Microsoft Visual C++ installs. (Unless it is of course:-). Be good to know how you solve it.

Ray

Was approaching Ketchikan. Have ORBX Global, ORBX NA, ORBX Pacific Fjords and ORBX PAKT. Also some freeware scenery in this region. 

Karl

I have Orbx Global and North America and got VCRuntime140.dll

I am getting this error also. Non-ORBX user. Reinstalling Visual Studio didn't fix it. Seems to always happen randomly when ATC calls me (like to change frequencies, etc). 

Anybody have a fix?  Usually I get this when requesting gsx pushback. But it doesn’t happen every flight. When it does it is always then though. 

Has anyone found a fix for this in HF2? Still getting it when opening the ATC or GSX windows.

I had this problem a lot with HF1 (and v5 without hotfix) -- crashes at least once per flight. With HF2, I did a complete uninstall and reinstall and this apparently solved the problem -- nomore vcruntime errors. A reinstall of Visual Studio did nothing on HF1 and earlier. I think it may be related to the flashing of the ATC window (and top menu). HF2 fixed that -- "Fixed issue causing Scaleform elements to flash including the menu bar and ATC window."

So, are you seeing the ATC window and top menu flashing? Did you do a complete reinstall? Have you run GSX Live Update?

P.

9 minutes ago, pgde said:

I had this problem a lot with HF1 (and v5 without hotfix) -- crashes at least once per flight. With HF2, I did a complete uninstall and reinstall and this apparently solved the problem -- nomore vcruntime errors. A reinstall of Visual Studio did nothing on HF1 and earlier. I think it may be related to the flashing of the ATC window (and top menu). HF2 fixed that -- "Fixed issue causing Scaleform elements to flash including the menu bar and ATC window."

So, are you seeing the ATC window and top menu flashing? Did you do a complete reinstall? Have you run GSX Live Update?

P.

I still sometimes get the green text bar flashing. I only reinstalled the three components, so not completely from fresh. I did reinstall 2015-2019 VC distro and have run the latest update. 

Have you done many flights since doing a full reinstall and not seeing this crash? The problem for me is it only happens every 5th flight or so, making it really hard to see if something worked.

I have done about 5 flights with no vcruntime issue. Before, it was happening at virtually every flight 😞 But what was strange is that once it crashed, and I restarted P3D it didn't happen again. I am about to do a Hawaii Islands flight and will update this once I have completed it (successfully I hope).

17 hours ago, pgde said:

I have done about 5 flights with no vcruntime issue. Before, it was happening at virtually every flight 😞 But what was strange is that once it crashed, and I restarted P3D it didn't happen again. I am about to do a Hawaii Islands flight and will update this once I have completed it (successfully I hope).

Update -- the Hawaiian flight completed without a problem. 

I just had a similar crash for the first time with HF2:

Faulting application name: Prepar3D.exe, version: 5.0.31.35253, time stamp: 0x5eebf566
Faulting module name: VCRUNTIME140.dll, version: 14.26.28720.3, time stamp: 0x5e74aeb1
Exception code: 0xc0000005
Fault offset: 0x00000000000012de
Faulting process id: 0x40cc
Faulting application start time: 0x01d64f3abf50ae98
Faulting application path: D:\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 2da27e3d-f8d9-43a5-8787-7ee40b6b1354
Faulting package full name:
Faulting package-relative application ID:

 

3 seconds prior, this .NET runtime error was reported in Event Viewer:

Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFAF46712DE

 

I ran the system file checker, and it didn't find any issues.  I have Orbx NA and OpenLC, ActiveSky, ChasePlane and was flying the Aerosoft A320 and approaching FSDT KCLT (about an hour into the flight) when it happened. Same deal - ATC called me and "bam." I had completed several flights with the Airbus without an issue, so I don't know if it is related to the scenery.  But as mentioned, it is really frustrating to try to pinpoint issues because these errors don't always have a pattern that can be traced to a specific addon - unless it is repeatable, it is hard to know if you are fixing it by removing the addon.

Did you update only the client? I did a fresh install using the setup program and haven't yet (knock on wood) had a vcruntime error.