maniamcool Posted June 6, 2013 Report Share Posted June 6, 2013 Started getting this error couple of days ago while flying from LOWW-TNCM in the PMDG 747.. I did some research and found out that FSUIPC fixes this problem but apparently for my case it didnt. Here's the error log I gathered from Event Viewer: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58 Exception code: 0xc0000005 Fault offset: 0x0008dc04 Faulting process id: 0xb08 Faulting application start time: 0x01ce62cd2a7e0a47 Faulting application path: D:\FSX\fsx.exe Faulting module path: D:\FSX\g3d.dll Report Id: cb08e11f-cec2-11e2-abd9-003067b9c1a3 I have also installed OpusFSX, REX, FSC, FSpassengersX and Ultimate Traffic 2. Help! Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 6, 2013 Report Share Posted June 6, 2013 I did some research and found out that FSUIPC fixes this problem but apparently for my case it didnt. No, it doesn't. I don't think you completed your research. The only one which is "fixable" is a relatively common one which just happens to be in an easy place to patch, a routine which returns an easy "true" or "false" result -- and not one where aborting the code sequence can yield non-crash results. The offset in G3D of your crash is not that one I'm afraid. There are a lot of crashes reported in modules like G3D, and most are simply not avoidable or recoverable without eliminating the cause -- in the case of G3D it is almost always something not quite right in the scenery somewhere. Pete Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now