Sign in to follow this  
Guest JustanotherPilot

Help needed to determine cause of CTD (twice) P3D3.4.9

Recommended Posts

Two CTD's today 1st flight after 40 mins enroute, 2nd flight after 20 mins during pushback. I have been looking through the Avsim CTD guide to try to find the cause but nothing obvious other than the Faulting module name: g2d.dll,

 

Here are the two crashes from AppCrashView

 

Version=1
EventType=APPCRASH
EventTime=131260025722110073
ReportType=2
Consent=1
UploadTime=131260025724158223
ReportIdentifier=83fd18fd-c03f-11e6-a9b3-7824af381716
IntegratorReportIdentifier=83fd18fc-c03f-11e6-a9b3-7824af381716
WOW64=1
AppSessionGuid=00001130-0001-0074-1c00-e22e3d54d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!Prepar3D.exe
TargetAppVer=2016//09//14:20:21:34!75f13!Prepar3D.exe
BootId=4294967295
Response.BucketId=c1679abf353b0178b08c78439c2a6a8e
Response.BucketTable=1
Response.LegacyBucketId=108453361706
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.9.18400


--------------------------------------------------------------------------------------------------------------------


Version=1
EventType=APPCRASH
EventTime=131260795880571857
ReportType=2
Consent=1
UploadTime=131260795882329410
ReportIdentifier=d5074504-c0f2-11e6-a9b4-7824af381716
IntegratorReportIdentifier=d5074503-c0f2-11e6-a9b4-7824af381716
WOW64=1
AppSessionGuid=00004208-0001-0075-ca1d-de41fb54d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!Prepar3D.exe
TargetAppVer=2016//09//14:20:21:34!75f13!Prepar3D.exe
BootId=4294967295
Response.BucketId=c461e2c9533b437d06ffe77bfda5016a
Response.BucketTable=1
Response.LegacyBucketId=108414527724
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.9.18400

 

 

And here is the first crash shown in event viewer

Log Name:      Application
Source:        Application Error
Date:          13/12/2016 4:13:08 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SteveS-PC
Description:
Faulting application name: Prepar3D.exe, version: 3.4.9.18400, time stamp: 0x57d9b14e
Faulting module name: g2d.dll, version: 3.4.9.18400, time stamp: 0x57d9b22e
Exception code: 0xc0000005
Fault offset: 0x000d30ee
Faulting process id: 0x4208
Faulting application start time: 0x01d254fb41de1dca
Faulting application path: E:\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: E:\Lockheed Martin\Prepar3D v3\g2d.dll
Report Id: d5074503-c0f2-11e6-a9b4-7824af381716
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-12-13T05:13:08.007095400Z" />
    <EventRecordID>42091</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SteveS-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>3.4.9.18400</Data>
    <Data>57d9b14e</Data>
    <Data>g2d.dll</Data>
    <Data>3.4.9.18400</Data>
    <Data>57d9b22e</Data>
    <Data>c0000005</Data>
    <Data>000d30ee</Data>
    <Data>4208</Data>
    <Data>01d254fb41de1dca</Data>
    <Data>E:\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
    <Data>E:\Lockheed Martin\Prepar3D v3\g2d.dll</Data>
    <Data>d5074503-c0f2-11e6-a9b4-7824af381716</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

 

 

dll.xml file below

 

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>iFly 747-400 Menu</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>Modules\iFly744.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>E:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG HUD interface</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>RAASPRO</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>.\RAASPRO\RAASPRO.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PDFKneeboard</Name>
    <Disabled>False</Disabled>
    <Path>.\modules\pdfkneeboard.dll</Path>
    <Commandline />
  </Launch.Addon>
  <Launch.Addon>
    <Name>Captain Sim 767 Menu</Name>
    <Disabled>False</Disabled>
    <Path>Captain_Sim\Captain_Sim.b767.menu.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Carenavigraph</Name>
    <Disabled>False</Disabled>
    <Path>.\Carenavigraph.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>XMLTools3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>XMLTools3D.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>E:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow_YMML_P3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>E:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_YPMQ\FTXAA_YMML\Scenery\ObjectFlow_YMML_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Captain Sim Sound</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>Captain_Sim\bin\cs.sound.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG Interface</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDG_Interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>XMLTools3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>XMLTools3D.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>as_connect</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp.dll</Path>
  </Launch.Addon>
</SimBase.Document>

 

 

 

And the exe.xml

 

 

<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>as_btstrp_config_manager</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp_config_manager.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Addon Manager</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>bglmanx.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PDFKneeboard</Name>
    <Disabled>False</Disabled>
    <Path>.\modules\pdfkneeboard.dll</Path>
    <Commandline />
  </Launch.Addon>
  <Launch.Addon>
    <Name>EZdok camera addon</Name>
    <Disabled>True</Disabled>
    <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>VFXCentral</Name>
    <Disabled>False</Disabled>
    <Path>C:/Program Files (x86)/OldProp Solutions Inc/VFXCentral/VFXCentral.exe</Path>
    <CommandLine>P3Dv3</CommandLine>
  </Launch.Addon>
