Jump to content
Sign in to follow this  
Empathica

FSX Crashing Constantly (.NET Framework HRESULT 0xC000014B

Recommended Posts

FSX has been working fine for ages on my computer but the last couple of days it's been 'fatal error'ing

It started out by happening once or twice, but now I can't even load a flight.

 

The same process is happening over and over.

I open the application, am able to choose my settings (date, aircraft etc) and I get into the game.

 

It loads up and I can see my aircraft for about 20 seconds. The traffic is about to activate from UT2 and that's when it crashes.

It causes a fatal error and restarts, and the process starts again.

 

The message I get upon restart says "Microsoft .NET Framework. Unhandled exception has occurred in your application. Exception HRESULT 0xC000014B"

 

The only difference from the last few days is I have been re-assigning livery paints in UT2, but not done anything else.

 

Any help appreciated.

Share this post


Link to post
Share on other sites

What happens if you turn off UT2?

 

regards,

Joe


The best gift you can give your children is your time.

sigbar.gif

Share this post


Link to post
Share on other sites

He's been getting Sim1.dll errors, possibly caused by a bad texture to one of the UT2 aircraft.


Charlie Aron

Awaiting the new Microsoft Flight Sim and the purchase of a new system.  Running a Chromebook for now! :cool:

                                     

 

Share this post


Link to post
Share on other sites

FSX has been working fine for ages on my computer but the last couple of days it's been 'fatal error'ing

It started out by happening once or twice, but now I can't even load a flight.

 

The same process is happening over and over.

I open the application, am able to choose my settings (date, aircraft etc) and I get into the game.

 

It loads up and I can see my aircraft for about 20 seconds. The traffic is about to activate from UT2 and that's when it crashes.

It causes a fatal error and restarts, and the process starts again.

 

The message I get upon restart says "Microsoft .NET Framework. Unhandled exception has occurred in your application. Exception HRESULT 0xC000014B"

 

The only difference from the last few days is I have been re-assigning livery paints in UT2, but not done anything else.

 

Any help appreciated.

Hi Mate did you get your problem resolved I'm also having the same issue of constant crashes with NET Framework. Only started when I installed vpilot...?

 

Regards

 

Lloyd

Share this post


Link to post
Share on other sites

The recommendation from PookyMacMan is a good one. Here's more info on the exception:

 

Exception from HRESULT: 0xc000014B error - The 0xc000014B is a "broken pipe" exception. A pipe is a communication channel between two applications (such as FSX and an addon program like vpilot). SimConnect offers addons 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 VPilot or ASN or OPUS tried to use the pipe (communications channel) and the “pipe” was broken. The 014B exception would then occur.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

Hi Jim.

 

sorry to bump an old topic.  The issue thats been plaguing me for months and months is this NET Framework HRESULT 0xC000014B

 

I had it tonight after shutting down the (you guessed it 777) at SYD after a succesfull 15 hour flight from LAX.

 

as ive explained in numerous other posts, the sim litterly just disappears from the screen.  

 

Its only happening with the 777 no other addons but im going through the hoops of pmdg saying its nothing to do with them

 

Have a look here please mate, many thanks as always. 

 

http://www1.metacraft.com/VRC/forums/viewtopic.php?t=4029


 
 
 
 
14ppkc-6.png
  913456

Share this post


Link to post
Share on other sites

That's a vPilot crash due to the sim crashing, not the root cause.

 

Cheers!
 

Luke


Luke Kolin

I make simFDR, the most advanced flight data recorder for FSX, Prepar3D and X-Plane.

Share this post


Link to post
Share on other sites

I agree with Luke.  The crash was caused by VPilot which has been the root of many crashes in the past (although it has gotten better lately).  I would simply uninstall/reinstall vPilot if it occurs again.

 

Best regards,

  • Upvote 1

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

 

 


The crash was caused by VPilot which has been the root of many crashes in the past (although it has gotten better lately). 

 

With respect, vPilot isn't the root of any crashes. It just doesn't handle a CTD gracefully, and unlike the sim it actually gives a visible crash report, hence it getting blamed. Look - a messenger. Quick, shoot him! :D

 

Cheers!

 

Luke


Luke Kolin

I make simFDR, the most advanced flight data recorder for FSX, Prepar3D and X-Plane.

Share this post


Link to post
Share on other sites

Thanks Luke for correcting me (again). :smile: I do like your description on what's happening.

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

It's better for apps to simply report the sim has shut down, rather than show an exception report. Especially when caused by FSX gone missing due to some other problem arising. Could simply be a missing texture in an AI aircraft or scenery that hangs the sim. What the OP needs to do is eliminate all other possibilities - run the 777 in stock FSX, no other addons. In actual fact you need to run the sim no addons at all first to check that's ok, but I usually assume it's OK and have been caught on that. hehe


Steve Waite: Engineer at codelegend.com

Share this post


Link to post
Share on other sites

Thanks for all the replies, some of which i agree and some I dont.

 

If you look at the post on the VRC forumn         http://www1.metacraft.com/VRC/forums/viewtopic.php?t=4029

 

Its the sim not the vrc client.  Like I said countless times, and I apolgise in advanced.  If its only the pmdg 777 (my 16000 hours on vatsim have to count for something) causing the issues then surely its an issue with the PMDG 777.  Ive mentioned this to them countless times, but they always want to shift the blame to LM coding of the sim even though its ONLY their 777 causing it. 


 
 
 
 
14ppkc-6.png
  913456

Share this post


Link to post
Share on other sites

How come so many others have no issues using the 777 on VATSIM?  Just you and a couple of others.  Your link did not prove anything.


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

Hello Friends,

 

I also experienced this problem: today in PMDG 777, but earlier in PMDG JS41. Before these two there was also similiar error (I don't remember in which aircraft) but I also suspected vPilot. So I reinstalled it, but it didn't help. I use MTL IVAO as an traffic and airlines presentation on VATSIM.

 

Today's reports:

 

a. from error window after crash:

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.v()

   at bz.g(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.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

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

vPilot

    Assembly Version: 1.1.5901.24775

    Win32 Version: 1.1.5901.24775

    CodeBase: file:///C:/Users/Lucas/AppData/Local/vPilot/vPilot.exe

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

Ninject

    Assembly Version: 3.2.0.0

    Win32 Version: 3.2.2.0

    CodeBase: file:///C:/Users/Lucas/AppData/Local/vPilot/Ninject.DLL

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

System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    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.8745 (WinRel.050727-8700)

    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.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

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

System.Core

    Assembly Version: 3.5.0.0

    Win32 Version: 3.5.30729.8763 built by: WinRel

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

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

Anonymously Hosted DynamicMethods Assembly

    Assembly Version: 0.0.0.0

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll

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

System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

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

System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

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

protobuf-net

    Assembly Version: 2.0.0.640

    Win32 Version: 2.0.0.640

    CodeBase: file:///C:/Users/Lucas/AppData/Local/vPilot/protobuf-net.DLL

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

6bmfopj7

    Assembly Version: 1.1.5901.24775

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

Accessibility

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

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

System.Management

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll

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

awsoujaq

    Assembly Version: 1.1.5901.24775

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.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

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

SharpDX.DirectInput

    Assembly Version: 2.6.3.0

    Win32 Version: 2.6.3

    CodeBase: file:///C:/Users/Lucas/AppData/Local/vPilot/SharpDX.DirectInput.DLL

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

SharpDX

    Assembly Version: 2.6.3.0

    Win32 Version: 2.6.3

    CodeBase: file:///C:/Users/Lucas/AppData/Local/vPilot/SharpDX.DLL

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

System.Web.Services

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll

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

lxfkdbxa

    Assembly Version: 1.1.5901.24775

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

msvcm80

    Assembly Version: 8.0.50727.9268

    Win32 Version: 8.00.50727.9268

    CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e/msvcm80.dll

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

dvenagb1

    Assembly Version: 1.1.5901.24775

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

Newtonsoft.Json

    Assembly Version: 6.0.0.0

    Win32 Version: 6.0.8.18111

    CodeBase: file:///C:/Users/Lucas/AppData/Local/vPilot/Newtonsoft.Json.DLL

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

System.Runtime.Serialization

    Assembly Version: 3.0.0.0

    Win32 Version: 3.0.4506.8763 (WinRel.030729-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Serialization/3.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll

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

System.Xml.Linq

    Assembly Version: 3.5.0.0

    Win32 Version: 3.5.30729.8763 built by: WinRel

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml.Linq/3.5.0.0__b77a5c561934e089/System.Xml.Linq.dll

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

System.Data

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll

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

 

************** 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.

 

b. from GlobalExceptions.txt - file from vPilot installation folder:

DateStamp: 20-Nov-16 8:51:53 PM

Details: System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B

   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

   at Microsoft.FlightSimulator.SimConnect.SimConnect.SetClientData(Enum ClientDataID, Enum DefineID, SIMCONNECT_CLIENT_DATA_SET_FLAG Flags, UInt32 dwReserved, Object pDataSet)

   at bo.f(Boolean A_0)

   at bo.q()

   at bz.ac()

   at a9.a(Object A_0, FormClosingEventArgs A_1)

   at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)

   at System.Windows.Forms.Form.RaiseFormClosingOnAppExit()

   at System.Windows.Forms.Application.ExitInternal()

   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)

   at System.Windows.Forms.Timer.TimerNativeWindow.OnThreadException(Exception e)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

   at System.Windows.Forms.Application.Run(Form mainForm)

   at dt.a(String[] A_0)

 

What can I do to resolve it?

 

Lucas

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...