By Rodrigo Abulafia 874508
#501280 Hello, and as per suggestion of Mr. Kyle Ramsey (Vatsim President) who has instantly and very kindly responded my emails I am posting this message in order to understand and look for a work around to the problem.
It is known that SB is not working nor FSinn in FSX:SE; for that I have tried several times installing vPilot and still got always the same problem: BOTH FSX and pilot CRASHES. I really don´t know why and I cannot get any software to fly online with Vatsim. Here is my H&S Configuration. Hope anyone has the same problem and can give me a clue:
- Windows 10 Home Updated, FSX SE updated, FSUIPC last update, REX, Soft Clouds, PMDG, FSPS, Several Tropical Sim and others add-on sceneries. Core i7+Nvidia GTX960 FTW, 32 RAM.

Thanks in advanced for the support.

RA
By Ernesto Alvarez 818262
#501284 Rodrigo, normally what happens is the sim will crash, which in turn crashes vpilot as it cant keep running after that point.

so first, as Don says, you need to open the error report and it will contain more information you can provide here as it will clue you as to whats causing your sim to crash. it can be the addon you are using, it could be memory or any number of other things thatll cause the sim to crash.

start with the error report, then also what addons were being used at the time (including any addon scenery areas you were flying over or near)

it can be daunting sometimes trying to figure these out
By Rodrigo Abulafia 874508
#501373 Hi Guys,

This is the error I am getting

************** 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.8689 (QFE.050727-8600)
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/rabulafia/AppData/Local/vPilot/vPilot.exe
----------------------------------------
Ninject
Assembly Version: 3.2.0.0
Win32 Version: 3.2.2.0
CodeBase: file:///C:/Users/rabulafia/AppData/Local/vPilot/Ninject.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
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.8690 (QFE.050727-8600)
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.8681 (QFE.050727-8600)
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.8693 built by: QFE
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.8689 (QFE.050727-8600)
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.8679 (QFE.050727-8600)
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.8670 (QFE.050727-8600)
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/rabulafia/AppData/Local/vPilot/protobuf-net.DLL
----------------------------------------
zo_vryiv
Assembly Version: 1.1.5901.24775
Win32 Version: 2.0.50727.8690 (QFE.050727-8600)
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.8670 (QFE.050727-8600)
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.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
kyp9i9gi
Assembly Version: 1.1.5901.24775
Win32 Version: 2.0.50727.8690 (QFE.050727-8600)
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/rabulafia/AppData/Local/vPilot/SharpDX.DirectInput.DLL
----------------------------------------
SharpDX
Assembly Version: 2.6.3.0
Win32 Version: 2.6.3
CodeBase: file:///C:/Users/rabulafia/AppData/Local/vPilot/SharpDX.DLL
----------------------------------------
System.Web.Services
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
ow4o8qw-
Assembly Version: 1.1.5901.24775
Win32 Version: 2.0.50727.8690 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
msvcm80
Assembly 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
----------------------------------------
kjcyziki
Assembly Version: 1.1.5901.24775
Win32 Version: 2.0.50727.8690 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.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.
By Ross Carlson 887155
#501377 The error you posted is from the vPilot crash. The vPilot crash happens as a side effect of FSX crashing. We need to see the FSX crash information. Try looking in the Windows event viewer.
By Rodrigo Abulafia 874508
#501388 Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: ntdll.dll, version: 10.0.10586.306, time stamp: 0x571afb7f
Exception code: 0xc0000005
Fault offset: 0x00026d79
Faulting process id: 0xc5c
Faulting application start time: 0x01d1c4aa13e47126
Faulting application path: F:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 756bc9fa-b2a8-43a2-8352-4b1c822f7b76
Faulting package full name:
Faulting package-relative application ID:
----------------------------------------------------------------------------------------------------------
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: ntdll.dll, version: 10.0.10586.306, time stamp: 0x571afb7f
Exception code: 0xc000041d
Fault offset: 0x00026d79
Faulting process id: 0xc5c
Faulting application start time: 0x01d1c4aa13e47126
Faulting application path: F:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 12b90877-7d74-41a5-a5fd-19f836ba0af8
Faulting package full name:
--------------------------------------------------------------------------------------------------------------
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: ntdll.dll, version: 10.0.10586.306, time stamp: 0x571afb7f
Exception code: 0xc0000005
Fault offset: 0x00026d79
Faulting process id: 0x107c
Faulting application start time: 0x01d1c4adcd2756d8
Faulting application path: F:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b6a9bd49-39cd-47ef-a4f4-8a89c6d3f13b
Faulting package full name:
By Don Desfosse 1035677
#501389 Ah, the old ntdll.dll issue.

Were you using addon scenery when the crash occurred? The 14B/ntdll.dll issue is discussed a bit on the net, but no clear root cause has been identified/proven. Most common theories that I've seen for the ntdll.dll center around add-on scenery/terrain. A lot of discussion on the net is memory problems associated with scenery, and some discussion about video drivers (I've seen discussion about needing to update, and also discussion about needing to roll back; neither was very definitive).

Most frequent advice is to troubleshoot by reducing graphics sliders. A decent amount of folks have rebuilt their fsx.cfg files which has solved the issue for them. Of course, that kills all the tweaks that you've made over time, so make sure you back it up first so you can compare and slowly add in tweaks again if you want to. You may want to start out more slowly by just dialing back some of your graphics settings and see if that gets your system/installation more stable. Please do report back if you try things and they do/don't work -- we give out a lot of advice and don't often get a lot of feedback, and where this one really hasn't had a stake nailed through it yet, it would be good to collect more data.
By Rodrigo Abulafia 874508
#501395 Hi Don,

Thanks for the constant input and support; I have read carefully and still don´t understand what that DLL has to be with vPilot. The drivers are updated, and I don´t get why that DLL drops error with vPilot with some scenery installed. How can I fix and what extra input to you need to workout that issue.

thanks in advanced,

RA
By Don Desfosse 1035677
#501401 Hi Rodrigo,

The DLL has nothing to do with vPilot. Your sim is crashing, which then forces vPilot to crash. To solve the root cause of vPilot crashing, you need to stop your sim from crashing. The ntdll.dll error is a memory error most often associated with add-on scenery/terrain issues. Most common advice there is to start by reducing your traffic sliders, and if you're not having luck there, rebuild your .cfg file.

Have a look here for more discussion: http://www.avsim.com/topic/350230-ntdlldll-crashes

Hope this helps!
By Kyle Ramsey 810181
#501419 I would try disabling any add on scenery. Start by disabling it all, then start up and see if it faults. If it does, that's not it. If it doesn't add half the sceneries back in and restart to see if it faults. If it does take out half of those and retest. If not add another quarter back in, test again. If at any time after all scenery is out without a fault then slowly add in and take away chunks so you can figure out which one is bad will sort through it.
By Rodrigo Abulafia 874508
#501420 Kyle/Don:

Thanks again for your time!

As I mentioned before, it only happens with vPilot, that´s why a really don´t see the sense to disable the add-on scenery & others.

I guess should be a reason why only happens with vPilot with this DLL. Anyway, I am unable to continue flying in with Vatsim as I don´t have any software working 100% as IVAO, and please excuse me for the comparison, but -as many other collegues- I am Vatsim user since 2003.

cheers
thanks