Jump to content

vPilot + FSX SE Crashes Constantly


Recommended Posts

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

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

Rodrigo Abulafia

VATSIM 874508

Southern Winds Virtual Member (SWD450)

Argentina FIR Controler

Link to post
Share on other sites

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

Link to post
Share on other sites

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 [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/rabulafia/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/rabulafia/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/rabulafia/AppData/Local/vPilot/protobuf-net.DLL

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

zo_vryiv

[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

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

kyp9i9gi

[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/rabulafia/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/rabulafia/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

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

ow4o8qw-

[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

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

kjcyziki

[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

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

 

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

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

Rodrigo Abulafia

VATSIM 874508

Southern Winds Virtual Member (SWD450)

Argentina FIR Controler

Link to post
Share on other sites

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:

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

Rodrigo Abulafia

VATSIM 874508

Southern Winds Virtual Member (SWD450)

Argentina FIR Controler

Link to post
Share on other sites
  • Board of Governors

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 [Mod - Happy Thoughts]ociated 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.

Don Desfosse
Vice President, Membership

Link to post
Share on other sites

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

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

Rodrigo Abulafia

VATSIM 874508

Southern Winds Virtual Member (SWD450)

Argentina FIR Controler

Link to post
Share on other sites
  • Board of Governors

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 [Mod - Happy Thoughts]ociated 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!

Don Desfosse
Vice President, Membership

Link to post
Share on other sites

Hi Don

 

Thanks for the quick reply; my question was pointed that that the DLL crashes only with vPilot, in no other cases FSX SE is crashing; nor using icao software, REX, FSPS, PMDG or any other add-on.

 

any clue though?

 

thanks!

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

Rodrigo Abulafia

VATSIM 874508

Southern Winds Virtual Member (SWD450)

Argentina FIR Controler

Link to post
Share on other sites

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.

Kyle Ramsey

 

0

Link to post
Share on other sites

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

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

Rodrigo Abulafia

VATSIM 874508

Southern Winds Virtual Member (SWD450)

Argentina FIR Controler

Link to post
Share on other sites

Hello and thanks for the help, but I insist: it only happens the freezing with vPilot, nor any of the others add-ons make FSX SE to freeze. I guess all of them are "informally" certified to work with FSX SE while vPilot or any other Vatsim Software isn´t. The thing is that FSX SE has been out for some years from now and none of the software has been update. Curious.

 

Anyway,

Thanks to all for the support.

 

cheers

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

Rodrigo Abulafia

VATSIM 874508

Southern Winds Virtual Member (SWD450)

Argentina FIR Controler

Link to post
Share on other sites

 

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.

 

Because then you'd know the source of the error and can correct it. Sometimes just reloading that scenery will fix it and everything is good to go. It also adds to the body of knowledge about this error type as it seems to have mysterious elements to it so any new knowledge gets us closer to nailing it shut forever.

Kyle Ramsey

 

0

Link to post
Share on other sites
The thing is that FSX SE has been out for some years from now and none of the software has been update. Curious.

Eh.. not too curious, given that the most significant changes that FSX:SE seems to have brought are where FSX gets installed on your hard drive, a new splash screen, new defaults for .cfg file values, and a new multiplayer network. I'd be shocked to learn they really changed the SDK that addon developers use in any meaningful way.

 

it only happens the freezing with vPilot

The one thing off the top of my head that vPilot could do differently than, for example, IvAP, would be the choices for models it tells FSX to use when displaying other aircraft from VATSIM.

 

@Ross: Before v2.0, you had the "Run Model Matching Test" functionality. Did this iterate through all model rules force FSX to create and render an aircraft (even if momentarily) with each model? For some reason I thought it did, because I remember some models causing FSX to crash when used and the model matching test helped identify such models. All that to say... could it not be a specific aircraft model (e.g. one that IvAP wouldn't be using) that is causing Rodrigo's crashes?

Link to post
Share on other sites

Hi @Ross and thanks for the support.

 

I have checked base on your question and I am only using the matching models of IA of FSX SE. Make Sense? Do you suggest to make any change about that?

 

Reinforcing my comparison with IVAO -> Why they do have a Software that works absolutely perfectly really without any complaint at all, even thought inside FS with Full Screen, why Vatsim is not at the same stage?

 

We are -indeed- lot of Vatsim lovers for so many years with the aim of helping and make things done.

 

Greeting to all and sorry for the p[Mod - Happy Thoughts]ion beyond my words.

 

RA

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

Rodrigo Abulafia

VATSIM 874508

Southern Winds Virtual Member (SWD450)

Argentina FIR Controler

Link to post
Share on other sites

It's a matter of perspective. I have had issues with Squawkbox and FSInn in the past, but no problems with vPilot! So no complaints from me.

 

Of course, you'll see things a bit differently given your current situation.

David Zhong

Link to post
Share on other sites

Hello David & Vatsim Staff:

 

I have been trying different stuff these past days, and I have overcome the situation and would like to share with the community something that -most of the time- didin´t crash at all. First let me figure out the configuration I am using:

 

-FSX SE (updated via steam)

- Activeweather 5

- FSPS

- PDMG Products (737, 777 and 747)

- FSPS xtreme FSX Booster v2

- REX4 (Plus+Overdrive)

- Windows 10 Home, updated

- Core i7+32GB RAM+nVidia GTX 760 FTW+

 

Usually, I used to load first REX, define the route, load the textures and run FSX from REX. I shift the loading process and FIRST load FSX SE as ADMINISTRATOR and all of the following software to run in the SAME MODE.

 

SO basically the loading process follows like this:

 

- xtreme FSX Booster (should be loaded before FSX)

- FSX SE

- REX

- Active Weather

- FSPS

 

and of course, happy to be online again!

 

Hope it helps

 

cheers

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

Rodrigo Abulafia

VATSIM 874508

Southern Winds Virtual Member (SWD450)

Argentina FIR Controler

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...