</SimBase.Document>

 

Any help would be greatly appreciated.

 

thanks

 

steve s

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

It's a g2d.dll error, and there's no quick fix. Try the AVSIM CTD guide and read through the g2d.dll section, but it's a long shot.

 

Most CTDs are caused by some addon or an unstable computer.

 

If it happens often check that your computer hardware drivers, BIOS etc. are up to date. Also make sure that you keep your computer in good shape by keeping the internal components free of dust and check that all the components are connected properly, especially the GPU which more often than not is a bit too heavy for the PCI slot to sit real tight.

Share this post


Link to post
Share on other sites

It's a g2d.dll error, and there's no quick fix. Try the AVSIM CTD guide and read through the g2d.dll section, but it's a long shot.

 

Most CTDs are caused by some addon or an unstable computer.

 

If it happens often check that your computer hardware drivers, BIOS etc. are up to date. Also make sure that you keep your computer in good shape by keeping the internal components free of dust and check that all the components are connected properly, especially the GPU which more often than not is a bit too heavy for the PCI slot to sit real tight.

 

 

Thanks for the reply, I'll open the case and inspect the internals, I keep the BIOS and drivers up  to date. I added more RAM, recently might have dislodged the Graphics card.

Share this post


Link to post
Share on other sites

It's a g2d.dll error, and there's no quick fix. Try the AVSIM CTD guide and read through the g2d.dll section, but it's a long shot.

 

Most CTDs are caused by some addon or an unstable computer.

 

If it happens often check that your computer hardware drivers, BIOS etc. are up to date. Also make sure that you keep your computer in good shape by keeping the internal components free of dust and check that all the components are connected properly, especially the GPU which more often than not is a bit too heavy for the PCI slot to sit real tight.

Totally agree.  Too bad there is not one fix that fits everyone who gets the g2d.dll error.  But, if the graphics card is not properly seated or the drivers not properly or completely installed, then I would check those things first.  I recently was getting ntdll.dll errors in P3D until I reinstalled my graphics card drivers as an Administrator.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Just a quick note to check for heat related issues, and if you don't find anything with the above noted items and heat is fine, then I'd consider running a memory diagnostic and processor stress test.

Share this post


Link to post
Share on other sites

 

 


<Launch.Addon>
    <Name>Addon Manager</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>bglmanx.dll</Path>
  </Launch.Addon>

 

Just looking at your exe.xml and I know for a fact this entry does not belong in the exe.xml but only in the dll.xml.  The AddonManager is loaded via the dll.xml.

 

The following entry for Dreamteam is required in the exe.xml instead:

 

 <Launch.Addon>
        <Name>Couatl</Name>
        <Path>fsdreamteam\couatl\couatl.exe</Path>
    </Launch.Addon>

 

So, this is most likely the cause of your g2d.dll error.  You need to know too that in P3D only, there are two active dll.xml's and exe.xml's.  One in the same folder as your P3D.cfg (which is the old default) and one in the same folder as your scenery.cfg (the new default).  You are only showing one dll.xml and exe.xml.  Hopefully you did not copy these files from another installation.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thanks Jim, I was hoping you would have a look at it - Dave and Simmerhead likewise for your help.

 

Steve

 

Late Mail: Opened up my case and found the following (system is i74790K @4.5, GTX 960, Asus Z97 Gryphon, 20gig RAM, win 10 64bit pro)

 

The graphics card was indeed loose in it's slot (how I don't know) I re-seated and tightened with 2 screws to the chassis. I have 6 on board case cooling fans and my CPU has a CoolerMaster Hyper 212 air cooler fitted. ALL fans were caked in dust as was the power supply fan and ALL filters. Everything meticulously cleaned and refitted.

 

I changed the exe and dll xml to what they should be.

 

Powered up my computer, it was noticeably quieter and running several degrees cooler.

 

The big test was when I flew the 737ngx from  Orbx YBCS Cairns to YBBN Brisbane - a 90 minute flight that I could previously only get 20-30 minutes out of before CTD (the subject of this post).

 

The flight went flawlessly gate to gate, strangely, I noticed VAS was stable with around 700mb remaining at Brisbane.

 

I will now implement a regular internal cleaning regime.

 

Gentlemen I thank you! I have a lot of flying to catch up with

 

Steve

Share this post


Link to post
Share on other sites

Hi Steve,

 

Thanks for posting that you got it fixed.  That's great!  The video card slots are tight on many MotherBoards and the latches holding them down sometimes pop open if not latched completely. 

 

I've never heard of 20GB's of RAM before.  Simms usually come in the 4GB or 8GB flavor and there are four slots to insert each simm.  But, if it is being recognized and working properly, that works!!

 

Hope you continue to fly crash free.  It's frustrating fighting CTD's and freezes!!

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this