Sign in to follow this  
mario340500

P3D v3.2 / 3.3 g2d.dll error Exception Code c0000005 Exception Offset 000d7803

Recommended Posts

Hi there,

 

Just reaching out to anyone who can help. 

 

I have P3D CTDs when flying PMDG 777-300ER. 

 

Scenario:

 

I load PMDG from P3D scenario screen in clod and dark panel state.

Am testing on the stock YMML to YSSY route. Once the 777 is fully configured and the PFPX route loaded, take off is smooth from Melbourne.

CTD occurs either just before reaching cruise of FL370 at FL340 or during the descent between FL200 and FL120.

Every other route I fly in any other region, the same thing occurs..

 

Error Details as follows:

 

Log Name:      Application
Source:        Application Error
Date:          6/5/2016 6:03:49 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-K7LRFKD
Description:
Faulting application name: Prepar3D.exe, version: 3.3.3.17556, time stamp: 0x5747897d
Faulting module name: g2d.dll, version: 3.3.3.17556, time stamp: 0x57478a15
Exception code: 0xc0000005
Fault offset: 0x000d7803
Faulting process id: 0x4a0
Faulting application start time: 0x01d1befd1b22bae4
Faulting application path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: D:\Lockheed Martin\Prepar3D v3\g2d.dll
Report Id: 086888fc-2af4-11e6-bdf3-305a3a0172c9
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-05T08:03:49.286926400Z" />
    <EventRecordID>4784</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-K7LRFKD</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>3.3.3.17556</Data>
    <Data>5747897d</Data>
    <Data>g2d.dll</Data>
    <Data>3.3.3.17556</Data>
    <Data>57478a15</Data>
    <Data>c0000005</Data>
    <Data>000d7803</Data>
    <Data>4a0</Data>
    <Data>01d1befd1b22bae4</Data>
    <Data>D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
    <Data>D:\Lockheed Martin\Prepar3D v3\g2d.dll</Data>
    <Data>086888fc-2af4-11e6-bdf3-305a3a0172c9</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
 
I have tried with a fresh install of P3Dv3.2 or 3.3 on W7x64 or W10x64.
 
Addons installed:
FTX Global, Vecto.
Pilots Ultimate Global Mesh (all 3 DVD packs)
Mytraffic 6 (currently disabled)
PMDG 777 LR / 300ER
RAAS latest version.
PFPX, NavDataPro (1604 dataset installed).
REX Ess +, REX 4 TD + SoftClouds.
 
All installers are freshly downloaded (latest patched versions)
Have been experiencing a lot of CTD's since last year (Nov onwards) but never got round to investigating the reason until I bumped into the CTD guide.
 
Please help.. System (stock state with no overclocking whatsoever) in my sig.
 
Regards,
Mario

Share this post


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

Thanks for the detailed report.  The AVSIM CTD Guide (see link in my signature) has information about the G2D error -

 

G2D.dll - This module handles plain text messages, like the frame rate counter and those other plain text messages you see periodically while running any simulator and the plain text words in the respective Menu, like the words Options, View, etc. There may be something corrupted in your dll.xml which loads menu items.

 

See page 32 for possible fixes to the G2D error.  These suggestions were found by conducting searches at all Flight Simulator websites and finding the solutions that worked for others.

 

I would disable everything in your dll.xml except for the things you really need for the flight (like the PMDG entry).  I would move your p3d.cfg to a temp folder and let it be rebuilt when you restart P3D.  I would disable all addon scenery in your scenery.cfg to include ftx global.  I would then fly the flight again. 

Share this post


Link to post
Share on other sites

Thanks for getting back to me Jim, I will give your steps ago and get back to you later tonight / tomorrow night. I really want to get to the bottom of what is causing the errors before installing anything else. I hope it is not Hardware related.

 

I forgot to mention that the latest version of FSUIPC is installed for P3Dv3.3 and have not activated the VAS monitor settings in FSUIPC yet.

 

Regards,

Mario

Share this post


Link to post
Share on other sites

Thanks for the detailed report.  The AVSIM CTD Guide (see link in my signature) has information about the G2D error -

 

 

Got G3D.dll  error on 3.3 also - have to look into your suggestions - thank you Jim   :wink: 

