September 29, 201510 yr I copied most of this post from the Simconnect forum I recently updated to Win 10 pro, reinstalled FSX, updates and X pack. I'm getting intermittent exception handler failures during online flights. The details of the failure calls out Simconnect.When I looked for Simconnect on the hardrive, I found threeXpack Version 10.0.61637.0Sp1 Version 10.0.61355.0FSX version 10.0.60905Is there a conflict having all three?Could this be causing the problem?here's the details for the report_________________________________________________________________________________________________************** Exception Text **************System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014Bat 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.8662 (QFE.050727-8600)----------------------------------------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.8662 (QFE.050727-8600)----------------------------------------System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8663 (QFE.050727-8600)----------------------------------------System.Core Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.8674 built by: QFE----------------------------------------Anonymously Hosted DynamicMethods Assembly Assembly Version: 0.0.0.0 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------okxqup6- Assembly Version: 1.1.5638.40065 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------Accessibility Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------System.Management Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------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----------------------------------------vclfita- Assembly Version: 1.1.5638.40065 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------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.8662 (QFE.050727-8600)----------------------------------------4tqfgxyq Assembly Version: 1.1.5638.40065 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------msvcm80 Assembly Version: 8.0.50727.9185 Win32 Version: 8.00.50727.9185----------------------------------------y2mwjk_g Assembly Version: 1.1.5638.40065 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------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.8674 (QFE.030729-8600)----------------------------------------System.Xml.Linq Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.8674 built by: QFE----------------------------------------System.Data Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8662 (QFE.050727-8600)----------------------------------------************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.For example:<configuration> <system.windows.forms jitDebugging="true" /></configuration>When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box.____________________________________________________________________________________________I use mostly VpilotI installed Squawkboxbut Squawkbox caused a initial FSX CTD then restart, then runs very slowly on ground, have not tried it in the airI did sit on the ground at KIAH the other night for awhile and didn't get the failure with either software. I do most of my flying online for the virtual airlines - WestWindsthanks for any help you can give meRon WilsonWWA185ASUS P8-Z77-V PRO MOTHERBOARDIntel core i7-3770 @ 3.40GhzWINDOWS 10 pro X6416 gb RamUsing on board intel HD 4000 graphicsON BOARD AUDIOWD 10EZEX 1TB HARDRIVE
September 29, 201510 yr You have a problem with your network and/or Simconnect. Here's the guidance as stated on page 12 of 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, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
Create an account or sign in to comment