Hello friends. I have CTD again and again.

This is the logfile.

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.FlightSimulator.SimConnect.SimConnect.RequestDataOnSimObjectType(Enum RequestID, Enum DefineID, UInt32 dwRadiusMeters, SIMCONNECT_SIMOBJECT_TYPE type)
   at bo.x()
   at by.h(Object A_0, EventArgs A_1)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
vPilot
    Assembly Version: 1.1.5638.40065
    Win32 Version: 1.1.5638.40065

----------------------------------------
Ninject
    Assembly Version: 3.2.0.0
    Win32 Version: 3.2.2.0

----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400)

----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.5420 built by: Win7SP1

----------------------------------------
Anonymously Hosted DynamicMethods Assembly
    Assembly Version: 0.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
4tg-qtn5
    Assembly Version: 1.1.5638.40065
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
Microsoft.DirectX.AudioVideoPlayback
    Assembly Version: 1.0.2902.0
    Win32 Version: 5.04.00.2904

----------------------------------------
Microsoft.DirectX
    Assembly Version: 1.0.2902.0
    Win32 Version: 5.04.00.2904

----------------------------------------
pgz4azya
    Assembly Version: 1.1.5638.40065
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
Microsoft.FlightSimulator.SimConnect
    Assembly Version: 10.0.61259.0
    Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

----------------------------------------
SharpDX.DirectInput
    Assembly Version: 2.6.3.0
    Win32 Version: 2.6.3

----------------------------------------
SharpDX
    Assembly Version: 2.6.3.0
    Win32 Version: 2.6.3

----------------------------------------
System.Web.Services
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
zmuwlzfu
    Assembly Version: 1.1.5638.40065
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
msvcm80
    Assembly Version: 8.0.50727.6229
    Win32 Version: 8.00.50727.6229

----------------------------------------
ulu5dts6
    Assembly Version: 1.1.5638.40065
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
Newtonsoft.Json
    Assembly Version: 6.0.0.0
    Win32 Version: 6.0.8.18111

----------------------------------------
System.Runtime.Serialization
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.4506.5463 (Win7SP1GDR.030729-5400)

----------------------------------------
System.Xml.Linq
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.5420 built by: Win7SP1

----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
xpx9zf4k
    Assembly Version: 1.1.5638.40065
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

 

 

According to the AVSIM CTD Guide -

 

HRESULT: 0xc000014B error – Mostly occurs in networked computers. This is a Microsoft.net error. The 0xc000014B is a "broken pipe" exception.  A pipe is a communication channel between two applications (such as FSX/P3D and an add-on program like ASN or OPUS, or network).  SimConnect offers add-ons the possibility to use pipes to communication with FSX.  A "broken pipe" is a situation where one of the pipes no longer exists, while the other tries to communicate using the pipe.  A typical scenario would be fsx crashing and then ASN or OPUS tried to use the pipe (communications channel) and the “pipe” was broken.  The 014B exception would then occur.  Check your network setup or an application that uses SimConnect and troubleshoot. 

 

Best regards,

What are these modules? When I see names like this, I think malware:

 

4tg-qtn5

pgz4azya

zmuwlzfu

ulu5dts6

xpx9zf4k

Files belong to vPilot v1.1.5638.40065. Not malware.

 

Best regards,

Ok. And why crashes my P3D?

Could  be worth asking on the official P3D forum?

 

http://www.prepar3d.com/forum-5/

 

Looks a bit technical!

I would be asking which addon is using a pipe and then contact that developer first.

Most likely vPilot is not communicating....  I would reinstall it.

 

Best regards,

And again CTD.

I have reinstalled v pilot. The crash is on the RWY, when i push the TOGA button on my saitek controls.

I use the pmdg777 and fs2crew.

ASN next am v pilot are also in use. Could it be that one of this programms switching from taxi to fly mode or something like this?

Perhaps the following link will help - http://forums.vatsim.net/viewtopic.php?t=64716&f=6

 

This is a Microsoft.net error message and it's telling you that something associated with simconnect is not installed properly.  Something is making a call to simconnect and that connection failed.  I think it is vPilot that is making the call.  It appears you do have Microsoft.net 2.0 and 3.5 installed and they are required for many of your older applications.  P3D is using Microsoft.net 4.0 but that should not interfere with your older applications.  Has others gotten vPilot to work successfully in P3DV2?

 

Also, make sure the products were installed properly with Admin privileges and UAC was turned off before the installation and so was any anti-virus program.  These security elements do more damage to installations.

 

Best regards,

Thanks. I have reinstalled vpilot, pmdg777 and fs2crew. I dont have a CTD anymore at the first try. But i dont have used v pilot and ASN. Next fime i fly with this addons. Hope it would be fixed.