Hello,

 

Looking for a little guidance here. I run a i5 overclocked to 4ghz with 8Gig 1600 ram and windows 7 home 64 bit.

This is the 3rd time now where I have been proposing to fly the NGX and am going thru the preliminary cold startup routine. I have the FMC open in its popup mini window (Full screen 1920x1080). I input the start airport and am going thru the initial info before planning the route - when ban - quit to desktop.

 

Now I am not a novice in this field so would request a pointer as to where I can start troubleshooting please.

Looking through the event viewer I found this error that corresponds to my last sudden exit from FSX

 

Faulting module path: C:\FSX\SimObjects\Airplanes\b747_400\panel\GPWS_Sound.GAU

 

Now my question is - what the heck has the B747_400 GPWS Sound Gauge got to do with the PMDG 737 ?

 

Does this load automatically even though I never fly the default 747 anymore and does the PMDG 737 actually use this gauge ?

 

Any help or pointer appreciated.

 

Many thanks

And just to throw in another toothless gear, it quit again after I tried to ALT ENTER. This only appears to happen using the NGX. Getting frustrating..... And I was two thirds of the way thru a flight after successfully programming the FMC this time - so maybe the FMC was a red herring. Anyway, like I said in my first post.. anyone point me in the investigative direction?

Ray,

 

My first question to you would be are you running FSX as an administrator?

 

R/ Pete McMahon

yes - sure am

Now I am not a novice in this field so would request a pointer as to where I can start troubleshooting

 

Noted, but some obvious questions spring to mind.

 

Do these CTD's display any error message, or are they the kind which dump you immediately to the desktop, and FSX just vanishes?

 

Do you have any more examples from your event viewer, and does the same error present itself more than once?

 

What other add-ons do you use with the NGX, i.e. weather, FS2Crew, MCE, FSUIPC, etc. and are they all up to date?

GPWS_Sound.GAU is certainly not a 'module'. A module has an extension of a .DLL

 

Please report your ENTIRE crash report back, so we can take a look at some other information.

In Reply to the above

 

Summer1 - Doing my best. Have you any suggestions

Tipitout - Thanks for your questions so far and to answer them best I can

 

It is an unceremonious dumping to the desktop - just poof - quit and fsx vanishes - yes sir those type.

 

The event viewer is a bit hit and miss - sometimes captures the application error -sometimes not - as in the last case.

I decided to scratch the Even Viewer and start over from yesterday - that way it will hopefully become immediately obvious if an error springs

 

The other add-ons I have installed in FSX are;

unregistered FSUIPC. (Just the basic)

Accufeel version 2.0

FS Captain

Ultimate Traffic 2

FSDT Ground handling

I have uninstalled EZdok again

Orbx sceneries

Shader

GEX (just cloud and sea textures in HD)

I usually run FSRealWx Lite freeware - external programme for real world weather

And I don't know if this is running or not?

VasFMC - can't remember anything else about this program or why I installed it.

 

Thanks for all your help so far

Ray,

 

I had a similar problem when I first got the 737ngx. I was running it on an old machine in my case it ended up being the antivirus kicking off a scan or both windows and the antivirus deciding they needed to download updates. I built a new rig which helped greatly but the antivirus doing its thing can still cause problems. Before I launch FSX I turn off the live scanning feature of the Antivirus. Just a thought.

 

R/ Pete McMahon

GPWS_Sound.GAU is certainly not a 'module'. A module has an extension of a .DLL

 

A .gau is also compiled C++ just like a .dll. I don't know why they called it a .gau. I know of no reason why a .gau couldn't be a faulting "module" just the same as a .dll.

To quote the SDK a .gau is actually a windows dll with the .gau extension. The extension is the only difference.

When it comes to crashes and crash reports, the crash report will never say the "faulty module name" as a .GAU.

 

Ray Hughes, does this problem only happen with the NGX? Or does it also sometimes happen when you are trying to go back to the flight menu for example?

 

Do you have ENB installed? This could be a cause.

Have you tried applying stability tweaks? It is always worth a try for these types of crashes.

 

Two essential stability tweaks many people recommend are:

HIGHMEMFIX=1 in FSX.cfg, which largely eliminates aircraft graphics rendering (“skeleton”) issues.

UIAutomationCore.dll in the FSX main folder, which largely eliminates memory insufficiency/usage errors (e.g., after long periods of flight, using menus too frequently, etc.).

 

The latter is probably more relevant to your issues. For specific instructions, please reference the appropriate sections of Word Not Allowed's Guide (use Find in your browser).

In reply to all the above;

 

I am running Microsoft security essentials and have as an exception FSX

I Do not use ENB - but I have recently installed sweetfx.

I do have the HIGHMEM fix but have shied away from UIAutomationCore.dll but am willing to readdress this.

 

Ray

I do have the HIGHMEM fix but have shied away from UIAutomationCore.dll but am willing to readdress this.

As long as you use an appropriate version, you should not run into problems. Addition and removal of the file from the FSX root folder is easy, so the tweak is conveniently reversible should you experience issues.

 

but I have recently installed sweetfx.

 

 

Remove it. And test it out.