P3D 2.5 crashed on landing! OOM!

[Berike 13]

After long hours flying from EGLL to SBGR guess what...

 

Flying to the final approach, P3D crashed OOM!

 

Using a Asus GTX680 DirectCU II Top 2GB + 16gb Corsair Platinum 2600mhz....

 

My settings are exactly as Rob posted on his blog:

http://www.robainscough.com/Prepar3D_Settings_2.html

 

My scenery instead of 2048 is 4096, but I use only one monitor of 1080p.

 

It's very frustrating to get this stuff happening this days...

 

Got this message:

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 bm.x()
   at bw.h(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.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
vPilot
    Assembly Version: 1.1.5514.37598
    Win32 Version: 1.1.5514.37598

----------------------------------------
Ninject
    Assembly Version: 3.2.0.0
    Win32 Version: 3.2.2.0

----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.5420 built by: Win7SP1

----------------------------------------
Anonymously Hosted DynamicMethods Assembly
    Assembly Version: 0.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
ivm2fkt9
    Assembly Version: 1.1.5514.37598
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
Microsoft.DirectX.AudioVideoPlayback
    Assembly Version: 1.0.2902.0
    Win32 Version: 5.04.00.2904

----------------------------------------
Microsoft.DirectX
    Assembly Version: 1.0.2902.0
    Win32 Version: 5.04.00.2904

----------------------------------------
mxdd_xce
    Assembly Version: 1.1.5514.37598
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
Microsoft.FlightSimulator.SimConnect
    Assembly Version: 10.0.61259.0
    Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

----------------------------------------
SharpDX.DirectInput
    Assembly Version: 2.6.3.0
    Win32 Version: 2.6.3

----------------------------------------
SharpDX
    Assembly Version: 2.6.3.0
    Win32 Version: 2.6.3

----------------------------------------
System.Web.Services
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
b328qy3b
    Assembly Version: 1.1.5514.37598
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
msvcm80
    Assembly Version: 8.0.50727.6195
    Win32 Version: 8.00.50727.6195

----------------------------------------
denkcknk
    Assembly Version: 1.1.5514.37598
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
Newtonsoft.Json
    Assembly Version: 6.0.0.0
    Win32 Version: 6.0.8.18111

----------------------------------------
System.Runtime.Serialization
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.4506.5463 (Win7SP1GDR.030729-5400)

----------------------------------------
System.Xml.Linq
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.5420 built by: Win7SP1

----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

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

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

[Jim Young 2,356]

You received a simconnect error. As stated on page 12 of the AVSIM CTD Guide:

HRESULT: 0xc000014B error – Mostly occurs in networked computers. This is a Microsoft.net error. The 0xc000014B is a "broken pipe" exception. A pipe is a communication channel between two applications (such as FSX/P3D and an add-on program like ASN or OPUS, or network). SimConnect offers add-ons 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 ASN or OPUS tried to use the pipe (communications channel) and the “pipe” was broken. The 014B exception would then occur. Check your network setup or an application that uses SimConnect and troubleshoot.

 

In the debug, it shows Microsoft.FlightSimulator.SimConnect Assembly Version: 10.0.61259.0 being loaded.  Not sure if this is the version used by P3D (not my expertise).

 

Best regards,

[Berike 13]

I was using FSGRW, this error came after P3D crashed

 

The SimConnect version is for the EzCa 1.185 they released couple months ago

[WarpD 824]

Take your textures back to 1024x1024. Seriously. Your video card isn't large enough to support anything larger with high end settings (and I'm willing to bet you have all the sliders to the right).

[Berike 13]

I don't think it would be a problem, I have solid ~40fps exterior and ~30fps interior

[WarpD 824]

It's not about the FPS... has absolutely nothing to do with that. You're taking a deep sea ocean cruise ship that carries thousands of passengers and trying to drive it through a drainage ditch on a small country road and then complaining when it gets stuck.

[vc10man 732]

It's not about the FPS... has absolutely nothing to do with that. You're taking a deep sea ocean cruise ship that carries thousands of passengers and trying to drive it through a drainage ditch on a small country road and then complaining when it gets stuck.

Superb analogy. Could not have put it better. And more to the point, you are spot-on too.

 

More or less same time-frame flight, no OOM.

[Jazzfan 57]

 

 

You're taking a deep sea ocean cruise ship that carries thousands of passengers and trying to drive it through a drainage ditch on a small country road and then complaining when it gets stuck.

 

     Too funny!   But it really is like beating a dead horse.

 

  Jazz
 

[SolRayz 392]

I got to be honest guys, these OOM's have me pretty well fed up myself.  I attempted a Q400 flight out of default EGLL to EGJJ the other night, running only Orbx England, and never made it to the runway before an OOM. Luckily I saved my flight and flightplan, managed to take off and made it over the channel, then OOM. Running only 1024 textures here. EGLL is impossible, even at default.

[eminyilmaz 17]

Hi Marc, 

 

I also get OOMs when I am flying over Orbx England. I am suspecting this is not a coincidence and something wrong with Orbx England.

[Berike 13]

Just happened again here

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    Prepar3D.exe
  Application Version:    2.5.12942.0
  Application Timestamp:    54d283cc
  Fault Module Name:    MSVCR100.dll
  Fault Module Version:    10.0.40219.325
  Fault Module Timestamp:    4df2be1e
  Exception Code:    40000015
  Exception Offset:    0008d6fd
  OS Version:    6.1.7601.2.1.0.256.1
  Locale ID:    1046
  Additional Information 1:    fc6c
  Additional Information 2:    fc6cb936821fda002bbb2024199d0d8f
  Additional Information 3:    1560
  Additional Information 4:    15604ff71e579711736a3d38ef45f747

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
 

[virtualstuff 758]

It's not about the FPS... has absolutely nothing to do with that. You're taking a deep sea ocean cruise ship that carries thousands of passengers and trying to drive it through a drainage ditch on a small country road and then complaining when it gets stuck.

 

[SolRayz 392]

Hi Marc, 

 

I also get OOMs when I am flying over Orbx England. I am suspecting this is not a coincidence and something wrong with Orbx England.

 

Really? That's quite interesting, and you may be on to something, because I don't typically get OOM's except in England, particularly around EGLL. And I have many other Orbx regions, with no issues.

[ZKOKQ 984]

Marc, I have removed Orbx England. OOM magnet. It is the only Orbx terrain product that i cannot use.

[MikeT707 1,181]

If I remember correctly back a few months ago, some users were commenting that Orbx England was problematic in regards to OOM's.