Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: Prepar3D.exe
Anwendungsversion: 4.5.14.34698
Anwendungszeitstempel: 5e94b5c2
Fehlermodulname: terrain.dll
Fehlermodulversion: 4.5.14.34698
Fehlermodulzeitstempel: 5e94b52d
Ausnahmecode: c0000005
Ausnahmeoffset: 0000000000031535
Betriebsystemversion: 6.3.9600.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 0c09
Zusatzinformation 2: 0c094349ffe81a1960f281db369c5fca
Zusatzinformation 3: 1684
Zusatzinformation 4: 1684548929caa07d87c93fdcd69ef093
"unknown software exception"
when lowering the flaps, looking around, or even directly after starting the application.
The A2A P40 works fine, the A2A C182 too. For hours. No crash at all.
But the P51 !!! Horrible !!!! Sometimes after Minutes, sometimes immediately after running P3D and running the flightsituation for the first time or after changing the airplane to the P51 after using another airplane.
The situations are very different.
P3Dv4 latest Version
Windows 8.1 PRO
Core i7, 8700K CPU @ 3.70GHz
MSI Z370 PC PRO, Mainboard
Samsung 960 EVO 250 GB, Solid State Drive
G.Skill DIMM 16GB DDR4-3000 Kit, Arbeitsspeicher
Is there someone who can help me before I go down with all hands?
Thanks a lot for every competent help and answere.
P51 APPCRASH on and on and on
- Nick - A2A
- A2A Captain
- Posts: 13805
- Joined: 06 Jun 2014, 13:06
- Location: UK
Re: P51 APPCRASH on and on and on
Hello,
Sorry to hear you're having some problems. Is it always the "terrain.dll" which is mentioned as the crashing module? This isn't part of the P-51 installation, but please can you confirm if you're using the military version of the P-51, or the civilian version with the GPS. If it's the latter, please can you let us know which GPS you're using?
However, as a general rule, if you're experiencing a CTD in P3D, the first thing I'd recommend when troubleshooting is reverting the sim to its default settings. To do this, you can simply rename the Prepar3D.cfg which will cause the sim to generate a new copy next time you run it.
Thanks,
Nick
Sorry to hear you're having some problems. Is it always the "terrain.dll" which is mentioned as the crashing module? This isn't part of the P-51 installation, but please can you confirm if you're using the military version of the P-51, or the civilian version with the GPS. If it's the latter, please can you let us know which GPS you're using?
However, as a general rule, if you're experiencing a CTD in P3D, the first thing I'd recommend when troubleshooting is reverting the sim to its default settings. To do this, you can simply rename the Prepar3D.cfg which will cause the sim to generate a new copy next time you run it.
Thanks,
Nick
A2A Simulations Inc.
-
- Airman Basic
- Posts: 4
- Joined: 03 May 2021, 01:17
Re: P51 APPCRASH on and on and on
04.05.2021 with Photoreal Groundscenery
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: Prepar3D.exe
Anwendungsversion: 4.5.14.34698
Anwendungszeitstempel: 5e94b5c2
Fehlermodulname: terrain.dll
Fehlermodulversion: 4.5.14.34698
Fehlermodulzeitstempel: 5e94b52d
Ausnahmecode: c0000094
Ausnahmeoffset: 0000000000038528
Betriebsystemversion: 6.3.9600.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 6669
Zusatzinformation 2: 66690ff761113994d1803157cd3fbd6e
Zusatzinformation 3: 5891
Zusatzinformation 4: 58915209c8514c7967dfdfd52ee7
and another time:
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: Prepar3D.exe
Anwendungsversion: 4.5.14.34698
Anwendungszeitstempel: 5e94b5c2
Fehlermodulname: terrain.dll
Fehlermodulversion: 4.5.14.34698
Fehlermodulzeitstempel: 5e94b52d
Ausnahmecode: c0000094
Ausnahmeoffset: 0000000000038528
Betriebsystemversion: 6.3.9600.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 45d4
Zusatzinformation 2: 45d4cb98e32fb7d9817d67b9462a733e
Zusatzinformation 3: 81ed
Zusatzinformation 4: 81ed1298df7753549c39d167fc7573d7
without Photoreal Groundscenery and new P3D.cfg
Options:
Display: no changes
World: Terrain and scnery Objects were set to higher values
Lighting: Shadow: Casting and no receiving: Buildings
I started for another time. But then the next CTD:
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: Prepar3D.exe
Anwendungsversion: 4.5.14.34698
Anwendungszeitstempel: 5e94b5c2
Fehlermodulname: terrain.dll
Fehlermodulversion: 4.5.14.34698
Fehlermodulzeitstempel: 5e94b52d
Ausnahmecode: c0000005
Ausnahmeoffset: 0000000000037ef4
Betriebsystemversion: 6.3.9600.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 0c09
Zusatzinformation 2: 0c094349ffe81a1960f281db369c5fca
Zusatzinformation 3: e048
Zusatzinformation 4: e04896fdd3d1d5caf1da4102b93672ec
--------------------------------------------
Hello Nick,
thank you very much for your very quick answere.
I checked some things i.e. the new Prepar3d.cfg by deleting the old one as suggested from you.
I set some key assignments and like mentioned above, some settings in: World and Lightning.
But there is no significant changing notable exept that I could fly for some minutes when the next CTD occurred.
In conclusion I can say, that only one change can take effect in solving the problem: Not using the A2A P51
Please note: The A2A P40 and the A2A C182 are working very fine and reliable.
A wonderful simulation experience for hours. And no Carenado product makes the same problems.
But only the A2A P51 leads to the CTD's regarding the P3D-terrain.dll.
So, what can we do to solve the problem also in favour of surely some other disappointed purchasers of the A2A P51.
I would appreciate some other possible solutions. Thanks a lot for your kind help and answere.
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: Prepar3D.exe
Anwendungsversion: 4.5.14.34698
Anwendungszeitstempel: 5e94b5c2
Fehlermodulname: terrain.dll
Fehlermodulversion: 4.5.14.34698
Fehlermodulzeitstempel: 5e94b52d
Ausnahmecode: c0000094
Ausnahmeoffset: 0000000000038528
Betriebsystemversion: 6.3.9600.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 6669
Zusatzinformation 2: 66690ff761113994d1803157cd3fbd6e
Zusatzinformation 3: 5891
Zusatzinformation 4: 58915209c8514c7967dfdfd52ee7
and another time:
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: Prepar3D.exe
Anwendungsversion: 4.5.14.34698
Anwendungszeitstempel: 5e94b5c2
Fehlermodulname: terrain.dll
Fehlermodulversion: 4.5.14.34698
Fehlermodulzeitstempel: 5e94b52d
Ausnahmecode: c0000094
Ausnahmeoffset: 0000000000038528
Betriebsystemversion: 6.3.9600.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 45d4
Zusatzinformation 2: 45d4cb98e32fb7d9817d67b9462a733e
Zusatzinformation 3: 81ed
Zusatzinformation 4: 81ed1298df7753549c39d167fc7573d7
without Photoreal Groundscenery and new P3D.cfg
Options:
Display: no changes
World: Terrain and scnery Objects were set to higher values
Lighting: Shadow: Casting and no receiving: Buildings
I started for another time. But then the next CTD:
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: Prepar3D.exe
Anwendungsversion: 4.5.14.34698
Anwendungszeitstempel: 5e94b5c2
Fehlermodulname: terrain.dll
Fehlermodulversion: 4.5.14.34698
Fehlermodulzeitstempel: 5e94b52d
Ausnahmecode: c0000005
Ausnahmeoffset: 0000000000037ef4
Betriebsystemversion: 6.3.9600.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 0c09
Zusatzinformation 2: 0c094349ffe81a1960f281db369c5fca
Zusatzinformation 3: e048
Zusatzinformation 4: e04896fdd3d1d5caf1da4102b93672ec
--------------------------------------------
Hello Nick,
thank you very much for your very quick answere.
I checked some things i.e. the new Prepar3d.cfg by deleting the old one as suggested from you.
I set some key assignments and like mentioned above, some settings in: World and Lightning.
But there is no significant changing notable exept that I could fly for some minutes when the next CTD occurred.
In conclusion I can say, that only one change can take effect in solving the problem: Not using the A2A P51
Please note: The A2A P40 and the A2A C182 are working very fine and reliable.
A wonderful simulation experience for hours. And no Carenado product makes the same problems.
But only the A2A P51 leads to the CTD's regarding the P3D-terrain.dll.
So, what can we do to solve the problem also in favour of surely some other disappointed purchasers of the A2A P51.
I would appreciate some other possible solutions. Thanks a lot for your kind help and answere.
-
- Airman Basic
- Posts: 4
- Joined: 03 May 2021, 01:17
Re: P51 APPCRASH on and on and on
...in addition:
I use the civilian model with the default-GPS. By the hand: I am not able to change the GPS with the Aircraft Configurator. Not even to the reality xp GNS430.
Greetings
Chris
I use the civilian model with the default-GPS. By the hand: I am not able to change the GPS with the Aircraft Configurator. Not even to the reality xp GNS430.
Greetings
Chris
- Nick - A2A
- A2A Captain
- Posts: 13805
- Joined: 06 Jun 2014, 13:06
- Location: UK
Re: P51 APPCRASH on and on and on
Thanks for the additional info Chris.
This terrain.dll appcrash certainly isn't something we've seen regularly associated with the P-51 or any other A2A add-ons for that matter. As a quick troubleshooting step, something you can try is deleting the saved log.dat files for the P-51 in case these have become corrupted at some point in the past. To do this, please manually delete the "Documents\A2A\FSX\P51civ" folder.
When you say you are "not able to change the GPS with the Aircraft Configurator" please can you clarify what you mean? Are you seeing an error message, or do you just mean that the other GPS gauges don't actually work in the cockpit? This would be normal if you don't have the third-party GPS modules is question installed (i.e. RealityXP and FLight1).
Regards,
Nick
This terrain.dll appcrash certainly isn't something we've seen regularly associated with the P-51 or any other A2A add-ons for that matter. As a quick troubleshooting step, something you can try is deleting the saved log.dat files for the P-51 in case these have become corrupted at some point in the past. To do this, please manually delete the "Documents\A2A\FSX\P51civ" folder.
When you say you are "not able to change the GPS with the Aircraft Configurator" please can you clarify what you mean? Are you seeing an error message, or do you just mean that the other GPS gauges don't actually work in the cockpit? This would be normal if you don't have the third-party GPS modules is question installed (i.e. RealityXP and FLight1).
Regards,
Nick
A2A Simulations Inc.
-
- Airman Basic
- Posts: 4
- Joined: 03 May 2021, 01:17
Re: P51 APPCRASH on and on and on
Hello Nick,
thank you for your tip with the P51civ-folder. I fully deleted the contained files and now will test if something good happens.
Question: Does the P51 need some certain Windows-Services running? => Services configurated by the msconfig.exe which you can find in: C:/Windows/System32/
Or is something special important when using Windows 8.1 PRO ?
You mention that the problem with the terrain.dll is not quite normal. Because I can not even solve this problem I am interested in grabbing deeper to understand the working of the P51-program within the OS and the Prepar3Dv4.
Thank you very much for helping me investigating the reason.
Regards
Chris
thank you for your tip with the P51civ-folder. I fully deleted the contained files and now will test if something good happens.
Question: Does the P51 need some certain Windows-Services running? => Services configurated by the msconfig.exe which you can find in: C:/Windows/System32/
Or is something special important when using Windows 8.1 PRO ?
You mention that the problem with the terrain.dll is not quite normal. Because I can not even solve this problem I am interested in grabbing deeper to understand the working of the P51-program within the OS and the Prepar3Dv4.
Thank you very much for helping me investigating the reason.
Regards
Chris
Who is online
Users browsing this forum: No registered users and 32 guests