HI

 

I have had a stable system running FSX on WIN 7 64 with active sky 2012 my traffic 5.4b and pmdg ngx. I have the latest registered version of fsuipc. In the last month I have had two ctd's, the first was unknown and the second a g3d.dll. I would be grateful if anyone can help with this. I have posted on the fsuipc forum and Pete suggested posting here.

 

<Provider Name="Application Error" />

  <EventID Qualifiers="0">1000</EventID>

  <Level>2</Level>

  <Task>100</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2013-08-17T13:13:52.000000000Z" />

  <EventRecordID>22635</EventRecordID>

  <Channel>Application</Channel>

  <Computer></Computer>

  <Security />

  </System>

- <EventData>

  <Data>fsx.exe</Data>

  <Data>10.0.61472.0</Data>

  <Data>475e17d3</Data>

  <Data>g3d.dll</Data>

  <Data>10.0.61472.0</Data>

  <Data>475e180c</Data>

  <Data>c0000005</Data>

  <Data>0003e5f7</Data>

  <Data>6a0</Data>

  <Data>01ce9b3f654b8b8f</Data>

  <Data>D:\fs\fsx\fsx.exe</Data>

  <Data>D:\fs\fsx\g3d.dll</Data>

  <Data>dc56b50c-073e-11e3-905b-14dae9041e19

 

latest version of FSUIPC can help this http://forum.simflight.com/topic/66139-updated-modules/

 

Sorry, now i see that you actaully have the latest version However, try to re-install, FSUIPC can easilly be overwritted by some addons or get corupted 

Edited August 17, 201312 yr by B247NG

 

 

In the last month I have had two ctd's, the first was unknown and the second a g3d.dll.

 

Some g3d.dll errors can be fixed with the latest fsuipc.dll and I see you are well aware of that fact.  Obviously, you got an error that could not be trapped.  One individual got the g3d.dll crash after updating the NvidiaInspector and changing some NI settings.  He went back into the NI and changed the display driver settings back to the default and the problem went away.  There is no known solution to the g3d.dll error other than what was done by the developer of the fsuipc.dll.  It's related to system memory and I suspect high fsx/display driver settings.  Usually an unknown faulting module will indicate you are close to getting a BEX (Buffer_Exception_Overrun) and StackHash crash which is also not fixable with a "magic bullet". 

 

Try downloading and running AppCrashView - http://www.nirsoft.net/utils/app_crash_view.html and copy the error data in the lower section and paste the results here.  It provides a lot more information than the Microsoft crash report (.wer).  It looks like the info you provided above is from the Event Viewer which is useful but does not provide a complete report of the crash.

 

Some have solved fsx ctd's by uninstalling SP2, running FSX, then reinstalling SP2.

 

If you are overclocked, you should bring your overclock back to the default settings (save your current overclock settings first if you can).  If you have any tweaks in your fsx.cfg, save your fsx.cfg to fsx.orig then restart fsx and let the config rebuild.  This procedure has fixed a lot of problems. 

 

Posting your system specs like Zeljko and I have done in the sidebar would help too.

 

Best regards,

Jim

Jim

 

Many thanks for your reply it has given me a better understanding of were the problem maybe coming from. I had indeed changed my Nvidia settings a couple of months ago so I think I will start here. My system is also overclocked so I can also take it back to the default. I will download the AppCrashView and post in that format in the future. I have let fsx.cfg file rebuid recently so I may be able to rule that out.

 

I have added my system specs to my profile as well.

 

Many thanks again to both yourself and Zeljko.

 

Kind regards

 

Aidan