Stackhas CTD after FSDT JFK and GSX Install /P3D 2.5

[asegm08]

 Hey guys,

 I installed P3D 2.5 with the latest hotfix when it came out on the 21st. Did a few flights but did not have time to finish installing my add-ons. Then I installed Hifi Activesky and it worked ok. I then installed FSDT JFKv2 and GSX started the sim with the Aerosoft A320 and I finally had it set in the ground at JFK. At times the sim would crash only 2 minutes after selecting the aircraft and doing a few things in the VC. But every time I set a new flight it continued crashing with the CTD stackhash as the faulty module. I went to the LM forums and found this http://www.prepar3d.com/forum-5/topic/problems-after-hotfix/#post-101148 thread where they are describing the same issue with the same stackhash code as mine.


My specs

Please help

Alcides Segovia

I7 2600K 3.14 8GM RAM Nvidia 550TI GTX

Here are the logs

Code: [Select]

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Windows Error Reporting" />
  <EventID Qualifiers="0">1001</EventID>
  <Level>4</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2015-02-26T16:04:48.000000000Z" />
  <EventRecordID>4802</EventRecordID>
  <Channel>Application</Channel>
  <Computer>Alcides-PC</Computer>
  <Security />
  </System>
- <EventData>
  <Data />
  <Data>0</Data>
  <Data>APPCRASH</Data>
  <Data>Not available</Data>
  <Data>0</Data>
  <Data>Prepar3D.exe</Data>
  <Data>2.5.12943.0</Data>
  <Data>54e39da6</Data>
  <Data>StackHash_0a9e</Data>
  <Data>0.0.0.0</Data>
  <Data>00000000</Data>
  <Data>c0000005</Data>
  <Data>ffb10016</Data>
  <Data />
  <Data />
  <Data />
  <Data>C:\Users\Alcides\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_44a9c2c46898c0639780120657bad191df3db13_184e0dc6</Data>
  <Data />
  <Data>0</Data>
  <Data>13026e11-bdd1-11e4-9f45-1078d2da087b</Data>
  <Data>0</Data>
  </EventData>
  </Event>

Code: [Select]

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name=".NET Runtime" />
  <EventID Qualifiers="0">1026</EventID>
  <Level>2</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2015-02-26T16:19:46.000000000Z" />
  <EventRecordID>4803</EventRecordID>
  <Channel>Application</Channel>
  <Computer>Alcides-PC</Computer>
  <Security />
  </System>
- <EventData>
  <Data>Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address FFB10016</Data>
  </EventData>
  </Event>

[asegm08]

Solved it using the 2013 Addon Manager posted by umberto here

http://www.fsdreamteam.com/forum/index.php/topic,11597.45.html

Its important that I let you guys know that I had issues even in FSX with this. It completely messed up both sims. I know that Umberto has been saying that its not possible but the 2013 add on manager is working with no stackhash CTD on start up.

[virtuali]

Its important that I let you guys know that I had issues even in FSX with this. It completely messed up both sims. I know that Umberto has been saying that its not possible but the 2013 add on manager is working with no stackhash CTD on start up.

I never said "it's not possible". How I could post a fix otherwise ? I said that it's nothing *caused* by the Addon Manager, because up to today, the version using the 2005 runtimes always worked for years.

Something must have changed, possibly caused by a recent Windows update or by some other popular FSX addon that has been updated (or a combination of the two) resulting in issues when modules using both the 2005 are running *together* with modules running other versions, and the Addon Manager was the VICTIM of this, not the cause.

That's why, without changing a single line of code in it, but just compiling it with VS 2013, seems to have fixed all issues, because it now relies on the 2013 runtime libraries, instead of the 2005 ones which, strangely enough, are used by FSX itself, which was the main reason why we stayed with it until now.