nikejp63

Ok thanks.

Do you need to uninstall the current version of FSUIPC (5.121b) on your system before you install 5.124? This is in regards to updating P3D from v4.1 to v4.2. Thanks.

Do you need to uninstall the current version of FSUIPC (5.121b) on your system before you install 5.124? This is in regards to updating P3D from v4.1 to v4.2. Thanks.

Appreciate the response, but it doesn't help me. I've been through all this. Everything you suggested has been tried or checked. I am the only user on my PC. I understand nobody else has this issue as I have not seen this particular issue in my countless hours of researching the problem. I troubleshoot software and hardware issues for a living and the bottom line is, plain P3D with no addons runs fine, add Orbx products through FTX Central and the sim crashes with a g2d.dll application error while the scenario is loading terrain. Worked fine for 2 years with P3D v2.5, 3.0 and Orbx products and all of sudden doesn't work. I still say the scenery files are getting corrupted, but I don't know how or why. Is it a Windows 7 issue? I was hoping for a miracle that there was a software guru looking at these posts and could say that he knew what the issue is. Apparently not. My only other option is to buy Windows 10 and install. But that doesn't guarantee that my problem will be solved. Heavy sigh.

I'll try to be brief. When I have the latest P3D v4 loaded with no addons, I have no issues. When I install Orbx Global Base or Vector via FTX Central 3, I get a g2d.dll error and P3d crashes. This happens when the scenario is loading the terrain. It doesn't happen all of the time. What happens is I'll choose a default aircraft, choose a random airport and it will either crash while the scenario is loading the terrain or it will load successfully. If the airport I choose crashes, it will always crash. If the airport I choose doesn't crash, it will always not crash. To me it sounds like certain scenery files are getting corrupted. I then have to reinstall P3D. I have tried manually downloaded the Orbx files and then point FTX Central 3 to install the downloaded files. I have deleted and reinstalled FTX Central. I have completely deleted and installed my nvidia drivers. I have cleaned my registry. I have ran Windows system file check. I have ran chkdsk /f /r on my drives. Antivirus is off while I run FTX Central. Please don't point me to the "CTD guide", I have done that. This problem has been going for a month. I posted on Orbx's forum, the response I got was " a simple search on the internet of g2d.dll will guide you". That doesn't help. Posted on P3D forum, no help there except for the typical standard "try our troubleshooting guide". I need someone who is PC software smart to help me with this. I don't know what else to try. Thanks in advance. Nick

Hi, This is a frustrating problem. I have v3.4 installed and a couple of weeks ago P3D started CTD while loading terrain after starting a scenario. This would happen at about 25% during the load. Never happened before. The only thing that changed after my last successful flight was that I downloaded and installed some of the 55% off scenery ORBX had on sale. I tried all the old tricks of deleting cfg, shaders etc. Even deleted the new Orbx stuff. Nothing worked. So, I decided to stop troubleshooting since v4 was being released. So yesterday, I installed v4 and I'm getting the same CTD. After booting up P3D v4 for the first time and loading the default scenario, it crashes at about 25% during the load. The dreaded g2d.dll error on both versions. I completely removed my nvidia driver using the DDU program. Loaded the latest nvidia driver. Today, I launched v4 and was able to actually fly without crashing for awhile. I kept changing airport locations after a test flight. About the third flight, I moved to another airport and it CTD while loading terrain scenery. The three events are pasted below. I have no addon's in my v4. It's plain stock P3d. I would've said the issue was the Orbx install, but v4 has no idea Orbx is even on my PC. What is the commonality between v3.4, v4 and this g2d.dll error. I hope someone can help. I want to fly again! Thanks. Nick PC I7 4790k 16g ram EVGA 1080 Win 7 Home Error Log Log Name: Application Source: .NET Runtime Date: 6/8/2017 8:30:52 PM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Nike-PC Description: 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 000007FED255B9F3 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-06-09T00:30:52.000000000Z" /> <EventRecordID>80768</EventRecordID> <Channel>Application</Channel> <Computer>Nike-PC</Computer> <Security /> </System> <EventData> <Data>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 000007FED255B9F3 </Data> </EventData> </Event> Log Name: Application Source: Application Error Date: 6/8/2017 8:30:53 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Nike-PC Description: Faulting application name: Prepar3D.exe, version: 4.0.23.21468, time stamp: 0x59279be2 Faulting module name: g2d.dll, version: 4.0.23.21468, time stamp: 0x59279ca2 Exception code: 0xc0000005 Fault offset: 0x000000000010b9f3 Faulting process id: 0x254 Faulting application start time: 0x01d2e0a966e3b96b Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: E:\Lockheed Martin\Prepar3D v4\g2d.dll Report Id: e49f679b-4caa-11e7-b90d-d050995ccf1b 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="2017-06-09T00:30:53.000000000Z" /> <EventRecordID>80769</EventRecordID> <Channel>Application</Channel> <Computer>Nike-PC</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>4.0.23.21468</Data> <Data>59279be2</Data> <Data>g2d.dll</Data> <Data>4.0.23.21468</Data> <Data>59279ca2</Data> <Data>c0000005</Data> <Data>000000000010b9f3</Data> <Data>254</Data> <Data>01d2e0a966e3b96b</Data> <Data>E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data> <Data>E:\Lockheed Martin\Prepar3D v4\g2d.dll</Data> <Data>e49f679b-4caa-11e7-b90d-d050995ccf1b</Data> </EventData> </Event> Log Name: Application Source: Windows Error Reporting Date: 6/8/2017 8:31:12 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: Nike-PC Description: Fault bucket 511725035, type 28 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 4.0.23.21468 P3: 59279be2 P4: g2d.dll P5: 4.0.23.21468 P6: 59279ca2 P7: c0000005 P8: 000000000010b9f3 P9: P10: Attached files: C:\Users\Nike\AppData\Local\Temp\WERD79.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\Nike\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_d3206bee628b19b5b446344f2c1f60654a6ac15e_14505716 Analysis symbol: Rechecking for solution: 0 Report Id: e49f679b-4caa-11e7-b90d-d050995ccf1b Report Status: 0 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-06-09T00:31:12.000000000Z" /> <EventRecordID>80770</EventRecordID> <Channel>Application</Channel> <Computer>Nike-PC</Computer> <Security /> </System> <EventData> <Data>511725035</Data> <Data>28</Data> <Data>APPCRASH</Data> <Data>Not available</Data> <Data>0</Data> <Data>Prepar3D.exe</Data> <Data>4.0.23.21468</Data> <Data>59279be2</Data> <Data>g2d.dll</Data> <Data>4.0.23.21468</Data> <Data>59279ca2</Data> <Data>c0000005</Data> <Data>000000000010b9f3</Data> <Data> </Data> <Data> </Data> <Data> C:\Users\Nike\AppData\Local\Temp\WERD79.tmp.WERInternalMetadata.xml</Data> <Data>C:\Users\Nike\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_d3206bee628b19b5b446344f2c1f60654a6ac15e_14505716</Data> <Data> </Data> <Data>0</Data> <Data>e49f679b-4caa-11e7-b90d-d050995ccf1b</Data> <Data>0</Data> </EventData> </Event>