Hi,I just have a CTD with the SP1 on my first flight with it :( .I had this :Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: MSVCR80.dllAs it is the first time i'm having this module failing i'm wondering if it could be linked with FS2Crew and if yes what can i do to prevent any other CTD with it ?Thank you !Théo

Hi Theo,That's not good! Try this thread:http://forum.avsim.net/topic/247918-msvcr80dll-causes-frequent-crashes/A lot of random crashes can be traced back to excessive heat (dust in in computer components) for example. Faulty drivers, etc. Memory leaks.Try again, it could just be a one off thing.Cheers,

Ok thanks i'll check that !

Ok thanks i'll check that !

Be sure to focus on any 3rd party scenery you have.From experience, they tend to be the worst culprit when it comes to making FSX go south.Cheers,

I'm becoming a bit crazy today :( , on my second flight of the day got another CTD each time soon after descent with that :Fault Module Name: StackHash_8889Fault Module Version: 6.1.7601.17725There is nothing there on google wich link StackHash_8889 and fsx... these are my very first CTD since a very long time ago (before tweaks) i have not installed any new scenery, only things i installed is FS2CrewNGX then i'm wondering if running the FS2Crew SP1 could be linked ?it never happened to me...'till now

I was going to make a new thread but as we seem to have similar problems I'll write here.This is the error I'm getting while on climbout from ENVA (Trondheim Vaernes X from Aerosoft)Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Fault Module Name: StackHash_0a9e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 00000000 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1053 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789The CTD was quick, not the usual freeze "not responding" symptoms and then a Fatal Error pop-up but immediate.The error happened just after I told the FO to "Set Altitude Two Six Thousand" at maybe 6000 feet so away from the airport.First time I've had this CTD happen but I did do a reinstall of FS2Crew and the SP1C patches for 738/900NGX and 737/600 just before the flight.EDIT: To clarify I reinstalled the SP1C patch for NGX & 700/600 and uninstalled FS2Crew NGX vanilla and installed the new SP1 following the order in the change log.

First time I've had this CTD happen but I did do a reinstall of FS2Crew and the SP1C patches for 738/900NGX and 737/600 just before the flight.

Same here for me, unfortunately. I went through the same process described above and FSX bluescreened BIGTIME the first time I tried to start FS2Crew Voice SP1 for the NGX. I tried reinstalling but I'm still encountering CTD's left and right. Weird. For now I'm going to try installing the non-SP1 version again as it was stable on my particular setup. Gee Whiz though, I was kinda excited about the SP1 and all the new features. I'm using FSX Acceleration + W7 Ultimate 64 bit.

Same here for me, unfortunately. I went through the same process described above and FSX bluescreened BIGTIME the first time I tried to start FS2Crew Voice SP1 for the NGX. I tried reinstalling but I'm still encountering CTD's left and right. Weird. For now I'm going to try installing the non-SP1 version again as it was stable on my particular setup. Gee Whiz though, I was kinda excited about the SP1 and all the new features. I'm using FSX Acceleration + W7 Ultimate 64 bit.

Yeah, I think I will do that as well. I just had another, identical ctd, but this time in cruise trying to finish the flight that failed before :( (Actions done at the time of the fatal error was the descent checklist)

okay, i got a third CTD just as described by MrGreen involving again another

StackHash...module

when shutting down at the gate. It occurs when i call the ground crew.

I ran a memorie test successfully, ran an antimalware/antivir scan which found few things to remove. I did'nt reinstall FS2Crew.

i've started a flight again(the 4th :( ) but i've experienced a lot of issues :

- FO ask me to "check that" for almost all items of the preflight checklist and also for the before start

- He told me that the aircraft was not configured for engine start but it was as usually...

- I was unable to ask fot a heading or an altitude both on ground and in the air. (heading rounding without end and altitude climb up to maximum available on MCP) voice button on/off/on stop that but didn't "reset" it to normal.

BUT,

i didn't experience any CTD at all this time. As FS2Crew wasn't working properly i can't call that a good test.

I'll try another flight tomorow after a fresh install of FS2Crew SP1.

3 CTD the same day, at each flight, after installing SP1, without adding anything else and when i know that i never experienced these modules fault before, i'm pretty sure it can't be a coincidence.

(Actions done at the time of the fatal error was the descent checklist)

Yeah two of mines were during that one too !

I've just uninstalled FS2Crew SP1, downloaded it again and installed it. I ran the config manager and habe disabled then reenabled FS2Crew Voice.I did a 30 mins roundtrip flight LOWW->LOWW (without using circuit training but using normal op procedure) with 737 up to FL200. I had absolutely no issues. everythings works perfectly. No CTD when running descent checklist, no CTD at all.I'll still do a longer flight tomorow to confirm that.

I've just uninstalled FS2Crew SP1, downloaded it again and installed it. I ran the config manager and habe disabled then reenabled FS2Crew Voice.I did a 30 mins roundtrip flight LOWW->LOWW (without using circuit training but using normal op procedure) with 737 up to FL200. I had absolutely no issues. everythings works perfectly. No CTD when running descent checklist, no CTD at all.I'll still do a longer flight tomorow to confirm that.

Glad you had a trouble free flight that time.But, as mentioned, check your scenery. Bugs in 3rd party scenery are famous for causing problems.Cheers,

Hi,I've downloaded the latest microsoft Visual C++ version. I didn't change anything about scenery then I try a LOWW-EDDM flight wich crashed yesterday.So same sceneries, Same aircraft, Same FP, same FL.Problems looks to be solved as everythings was perfect.Again thanks for your help.

Hi,I've downloaded the latest microsoft Visual C++ version. I didn't change anything about scenery then I try a LOWW-EDDM flight wich crashed yesterday.So same sceneries, Same aircraft, Same FP, same FL.Problems looks to be solved as everythings was perfect.Again thanks for your help.

Glad you got it sorted.

Hi Bryan,

 

I am also getting frequent crashes after FS2Crew installation. My latest crash was the MSVCR80.dll,

Try downloading the latest microsoft Visual C++ runtimes.

 

That worked for Gate 51 above.