PMDG P3D v3 crash after few hours

[downscc]

Chris, there are a couple of workarounds. The easiest is to simply save and reload the flight every 3-5 hrs if you use the Left Outboard DU (PFD) 2D popup. Also, I found that using the Right (FO) Outboard DU as the 2D popup does not cause the error. I have flown both NGX and 777 sessions using the FO PFD popup without a problem, that's not a guarantee but it's promising. Of course, you can just skip using a 2D PFD popup altogether, but in the 777 without HGS I find that unsatisfactory.

[Chris0007]

Chris, there are a couple of workarounds. The easiest is to simply save and reload the flight every 3-5 hrs if you use the Left Outboard DU (PFD) 2D popup. Also, I found that using the Right (FO) Outboard DU as the 2D popup does not cause the error. I have flown both NGX and 777 sessions using the FO PFD popup without a problem, that's not a guarantee but it's promising. Of course, you can just skip using a 2D PFD popup altogether, but in the 777 without HGS I find that unsatisfactory.

Thanks, do we know if Lockheed are looking into the issue?

[germanygreece93]

I have made now a clean install and made 2 flights with the 777. There must be a problem with Prepar3D, as PMDg says, it has nothing to do with the 777, because I got again 2 kernel.dll error. Is there no solution regarding Lockheed Martin ?

[Chris0007]

Message for P3D Developers:
Is anyone working to fix this issue? As you can see this bug effects quite a few people. If you need any data let us know and I am sure we will be happy to supply.

[sharmes6]

I see there are plenty of users having this same issue. This problem just came up for me the other day. The last three times I have exited P3D V3.1, I get a CTD with the faulting module being MSVCR120.dll in the Windows/system32 folder.

I have no problem with this during flights, and I have entered and exited the menus, changed aircraft, changed airport with no issue. It is just when I click on Exit Prepar3D after pressing Escape I get the CTD.

Not sure why this has just started. I had ORBX SoCal and NorCAl as well as Open LC and Global base installed with no issues. I also had a few Latin VFR and freeware addon airports installed. The past few days I have installed the rest of the ORBX regions and a few aircraft, and now I am having the problem.

Cheers,

[gerard2101]

hi ,

allmost 4 months later since this topic is started and both p3d and pmdg don't acknowledge that there is a problem .PMDG says it s a p3d problem and from p3d we don't get a answer anymore .

In the beginning there were only Dan and myself with this problem but at this moment there are many users with this error ,and it seems that everytime more people are getting this error , posted in both the p3d and pmdg forum , without any answers how to solve this , only workarounds , not even a single response they are still looking in solving this error .

[newtie]

I started getting this error this week on exit...

Mark

[Martyson]

Mark,

Which aircraft were you flying?

You mentioned in a previous post here:
http://www.prepar3d.com/forum/viewtopic ... 96#p123414

"I've set up a dual boot Win7/Win10 to transition over to Win10 permanently.
I set AffinityMask=14 in prepar3d.cfg as I've done on my Win7 original side. Doesn't work inWin10. Task manager shows Core 0 @ 100%."

Could this be causing problems?

[ockwellk]

I also get this problem with the Majestic Dash q400 pro edition in P3d V3.1, after a short flight EGAA to EGCC. Happens in the same place after about 20 mins.

I have ASN, ORBX Global/vector/openlc.

Windows7, 64bit, I5, Nvida GTX560ti2 gig.

[ockwellk]

This is the content of the error log if it helps?

<?xml version="1.0" encoding="UTF-16"?>

-<WERReportMetadata>
-<OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion>
<Build>7601 Service Pack 1</Build>
<Product>(0x1): Windows 7 Ultimate</Product>
<Edition>Ultimate</Edition>
<BuildString>7601.19110.amd64fre.win7sp1_gdr.151230-0600</BuildString>
<Revision>1130</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>

-<ProblemSignatures>
<EventType>APPCRASH</EventType>
<Parameter0>Prepar3D.exe</Parameter0>
<Parameter1>3.1.2.15831</Parameter1>
<Parameter2>5672b60a</Parameter2>
<Parameter3>MSVCR120.dll</Parameter3>
<Parameter4>12.0.21005.1</Parameter4>
<Parameter5>524f7ce6</Parameter5>
<Parameter6>c0000005</Parameter6>
<Parameter7>00011595</Parameter7>
</ProblemSignatures>
-<DynamicSignatures>
<Parameter1>6.1.7601.2.1.0.256.1</Parameter1>
<Parameter2>2057</Parameter2>
<Parameter22>9e27</Parameter22>
<Parameter23>9e2778096e7e1e2a2e0302fe58f3eea8</Parameter23>
<Parameter24>9e27</Parameter24>
<Parameter25>9e2778096e7e1e2a2e0302fe58f3eea8</Parameter25>
</DynamicSignatures>
-<SystemInformation>
<MID>F9C7D205-023B-4534-AE1E-AB68D5F896EB</MID>
<SystemManufacturer>System manufacturer</SystemManufacturer>
<SystemProductName>System Product Name</SystemProductName>
<BIOSVersion>2103</BIOSVersion>
</SystemInformation>
</WERReportMetadata>