Share this post


Link to post
Share on other sites

Jim,

 

Here are the actions and results:

 

I upgraded NavDataPro to 1606 r1 dataset. Updated PFPX and PMDG via NavDataPro.

 

1. Moved dll.xml & Prepar3d.cfg to a temporary folder.
2. Moved Scenery.cfg to a temporary folder.
Allowed P3D to rebuild both files and flew the flight perfectly to Sydney.
3. Moved dll.xml back to, enabled PMDG modules.
Disabled FSUIPC and Orbx Flow modules.
Flew the flight perfectly to Sydney.
4. Enabled FSUIPC
Flew the flight perfectly to Sydney.
 
So far so good. I even had FTG-ACARS running and recorded a Virtual flight too.. All good . No g2d.dll errors so far.
 
Regarding ORBX Flow module, do I enable it in the dll.xml although scenery.cfg is not moved back to the appdata folder and then fly a test flight?
Or do I move the scenery.cfg file back, enable the orbxflow module and then test?
 
Regards,
Mario

Share this post


Link to post
Share on other sites

 

 


Regarding ORBX Flow module, do I enable it in the dll.xml although scenery.cfg is not moved back to the appdata folder and then fly a test flight?
Or do I move the scenery.cfg file back, enable the orbxflow module and then test?
 

 

You can enable Orbx ObjectFlow.  It will be enabled just in case you decide to enable it.  I have already move all of the items in the dll.xml and exe.xml located in the AppData\Roaming\Lockheed Martin\Prepar3d folder to the new location (since v3.3) (c:\ProgramData\LockheedMartin\Prepar3d_v3 folder).  It's probably best not to have two dll.xml's and exe.xml's loading but it works if you do have that situation.  FSDT already moved their modules to the new location.

 

Best regards,

Share this post


Link to post
Share on other sites

Hi Jim,

 

Here is the detailed list of all the actions I took to get to the bottom of the g2d.dll error. Looks like g2d.dll is gone but ntdll.dll is now in play..(pls see lower for details)

 

1. Moved dll.xml & Prepar3d.cfg from AppData\Roaming\Lockheed Martin\Prepar3D v3 to temp folder
2. Moved C:\ProgramData\Lockheed Martin\Prepar3D v3\Scenery.cfg to a temp folder
Flew the flight perfectly to Sydney.
3. Moved dll.xml back to AppData\Roaming\Lockheed Martin\Prepar3D v3
PMDG stuff enabled
FSUIPC and Orbx Flow disabled
Flew the flight perfectly to Sydney.
4. Enabled FSUIPC
Flew the flight perfectly to Sydney.
5. Enabled Orbxflow and moved Scenery.cfg back to C:\ProgramData\Lockheed Martin\Prepar3D v3\
Flew the flight perfectly to Sydney.
6. Reinstalled Mytraffic6 and ran P3d.. I renamed MyTrafficmil.bgl to MyTrafficmilbgl.passive in D:\MyTraffic Professional\MyTraffic\Scenery but still, bang; just after obtaining cruise altitude, now ntdll.dll error
I thought disabling this would prevent it.. Please help.
 
Log Name:      Application
Source:        Application Error
Date:          6/8/2016 2:14:05 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-K7LRFKD
Description:
Faulting application name: Prepar3D.exe, version: 3.3.3.17556, time stamp: 0x5747897d
Faulting module name: ntdll.dll, version: 10.0.10586.306, time stamp: 0x571afb7f
Exception code: 0xc0000374
Fault offset: 0x000dc7c9
Faulting process id: 0x6d4
Faulting application start time: 0x01d1c13805e516df
Faulting application path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 4f0ea337-f7f0-433c-87ce-7f58d02bc408
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-08T04:14:05.183873900Z" />
    <EventRecordID>5100</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-K7LRFKD</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>3.3.3.17556</Data>
    <Data>5747897d</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.10586.306</Data>
    <Data>571afb7f</Data>
    <Data>c0000374</Data>
    <Data>000dc7c9</Data>
    <Data>6d4</Data>
    <Data>01d1c13805e516df</Data>
    <Data>D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>4f0ea337-f7f0-433c-87ce-7f58d02bc408</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
 
 
