Prepar3D v2 Hotfix (2.5.12943.0) **SOLVED**

[Peter22]

Yes I am experiencing CTD also after re install  KLAX and KLAS.....However, I do have ORBx base,vector,and some USA regions previously tested with NOT issues for several hours, my question is should I move fsdream airports down to scenary list or I should keep them in the default install order???..I am asking just to make sure that Orbx Lib should be on top??? , I believe, and then everything else???.....but regardless the order I do have crash after last Fsdream add manager (KLAS-KLAX) update that covered the last P3D fix...
Thanks
Pedro
no specific error just "P3D stop working"

[virtuali]

I don't have any idea about where the Orbx library should be, but the airports will surely be on top of everything else. But I don't thing this is an issue regarding the crash. See my previous reply about it.

[Peter22]

yeah I saw it...There are three thing that came out pretty much at same time..The P3D fix, the ASN for that fix and the new FSD addon manager for the last P3D update....we have to test them individually so we can come out with a conclusion.....any of them can maybe mismatching some how with each others.....
I am going to uninstall FSD and fly same route .  (No ASN) .will report back tonight
Thanks
Pedro
Thanks for let me know that FsD must to be on top...I have it that way though..

[akstirling]

Did a clean install of Win7 + P3Dv2.5+ Hotfix at the weekend and plain sailing until this afternoon when I installed one and only addon so far ... FSDT PHNL and I get the crash ...

[rdtv91]

I can also confirm I am receiving a CTD with Stackhash error ONLY when installing addon manager with GSX, uninstalling GSX and Addon Manager results in no crashes.

[SN737]

Hi Umberto

I've installed P3D v2.5 hotfix and the latest FSDT addon manager too, I'm getting CTD's StackHash_0a9e error like crazy.
I've un-installed all my FSDT and FlightBeam addons and could complete a 90min flight without any sort of CTD's.

So for me the latest FSDT update that works with P3D's hotfix, causes CTD, StackHash_0a9e module error, almost every time I open the sim.

Regards

I'd like to add, that I also have Estonia Migration Tool, the latest version installed (but disabled). May be the culprit may be not.

[Ifikratis]

Hello,

I am also seeing the same thing...CTDs during the first minutes of flight or even before it (when selecting an aircraft). That after installing the latest hotfix and running the Addon Manager downloaded from the website of GSX to update the files for the hotfix.

Event Viewer gives me the following errors:

--------------------------------------------------------------------------
Fault bucket 879237685, type 17
Event Name: APPCRASH
Response: Not available
Cab Id: 0
 
Problem signature:
P1: Prepar3D.exe
P2: 2.5.12943.0
P3: 54e39da6
P4: StackHash_0a9e
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: ff990016
P9:
P10:
 
Attached files:
C:\Users\Ifikratis\AppData\Local\Temp\WERCEB4.tmp.WERInternalMetadata.xml
 
These files may be available here:
C:\Users\Ifikratis\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_a69d25d74b7150d28477689826a0c361ac93896d_1f8bfdcf
 
Analysis symbol:
Rechecking for solution: 0
Report Id: a63cd2b7-bc4b-11e4-b3a0-902b34da42e2
Report Status: 0
----------------------------------------------------------------------------
Faulting application name: Prepar3D.exe, version: 2.5.12943.0, time stamp: 0x54e39da6
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xff9e0016
Faulting process id: 0x1e0
Faulting application start time: 0x01d05050280095cd
Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: unknown
Report Id: baebee68-bc47-11e4-b3a0-902b34da42e2
----------------------------------------------------------------------------
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 FF9E0016
----------------------------------------------------------------------------


Any help would be really appreciated.

[Dazzlercee]

Me too, same error following install of FSDT / Addon Manager.

Daz

[virtuali]

I can also confirm I am receiving a CTD with Stackhash error ONLY when installing addon manager with GSX, uninstalling GSX and Addon Manager results in no crashes

