PMDG P3D v3 crash after few hours

[downscc]

I agree with your suspicion.

Just finished a 4 hr trip KSFO-KORD no crash.
Default config plus all my scenery and ASN. Blocked couatl, raas, fsuipc and vistamare from loading.

Next trip will be with vistamare just to check that as a strong possibility, but it will be morning. 2330z is end of day for me here in So Texas where it is 1830L and time for my daily walk.

I would very much like to be able to point to vistamare. We'll see.

[gerard2101]

ok Dan , have a nice evening..

[gerard2101]

update 0245 z

Just completed my flight KIAH EHAM with P3D + PMDG 777 and ASN , without OPUS....no problems,
since i m not running OPUS for the cameras anymore i didn't had a CTD...

Tomorrow adding some FSD scenery wich adds QUATL...

[jffry0112]

Morning guys,

Again a ctd. Did a flight from edfh-fsia and when i'm waked up my p3d was crashed.
No errors log from P3D only from ezdok.
it can be that this error switched off ezdok (my camera's were not responding on the shortcurts from my 2nd keyboard)
but it's strange that this can do a ctd.

here the error log.


Foutbucket 73911474704, type 1
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: EZCA.exe
P2: 1.1.8.6
P3: 2a425e19
P4: StackHash_4ff2
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: PCH_86_FROM_ntdll+0x0006919C
P9:
P10:

Toegevoegde bestanden:

Deze bestanden zijn mogelijk hier beschikbaar:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_EZCA.exe_91f22732ebbe65dc177e47f7dfcaa4ef7682266_7bb12d02_2178cd40

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: 14addedf-f819-4b01-b63b-fe93a3df70f7
Rapportstatus: 0
Opgedeelde bucket: 97e5ecd4c8e5501f0970f4e04f94e463

[gerard2101]

Hi , i suspect that it is your ezdoc what s causing your crash , just read an topic that ezdoc isn't compattible yet , so rerun ezdoc config so that you get your original panel files back uninstall ezdoc and try to run p3d only without ezdoc , check that there are no ezdoc entry s anymore in the p3d dll

[gerard2101]

HI,

just after 3 hours in flight i had a crash with the same error...addons installed where pmdg 777 fb kiah , flytampa loww and asn..

Gérard

[speedbird1]

Not addressed at anyone. Just wanted to chime in

I think some guys are taking the wrong approach in troubleshooting this.

As Beau suggested, first try running P3D Vanilla for hours with any default aircraft. Not a single add-on. Nothing in "exe.xml" or "dll.xml", and no flight over third party custom scenery.

When you have established P3D V3 is stable for you, start adding one thing at a time.

Since the affected users appear to be using PMDG 777, load that aircraft, and that one only.

Perform a few long haul flights and see what happens.

If thinks are OK, add one and only one other add-on....

Then repeat the testing process.

Let's not forget that P3D V3 was only released within the last 2 weeks and it's not right to assume that add-ons are fuly compatible just because they used to in V2.5

For instance, we found out our own interface to the P3D ATC system was broken (it used to work with V2.5), until we fixed it via a new version posted yesterday.

[gerard2101]

Hi speedbird ,

I allready went that way ,

reinstalled p3dv3 let it run for hours , reinstalled pmdg777 let it sit on the runway for hours , with engines running , fully configured for take off ,no problems , continue after hours with taking off and flying KIAH EHAM ..no problems , reinstalled ASN yesterday and again let it sit on the runway for hours , with engines running , fully configured for take off ,no problems , continue after hours with taking off and flying KIAH EHAM with a holding for hours over LAMSO ..no problems , my p3d was running over 24 hours in total with the pmdg ..

For testing i used everytime the same flight KIAH EHAM , dafault settings , default scenery , the first flights crashed and the last 2 without any problems .

This morning left KIAD for LOWW and 3.15 in flight i tried to enlarge the screen and the error returned ...

[Jeeveegee]

Hey everybody,

Just want to let you guys know I've had the same MSVCR120.dll error as well on a flight this week. Sim had been running for over 3 hours. Flight was with the PMDG 737NGX. Had a bunch of addons installed so it's hard to tell what might have caused it, but from what I've read on here it seems to me everyone has been using a PMDG plane while experiencing the CTD so perhaps it's time to look into that?

I'm gonna try and see if the CTD might occur in another plane, I'll keep you guys updated.

[RVxSpeed]

update: this time only pmdg 777 & 777 immersion.
crash without even touching anything.

[gerard2101]

Hi Dan ,

the error returned a few hours ago...it seems everyone who is having this error is having one thing in common....pmdg...

if the flight wich i m doing right now crashes again , i m going to fly with only the 777 installed , wich i allready did a few times without problems ,

Gérard

[downscc]

I've run the vanilla flight using default prepar3d.cfg and scenery.cfg and all modules in dll.xml and exe.xml turned off except for PMDG. No CTD with only PMDG.

I am currently running trials that don't crash adding one thing back at a time until it crashes. Hope this approach works.

So far I can run a crash free trial with PMDG, all my scenery an and ASN. Excluded are couatl, bglmanx, raas, fsuipc and vistamare. Prepare3D.cfg is default except I have to set HDR and FXAA off of course.

My current trail adds vistamare, but I noticed that the dll has a log file ViMaCoreLog.txt that says ViMaCore stopped due to incompatible FS X. So this will probably be a boring trial. I'll let it run regardless.

[gerard2101]

Last flight went without problems , total duration 8.33 hours. installed only vanilla p3d with pmdg 777 , raas excluded in the dll... default p3d cfg, default settings ...only fxaa off , msa 4 in game , vsynch tripple buf on .

next flight going to install ASN again but it will be for tomorrow , going to bed now

[RVxSpeed]

those who are having crash free trial can u guys pls post the .dll screenshot.

[gerard2101]

Hi,
just took off KIAD heading LIRF , instead of installing ASN i decided to install one scenery ...LIRF, so that QUATl from Flightbeam KIAD didn't get loaded .

I m beginning to think that something dynamic is causing the error, and not a scenery or something...when reading the different posts the error occured in all different stages , but all have one common ,,they are all in flight after some time..i think when it is caused by a scenery the error comes when a scenery gets loaded , while departing or arriving .

Yesterday i had only 2 scenerys installed and activated KIAD and LOWW and the error occured after 3.15 hours when cruising above the atlantic., with my little knowledge about errors i m beginning to think this way , so correct me please if i m wrong ...

ASN on the other hand dynamically updates the weather from time to time ,maybe sometimes this triggers the error ..

Continue testing ..


Gérard