Sign in to follow this  
nighthawk65

P3D V3.2 G3D.DLL

Recommended Posts

Hello all, I could please greatly utilize some assistance. I have been having sever issues since upgrading to v3.2 that I even did a complete reinstall of windows and P3D. I would go back to 3.1 but I can't find my installers. P3D keeps having issues where it will crash mid-flight, doesn't matter on what aircraft what scenery or weather etc. It also crashes every time I turn P3D off, even if I close it through the main menu. Each time it says that it is due to a G3D.dll. I have rebuilt the CFG from scratch, I have remade both the exe and dll files with the original settings, all with no luck. I am now in the process of re-downloading all of my current addons which are suppose to be working with P3D. If anybody has any thought or ideas, I would be greatful.

Prepar3D.exe 
3.2.3.16769 
56df48ce 
g3d.dll 
3.2.3.16769 
56df4861 
c0000005 
000b7f8d 
520 
01d19d90694477ac 
D:\P3D\Prepar3D v3\Prepar3D.exe 
D:\P3D\Prepar3D v3\g3d.dll 
5ce111a1-0984-11e6-8409-e03f49b46571 

- <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-04-23T18:51:18.000000000Z" /> 
<EventRecordID>6240</EventRecordID> 
<Channel>Application</Channel> 
<Computer>Home</Computer> 
<Security /> 
</System>
- <EventData>
<Data>Prepar3D.exe</Data> 
<Data>3.2.3.16769</Data> 
<Data>56df48ce</Data> 
<Data>g3d.dll</Data> 
<Data>3.2.3.16769</Data> 
<Data>56df4861</Data> 
<Data>c0000005</Data> 
<Data>000b7f8d</Data> 
<Data>520</Data> 
<Data>01d19d90694477ac</Data> 
<Data>D:\P3D\Prepar3D v3\Prepar3D.exe</Data> 
<Data>D:\P3D\Prepar3D v3\g3d.dll</Data> 
<Data>5ce111a1-0984-11e6-8409-e03f49b46571</Data> 
</EventData>
</Event>
 

Share this post


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

This was a common crash in FSX and the subject of one of the largest topics ever in the history of these forums.  The cause of the g3d.dll error is unknown but, for FSX, the developer of the fsuipc4.dll utility added a trap for this error.  In other words, if the g3d.dll error was about to occur, the fsuipc4.dll would trap the error.  Neat huh?  It does not trap all of the causes for this error, just some. 

 

The developer did not add this fix in the fsuipc4.dll for P3D as there were indications this problem was fixed by Lockheed Martin.  I know I could replicate the crash 100% of the time in FSX if I flew around the Seattle, Washington area with FTX/Orbx scenery.  Anywhere else, no crash.  I cannot replicate it in P3Dv3.2 (or any previous versions). 

 

If you have addon scenery, I would disable them and run P3D again.  If no g3d.dll crash, then it is one of the scenery.  You will then have to investigate and enable 3-4 scenery at a time until the problem reoccurs.  I would suspect the most recent scenery added.  Look at your Event Viewer and see when those crashes began occurring.  That will give you a clue. 

 

I think the problem is caused with an addon scenery where static aircraft were placed on the ground.  That's what I believed occurred when I got the crashes around Seattle as there were many freeware addons nearby that included static aircraft on the ground.  If you were looking in that direction or the aircraft was aimed in that direction, the g3d.dll error would occur.  I believe the crash is associated with FTX/Orbx scenery but not everywhere.

 

Here are some links I found that might be helpful - http://www.avsim.com/topic/469807-g3ddll-freeze-again/; http://www.avsim.com/topic/441704-recovering-from-g3ddll-crashes-and-tips-to-diagnose/

 

Good luck finding the cause.

 

Best regards,

Share this post


Link to post
Share on other sites

Thanks for the help, but no luck.  I disabled all items in both the exe and dll and disabled all scenery.  The sim loads fine, sometimes you can do flights no issue.  I just can't figure out why it Sporadically ctd's with that error, or why each time I shut down I get that error.

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