Hi guys

 

I have a reasonable setup. Not cutting edge for sure, but I'm still getting OOMs after a complete reinstall and checking all MS software & drivers etc.

 

It only happens when I'm pretty much hammering the system... All settings nearly maxed except autogen, which I keep a bit lower. This happens always now when using FTX England, UK2000 Gatwick EGKK on approach, with the magical 737NGX by PMDG.

 

Often, I do actually manage to touchdown before it quits, giving the std oom message, but mostly it happens on finals :-(

 

Am I just pushing to hard, or is there a fix? Is this still happening to others also?

 

Thanks

Traffic settings including airport and other ground vehicles? You could try bumping those down a notch and see if your OOMs disappear. How long do your flights last before this happens?

Traffic settings are 44% commercial and 22% GA. Airport, car and boat traffic minimum.

 

The flight I'm for testing is only EGNX to EGKK which is about 120nm only. OOM is always on either final approach or during roll out. Guess I'll have to start dialling stuff back. SOOOOoooo..... frustrating ;-)

what's your LOD setting?

Have just started getting the same Phil, never had it before I installed ORBX EU. such a shame as I love it. VMMAPP is showing 3.9 just as i get the message "Your computer has ran out of available memory"

As Ahmed said above, you should check you LOD setting in fsx.cfg. A lot of people changed this to around 6.5 and can cause you to run out of memory.

 

You may also want to run your fsx.cfg file through Bojote's Tweaking and Tuning tool for FSX here: http://www.venetubo.com/fsx.html. That should fix you right up!

After a complete Windows and FSX reinstall, I'm now getting a crash on exiting FSX with:

Problem signature:

Problem Event Name: APPCRASH

Application Name: fsx.exe

Application Version: 10.0.61637.0

Application Timestamp: 46fadb14

Fault Module Name: StackHash_ac05

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 00000000

Exception Code: c0000005

Exception Offset: 74f4c9f1

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 2057

Additional Information 1: ac05

Additional Information 2: ac0507478d1c5bd693cfc4fe3987e900

Additional Information 3: 8dc1

Additional Information 4: 8dc198dd8745d5fca9891bcc7688f232

 

Any ideas?

Phil,

 

I mainly fly GA and (/so ?) never had an OOM but you could try this if you are running W7-64.

That "fix" didn't make any difference to my own OOM errors. Like Dougal, mine occur in very highly detailed areas, but I guess that's the price you pay for running FSX at maximum detail levels, and with UT2 AI @ 100%....

Are you still experiencing this issue with Stackhash? Unfortunately, when it comes to stackhash errors, they are almost impossible to indentify why you are getting them. Stackhash errors are hardware related, and your exception code was 0x000005 which is a MEMORY_ACCESS_VIOLATION. The only advise I can give you, is to check for updated video card drivers, and updates. If you are using Direct X10 Preview mode, users have reported problems with stackhash errors and the DX10 shader fix.

 

When it comes to your OOM errors, yes, you are pushing your system too hard. Ai traffic is probably your biggest downfall. And the other traffic you say is at "Minnimum". What is minnimum exactly? Even with your system, all of those things are adding up to be too much. Even with 32 GB of ram, I still can't run what you are running. FSX is a 4GB ram program, and I can imagine FSX developers lauging at us loading all of our addons up to this extent and wonder why we are experiencing crashes and oom errors. My advice to you, is to turn your AI traffic DOWN, especially at addon airports. Turn other traffic OFF, and turn your autogen density down.

 

Good luck, happy new year!