[downscc]

Interesting. A non-PMDG related event. I notice the exception code is the same (c0000005) but the exception offset is not one of the two we've seen with the PMDG related events.

Maybe this will help LM trap the error.

Refresh memory: These started with v3.0.

[PGB]

Hi,

i have the same issues doing KLAX - YSSY trying several times. But on my PC P3D stops working meanwhile "silently" without pointing to any vc++ libraries. Between the fixes WOSLU and WACOS (near equador on B581) P3D had stopped working yesterday and the day before.

route:
KLAX ZILLI1 FICKY B581 NN A579 JORDY DCT MARLN MARLN1 YSSY

Even though i have stored older error logs like these, pointing to fsuipc (updated meanwhile) and older nvidia driver.
_____________________________________________________________________________________
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.1.2.15831, Zeitstempel: 0x5672b60a
Name des fehlerhaften Moduls: FSUIPC4.dll_unloaded, Version: 0.0.0.0, Zeitstempel: 0x56792080
Ausnahmecode: 0xc0000005
Fehleroffset: 0x5fc51dee
ID des fehlerhaften Prozesses: 0x13b0
Startzeit der fehlerhaften Anwendung: 0x01d1402c937479bb
Pfad der fehlerhaften Anwendung: D:\P3Dv3\Prepar3D.exe
Pfad des fehlerhaften Moduls: FSUIPC4.dll
Berichtskennung: d9d93936-ac24-11e5-9013-f46d044fceb0
____________________________________________________________________________________
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 5FC51DEE
____________________________________________________________________________________
and
____________________________________________________________________________________
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.1.2.15831, Zeitstempel: 0x5672b60a
Name des fehlerhaften Moduls: nvwgf2um.dll, Version: 10.18.13.6143, Zeitstempel: 0x56717009
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0077b74b
ID des fehlerhaften Prozesses: 0xf1c
Startzeit der fehlerhaften Anwendung: 0x01d14e487c39281b
Pfad der fehlerhaften Anwendung: D:\P3Dv3\Prepar3D.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\nvwgf2um.dll
Berichtskennung: 736faff9-ba3e-11e5-a871-f46d044fceb0
____________________________________________________________________________________

Environment:
Windows 7 64bit; latest P3Dv3.1
Nvidia driver latest 361.75 WHQL /Soundblaster Audigy platinum/ Open AL
I5 Intel 2500K/ Nvidia 680GTX/8 GB RAM, ASUS P8Z68 board
FSUIPC 4.949c (autosave active)
.NET framework 4.6
Simconnect: ESP 1.0.20/FSX rtm/SP1/Sp2

NV inspector running SGSS 2x
latest IVAP client IVAO software.
PrecipitFX P3D
777 Immersion
Navigraph AIRAC 1601

addons:
FTX GLOBAL/Vector openLC NA/Europe latest patched
FSDT KLAX
FSDT GSX
PMDG 777
FT YSSY
EZDOK 1.8.7
REX DT4 and softclouds
777 immersion

Tonight i'll do this flight a third time.

changes:

stopped using Nvidia inspector, will quit EZDOK inflight, totally disabled DEP in W7,
reinstalled vc++ 2005 x86; vc++ 2008, 2010, 2012, 2013 x86 + x64bit

Maybe i'll reach at least the equator, tonight. :D

regards
PGB

[RVxSpeed]

ok the issue is back.i am definitely sure clicking on the PFD or ND on the captain side triggers something.Last night i was doing 13hrs flight.i accidentally clicked cntrl+something to enlarge the PFD instantly nothing happened.but,after landing when docked at gate.i just switched to overhead panel & bam.CTD.
so,the theory with HT : Off doesn't really solve the issue.

[downscc]

ok the issue is back.i am definitely sure clicking on the PFD or ND on the captain side triggers something.Last night i was doing 13hrs flight.i accidentally clicked cntrl+something to enlarge the PFD instantly nothing happened.but,after landing when docked at gate.i just switched to overhead panel & bam.CTD.
so,the theory with HT : Off doesn't really solve the issue.

Yup, the HT issue was resolved earlier in this long long thread. Not an issue.

I've not had a problem with the inboard DU used for ND, only the left outboard (Capt PFD). My workaround is to set up the FO PFD for 2D popup use and after a half dozen sessions it has not created an event.

Also, anytime you save and reload the flight any previous use of the offending DU is "forgotten" so this is in effect another workaround.

[Adam Breed]

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."

All,

We have been in contact with PMDG and they are working to provide us more information. It is not clear what is causing the issue at this time. We continue to investigate reproduction steps. The further PMDG is able to isolate the issue, the easier it will be to track down a viable fix on either end. MSVCR120.dll is a Microsoft C++ redistributable dll and is likely just a failing location of a call - not the cause. We continue to work with PMDG and I encourage you to continue to contact them if you are having issues with their add-ons.

Regards,
Adam