CTD P3D v3.4 & v4-g2d.dll Error Loading Scenario

[nikejp63 0]

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>

[Jim Young 2,356]

The AVSIM CTD Guide (see link in my signature) provides possible solutions based on my searches across the Internet at various FS sites.  The g2d.dll "solutions" worked for some. 

One of the other errors belongs to .net or Microsoft.net.  Dotnets are used to run applications in the manner the developer intended.  Make sure you have the proper dotnet installed.  I think their website indicates you must have a certain version installed.

The AVSIM CTD Guide also provides a technique to investigating your crashes.  Page 10 has a procedure that fixes most CTD's and Freezes.  In your case, I would disable the scenery you installed from Orbx one at a time until the problem goes away.  This way you can narrow down the offending scenery.  Most of their scenery requires objectflow and that is loaded at startup via the dll.xml.  If it is corrupted or an old version, then it could cause the crashes. 

None of the scenery from FTX/Orbx that uses objectflow will work in P3DV4 until they make objectflow compatible.

Hope this helps.

Best regards,

Jim

[PascalK 0]

Hei NIck i have exactly the same issue.

Did you manage to solve it?

 

Best,

Pascal