Patrick Mollette 1192342 Posted July 6, 2016 at 07:43 PM Posted July 6, 2016 at 07:43 PM Hello, I have used Vpilot for quite a while, but just moved into new apartment and tried to start up the sim to do a flight. when i load FSX (JUST FSX... no ACARS or weather engines running at the time) it runs just fine. However, whenever I load Vpilot and do not click connect, it works just fine as well, and FSX has no problems (checked with me flying around with Vpilot running but not connected), but whenever I click "Connect" and successfully connect to the network (noted that I am fully connected), FSX will run for a few seconds then freeze and fatal errors. This is the message I receive from Vpilot Exception from HRESULT: 0x000014B Also I included the Details of the error to see if that helps at all... 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 [Mod - Happy Thoughts]emblies ************** mscorlib [Mod - Happy Thoughts]embly Version: 2.0.0.0 Win32 Version: 2.0.50727.8689 (QFE.050727-8600) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- vPilot [Mod - Happy Thoughts]embly Version: 1.1.5901.24775 Win32 Version: 1.1.5901.24775 CodeBase: file:///C:/Users/patrick/AppData/Local/vPilot/vPilot.exe ---------------------------------------- Ninject [Mod - Happy Thoughts]embly Version: 3.2.0.0 Win32 Version: 3.2.2.0 CodeBase: file:///C:/Users/patrick/AppData/Local/vPilot/Ninject.DLL ---------------------------------------- System.Windows.Forms [Mod - Happy Thoughts]embly Version: 2.0.0.0 Win32 Version: 2.0.50727.8670 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System [Mod - Happy Thoughts]embly Version: 2.0.0.0 Win32 Version: 2.0.50727.8690 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing [Mod - Happy Thoughts]embly Version: 2.0.0.0 Win32 Version: 2.0.50727.8681 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Core [Mod - Happy Thoughts]embly Version: 3.5.0.0 Win32 Version: 3.5.30729.8693 built by: QFE 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 [Mod - Happy Thoughts]embly Version: 0.0.0.0 Win32 Version: 2.0.50727.8689 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll ---------------------------------------- System.Xml [Mod - Happy Thoughts]embly Version: 2.0.0.0 Win32 Version: 2.0.50727.8679 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Configuration [Mod - Happy Thoughts]embly Version: 2.0.0.0 Win32 Version: 2.0.50727.8670 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- protobuf-net [Mod - Happy Thoughts]embly Version: 2.0.0.640 Win32 Version: 2.0.0.640 CodeBase: file:///C:/Users/patrick/AppData/Local/vPilot/protobuf-net.DLL ---------------------------------------- w6gqcoq9 [Mod - Happy Thoughts]embly Version: 1.1.5901.24775 Win32 Version: 2.0.50727.8690 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- Accessibility [Mod - Happy Thoughts]embly Version: 2.0.0.0 Win32 Version: 2.0.50727.8670 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- System.Management [Mod - Happy Thoughts]embly Version: 2.0.0.0 Win32 Version: 2.0.50727.8670 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll ---------------------------------------- riwvrh3k [Mod - Happy Thoughts]embly Version: 1.1.5901.24775 Win32 Version: 2.0.50727.8690 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- Microsoft.FlightSimulator.SimConnect [Mod - Happy Thoughts]embly Version: 10.0.61259.0 Win32 Version: 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 [Mod - Happy Thoughts]embly Version: 2.6.3.0 Win32 Version: 2.6.3 CodeBase: file:///C:/Users/patrick/AppData/Local/vPilot/SharpDX.DirectInput.DLL ---------------------------------------- SharpDX [Mod - Happy Thoughts]embly Version: 2.6.3.0 Win32 Version: 2.6.3 CodeBase: file:///C:/Users/patrick/AppData/Local/vPilot/SharpDX.DLL ---------------------------------------- System.Web.Services [Mod - Happy Thoughts]embly Version: 2.0.0.0 Win32 Version: 2.0.50727.8670 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll ---------------------------------------- vh3arcu0 [Mod - Happy Thoughts]embly Version: 1.1.5901.24775 Win32 Version: 2.0.50727.8690 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- msvcm80 [Mod - Happy Thoughts]embly Version: 8.0.50727.9193 Win32 Version: 8.00.50727.9193 CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9193_none_d09188224426efcd/msvcm80.dll ---------------------------------------- 7azch5hh [Mod - Happy Thoughts]embly Version: 1.1.5901.24775 Win32 Version: 2.0.50727.8690 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- Newtonsoft.Json [Mod - Happy Thoughts]embly Version: 6.0.0.0 Win32 Version: 6.0.8.18111 CodeBase: file:///C:/Users/patrick/AppData/Local/vPilot/Newtonsoft.Json.DLL ---------------------------------------- System.Runtime.Serialization [Mod - Happy Thoughts]embly Version: 3.0.0.0 Win32 Version: 3.0.4506.8693 (QFE.030729-8600) 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 [Mod - Happy Thoughts]embly Version: 3.5.0.0 Win32 Version: 3.5.30729.8693 built by: QFE CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/GAC_MSIL/System.Xml.Linq/3.5.0.0__b77a5c561934e089/System.Xml.Linq.dll ---------------------------------------- System.Data [Mod - Happy Thoughts]embly Version: 2.0.0.0 Win32 Version: 2.0.50727.8677 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/[Mod - Happy Thoughts]embly/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: 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. I have tried reading other forums and no help in any of them, so I am hoping somebody smarter than I could help me with this problem! Regards, Patrick Mollette Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted July 6, 2016 at 07:54 PM Board of Governors Posted July 6, 2016 at 07:54 PM The 14B error is most often [Mod - Happy Thoughts]ociated with scenery errors and/or out of memory errors. From your post, though, it seems like the only variable that changed is your location? From the event viewer, is it safe to [Mod - Happy Thoughts]ume that the faulting module is FSX? Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Patrick Mollette 1192342 Posted July 6, 2016 at 08:00 PM Author Posted July 6, 2016 at 08:00 PM The 14B error is most often [Mod - Happy Thoughts]ociated with scenery errors and/or out of memory errors. From your post, though, it seems like the only variable that changed is your location? From the event viewer, is it safe to [Mod - Happy Thoughts]ume that the faulting module is FSX? Well the event viewer is not showing any error messages or anything regarding FSX crashing OR Vpilot crashing. I dont see how the faulty module could be FSX, when FSX is running perfectly all the time, until I try to connect to Vpilot. Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted July 6, 2016 at 08:13 PM Board of Governors Posted July 6, 2016 at 08:13 PM I understand, but since we've seen hundreds of these errors, all showing the FSX was the faulting module, and not one yet showing that vPilot was, I thought it prudent to ask.... Please provide the faulting module name from the Event Viewer. It's just one more data point. Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted July 6, 2016 at 08:20 PM Board of Governors Posted July 6, 2016 at 08:20 PM The 0xc000014B is a "broken pipe" exception. A pipe is a communication channel between two applications (such as FSX and an addon program like ASN, vPilot, etc.). SimConnect offers addons the possibility to use pipes to communicate 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 trying to use the pipe (communications channel) and the “pipe” was broken. The 14B exception would then occur. Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Patrick Mollette 1192342 Posted July 6, 2016 at 08:32 PM Author Posted July 6, 2016 at 08:32 PM Well the Event viewer wasn't showing any errors, only thing recently (today) that shows something with FSX and Vpilot is this one. I appreciate you trying to help with this problem. hopefully this event view log helps somehow. Problem signature: P1: vpilot.exe P2: 1.1.5901.24775 P3: 56d1efc5 P4: Microsoft.FlightSimulator.SimConnect P5: 10.0.61259.0 P6: 46fad670 P7: 175 P8: 37 P9: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX P10: Attached files: C:\Users\patrick\AppData\Local\Temp\WER8C28.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_vpilot.exe_14f2e9c06893d27d71a419db26140d5b47371eb_00000000_1214934c Analysis symbol: Rechecking for solution: 0 Report Id: 3e7bd00f-43b3-11e6-aa2b-70188b25473e Report Status: 1 Hashed bucket: 2d9f48deaefed1b240199418c6665829 Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted July 6, 2016 at 08:44 PM Board of Governors Posted July 6, 2016 at 08:44 PM Thanks. The faulting module name is found under the Windows Event Viewer, under Windows Logs > Application. Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Patrick Mollette 1192342 Posted July 6, 2016 at 09:20 PM Author Posted July 6, 2016 at 09:20 PM The only event I see is the one copied and pasted, does the event I posted in the comment above yours show the faulting Module? The Event viewer doesn't show any error events or anything other than the one I posted above your last comment. Patrick Link to comment Share on other sites More sharing options...
Patrick Mollette 1192342 Posted July 6, 2016 at 09:30 PM Author Posted July 6, 2016 at 09:30 PM Ironically enough, when I tried to google the problem again, I found an article where you asked about the faulting module for another user, unfortunately they didn't even reply... Appreciate your help Link to comment Share on other sites More sharing options...
Bradley Grafelman Posted July 6, 2016 at 09:43 PM Posted July 6, 2016 at 09:43 PM The only event I see is the one copied and pasted, does the event I posted in the comment above yours show the faulting Module? No, because the event is related to vPilot. The reason vPilot crashed is because its communication with SimConnect was unexpectedly severed. Find out why that happened (which typically means: find out why FSX crashed) so that you can fix that issue. Once you do, you'll find vPilot won't crash because of it (thus you're done). EDIT: Did you try this several times in the same area? It could be that a model used to render a nearby pilot was causing FSX to crash. Which model matching rule set(s) in vPilot do you have? Link to comment Share on other sites More sharing options...
Patrick Mollette 1192342 Posted July 6, 2016 at 09:52 PM Author Posted July 6, 2016 at 09:52 PM Well how could one go about fixing an error with simconnect? Link to comment Share on other sites More sharing options...
Recommended Posts