Regards,
Mario

Share this post


Link to post
Share on other sites

UPDATE : I just completed a successful flight into Sydney with absolutely  no issues after restoring all the dll.xml, scenery.cfg and prepar3d.cfg files back to their respective folders.

 

FIX: I uninstalled Mytraffic 6 and deleted the d:\MyTraffic Professional folder.

I then downloaded and installed MyTraffic_Professional_6.0a as per the instructions here http://www.avsim.com/topic/483116-how-do-i-install-my-traffic-60a-for-prepar3d-v3/

The g2d.dll and ntdll errors are now gone.. WooHoo!!!

 

The installer can be downloaded from the same place where the original MyTraffic_Professional_6.0 is.. (In my case, from my downloands in SimMarket as that is where I bought version 6)

 

Jim,

Thanks so much for all your help. After 6 months of g2d.dll erros and finally its fixed.. 

 

Best Regards,

Mario

Share this post


Link to post
Share on other sites

Further action taken :

 

I flew out of ORBX KTVL and got ntdll.dll CTD in P3D v3.3 with hotfix straight after takeoff.

I renamed MyTrafficmil.bgl to MyTrafficmilbgl.passive in <drive>:[path]\MyTraffic Professional\MyTraffic\Scenery and the crash disappeared.

Something is wrong somewhere with MyTrafficmil.bgl in MyTraffic_Professional_6.0a

 

This thread is open with MyTraffic vendor for a fix http://forum.simflight.com/topic/81543-ntdlldll-error-update/

Share this post


Link to post
Share on other sites

I have MyTrafficPro v6.0a and so far have not seen an ntdll.dll error.  NTDLL.dll errors go away fast many times for the weirdest reasons.  Did you try enabling the MyTrafficMil to see if the error reoccurs?  This is another one of those errors where the crash does not occur with everyone (at least not for me).  This is why it will be difficult for the developer to find the problem.

 

Best regards,

Share this post


Link to post
Share on other sites

Then that is definitely the problem for you.  Wonder why I am not getting it?  I fly P3D v3 most of the time.

Share this post


Link to post
Share on other sites

Jim,

The error is not wide spread in P3D either.. It is only at certain locations in the US - more specifically at Orbx - Northern California and Lake Tahoe Airport Scenery. Where it is very evident - soon after take off in any default P3D a/c. If I rename the file, all good and no issues.

 

M

Share this post


Link to post
Share on other sites

Then that is definitely the problem for you.  Wonder why I am not getting it?  I fly P3D v3 most of the time.

 

Jim,

The error is not wide spread in P3D either.. It is only at certain locations in the US - more specifically at Orbx - Northern California and Lake Tahoe Airport Scenery. Where it is very evident - soon after take off in any default P3D a/c. If I rename the file, all good and no issues.

 

M

 

Just a thought not sure this will help but since Orbx updated Their new one stop shopping system I had really bad blurry terrain textures

 

It seems when I turned off my LC it was fixed terrain looked way better so I dont think old LC such as Xclass or fsgenesis does not play well with new Orbx system which is fine US LC is around the corner I hope - didnt try fsgenesis but confirmed Xclass is a huge issue - I didnt have this issue until loading new Orbx system

 

I find this very interesting - I might be off on this one but I saw an immediate fix by removing LC from P3D library and order was fine it was way below any Orbx products 

 

So Orbx please release the US LC   :wink:

Share this post


Link to post
Share on other sites

 

 


It seems when I turned off my LC it was fixed terrain looked way better so I dont think old LC such as Xclass or fsgenesis does not play well with new Orbx system which is fine US LC is around the corner I hope - didnt try fsgenesis but confirmed Xclass is a huge issue - I didnt have this issue until loading new Orbx system

 

Good points Rich.  So you think LC layering is the cause of this problem?  I would have a hard time agreeing with that thesis but software and computers do the strangest things!

 

