Jump to content

vPilot error 0xC00014B (FSX Crash)


Krzysztof Jakis 1329316
 Share

Recommended Posts

PostPosted: Sat Nov 28, 2015 11:27 am Post subject: vPilot error 0xC00014B (FSX Crash) Reply with quote

Hello. I decited to change FSinn to vPilot. I have problem with vPilot. After takeoff i can fly 2 minutes and then my fsx crashed and i have a error:

 

 

************** Tekst wyjątku **************

System.Runtime.InteropServices.COMException (0xC000014B): Wyjątek od HRESULT: 0xC000014B

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

w Microsoft.FlightSimulator.SimConnect.SimConnect.RequestDataOnSimObjectType(Enum RequestID, Enum DefineID, UInt32 dwRadiusMeters, SIMCONNECT_SIMOBJECT_TYPE type)

w bo.v()

w by.g(Object A_0, EventArgs A_1)

w System.Windows.Forms.Timer.OnTick(EventArgs e)

w System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

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

 

 

************** Zestawy załadowane **************

mscorlib

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000)

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

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

vPilot

Wersja zestawu: 1.1.5638.40065

Wersja Win32: 1.1.5638.40065

CodeBase: file:///C:/User/AppData/Local/vPilot/vPilot.exe

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

Ninject

Wersja zestawu: 3.2.0.0

Wersja Win32: 3.2.2.0

CodeBase: file:///C:/User/Krzysztof/AppData/Local/vPilot/Ninject.DLL

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

System.Windows.Forms

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.8008 (FX35W81RTMGDR.050727-8000)

CodeBase: C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

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

System

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.7905 (win9rel.050727-7900)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

System.Drawing

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

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

System.Core

Wersja zestawu: 3.5.0.0

Wersja Win32: 3.5.30729.7903 built by: Win9Rel

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

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

Anonymously Hosted DynamicMethods [Mod - Happy Thoughts]embly

Wersja zestawu: 0.0.0.0

Wersja Win32: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll

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

System.Xml

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

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

System.Configuration

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

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

eugguwti

Wersja zestawu: 1.1.5638.40065

Wersja Win32: 2.0.50727.7905 (win9rel.050727-7900)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

Accessibility

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

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

System.Management

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll

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

Microsoft.DirectX.AudioVideoPlayback

Wersja zestawu: 1.0.2902.0

Wersja Win32: 5.04.00.2904

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC/Microsoft.DirectX.AudioVideoPlayback/1.0.2902.0__31bf3856ad364e35/Microsoft.DirectX.AudioVideoPlayback.dll

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

Microsoft.DirectX

Wersja zestawu: 1.0.2902.0

Wersja Win32: 5.04.00.2904

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC/Microsoft.DirectX/1.0.2902.0__31bf3856ad364e35/Microsoft.DirectX.dll

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

n80i6w6z

Wersja zestawu: 1.1.5638.40065

Wersja Win32: 2.0.50727.7905 (win9rel.050727-7900)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

System.resources

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.7905 (win9rel.050727-7900)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.resources/2.0.0.0_pl_b77a5c561934e089/System.resources.dll

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

Microsoft.FlightSimulator.SimConnect

Wersja zestawu: 10.0.61259.0

Wersja Win32: 10.0.61637.0 (FSX-Xpack.20070926-1421)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll

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

SharpDX.DirectInput

Wersja zestawu: 2.6.3.0

Wersja Win32: 2.6.3

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

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

SharpDX

Wersja zestawu: 2.6.3.0

Wersja Win32: 2.6.3

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

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

System.Web.Services

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.7905 (win9rel.050727-7900)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll

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

mscorlib.resources

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000)

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

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

-fwwxwry

Wersja zestawu: 1.1.5638.40065

Wersja Win32: 2.0.50727.7905 (win9rel.050727-7900)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

msvcm80

Wersja zestawu: 8.0.50727.8428

Wersja Win32: 8.00.50727.8428

CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d/msvcm80.dll

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

fqqpdgls

Wersja zestawu: 1.1.5638.40065

Wersja Win32: 2.0.50727.7905 (win9rel.050727-7900)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

Newtonsoft.Json

Wersja zestawu: 6.0.0.0

Wersja Win32: 6.0.8.18111

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

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

System.Runtime.Serialization

Wersja zestawu: 3.0.0.0

Wersja Win32: 3.0.4506.7903 (Win9Rel.030729-7900)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Runtime.Serialization/3.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll

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

System.Xml.Linq

Wersja zestawu: 3.5.0.0

Wersja Win32: 3.5.30729.7903 built by: Win9Rel

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Xml.Linq/3.5.0.0__b77a5c561934e089/System.Xml.Linq.dll

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

System.Data

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll

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

System.Windows.Forms.resources

Wersja zestawu: 2.0.0.0

Wersja Win32: 2.0.50727.7905 (win9rel.050727-7900)

CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_pl_b77a5c561934e089/System.Windows.Forms.resources.dll

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

 

************** Debugowanie w trybie JIT **************

Aby włączyć debugowanie w trybie JIT (just-in-time), plik .config tej

