PMDG P3D v3 crash after few hours

[RVxSpeed]

Hi all,

A few weeks ago i replaced my MSI GTX980 Gaming 4G with a GTX980Ti Gaming 6G and since then never had a CTD anymore , left Friday EHAM for KIAD , about 9 hours flying time , 2 hours later departed KIAD for OMDB , 1230 flying time, and after 1 hour departed OMDB for KSEA , 1341 flying time and right now i am at the JAWBN star into KSEA , this is all without shutting down or restarting P3D since Friday afternoon , just tried to enlarge the PFD or ND and absolutely no problems .

The only thing i changed is upgrading to a GTX980Ti , reinstalled the driver (wich i also did previously with my GTX9800 ) and 4 K television and upp the resolution to 3840 UHD , running P3D with the NCP settings provided at Rob's page , P3D settings maxed out , clouds 1 step out of max .

Why upgrading from a GTX980 to a GTX980Ti solved it for me i don't know , a GTX980 is absolutely no light card either .


Best regards ,

Gérard

wow.joke aside.so,the verdict that u two are on right now that whoever is using anything lower than GTX 980 should upgrade their cards to just get rid a of a CTD which occurs 8hrs + long haul :P
very very interesting theory.

[FRAX]

Is anyone of you using FS2Crew and has installed the English UK Voice Pack for windows in order to use voice recognition on a german OS?

[espresso]

I just think that everyone having these problems is quite desperate and we are letting everyone know what we did to make the problem go away.
The support coming from LM and PMDG is rather disappointing so far...
A solution is yet to be found.

[RVxSpeed]

I just think that everyone having these problems is quite desperate and we are letting everyone know what we did to make the problem go away.
The support coming from LM and PMDG is rather disappointing so far...
A solution is yet to be found.

agree

[gerard2101]

Hi ,

i don't say that everyone should be upgrading there videocard to al least a GTX980 , i know there are a lot of uses who don't have a problem with other graphic cards than a 980 , just saying in my case it solved my problems, the problem is why only a few of us are having these problems and why they went away after upgrading our videocard only , while i had a lot of problems while running a gtx980 , a gtx980 is allready a high power card , maybe it is related to a combination of hardware , drivers chipsets or whatever , like Dan said

LM and PMDG tested this also but could not reproduce this error , a lot of users don't get this error and everyone says you should do this or you should that and believe me , we tried it all , again and again without a solution. .

I had a standard flight , KIAD LOWW wich i flown a lot of times , startingfrom a completely vanilla P3D , all default settings , with nothing else installed than the 777 , it crashed but only after 8-8.30 hours and only in air.I could let the plane standing at the gate for 2 days , in take off config with engines running , no probs , clicking everywhere .
In flight after 8 hours it crashed when clicking the left pfd , and when i increased the P3D settings it crashed earlyer in flight, sometimes when doing nothing at all ,
We tested this with and without all the different addons , reinstalled P3D and even reinstalled Windows7 several times , nothing worked , and the error for us was reproducable .

I hope someday we get to know what was causing this but if LM or PMDG even doesn't know what is causing this ...

Best regards ,

[downscc]

After 11 flights I finally ran into a CTD of same type, event code, offset etc., as all others using the GTX980Ti and HT off.

I assume the increase in video memory from the 2G GTX750Ti to the 6G GTX980Ti doesn't eliminate the error, it just makes it less likely. Other info: Using Win7 P3Dv3.1 and an i7-4790K with 16G RAM.

The scenario was a PMDG NGX from FSDT PHNL to T2G KSEA with Orbx PNW, VAS remaining at time of event was over 1G. Block time was 5.1 hrs from pushback. Left DU PFD was used on departure and the event happened when I clicked on the L DU PFD at the IAF for the approach.

IMHO this points a big ugly finger at the way LM has moved work to the GPU. Maybe others don't see it because they aren't retired and use P3D almost 8 hr/day.