When I get unexplained errors on my computer, I look immediately at what I installed as the culprit as some software may appear to be compatible with a product but, in reality, it is not.  This is why I have stayed away from things not specifically made for P3Dv3.3.  You can see with just the slightest updates of P3D, FSUIPC (a normally compatible utility for P3D) has to be updated.  FSDT and FlightBeam stuff are normally compatible with P3D but require an update whenever P3D is updated.  So, how can all of this software that was not specifically developed for P3D get away with not having to be updated?  I think it takes just one piece of badly programmed software not made for P3D to cause unexplained issues with P3D.  Everyone wants to blame LM even when there are potential compatibility issues with software installed into P3D.

 

One of the things I have started doing is moving the dll.xml and exe.xml that was located in the same folder as the P3D.cfg to the new location (C:\ProgramData\Lockheed Martin\Prepar3D or where the P3D scenery.cfg is located).  Just little things like that.

 

Best regards,

Share this post


Link to post
Share on other sites

Good points Rich.  So you think LC layering is the cause of this problem?  I would have a hard time agreeing with that thesis but software and computers do the strangest things!

 

 

I have no idea Jim - thought I would throw that out there - I coudnt believe it when I figured it out - does make sense - not sure if its a LC issue only on my end - need to see if anyone else is seeing this

Share this post


Link to post
Share on other sites

One of the things I have started doing is moving the dll.xml and exe.xml that was located in the same folder as the P3D.cfg to the new location (C:\ProgramData\Lockheed Martin\Prepar3D or where the P3D scenery.cfg is located).  Just little things like that.

 

Best regards,

 

 

Jim whats the advantage to moving those files out ?  thanks

Share this post


Link to post
Share on other sites

Jim whats the advantage to moving those files out ?  thanks

Hi Rich,

 

