I'm running FSX steam edition on windows 7 64bit. Looking at my Arcas log it appears to be happening when I the pause at top of descent turns on in the PMDG 777

Info from the box 

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.ReceiveDispatch(SignalProcDelegate pfcnSignal)

   at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage()

   at FSXWX.Form1.DefWndProc(Message& m)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.ContainerControl.WndProc(Message& m)

   at System.Windows.Forms.Form.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.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)

 

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

FSXWX

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

 

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

System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5491 (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.5491 (Win7SP1GDR.050727-5400)

 

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

Microsoft.FlightSimulator.SimConnect

    Assembly Version: 10.0.61259.0

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

 

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

msvcm80

    Assembly Version: 8.0.50727.6195

    Win32 Version: 8.00.50727.6195

 

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

System.Core

    Assembly Version: 3.5.0.0

    Win32 Version: 3.5.30729.5420 built by: Win7SP1

 

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

System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

 

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

System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5485 (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.

Last time I had any C++ errors, I didn't have the latest runtimes. I like to make sure I have them all just in case. Same with .NET Framework. I make sure that is all up to date as well. Windows 7 comes with .NET 3.5 SP1 by default if I recall. I wouldn't use the .NET 4.6 RC yet. I would tend to stick with the official 4.5.2 package for now.

Last time I had any C++ errors, I didn't have the latest runtimes. I like to make sure I have them all just in case. Same with .NET Framework. I make sure that is all up to date as well. Windows 7 comes with .NET 3.5 SP1 by default if I recall. I wouldn't use the .NET 4.6 RC yet. I would tend to stick with the official 4.5.2 package for now.

When I ran the installer for 4.5.2 it said it was already installed. Should I try installing some of the earlier ones or are these comprehensive updates.

I just responded to an individual in the CTD Forum regarding this type of crash.  It's a Microsoft.net error telling you there is something wrong with Simconnect communications.  I'm moving this to the CTD Forum where it belongs.

 

Best regards,

 

 

 

I just responded to an individual in the CTD Forum regarding this type of crash. It's a Microsoft.net error telling you there is something wrong with Simconnect communications. I'm moving this to the CTD Forum where it belongs.

 

Best regards,

 

 

Did you find a fix Jim?

Thanks David

There is no fix for this type of crash. It's a com problem where your system is not communicating properly. It means your Simconnect is not set up properly or the program running simconnect is not communicating properly. Each case has to be investigated. See the topic just next to this one for more details and suggestions.

 

Best regards,