FSX Crashing after connecting to vPIlot

Support Pilot Software
1

After I installed the Airbus X A320/A321 I keep getting this error ************** 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.ReceiveDispatch(SignalProcDelegate pfcnSignal)
at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage()
at FSXWX.Form1.DefWndProc(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.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.9168 (WinRelRS6.050727-9100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

FSXWX
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Nelson/Downloads/fsxwx/FSXWX.exe

System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

Microsoft.FlightSimulator.SimConnect
Assembly Version: 10.0.61259.0
Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)
CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll

msvcm80
Assembly Version: 8.0.50727.9680
Win32 Version: 8.00.50727.9680
CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9680_none_d090cb7c44278b28/msvcm80.dll

System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.9151 built by: WinRelRS6
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

My idea is something to do with the model matching or sim connect? Either way its getting on my last nerve and has stopped me from doing flights I could easily do.

2

Can you post the data from the Windows Event Viewer. The 0xC000014B is a .NET error. Most common causes that I’ve seen for that are the uiautomationcore issue, a bad terrain file, a corrupt AI file, or something wrong with a flyable add-on aircraft. You’d have to get the faulting module name from the Event Viewer entry for that error/crash to troubleshoot more.

Several posts on the topic over the years (Programmable Search Engine). It’s a very elusive error to find/fix. Best recollection I’ve had (from years ago, almost no one uses FSX anymore) is that it’s a broken communication pipe, usually due to something (like addon aircraft or AI) making a Simconnect call that’s not possible/successful. You’ll likely find that the faulting module is FSX. After FSX crashes, vPilot reports the error (in other words, vPilot is REPORTING that there’s an error, it’s NOT CAUSING the error).

If you FULLY uninstall the Airbus X A320/A321, does the error persist?