AppCrashView:
Version=1
EventType=APPCRASH
EventTime=130975426195407993
ReportType=2
Consent=1
UploadTime=130975426195838017
ReportIdentifier=06551d5b-bd68-11e5-826c-448a5b9db06e
IntegratorReportIdentifier=06551d5a-bd68-11e5-826c-448a5b9db06e
WOW64=1
Response.BucketId=465456676
Response.BucketTable=25
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.1.2.15831
Sig[2].Name=Application Timestamp
Sig[2].Value=5672b60a
Sig[3].Name=Fault Module Name
Sig[3].Value=MSVCR120.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=12.0.21005.1
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=524f7ce6
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000ee2c
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033

Well this is both disheartening and comforting, at least the illogic of updating video card has been resolved.

[sgreen91]

I'm not sure Dan. A new system with a fresh W10 install. I also use now a 980Ti. Just had the CTD again with the MSVR120.dll error.

Im using a 6700k with 16g memory and a 980ti. First time in about 10 flights since I built the system that the error has occured. I was hopeful it was just the video card but for me its not the solution.

Back to square one. No more touching the PFD I suppose.

Sean

[RVxSpeed]

After 11 flights I finally ran into a CTD of same type, event code, offset etc., as all others using the GTX980Ti and HT off.

I assume the increase in video memory from the 2G GTX750Ti to the 6G GTX980Ti doesn't eliminate the error, it just makes it less likely. Other info: Using Win7 P3Dv3.1 and an i7-4790K with 16G RAM.

The scenario was a PMDG NGX from FSDT PHNL to T2G KSEA with Orbx PNW, VAS remaining at time of event was over 1G. Block time was 5.1 hrs from pushback. Left DU PFD was used on departure and the event happened when I clicked on the L DU PFD at the IAF for the approach.

IMHO this points a big ugly finger at the way LM has moved work to the GPU. Maybe others don't see it because they aren't retired and use P3D almost 8 hr/day.

AppCrashView:
Version=1
EventType=APPCRASH
EventTime=130975426195407993
ReportType=2
Consent=1
UploadTime=130975426195838017
ReportIdentifier=06551d5b-bd68-11e5-826c-448a5b9db06e
IntegratorReportIdentifier=06551d5a-bd68-11e5-826c-448a5b9db06e
WOW64=1
Response.BucketId=465456676
Response.BucketTable=25
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.1.2.15831
Sig[2].Name=Application Timestamp
Sig[2].Value=5672b60a
Sig[3].Name=Fault Module Name
Sig[3].Value=MSVCR120.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=12.0.21005.1
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=524f7ce6
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000ee2c
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033

Well this is both disheartening and comforting, at least the illogic of updating video card has been resolved.

well we all don't have to upgrade our GPU then :D.
now that is a relief.

[RVxSpeed]

& to everyone.i already said i don't why i am not getting the error anymore :P since i don't enlarge the display anymore & come on for real it's not even realistic.
& btw i think everyone should try the below settings it's awesome:
https://www.youtube.com/watch?v=0grEYUv6bJ4

[HondaJet]

I would like to add to this thread hoping LM will fix our issue very soon. I am also flying the PMDG NGX and just finished a 6.1 hours flight. I did not have any tweaks in my cfg file and I turned off the Hyper-threading in my BIOS before this flight.
I intentionally did not use the 2D panels the entire flight but once I landed and was on the taxiway I clicked on the PFD and presto the crash happened (looks like the rest of the screenshots shown here). Faulting module name: MSVCR120.dll; Faulting Application name: Prepar3D.exe. My version is 3.1.

So the idea that turning off Hyper-threading and having no Affinity Mask in the cfg did NOT do the trick on my computer. If it helps to know, I have a dedicated PC for P3D and my ASN, EFB and other support programs run via network on my client laptop - both running Win7.

Also ASN was off at the time of this crash.

[Gazguzzler]

Hi ,

