Jump to content

Archived

This topic is now archived and is closed to further replies.

Goodfun

HRESULT: 0xC000014B

Recommended Posts

Hi Guys,

 

I've started to experience CTD only since I installed OPUS weather engine. I was trying to find a solution in forums but seems like nobody has same issue. 

Basically I get CTD always at the end of flight. Either when touchdown, taxiing or at gate when shutting down engines.

Which airport doesn't matter. The CTD is occurring at every airport I land after a normal flight.

 

Maybe someone of you has the knowledge to read and actually understand the following error. Your help is much appreciated. 

Thanks,

Tim

 

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 ..( timeRecvr, DateTime FSXStarted, DateTime FlightStarted)
   at ..()
   at ..(Object sender, EventArgs e)
   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.8000 (FX35W81RTMGDR.050727-8000)
 
----------------------------------------
UT2Services
    Assembly Version: 2.1.0.0
    Win32 Version: 2.1.0.0
 
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
 
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
 
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
 
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
 
----------------------------------------
Microsoft.FlightSimulator.SimConnect
    Assembly Version: 10.0.61259.0
    Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)
 
----------------------------------------
msvcm80
    Assembly Version: 8.0.50727.8428
    Win32 Version: 8.00.50727.8428
 
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
 
----------------------------------------
System.Transactions
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
 
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
 
----------------------------------------
System.EnterpriseServices
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
 
----------------------------------------
System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
 
----------------------------------------
System.ServiceModel
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.4506.7903 (Win9Rel.030729-7900)
 
----------------------------------------
SMDiagnostics
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.4506.7903 (Win9Rel.030729-7900)
 
----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8001 (FX35W81RTMGDR.050727-8000)
 
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.4506.7903 (Win9Rel.030729-7900)
 
----------------------------------------
System.IdentityModel
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.4506.7903 (Win9Rel.030729-7900)
 
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.7903 built by: Win9Rel
 
----------------------------------------
System.Xml.Linq
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.7903 built by: Win9Rel
 
----------------------------------------
 
************** 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.

Share this post


Link to post
Share on other sites

I would uninstall/reinstall OPUS.  After uninstalling OPUS, run fsx and see if the problem still exists.  If not then reinstall OPUS with Admin Rights.

 

The 0xc000014B is a "broken pipe" exception.  A pipe is a communication channel between two applications (in your case, FSX and OPUS).  SimConnect offers addons the possibility to use pipes to communication with FSX.  A "broken pipe" is a situation where one of the pipe no longer exists, while the other tries to communicate using the pipe.  So, if FSX did crash and OPUS tried to use the pipe, the addon would receive the 0xc000014B exception.

 

You can also try a system restore to the date prior to when the problem started occurring but think uninstalling/reinstalling Opus is the best option.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

×
×
  • Create New...