P3D5 crash due to a bug in P3D **SOLVED, not a GSX problem**

[jarisaizprua]

Hello all, new customer here to comment about a crash I had some days ago; any advise to avoid it will be really appreciated.

I was flying online (Vatsim) from KPDX to KSFO in the PMDG 737NGXu and it was a nice flight, the crash happened once I was at the gate and I tried to use the GSX; basically I called the jetway and it was perfect, then I called the stairs and no problem, then I called again to the GSX menu to see other options via "CTRL SHIFT F12" and then the flight sim crashed.

Jaris Aizprua

###########################################################################################

Nombre de la aplicación con errores: Prepar3D.exe, versión: 5.0.31.35253, marca de tiempo: 0x5eebf566
Nombre del módulo con errores: VCRUNTIME140.dll, versión: 14.27.29016.0, marca de tiempo: 0x5ee8384d
Código de excepción: 0xc0000005
Desplazamiento de errores: 0x000000000000137b
Identificador del proceso con errores: 0xc30
Hora de inicio de la aplicación con errores: 0x01d6849aa5dd0a6a
Ruta de acceso de la aplicación con errores: C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Ruta de acceso del módulo con errores: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Identificador del informe: f7f1fb0b-e166-46f3-bea5-24d54e11678e
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:

Prepar3D.exe
5.0.31.35253
5eebf566
VCRUNTIME140.dll
14.27.29016.0
5ee8384d
c0000005
000000000000137b
c30
01d6849aa5dd0a6a
C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
f7f1fb0b-e166-46f3-bea5-24d54e11678e


Aplicación: Prepar3D.exe
Versión de Framework: v4.0.30319
Descripción: el proceso terminó debido a una excepción no controlada.
Información de la excepción: código de la excepción c0000005, dirección de la excepción 00007FFF101D137B

Aplicación: Prepar3D.exe Versión de Framework: v4.0.30319 Descripción: el proceso terminó debido a una excepción no controlada. Información de la excepción: código de la excepción c0000005, dirección de la excepción 00007FFF101D137B

###########################################################################################

[virtuali]

I was flying online (Vatsim) from KPDX to KSFO in the PMDG 737NGXu and it was a nice flight, the crash happened once I was at the gate and I tried to use the GSX; basically I called the jetway and it was perfect, then I called the stairs and no problem, then I called again to the GSX menu to see other options via "CTRL SHIFT F12" and then the flight sim crashed.

Nombre del módulo con errores: VCRUNTIME140.dll, versión: 14.27.29016.0, marca de tiempo: 0x5ee8384d

The VCRUNTIME140.dll crash has been discussed so many times on the forum and no, it's NOT a crash caused by GSX. There's a known bug in P3D 5 which affect EVERY application with a the transparent Simconnect menu, like GSX, FS Passengers, SODE, and even the *default* ATC window.

LM is aware of the problem, and has confirmed a fix is coming, there's just nothing we can do to prevent it, since it happens entirely within the simulator, and it can happen each time a menu is opened.

I changed the title of your post, so other users won't be mislead thinking the crash was "caused" by GSX.

[jarisaizprua]

Thank you very much, I didn't know about the bug, anyway the product is awesome.

[airbumps]

Hi @Virtuali,

I didn't want to create a another topic for the same thing but wanted to ask the question. We know and accept that this is a P3D issue related to the SimConnect window but (for me at least) its usually triggered when I use GSX as that the only program I use that calls the SimConnect window.

I use PROATC X but that allows me to associate menu selections with key presses - so it avoids actually opening the window. That seems to mean I don't get crashes calling PRO ATC X actions.

So is there a way to associate GSX Menu selections with key or button presses? Would this prevent the crashes as the window itself isn't called?

This P3D bug is causing a crash in 50% of my flights. Sometimes at boarding, sometimes at pushback and sometimes at arrivial. Its ruining the experience and P3D have failed to actually acknowledge the issue let alone indicate if/when its going to be fixed. Just wondering if there is a "work around".

Cheers,

[airbadger]

I wish FSDT could've implemented some kind of workaround, even if it's not their fault that LM has left this game-killing crash which ruins about 4 out of 10 of my flights linger for 5 months now. The state of P3D right now is incredibly disappointing.

[virtuali]

I wish FSDT could've implemented some kind of workaround, even if it's not their fault that LM has left this game-killing crash which ruins about 4 out of 10 of my flights linger for 5 months now. The state of P3D right now is incredibly disappointing.

If there were a workaround, we would have implemented it already, of course. Unfortunately, the ATC-like menu is completely outside our control, other than a list of entries, there's nothing else we can do, and no alternate ways to call it.

I think the main issue comes with the menu made with Scaleform, which is derived from Adobe Flash, and when it was sold to Autodesk, it stopped being supported.

[fruitycocktail]

if its of any help.  Ive had 2 of these in the last 5 flights.  the VC run time error.  I get them only when using gsx though  

[airbadger]

if its of any help.  Ive had 2 of these in the last 5 flights.  the VC run time error.  I get them only when using gsx though  

I get them with the default ATC window, but that case is much rarer for some reason.

[airbumps]

Yeah I'm getting a crash in about 50% of my flights now. Its getting to the point where its really unsatisfying. You spend an hour setting up for cold and dark and then  crash when requesting pushback.....such a pain in the backside..

[virtuali]

It's no use posting here, as if it was a GSX problem or something we could fix. We already explained multiple times it's a P3D issue we don't have any control over it, and you'll get proof of that with the next simulator update...