i don't say that everyone should be upgrading there videocard to al least a GTX980 , i know there are a lot of uses who don't have a problem with other graphic cards than a 980 , just saying in my case it solved my problems, the problem is why only a few of us are having these problems and why they went away after upgrading our videocard only , while i had a lot of problems while running a gtx980 , a gtx980 is allready a high power card , maybe it is related to a combination of hardware , drivers chipsets or whatever , like Dan said

LM and PMDG tested this also but could not reproduce this error , a lot of users don't get this error and everyone says you should do this or you should that and believe me , we tried it all , again and again without a solution. .

I had a standard flight , KIAD LOWW wich i flown a lot of times , startingfrom a completely vanilla P3D , all default settings , with nothing else installed than the 777 , it crashed but only after 8-8.30 hours and only in air.I could let the plane standing at the gate for 2 days , in take off config with engines running , no probs , clicking everywhere .
In flight after 8 hours it crashed when clicking the left pfd , and when i increased the P3D settings it crashed earlyer in flight, sometimes when doing nothing at all ,
We tested this with and without all the different addons , reinstalled P3D and even reinstalled Windows7 several times , nothing worked , and the error for us was reproducable .

I hope someday we get to know what was causing this but if LM or PMDG even doesn't know what is causing this ...

Best regards ,

Hi Gerard, hi All,

Been flying for a long time now without any CTD, even upgraded to Win10 and P3Dv3.1 Then tonight during a 8-hr flight in the T7 I decided to enlarge the LH PFD and hay presto, CTD. :-)

I'm smiling because I have auto-save set-up in FUSIPC and just reloaded the flight. I am using two Titan Black's so I really don't think it's the graphics cards Gerard.

Regards
Gary

[gerard2101]

Hi Gary , hoping you re doing allright ..

I don't think it s the graphic card either , as i said the GTX980 is a heavy card either but just don't understand why it solved my problems , last weekend my p3d was running over 48 hours without restarting , made 4 long flights without shutting down p3d or restarting my pc and did not have a problem at all , just don't understand it .

Normally i don't touch the left PFD anymore ( have a 40 inch screen ) but for testing tried this my last flight without problems .

What i still do after installing a scenery addon , ASN or reinstalling PMDG is uninstall my C++ 2010 , 2012 and 2013 , 86 and 64 , and reinstall them after any addon in installed , so that i m running the latest MS files , I don't install C++2015 .

Best regards,

Gérard

[germanygreece93]

No, but i received this message from PMDG

Alexander,

I would very carefully check your system configuration for stability. Kernelbase.dll is one of the core Windows system files (the "kernel" is the fundamental code in an OS) - there's no way it's the airplane directly causing that crash, it isn't possible for programs run by the user to crash a kernel file.

[Chris0007]

If it's only happening with the one PMDG aircraft, then it's most likely an issue with that aircraft.

According to PMDG it isn't. I contacted their support and this is what they said.
"We're still waiting for help from Lockheed Martin on this - we don't think this is something we're causing because we don't even compile against the 2013 version of Visual C++ (which is what MSVCR120.dll is - we use 2010, which is MSVCR100.dll) - P3D 3.x itself *is* compiled against that version though and since our code doesn't call anything in the 120 version, the crash has to be coming from P3D itself somehow, likely down the line a bunch of function calls from something the 777 does. We can't possibly debug it without LM's help because we obviously don't have P3D's source code."

[Chris0007]

Has the issue been solved? I am having this problem too, tried numerous times to do a flight from KLAX-YSSY in the PMDG 777 but it crashes every time and when I contacted PMDG support they told me this:
"We're still waiting for help from Lockheed Martin on this - we don't think this is something we're causing because we don't even compile against the 2013 version of Visual C++ (which is what MSVCR120.dll is - we use 2010, which is MSVCR100.dll) - P3D 3.x itself *is* compiled against that version though and since our code doesn't call anything in the 120 version, the crash has to be coming from P3D itself somehow, likely down the line a bunch of function calls from something the 777 does. We can't possibly debug it without LM's help because we obviously don't have P3D's source code."
-Chris