It is the new location for those files.  So, if you have them in the old location (where the p3d.cfg is located), you could have duplicate entries loading.  I know FSDT has moved to the new location with their latest installers.  Think fsuipc too.  I moved all of my entries in the dll.xml to the new location including the PMDG and Carenado entries and everything loads properly.  Running duplicate entries at loading time can result in an NTDLL.dll error.  As proof, I had an unexplained StackHash and then an ntdll.dll error a year or two ago.  I went into the dll.xml to disable some entries so I could see if one of the modules was causing the crash.  I saw a duplicate entry for PMDG.  I removed one.  The CTD's stopped.  Go figure!  Simple things like that cause errors and the main reason I recommend, in the AVSIM CTD Guide, everyone move their dll.xml to a temporary folder after getting a CTD.  It's part of the investigative process.  Mostly the crashes are caused by a bad p3d.cfg, the scenery.cfg, or a module in the dll.xml and exe.xml files.  Occasionally it is hardware or a bad overclock and lastly, an incompatible add-on (whew, I'm out of breath!).  One has to figure out exactly which one was the cause.

 

Best regards,

  • Upvote 1

Share this post


Link to post
Share on other sites

Hi Rich,

 

It is the new location for those files.  So, if you have them in the old location (where the p3d.cfg is located), you could have duplicate entries loading.  I know FSDT has moved to the new location with their latest installers.  Think fsuipc too.  I moved all of my entries in the dll.xml to the new location including the PMDG and Carenado entries and everything loads properly.  Running duplicate entries at loading time can result in an NTDLL.dll error.  As proof, I had an unexplained StackHash and then an ntdll.dll error a year or two ago.  I went into the dll.xml to disable some entries so I could see if one of the modules was causing the crash.  I saw a duplicate entry for PMDG.  I removed one.  The CTD's stopped.  Go figure!  Simple things like that cause errors and the main reason I recommend, in the AVSIM CTD Guide, everyone move their dll.xml to a temporary folder after getting a CTD.  It's part of the investigative process.  Mostly the crashes are caused by a bad p3d.cfg, the scenery.cfg, or a module in the dll.xml and exe.xml files.  Occasionally it is hardware or a bad overclock and lastly, an incompatible add-on (whew, I'm out of breath!).  One has to figure out exactly which one was the cause.

 

Best regards,

 

At work now have to digest this - you are one smart Guy - many thanks  :wink:

Share this post


Link to post
Share on other sites

Jim,

 

I have dll.xml in both locations (%appdata% and the programdata locations) but exe.xml is only in %appdata%.

So from what you saying is that it is best practice to move both files to the programdata location (where scenery.cfg is located).

 

So in my case, I will 

 

1. Merge the dll.xml entries from the %appdata%dll.xml file to the programdata dll.xml file.

2. Delete the dll.xml file in the %appdata% location.

3. Cut exe.xml file from %appdata% and paste in programdata.location.

4. Fire up P3D and all should work.

 

Note:  I have a vanilla Prepare3d.cfg (unedited since 3.3.5 - latest build) which works perfect. (my settings are fairly normal with TML set to 1024) for best performance. 

 

I am guessing this should eliminate the ntdll.dll error which required renaming mytraficmil.bgl as a workaround.

Please confirm the above. I will then go ahead that do this after GSX and FSDT airports are all installed.

In other words, as a last and final step.

 

Provided this is confirmed to be best practice, moving forward, I will keep a close eye to ensure that those files dll.xml and exe.xml stay in programdata and any additions should follow the above steps.

 

Thanks for all your help.

 

Regards,

Mario

Share this post


Link to post
Share on other sites

Correction, the AppData\Roaming\Lockheed Martin\Prepar3D v3 folder contains ONLY a DLL.xml file containing:

 

<?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>ObjectFlow</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.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>RAASPRO</Name>
    <Disabled>False</Disabled>
    <Path>.\RAASPRO\RAASPRO.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow_P3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
</SimBase.Document>
 
The C:\ProgramData\Lockheed Martin\Prepar3D v3 contains dll.xml file and exe.xml.
Contents of the dll.xml file are:
 
<?xml version="1.0" encoding="Windows-1252"?>
 
<SimBase.Document Type="AceXML" version="3,0" id="dll">
    <Descr>AceXML Document</Descr>
    <Filename>dll.xml</Filename>
    <Launch.Addon>
        <Name>TargetInfo</Name>
        <Path>Gauges\TargetInfo.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Fury_1500</Name>
        <Path>Gauges\Fury_1500.dll</Path>
        <DLLType>PDK</DLLType>
    </Launch.Addon>
</SimBase.Document>
 
So if I were to delete the AppData\Roaming\Lockheed Martin\Prepar3D v3\DLL.xml file then add the entries to the C:\ProgramData\Lockheed Martin\Prepar3D v3\dll.xml which would look like this:
 
<?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>ObjectFlow</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.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>RAASPRO</Name>
    <Disabled>False</Disabled>
    <Path>.\RAASPRO\RAASPRO.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow_P3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
</SimBase.Document>
<SimBase.Document Type="AceXML" version="3,0" id="dll">
    <Descr>AceXML Document</Descr>
    <Filename>dll.xml</Filename>
    <Launch.Addon>
        <Name>TargetInfo</Name>
        <Path>Gauges\TargetInfo.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Fury_1500</Name>
        <Path>Gauges\Fury_1500.dll</Path>
        <DLLType>PDK</DLLType>
    </Launch.Addon>
</SimBase.Document>
 
Is this correct ?? I won't be surprised if it's not as I have no idea how the file is meant to look.
 
M

Share this post


Link to post
Share on other sites

 

 


Is this correct ?? I won't be surprised if it's not as I have no idea how the file is meant to look.

 

This is correct Mario but change the first entry you had as follows -

 

 

<?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>
 
To This -
 
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="dll">
  <Descr>AceXML Document</Descr>
  <Filename>dll.xml</Filename>
  <Launch.Addon>
 
You can keep both dll.xml's but you should not have duplicate entries between the two.  So anything in the location where the P3D.cfg is located should not be duplicated in the dll.xml located where the scenery.cfg is located.  Otherwise this could cause problems.
 
Best regards,

Share this post


Link to post
Share on other sites

Thanks Jim,

 

Have deleted the DLL.xml file from C:\Users\MnM\AppData\Roaming\Lockheed Martin\Prepar3D v3 and have merged the entries into the dll.xml file in C:\ProgramData\Lockheed Martin\Prepar3D v3

 

The file contents looks like:

 

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="dll">
  <Descr>AceXML Document</Descr>
  <Filename>dll.xml</Filename>
  <Launch.Addon>
    <Name>TargetInfo</Name>
    <Path>Gauges\TargetInfo.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Fury_1500</Name>
    <Path>Gauges\Fury_1500.dll</Path>
    <DLLType>PDK</DLLType>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.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>RAASPRO</Name>
    <Disabled>False</Disabled>
    <Path>.\RAASPRO\RAASPRO.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow_P3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
</SimBase.Document>
 
The g2d.dll errors are back despite removing all non-P3D sceneries and Mytraffic6a.. Here is the error below:
 
Log Name:      Application
Source:        Application Error
Date:          6/19/2016 11:06:57 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-K7LRFKD
Description:
Faulting application name: Prepar3D.exe, version: 3.3.5.17625, time stamp: 0x5758bb31
Faulting module name: g2d.dll, version: 3.3.5.17625, time stamp: 0x5758bbc2
Exception code: 0xc0000005
Fault offset: 0x000d7663
Faulting process id: 0x14b0
Faulting application start time: 0x01d1c9c03001a6fc
Faulting application path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: D:\Lockheed Martin\Prepar3D v3\g2d.dll
Report Id: 1e37dca7-35ba-11e6-be15-305a3a0172c9
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-19T01:06:57.858053900Z" />
    <EventRecordID>6867</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-K7LRFKD</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>3.3.5.17625</Data>
    <Data>5758bb31</Data>
    <Data>g2d.dll</Data>
    <Data>3.3.5.17625</Data>
    <Data>5758bbc2</Data>
    <Data>c0000005</Data>
    <Data>000d7663</Data>
    <Data>14b0</Data>
    <Data>01d1c9c03001a6fc</Data>
    <Data>D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
    <Data>D:\Lockheed Martin\Prepar3D v3\g2d.dll</Data>
    <Data>1e37dca7-35ba-11e6-be15-305a3a0172c9</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

back to troubleshooting

Share this post


Link to post
Share on other sites

Thanks Jim,

 

Have deleted the DLL.xml file from C:\Users\MnM\AppData\Roaming\Lockheed Martin\Prepar3D v3 and have merged the entries into the dll.xml file in C:\ProgramData\Lockheed Martin\Prepar3D v3

 

The file contents looks like:

 

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="dll">
  <Descr>AceXML Document</Descr>
  <Filename>dll.xml</Filename>
  <Launch.Addon>
    <Name>TargetInfo</Name>
    <Path>Gauges\TargetInfo.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Fury_1500</Name>
    <Path>Gauges\Fury_1500.dll</Path>
    <DLLType>PDK</DLLType>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.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>RAASPRO</Name>
    <Disabled>False</Disabled>
    <Path>.\RAASPRO\RAASPRO.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow_P3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
</SimBase.Document>
  

Note the duplicate entries in red in your dll.xml above.  Did you transfer your exe.xml to the new location too?

 

At least you know now it is not MyTraffic6a causing your problems.  The duplicate entries in your dll.xml could have caused this issue.  The AVSIM CTD Guide indicates the g2d.dll error could be caused by a corrupted dll.xml.

Share this post


Link to post
Share on other sites

Good pick up Jim,

 

Corrected the file which is now moved to C:\ProgramData\Lockheed Martin\Prepar3D v3 and contents looks like :

 

<?xml version="1.0" encoding="Windows-1252"?>
 
<SimBase.Document Type="AceXML" version="3,0" id="dll">
  <Descr>AceXML Document</Descr>
  <Filename>dll.xml</Filename>
  <Launch.Addon>
    <Name>TargetInfo</Name>
    <Path>Gauges\TargetInfo.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Fury_1500</Name>
    <Path>Gauges\Fury_1500.dll</Path>
    <DLLType>PDK</DLLType>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.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>RAASPRO</Name>
    <Disabled>False</Disabled>
    <Path>RAASPRO\RAASPRO.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>
</SimBase.Document>
 
I reinstalled MyTraffic 6a and during decent towards Flytampa Dubai, another g2d.dll crash..
Please would you review the above and let me know if all looks in order..
 
The exe.xml was always only in C:\ProgramData\Lockheed Martin\Prepar3D v3 and did not need moving. Its contents are :
 
<?xml version="1.0" encoding="Windows-1252"?>
 
<SimBase.Document Type="AceXML" version="3,0" id="exe">
    <Descr>AceXML Document</Descr>
    <Filename>exe.xml</Filename>
</SimBase.Document>
 

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this