aplikacji lub komputera (machine.config) musi mieć

wartość jitDebugging ustawioną w sekcji system.windows.forms.

Aplikacja musi być również skompilowana z włączonym

debugowaniem.

 

I have only FSX default aircraft add-on. And i tried to open SimConnect in debug mode,but nothing changed. Please help me Wink

 

Sorry for my Eng.

Link to comment
Share on other sites

  • Board of Governors

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.

Don Desfosse
Vice President, Operations

Link to comment
Share on other sites

Yesterday I had a problem with installing the .NET 3.5. I had to uninstall any update in windows to .net could be installed to operate vPilot.

 

Data:

Nazwa aplikacji powodującej błąd: fsx.exe, wersja: 10.0.62615.0, sygnatura czasowa: 0x559f9a9a

Nazwa modułu powodującego błąd: ntdll.dll, wersja: 6.3.9600.17031, sygnatura czasowa: 0x5308893d

Kod wyjątku: 0xc0000029

Przesunięcie błędu: 0x0009df82

Identyfikator procesu powodującego błąd: 0x474

Godzina uruchomienia aplikacji powodującej błąd: 0x01d12a1cb66db049

Ścieżka aplikacji powodującej błąd: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe

Ścieżka modułu powodującego błąd: C:\WINDOWS\SYSTEM32\ntdll.dll

Identyfikator raportu: 70b3627e-9613-11e5-800e-1c7508e13aae

Pełna nazwa pakietu powodującego błąd:

Identyfikator aplikacji względem pakietu powodującego błąd:

 

Nazwa aplikacji powodującej błąd: fsx.exe, wersja: 10.0.62615.0, sygnatura czasowa: 0x559f9a9a

Nazwa modułu powodującego błąd: acontain.dll, wersja: 10.0.62615.0, sygnatura czasowa: 0x559f9ab3

Kod wyjątku: 0xc0000095

Przesunięcie błędu: 0x000052ea

Identyfikator procesu powodującego błąd: 0x474

Godzina uruchomienia aplikacji powodującej błąd: 0x01d12a1cb66db049

Ścieżka aplikacji powodującej błąd: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe

Ścieżka modułu powodującego błąd: C:\Program Files (x86)\Steam\steamapps\common\FSX\acontain.dll

Identyfikator raportu: 635df4ad-9613-11e5-800e-1c7508e13aae

 

 

Nazwa aplikacji powodującej błąd: fsx.exe, wersja: 10.0.62615.0, sygnatura czasowa: 0x559f9a9a

Nazwa modułu powodującego błąd: nvwgf2um.dll_unloaded, wersja: 9.18.13.4788, sygnatura czasowa: 0x5503046a

Kod wyjątku: 0xc0000005

Link to comment
Share on other sites

  • Board of Governors

The problem is not tremendously well known, likely due to the almost infinite number of variables based on different peoples' installations. It seems to be a .net and/or memory access violation with FSX. FSX is crashing and vPilot is reporting the error. Are you running add-on scenery? Have you run the uiautomationcore fix?

 

