General Category > General Discussion
Couatl crashing P3Dv3.3.5
Emi:
I'm afraid there is no default aircraft in P3Dv3 that has a range long enough to replicate my crashes.
I'd need something with a range of about 5000NM. Since they took out the default 747 from FSX there is no such aircraft to do this kind of check. In fact there is no airliner at all.
Would you have a suggestion for one that works?
Emi:
Alright, I did a LOT more flights now.
25 flights and about 100 hours without issues, then I reinstalled GSX and it started crashing again.
Steps for you to reproduce: Install: Prepar3Dv3, GSX, PMDG's Queen of the Skies II.
Under these conditions I can, reliably, reproduce the crash.
VAS usage when the crash happened: 2.7GB.
And here's the OFP of the flight in which the crash occured:
https://www.dropbox.com/s/njkegaaqry3klme/ICNFRA.pdf?dl=0
Here's the latest crashlog:
Problemsignatur
Problemereignisame: APPCRASH
Anwendungsname: Prepar3D.exe
Anwendungsversion: 3.3.5.17625
Anwendungszeitstempel: 5758bb31
Fehlermodulname: StackHash_ae77
Fehlermodulversion: 10.0.14393.479
Fehlermodulzeitstempel: 58256ca0
Ausnahmecode: c0000374
Ausnahmeoffset: PCH_B3_FROM_ntdll+0x0006EB8C
Betriebsystemversion: 10.0.14393.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: ae77
Zusatzinformation 2: ae77539f15c6852208019c600e73c756
Zusatzinformation 3: 0e7d
Zusatzinformation 4: 0e7d18310c1b982de385a59184b5c8c6
virtuali:
--- Quote from: Emi on March 19, 2017, 07:20:01 pm ---Steps for you to reproduce: Install: Prepar3Dv3, GSX, PMDG's Queen of the Skies II.
--- End quote ---
Are you saying that it would be enough to "install" ONLY these 3 Addons, and remove EVERYTHING ELSE, and it will crash immediately, without doing anything ?
I'm asking, because that's what your reproduction steps seems to indicate. And of course, I already tell you it doesn't happen, because I already have all of them installed, and they work normally.
--- Quote ---Problemsignatur
Problemereignisame: APPCRASH
Anwendungsname: Prepar3D.exe
Anwendungsversion: 3.3.5.17625
Anwendungszeitstempel: 5758bb31
Fehlermodulname: StackHash_ae77
Fehlermodulversion: 10.0.14393.479
Fehlermodulzeitstempel: 58256ca0
Ausnahmecode: c0000374
Ausnahmeoffset: PCH_B3_FROM_ntdll+0x0006EB8C
Betriebsystemversion: 10.0.14393.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: ae77
Zusatzinformation 2: ae77539f15c6852208019c600e73c756
Zusatzinformation 3: 0e7d
Zusatzinformation 4: 0e7d18310c1b982de385a59184b5c8c6
--- End quote ---
I'm sorry, but nothing in that log shows the problem is caused by GSX. And you don't say if you did what I asked to do, which is DISABLE everything *except* the Addon Manager.
And, it would be best if you used the current P3D version (3.4.22.19868 Hotfix 3), because I would have an hard time even trying to reproduce something on a non-current version of the sim.
ColoniaAir:
Same Problems here (with the newest P3D Version)
My story:
During longhaul flights with the PMDG 777 at 3-6 hours flighttime I got a CTD (over Greenland or Canada), Error log shows ntdll.dll, this started some months ago. So I format my hd and reinstalled P3D.
With a clean P3D only with the 747 v3 and the 777 from PMDG there were 21 flights without an problem. After installing Addon Manager, my FSDT Addons (almost all Airports and GSX), problem was there again.
This was the time I found in some forums that this problem could be from couatl. So I formated again and rebuild P3D without FSDT Addons and had no problems with 17 flights. But after some weeks it was boring, longhaul flights to the US with default airports and I tried it again with FSDT Addons and the error was back again.
It's totally frustrating! I hope there would be a fix soon. I am willing to help :)
virtuali:
--- Quote from: ColoniaAir on April 08, 2017, 04:25:53 pm ---This was the time I found in some forums that this problem could be from couatl.
--- End quote ---
It's not possible that what you read in "some forums" is true, since Couatl, being an external .EXE, CANNOT crash the sim, period.
It's POSSIBLE that a problem in your sim installation can cause a crash with the Addon Manager instead, without this being an "Addon Manager" fault.
We discovered a potential weakness in it which, again, it's NOT the "Addon Manager fault's" but, sorry to say, it relates to some files in the sim which were replaced, so the sim has a version mismatching, and the Addon Manager requires to know exactly the precise version and no P3D file must be altered from the original installation, otherwise a couple of memory locations that needs to be accessed (to get data not available with Simconnect), will not be in the proper place anymore.
First, is there a reason why you are not using the current P3D V3, which is 3.4.22 ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version