As I've said, there's something strange about this, because I can see errors (which you can't see, if you don't run P3D under a debugger) even WITHOUT the Addon Manager loaded, and they happens only with the Hotfix.

The only theory I have, is those errors that happens even without the Addon Manager loaded, will become more serious when the Addon Manager is loaded, so they appear as proper errors with a crash, but they might be the original cause of the problem.

As I've said, the Addon Manager is unchanged, except for allowing to run with the Hotfix, because nothing of the things that needs to be updated has actually changed so, if there was an issue with the Addon Manager, it should have happened with plain 2.5 too, while all these reports are coming only after the Hotfix.

The issue is, I also get crashes with the Addon Manager loaded, but they are entirely random. Once I can run with no issue for quite a while, the next I get a crash within a minute. Perhaps there's some kind of conflict between VC++ libraries, but I just can't trace it to anything.

Again, the case is NOT considered closed or solved, it's just that right now I don't have any idea, other than the Hotfix doesn't seem to be very stable.

[Dazzlercee]

Once all airports have been activated via the Addon Manager will they still work if the Addon Manager is uninstalled to prevent the crashing?

Thanks,

Daz

[speedbird217]

As I've said, the Addon Manager is unchanged, except for allowing to run with the Hotfix, because nothing of the things that needs to be updated has actually changed so, if there was an issue with the Addon Manager, it should have happened with plain 2.5 too, while all these reports are coming only after the Hotfix.

Again, the case is NOT considered closed or solved, it's just that right now I don't have any idea, other than the Hotfix doesn't seem to be very stable.

The problem occurs even without the Hotfix. As I mentioned before, I had everything working in P3D 2.5 (No Hotfix). All I did was install your updated Addon Manager and the P3D 2.5 immediately started with the CTDs. No Hotfix involved. So there must have been something in the update you released for the Hotfix that causes this. P3D 2.5 No Hotfix + previous Addon Manager = no problems, P3D 2.5 No Hotfix + current Addon Manager = CTDs all the time.

I hope this can be resolved soon. Is LM aware of your findings regarding the errors in their program?

[virtuali]

Once all airports have been activated via the Addon Manager will they still work if the Addon Manager is uninstalled to prevent the crashing?

As explained, many times already, the Addon Manager is not needed "just" for the activation management, which is less than 1% of its features.

Both the Addon Manager and the Couatl programs are needed by all our products, because the *create* most of the scenery. In fact, if you don't run them, the scenery won't work even in Trial so, it's more or less like FSUIPC: if it cannot be loaded for any reason, lots of products won't work, regardless of their registration status.

[virtuali]

I hope this can be resolved soon. Is LM aware of your findings regarding the errors in their program?

I would like to find a more clear way to display such errors, because running P3D under the VS debugger is not how it's supposed to be used, it's even possible the debugger itself is causing this, so I would like to be sure, before reporting it.

So there must have been something in the update you released for the Hotfix that causes this

I agree that it SEEMS logical. But, again, since none of the memory locations we need to check has changed in the Hotfix, I really can't explain how this line:


if( ( build == 12942 ) || ( build == 12943 ))
{
  // go on loading
}

could cause a problem, while this one wouldn't:


if( build == 12942 )
{
  // go on loading
}


That's all that has changed in the latest build. So, the only possible explanation, if this is happening without the Hotfix installed, is that even the previous version was already unstable and nobody noticed it, because the same code it's running.

[speedbird217]

Thanks for the update Umberto.

I completely understand your frustration.

Is there any way of installing the last build (of your Addon Manager) before the update of your Addon Manager again? It would be interesting to see if I could install that and run it without CTDs again, as I did previously in 2.5 for over a week on many flights. Might also help in narrowing down on why this is happening?

[Dazzlercee]

Disabling the Addon Manager in dll.xml also stops the crashes but obviously also disables all of the FSDT addons.

Daz