If you haven't done run the uiautomationcore fix, I'd suggest trying that first (http://forums.flightsimlabs.com/index.php?/topic/3516-fsx-and-windows-7-in-64-bits-needs-uiautomationcoredll-to-stop-crashing/). There has been some anecdotal talk, no real evidence that I've found, though, that suggests that installing FSX in the default location (c:\program files (x86).... ) exacerbates the problem due to Windows file system protections (I've read that second-hand a few times over the years, but haven't seen any true evidence that proves/disproves it).

 

If the uiautomationcore fix doesn't help and reinstalling into a different location (i.e. c:\FSX) doesn't work (or you don't want to bother reinstalling -- I wouldn't blame you if you didn't want to do that!), then you could attempt to troubleshoot what add-on scenery might be causing the memory issue and stop using that scenery. My opinion, though? If you went through the trouble to buy or obtain freeware scenery, you probably want to use it, so I'd start with the uiautomationcore fix first if you haven't yet.

 

Please update us on your progress -- the more information we have, the better we can help others in the community, and there just isn't a lot of definitive information to help with this FSX/Windows error.

 

(PS, for the more technically inclined and/or inquisitive, one of the best posts I've read on the uiautomationcore issue can be found at http://www.flightsim.com/vbfs/showthread.php?260894-Newbie-Alert-FSX-APPCRASH-UIautomationCore-dll&p=1748575#post1748575)

(PPS, as a corollary to the SmallJet post, I've seen written in a few places that between the two Vista versions that a lot of folks recommend, the older 6.0.5840.16386 version works better for at least some folks.

A good discussion can be found here: http://www.avsim.com/topic/421820-wrong-version-of-uiautomationcoredll/

And the file can be found here: http://www.search-dll.com/dll-files/download/uiautomationcore.dll.html).

Don Desfosse
Vice President, Operations

Link to comment
Share on other sites

  • Board of Governors

For troubleshooting/data collection purposes, did you only start using the Drzewiecki demo sceneries after you switched to vPilot?

 

The 0xC00014B error has been identified by VATSIM users on all pilot clients (yep, even xPlane -- I just checked ), so it doesn't seem to be caused by any client, which aligns with the research I've done on the 14B error to date. I've also seen it occur with FSX, FSX:SE and P3D users.

 

Thanks for agreeing to keep us updated.

Don Desfosse
Vice President, Operations

Link to comment
Share on other sites

So..... After climbed FL100 FSX freezed and crahed. I installed this fix in my FSX main folder.

 

Previously, when i was trying to install vPilot I had that error https://encrypted-tbn3.gstatic.com/images?q=tbn:ANd9GcTPGcin2vhf6hPbiHvHU24N-lfx1oa2KISjatTTUog5ukkgsT3q. Two days ago i decited to make CHCKDSK in my computer. This freezed in 14% and i made hard reset. After that i uninstalled KB928368 .NET 3.5 update and vPilot was installed successfully. So maybe FSX is crashing,becouse i don't have KB928368 .NET 3.5 update? In windows update i can install few .NET 4.5 updates. Install,or not?

Link to comment
Share on other sites

  • 2 weeks later...

Finally made it to the talking to the controller stage. Final problem was connecting a USB headset, which came down to a change in the vPilot config file. Thought I was all set then along comes this error which the Windows 10 error message attributes to vPilot but examination of the Event Log relates it to FSX:

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: uiautomationcore.dll, version: 7.2.10240.16515, time stamp: 0x55fa4fc4

Exception code: 0xc0000005

Fault offset: 0x00064d55

Faulting process id: 0xe80

Faulting application start time: 0x01d1339ce861bec1

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator

 

Presumably have to locate a later version of uiautomationcore.dll and replace the existing version.

 

Searching the above faulting application path for uiautomationcore.dll produced 4 files with this version number:

C:\Windows\Sydtem32 [1.26 mb]

C:\Windows\WinSxS\amd64_microsoft-windows-uiautomationcore............. [1.26 mb]

C:\SysWOW64 [1.05 mb]

C:\Windows\WinSxS\wow64_microsoft-windows-uiautomationcore.............

 

So if I locate a later version which file(s) must I replace?

 

Cheers,

Ian

Link to comment
Share on other sites

Don, followed your instructions, downloaded the new file, for the record its version 6.0.6001.18000, put it in the top FSX directory , started up and now have lost sound !!!

 

Immediately prior to loading FSX was using Skype. Was asked if I wanted to use the USB headset with Skype and took"Yes" option.

 

To make sure Skype was out of the picture shut down, renamed new file to prevent it loading, confirmed vPilot config was still looking for the USB headset, made tbe USB headset the default mike and speaker and restarted - in short returned to the state in which the sound worked. Result ... still no sound.

 

Note that I didn't remove any of the uiautomationcore files mentioned in my previous post - not sure how it is putting the downloaded file in the top directory of FSX will override other instances on which the program previously depended and which exist outside the FSX directory?

 

Regretably am thinking I might have to go back to square zero to resolve this.

 

Cheers,

Ian

Link to comment
Share on other sites

  • Board of Governors

Ouch. I've never heard of that. Have you rebooted? At the very minimum, if, after a reboot, your sound issue isn't resolved, you may want to go back to a restore point prior to the change. I've been watching people do the uiautomationcore fix on various forums for years, and have never heard anything like this.

Don Desfosse
Vice President, Operations

Link to comment
Share on other sites

Getting the feeling that I'm not meant to be here. Have spent at least 20 hours removing vPilot and FSX SP2 from my system multiple times and working up from scratch. Haven't even reached the point of putting vPilot back am having so much trouble with FSX.

 

Uninstalled FSX SP2 which went through and left FSX installed. Uninstalled FSX. Reinstalled FSX, then SP1, then SP2. Program loaded OK, but when Fly Now selected the display became very distorted; looking at a set of stairs side on is the only way I can describe the display pattern.

 

Uninstalled FSX SP2, then FSX, and reinstalled FSX, then SP1, then SP2. Had a look at the FSX directory and was surprised to see the uiautomationcore file listed. Concluded firstly, that it was still there because the FSX uninstall works from the list of files installed and p[Mod - Happy Thoughts]es over those which are just copied in subsequently, as was the case with uiautomationcore.dll, and secondly, that being present before SP1 and SP2 were reinstalled somehow it was responsible for the display problem.

 

Uninstalled FSX SP2, then FSX again, this time also removing the Microsoft Games directory from drive C:\. Surely the drive would now be free of anything to do with FXS? As a precaution also ran a full Malaware scan to check that all was clear, and it was.

 

Reinstalled FSX, then SP1, then SP2, pressed Fly Now and there is the same distorted display again! Closed the program via CTL+Alt +Delete - the screen which came up was also distorted but you can see pick the Task Manager option. Clicking it brings up the Task Manager, also distorted, however again you can pick the FSX entry. Click on that and then on End Task and you return to a desktop correctly displayed, the distortion gone and other applications run subsequently not affected.

 

As a matter of recond the time to reinstall FSX alone was 5:37. Can't face too much more of this.

 

Will discuss with my dealer's technical support tomorrow, but will be interested to learn of any other display issues with FSX and how they were resolved.

 

Cheers,

Ian

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...