CTD coming into Honolulu

[dfreemanfso]

Guys,

I have no idea if this is FSDT related, but thought I'd ask.  It may be LDS 767 related as well, or a combination of both.

I've been running FSX with FSDT and complex airplanes such as PMDG with no issues for many months now. Today I flew from FSDT DFW to FSDT HNL in the Level D 763 with REX, UTX, and GEX. There were no issues until I somewhere around 20 miles from HNL, where I got a CTD. I tried ot reload the flight on the runway in HNL, and got 3 other CTDs in the process. This was my first flight to PHNL in the level D, but the only other change I made is updating REX textures a few days ago.  Plus, I've never had FSX running for 9 hours straight before. Still, after restarting my computer I was supprised I got a CTD at PHNL which would tell me memory isn't the issue. My gut, feeling is taht it is the PHNL scenery, FSDT, LDS, or a combination of both. I had four total errors; 3 of the 4 were g3d.dll, which I know can mean a lot of things.  I an example of each error below.

Just wanted to check with you and see if you've seen anything like this before.

Tomorrow, I'll remove the scenery and try to fly the 767 around a bit to try and isolate the problem down to FSDT, Level D, or something else.
 
I have applied the uiautomationcore fix for W764.
 
Thanks,
 
Dave

Win 7-64, i7 26K OC to 4.4GHz
8GB DDR3/1600 memory
GTX 580 1.5 GB EVGA Superclocked
3 monitor with TH2G

 - <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="2011-12-03T01:15:14.000000000Z" />
<EventRecordID>7483</EventRecordID>
<Channel>Application</Channel>
<Computer>FlightOperation</Computer>
<Security />
</System>
 - <EventData>
 <Data>fsx.exe</Data>
<Data>10.0.61637.0</Data>
<Data>46fadb14</Data>
<Data>g3d.dll</Data>
<Data>10.0.61637.0</Data>
<Data>46fadb58</Data>
<Data>c0000005</Data>
<Data>00059a3f</Data>
<Data>bcc</Data>
<Data>01ccb10a488e218a</Data>
<Data>C:\FSX Main\Microsoft Flight Simulator X\fsx.exe</Data>
<Data>C:\FSX Main\Microsoft Flight Simulator X\g3d.dll</Data>
<Data>40cece37-1d4c-11e1-a585-00268317052a</Data>
</EventData>
 </Event>\
 
- <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="2011-12-03T01:20:02.000000000Z" />
<EventRecordID>7486</EventRecordID>
<Channel>Application</Channel>
<Computer>FlightOperation</Computer>
<Security />
</System>
 - <EventData>
 <Data>fsx.exe</Data>
<Data>10.0.61637.0</Data>
<Data>46fadb14</Data>
<Data>acontain.dll</Data>
<Data>10.0.61637.0</Data>
<Data>46fadb56</Data>
<Data>c0000005</Data>
<Data>000087cb</Data>
<Data>838</Data>
<Data>01ccb15938b6fd96</Data>
<Data>C:\FSX Main\Microsoft Flight Simulator X\fsx.exe</Data>
<Data>C:\FSX Main\Microsoft Flight Simulator X\acontain.dll</Data>
<Data>ec21c9d6-1d4c-11e1-a585-00268317052a</Data>
</EventData>
 </Event>

[virtuali]

There were no issues until I somewhere around 20 miles from HNL, where I got a CTD.

That would safely discount the airport being a problem, since the loading range for all its objects is exactly 10 NM.

The g3d.dll crash is a very well known FSX problem, which is likely caused by simply too many addons installed and/or too high settings. Have a look at this thread, with a possible fix using the very latest FSUIPC (even the free version).

http://forum.avsim.net/topic/353179-gd3dllhelp/

[dfreemanfso]

That's kind of what I was thinking too.

Thanks for your great sceneries.

[johndrago]

Guys,

I have no idea if this is FSDT related, but thought I'd ask.  It may be LDS 767 related as well, or a combination of both.

I've been running FSX with FSDT and complex airplanes such as PMDG with no issues for many months now. Today I flew from FSDT DFW to FSDT HNL in the Level D 763 with REX, UTX, and GEX. There were no issues until I somewhere around 20 miles from HNL, where I got a CTD. I tried ot reload the flight on the runway in HNL, and got 3 other CTDs in the process. This was my first flight to PHNL in the level D, but the only other change I made is updating REX textures a few days ago.  Plus, I've never had FSX running for 9 hours straight before. Still, after restarting my computer I was supprised I got a CTD at PHNL which would tell me memory isn't the issue. My gut, feeling is taht it is the PHNL scenery, FSDT, LDS, or a combination of both. I had four total errors; 3 of the 4 were g3d.dll, which I know can mean a lot of things.  I an example of each error below.

Just wanted to check with you and see if you've seen anything like this before.

Tomorrow, I'll remove the scenery and try to fly the 767 around a bit to try and isolate the problem down to FSDT, Level D, or something else.
 
I have applied the uiautomationcore fix for W764.
 
Thanks,
 
Dave

Win 7-64, i7 26K OC to 4.4GHz
8GB DDR3/1600 memory
GTX 580 1.5 GB EVGA Superclocked
3 monitor with TH2G

Hi Dave,

Do you have (UT2) Ultimate Traffic II installed?

- John

[wb2002]

Hi Dave,

Do you have (UT2) Ultimate Traffic II installed?

- John

Hello John. Is this significant about UT2?

[johndrago]

Hi Dave,

Do you have (UT2) Ultimate Traffic II installed?

- John

Hello John. Is this significant about UT2?

I can't speak for Dave's exact issue yet, but there is a thread in this forum, where myself, and a couple others had issues approaching PHNL, and getting crashes.  After we made a couple changes to UT2 (turned off moving jetways, and turned off GA traffic), all was well.  We believe there was some overload with the amount of traffic generated, as well as the graphic strain to start moving the jetways when the airport was starting to pop into range.

Either way, it fixed both of our issues.  The other most common issue with this type of crash is duel AFCADs.  I didn't have any, but other have.  Here is the thread:

http://www.fsdreamteam.com/forum/index.php?topic=4201.0

- John

[virtuali]

as well as the graphic strain to start moving the jetways when the airport was starting to pop into range.

Not in that case, because he reported a crash at 20 nm, but the loading range for all objects at PHNL is exactly 10 nm, nothing related to the airport is loaded at 20 nm so, it's surely something else, most likely AI-related.

[airforce806]

Everytime I load Honolulu intl I get a crash to desktop.  All other fsdt scenerys are working.  Only when I load honolulu does my sim crash

[virtuali]

Everytime I load Honolulu intl I get a crash to desktop.  All other fsdt scenerys are working.  Only when I load honolulu does my sim crash

I don't see why you are attaching your issue, that doesn't have anything to do with this, with the fact that you (according to your description of the problem) can't load *FSX* after having installed PHNL.

This thread discussed an entirely different problem, since it's discussing a crash *approaching* PHNL, but it has been already established that, since it happens at 20 NM out, it's entirely unrelated to PHNL, and most likely related to AI.

So please, don't confuse other people reading this with your problem, which is entirely different, and please continue on its own thread, posting about the same problem on two separate threads, which one entirely unrelated (and that discussed a problem which wasn't even caused by PHNL in the first place) will not give you more chances to get replied to. Your issue has been already being dealt with, without the need to cross-post in other unrelated threads.

[airforce806]

I figured a crash is a crash in regards to the PHNL scenery and thought both issues perhaps could be linked.