Archived

This topic is now archived and is closed to further replies.

kolaf

Help diagnosing a crash problem

Recommended Posts

I am experiencing consistent crashes just north of Seattle in Orbx PNW. Is anyone else able to replicate this? Takeoff from WA96, climb to round 2-3000 feet and head directly to CAN NDB (274.0). No matter my settings and aeroplane of choice, P3D 1.4 always crashes with a simple "P3D has stopped working, should I attempt to restart?" message halfway between the airport and the NDB. Most settings are maxed out except for scenery complexity and autogen which is a few steps down.

 

Any takers?

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Check your Event Viewer and I bet its a G3D.dll error.

The latest version of FSUIPC being installed remedies one form of this crash though Im being plaqued with them in ORBX scenery and wasnt with version 1.3. Really cheesed off at the moment

Share this post


Link to post

Has anyone bothered to ask ORBX about this? Does the G3d.dll error occur when ORBX is not installed? Seems to me then it is their problem. The idea is to make the add-ons compatible with the simulator, not vice versa, IMHO.

Share this post


Link to post

Kolaf,

 

Flew the route, took off flew direct to CAN no issues to report. Even spent a good 10 mins or so flying a grid around that midpoint. ORBX PNW, PFJ, CRM and NRM (all installed via Estonia Migrator).

Share this post


Link to post

OK, thanks.

 

The only error I find is:

 

Faulting application name: Prepar3D.exe, version: 1.3.3708.0, time stamp: 0x4f516cc9
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x2200
Faulting application start time: 0x01cd1688b5244905
Faulting application path: F:\P3D\Prepar3D.exe
Faulting module path: unknown
Report Id: 4747a08e-827e-11e1-9d1b-5404a6be1baf

 

Not sure what this means.

Share this post


Link to post

Just checked again, and now I found lots of these:

Log Name:	  Application
Source:	    Application Error
Date:		  9/4/2012 21:27:10
Event ID:	  1000
Task Category: (100)
Level:		 Error
Keywords:	  Classic
User:		  N/A
Computer:	  fsx
Description:
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: 0x000ba67d
Faulting process id: 0x1d64
Faulting application start time: 0x01cd8ad1956176a2
Faulting application path: F:\P3D\Prepar3D.exe
Faulting module path: F:\P3D\g3d.dll
Report Id: 8528b0e2-f6c6-11e1-863d-5404a6be1baf
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="2012-09-04T19:27:10.000000000Z" />
   <EventRecordID>20896</EventRecordID>
   <Channel>Application</Channel>
   <Computer>fsx</Computer>
   <Security />
 </System>
 <EventData>
   <Data>Prepar3D.exe</Data>
   <Data>1.4.4747.0</Data>
   <Data>50253a53</Data>
   <Data>g3d.dll</Data>
   <Data>0.0.0.0</Data>
   <Data>50253ab4</Data>
   <Data>c0000005</Data>
   <Data>000ba67d</Data>
   <Data>1d64</Data>
   <Data>01cd8ad1956176a2</Data>
   <Data>F:\P3D\Prepar3D.exe</Data>
   <Data>F:\P3D\g3d.dll</Data>
   <Data>8528b0e2-f6c6-11e1-863d-5404a6be1baf</Data>
 </EventData>
</Event>

 

 

 

The time before I got this:

Faulting application name: Prepar3D.exe, version: 1.3.3708.0, time stamp: 0x4f516cc9
Faulting module name: ai_player.dll, version: 0.0.0.0, time stamp: 0x4f516cd6
Exception code: 0xc0000005
Fault offset: 0x00036c69
Faulting process id: 0x1328
Faulting application start time: 0x01cd16841d59cf12
Faulting application path: F:\P3D\Prepar3D.exe
Faulting module path: F:\P3D\ai_player.dll
Report Id: ca86735d-827a-11e1-9d1b-5404a6be1baf

 

I have a registered version of FSUIPC, updated to the latest version. Shouldn't this take care of g3d.dll crashes?

Share this post


Link to post
ai_player.dll is a super rare bug, its to do with addon airports and when you see double jetways at airports, if you have orbx pwn go on their forum as there is a thread with a patched version of KSEA which will fix the crash.

Thanks, I'll be sure to do that.

 

Sent from my HTC One X using Tapatalk 2

Share this post


Link to post

Faulting application name: Prepar3D.exe, version: 1.4.4747.0, time stamp: 0x50253a53Faulting module name: g3d.dll, version: 0.0.0.0, time stamp: 0x50253ab4Exception code: 0xc0000005Fault offset: 0x000ba67dFaulting process id: 0x1d64Faulting application start time: 0x01cd8ad1956176a2Faulting application path: F:\P3D\Prepar3D.exeFaulting module path: F:\P3D\g3d.dllReport Id: 8528b0e2-f6c6-11e1-863d-5404a6be1baf

 

You are getting the exact same Fault Offset Code as I am everytime. Going to notify Pete Dowson about it later

 

Chris Ibbotson

Share this post


Link to post

You are getting the exact same Fault Offset Code as I am everytime. Going to notify Pete Dowson about it later

 

Chris Ibbotson

He didn't seem very positive in the recent thread I saw in his forum on the subject. I think we also should report it to the P3D guys in their forum.

13

Share this post


Link to post

ai_player.dll is a super rare bug, its to do with addon airports and when you see double jetways at airports, if you have orbx pwn go on their forum as there is a thread with a patched version of KSEA which will fix the crash.

 

yea i agree since i had the same ctd(although iam using fsx) and always in the same area flying out of cyyr found out it was 2 bgl files that were causing the ctd in fsx, its in the orbox forum if you want to check. The solution was to update the patch or remove the 2 bgl files but it was easier to just install the patch

Share this post


Link to post