Crash at PHNL

[airforce806]

I am unsure if the FSDT PHNL scenery is causing but I thought a post here is worth a try.  I don't have any other crashes in FSX or with any of my other FSDT airports.  On approach into PHNL I get the following crash everytime.

Problem Event Name:   BEX
Application Name:   fsx.exe
Application Version:   10.0.61472.0
Application Timestamp:   475e17d3
Fault Module Name:   StackHash_ab46
Fault Module Version:   0.0.0.0
Fault Module Timestamp:   00000000
Exception Offset:   74d5c9f1
Exception Code:   c0000005
Exception Data:   00000008
OS Version:   6.1.7601.2.1.0.768.3
Locale ID:   1033
Additional Information 1:   ab46
Additional Information 2:   ab46b3b696c4386cb918452ef6a6a6e5
Additional Information 3:   3e3d
Additional Information 4:   3e3d69af832149c5f47c99a386ac7394

I have uninstalled and reinstalled the scenery, as well as installing the Stand alone manager.  I have just this week reformatted and reinstalled Windows 7 with just fsx and my fsdt airports to see if this would fix the issue.  However, upon descent, I received the following crash once again.  When this crash happens FSX just completely shuts down.  Any help would be great.  If the scenery is not the issue I will try and post elsewhere to find some help.

Thanks!

[virtuali]

That event code seems to be a general memory allocation problem.

A scenery can't cause this by itself, it might simply possible you have too many addons in that area OR too high settings OR, you have a problem with one of the AI (missing or corrupted texture), on a model with a livery that doesn't appear anywhere else, so you are mislead thinking the problem might be the scenery, because you don't see the crash anywhere else.

Try it with AI at 0% and see if it changes.

[airforce806]

Umberto, thank you for the reply. I have disabled the AI scenery and as soon as I hit 10 miles out for PHNL I received the following.

Problem Event Name:   APPCRASH
Application Name:   fsx.exe
Application Version:   10.0.61472.0
Application Timestamp:   475e17d3
Fault Module Name:   g3d.dll
Fault Module Version:   10.0.61472.0
Fault Module Timestamp:   475e180c
Exception Code:   c0000005
Exception Offset:   000583df
OS Version:   6.1.7601.2.1.0.768.3
Locale ID:   1033

I have the paid version of FSUIPC installed.  It appears as if during the load phase of the scenery it was triggered.  However perhaps it was not, I am not quite sure.  Any thoughts?

[virtuali]

Well, 10 NM out is consistent with the scenery loading area but, that doesn't mean the scenery it's the cause either. Maybe you simply have too few memory (or video memory) left, and as soon the scenery was loaded, it simply wasn't enough.

If the scenery had a problem, everyone should noticed it just the same. I've just checked it again now, both by enabling the ShowMissingTextureAlert=1 feature in FSX that would alert if there's a missing texture somewhere AND by enabling the FSUIPC log, that tells when FSUIPC is trying to fix a G3D.DLL.

There were no missing texture alerts, and no message from FSUIPC that even a single G3D.DLL crash might have happened and it tried to fix it, nothing at all, and I've went back and forth many times in and out the 10 NM threshold, forcing many scenery loads/unloads and stressing it on purpose just to make it intentionally crash, but nothing and no warning messages of any kind, from FSX or FSUIPC either.

You might use the free Process Explorer utility, and check the memory allocation for FSX.EXE when you load PHNL, that would give you an idea what's happening.

[airforce806]

Ok, I will give that a shot.  It is appearing to be a memory error I believe as well.  I have had PHNL up and running without a problem before so I will test and see what I find.

Thanks