- Loaded saved flight with default baron successfully
- changed to NGX and initialized successfully
- preflight, taxi and takeoff successful
- 10 minutes into flight switched to external view and remained in this view for about 30 seconds, then...

I don't know contributing factors as I do not know what the g3d.dll manages in the sim. All i can think of is the NVidia drivers i am using, which are 305.53. Any suggestions?

Faulting application name: Prepar3D.exe, version: 1.4.4747.0, time stamp: 0x50253a53
Faulting module name: g3d.dll, version: 0.0.0.0, time stamp: 0x50253ab4
Exception code: 0xc0000005
Fault offset: 0x000603d0
Faulting process id: 0xd64
Faulting application start time: 0x01cd80457cd75e87
Faulting application path: C:\Prepar3D\Prepar3D.exe
Faulting module path: C:\Prepar3D\g3d.dll
Report Id: ca378aa6-ec3a-11e1-b546-50e549ef9eac

Hi,

i have either crashes caused by the g3d.dll, but sitll more caused by the terrain.dll.

Just now 2 crashes by g3d.dll and 5 times by the terrain.dll.
Sim crashed in minutes. Coudn't even finish the start-up-procedure of the Dodo- Bell 206

Didn't had these problems in 1.3.

Some Addons are installed: German Airfields 1 & 2, VFR Germany 1 & 2 Lama X and DodoSim 206.
There were no probs in 1.3.
Wondering, if it could correlate whith the new updated version?

@ Jan:
What do you mean with FSUIPC 4850?
Has it to be installed?

Greetings
Marcus

Quote from janvaane on August 22, 2012, 09:22
Installed FSUIPC 4850? Run Windows update?

I have installed version 4884 and there were no g3d.dll crashes with version 1.3. Windows all up to date. I even rolled back the updates i did prior to the crash to see if any crashes occured but no luck.

also when you get a crash check the fsuipc log to see if there is anything in there.

is anyone at LM able to answer this ?

Hi,

Nothing changed between 1.3 and 1.4 should have introduced a g3d (graphics) or terrain error. It would be extremely helpful if you can reproduce the issue without the add-on content and applications. Additionally, if you updated from 1.3, you could have remnants of add-ons that could be triggering problems if you did not clear out all old files before installing 1.4.

Let us know if you see the issue without the third party content and we will try and recreate the issue here.

Have a good one,
Adam

Hi Adam,

Are advanced ( More detailed ) crash logs any good to you ?? I have not started clean testing yet but im just trying to get some more data together and test certain things

Here is the beginning of it as its a big report ( 1.03 meg )

General Exception Information:
Operating System: Windows 7 Ultimate (6.1.7601)
Report Time: 01/09/2012 22:15:59
Process Filename: H:\Prepar3D\Prepar3D.exe
Process ID: 4924
Thread ID: 184
Process Description: Lockheed Martin Prepar3D®
Process Version: 1.4.4747.0 (Prepar3D.20120810-1207)
Process Company: Lockheed Martin®
Product Name: Lockheed Martin® Prepar3D®
Product Version: 1.4.4747.0 (Prepar3D.20120810-1207)
Crash Address: 651DA67D
Crash Address (Relative): g3d.dll!Ordinal11+0x8f7d
Exception Code: C0000005
Exception Description: Access Violation - Failed to access 016FCC43 memory address (Read Access)
Exception Parameter (1): 00000000
Exception Parameter (2): 016FCC43
Crash Code Bytes:
8B 3E 8D 04 5B 8D 14 82 83 EA 0C 49 39 3A 74 09
85 C9 75 F4 8B 45 FC EB 30 8B 56 04 8B 45 FC 8D
7C 32 08 3B F8 77 3B 85 D2 74 1E 8B 55 08 8D 0C
49 8B 7C 8A 04 8D 0C 8A 8D 56 08 89 17 8B 49 08

There is lots of other stuff which i dont understand in the report.

Paul

G'day all, a bunch of amateur "fault busters" are trying to get a handle on this problem. I recently got a g3d.dll crash on touch down at YLVT. Flew the same route twice more and each time got CTD at the same spot. Switched from Orbx to Default scenery, no crash. I suggest it may help the teams at P3D and Orbx if we can identify the precise location where the CTD occurs and what if any third party software is running at the time. eg: Orbx, Active Sky. etc.