Crashes With GSX Update

[BIGSKY 316]

Anyone else getting these?

Both times when selecting overhead in NGX on shutdown at gate.

 

 

.LOG

 

9:06 PM 5/14/2012

Problem signature:

Problem Event Name: BEX

Application Name: fsx.exe

Application Version: 10.0.61637.0

Application Timestamp: 46fadb14

Fault Module Name: MSVCR80.dll

Fault Module Version: 8.0.50727.6195

Fault Module Timestamp: 4dcddbf3

Exception Offset: 00008aa0

Exception Code: c000000d

Exception Data: 00000000

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: e926

Additional Information 2: e9263950142051511ceadcb55c0aa80c

Additional Information 3: d0f9

Additional Information 4: d0f9503db77943574b06d7e8446f9b9b

 

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

 

9:08 PM 5/14/2012

[cmpbellsjc 2,960]

You'll probably need Umberto's help for that one. Post your question on the FSDT forum for best results.

[virtuali 4,421]

I really don't see how this could have anything to do with GSX:

 

- The crash is happening in MSVCR80.DLL, so it can be any FSX module, and it made the main FSX.EXE crash. GSX runs externally of GSX, inside the Couatl.exe module that, as a separate .EXE process, doesn't even have the ability to make FSX crash.

 

- As you said yourself, the crash happens: "Both times when selecting overhead in NGX on shutdown at gate."

 

Don't see the connection to GSX, and the update hasn't changed anything regarding the MS VC++ runtimes used (MSVCR80.DLL), it always use the same version since it was released, and the MS installer that GSX installer installs, doesn't do anything if you already have the correct version, and can't "downgrade" or corrupt an installed version

 

And no, nobody else has reported this, so it's surely nothing related to GSX, it's just that you happened to noticed it after the update, but this looks to be purely coincidental.

 

And, just to make it more clear: GSX has some interaction with the NGX (to read the door's status), but it's READ-ONLY, it doesn't write *anything* to it, and reading can't possibly create such problems.

[BIGSKY 316]

Thanks for the info, I guess I need to do some trouuble shooting :Thinking: