g2d.dll with terrain.dll following straight after ctd fsx

[Kimber 8]

Hello All,

 

I have a very confusing situation in FSX and I can't quite get my head around the issues.

 

I have been using FSX in the same config as I have now (with the same software and hardware) for at least six months. According to my private log book thats 344h in the PMDG B77W alone.

 

On Saturday while flying from EGLL to SKBO I suffered a CTD event 63 minutes from landing - with the following errors being displayed by windows:

 

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: fsx.exe
  Application Version: 10.0.61472.0
  Application Timestamp: 475e17d3
  Fault Module Name: g2d.dll
  Fault Module Version: 10.0.61472.0
  Fault Module Timestamp: 475e180c
  Exception Code: c0000005
  Exception Offset: 0008408c
  OS Version: 6.0.6002.2.2.0.768.3
  Locale ID: 2057
  Additional Information 1: f3b5
  Additional Information 2: 67157acfc10691bf1c01accd62406c5a
  Additional Information 3: b4f4
  Additional Information 4: 686b80d14c6be7494511e7ba36846343

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

 

HOWEVER when I clear this failure another is shown (as per below)

 

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: fsx.exe
  Application Version: 10.0.61472.0
  Application Timestamp: 475e17d3
  Fault Module Name: terrain.dll
  Fault Module Version: 10.0.61472.0
  Fault Module Timestamp: 475e180d
  Exception Code: c0000005
  Exception Offset: 00055a3e
  OS Version: 6.0.6002.2.2.0.768.3
  Locale ID: 2057
  Additional Information 1: c19e
  Additional Information 2: c40584a475c3f8555bbaab9ef93905b4
  Additional Information 3: ee42
  Additional Information 4: 84e5bf5eb2ce4166443ef41916b880ce

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

 

I reset the flight and started again, and once again 63 minutes before landing boom CTD with the same two errors as above (when I click the windows close programe and check on line etc the second error message comes up as well).

 

I tried for a third time and yep CTD 63 minutes before landing.

 

I then aborted trying to fly that flight and went to set up the return leg, SKBO to EGLL. This time I can't even get as far as loading FSX fully. Once I have selected the aircraft (PMDG 77W BA), airport (SKBO stand 25) and the weather (Active Sky Next) after three minutes CTD with the same two errors above!

 

I have tried loading a non PMDG aircraft into SKBO and it still crashes with the same two errors and I have also tried not using Active Sky Next - it still crashes as set above.

 

If I load any other airport all is fine! It seems be an issues around that airport.

 

I do not have any third party airports and I have not had any other crashes.

 

Any suggestions?

 

Kimberly RJ.

[Jim Young 2,356]

I do not have any third party airports and I have not had any other crashes.

Starting on page 9 of the AVSIM CTD Guide, you will find known/probable fixes for FSX crashes. The terrain.dll crash represents high settings. The g2d.dll handles plain text messages within FSX.

 

You say you have no third party airports but I want to make sure. Do you have the commercial version of EGLL? That airport is extremely resource intensive. The default textures and airport scenery is pretty bad and a lot of people upgrade the area for some eye-candy. Usually you can run fsx with default textures and programs at max settings with the latest computer system technology.  It is when you install commercial aircraft and scenery that fsx will begin to have issues.  If your settings are set too high, FSX cannot call and render textures fast enough. You should try removing your fsx.cfg to a temporary folder, restarting FSX, and letting the config rebuild. Once rebuilt, just make some very minor changes to your setup. For instance, make sure the resolution under the General tab is set to the resolution of your monitor. Make sure Anti-Aliasing and Anisotropic filtering is ticked and turned on. Do not mess with the Scenery tab whatsoever. The default settings are what FSX has determined to be the best settings for your computer system. Of course it is never right but it is close. 

 

A lot of individuals tweak their FSX.cfg with things like BufferPools and AffinityMask and they put in the wrong settings and these "tweaks" cause many crashes.  It is another reason why I suggested to rebuild your FSX.cfg.  It gets rid of the bad tweaks.  I know ASN throws in the AffinityMask tweak and I see no reason why you should allow that to happen.

 

Make sure you installed FSX, started it up and ran it once, then installed SP1, ran FSX at least once, and then installed SP2.  SP1 contains updated and optimized textures that replaced the default textures.

 

The AVSIM CTD Guide also has some guidance for freezes during a flight that you might want to check out on page 12.  At the beginning of the guide there are some suggestions for investigating the crashes and how to do it.

 

Monitor VAS as suggested on page 3 of the guide.  You may not run out of Virtual Address Space (VAS) during a flight, but you may run low on VAS remaining and, when a program is calling for textures, it may temporarily run low on VAS and, if there is no freeze or crash, the amount of VAS will get larger.  Microsoft Windows only gave everyone 4GB's of VAS for each application.  When it is gone or gets very low in space, the application will crash or freeze.  There are many more suggestions on checking out your system and FSX with guidance on how to do each.  I found the solution to my freezes at the exact spot on the flights by running Process Monitor during a flight and determined it was an AI in MyTrafficX that caused the crash.  Evidently it had no flightplan and the system was calling for it and couldn't find it so FSX froze up at the same spot every time.  But that caused another error not related to yours so I doubt that is your problem.  Still there is the tool you can use if you want to investigate further.  I wish I could say what setting or tweak or texture or aircraft that caused your crash based on the module that caused it but that is impossible even for the computer experts.

 

Hope this helps.

 

Best regards,