I let the aircraft sit at KLAX (FSDT and Mega So cal sceneries) and went to bed, checked this morning.. I had a pop up with an out f memory error message.

 

Windows Task Mgr shows Free Memory = 22. What does that "free memory" mean? Is that the problem? Any ideas?

 

I also have HIGHMEMFIX=1 in my fsx.cfg. I have a Total 8GB memory. a GTX 670 with 2GB (Running 3 X 24 Dell) surround view.

 

Manny

 

FSX run out of memory. It can alocate up to 4GB of memory. Nothing to do with physical RAM.

Do you have your LOD set higher than 4.5 in the fsx.cfg?

My LOD is the max within FSX. I did not do any cfg changes to LOD

 

Manny

 

I doubt its even using the 4GB

FSX run out of memory. It can alocate up to 4GB of memory. Nothing to do with physical RAM.

Do you have your LOD set higher than 4.5 in the fsx.cfg?

 

Do you think it maybe because of too small a Pagefile?

 

Manny

I notice that the Cached and Available memory in Win Task mgr never goes beyond 2000. Does that mean, its using only 2Gigs of memory?

Anyone know how to set this? I believe FSX was complied with Large address aware thingi.

 

Memory type Limit in 64-bit Windows

User-mode virtual address space for each 32-bit process

 

2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)

4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set

Manny

 

2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)

4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set

 

These figures are not what is reported in Task manager, they relate to the Virtual Address space (VAS) set by Windows - which cannot be altered upwards in a 64-bit OS ie it is alreadty set at 4Gb. In a 32-bit OS using the /3G flag you can increase the VAS from 2GB to 3GB and these the MAXIMUM values and cannot be altered upwards. They are not related to any PHysical RAM installed or the size/location of the paging file. Free memory will always be a fairly low figure due to the way superfetch/prefetch operates in a Windows OS.

 

The important one on your screenie above is the 'available' memory which was pretty low considering you have 8 Gb on board. That error message indicates that you are running low on Physical RAM due to some other processes -(bearing in mind that FSX can address a maximum of 4GB of Physical RAM). It does not indicate any issue with the VAS. It should be noted in a 64-bit OS windows 7 itself can access several terabytes of VAS and so is unlikely to interfere with the FSX VAS.

So something running side by side with FSX - another exe/dll file(s) may be depleting the Physical RAM - the message tells you that the system is now probably accessing the paging file and needs you to turn something off or down in order to conserve physical RAM and performance.

You may want to try a clean boot (google to see what I mean) and then see if the figures change when you run FSX.

Regards

pH

Manny

 

 

 

These figures are not what is reported in Task manager, they relate to the Virtual Address space (VAS) set by Windows - which cannot be altered upwards in a 64-bit OS ie it is alreadty set at 4Gb. In a 32-bit OS using the /3G flag you can increase the VAS from 2GB to 3GB and these the MAXIMUM values and cannot be altered upwards. They are not related to any PHysical RAM installed or the size/location of the paging file. Free memory will always be a fairly low figure due to the way superfetch/prefetch operates in a Windows OS.

 

The important one on your screenie above is the 'available' memory which was pretty low considering you have 8 Gb on board. That error message indicates that you are running low on Physical RAM due to some other processes -(bearing in mind that FSX can address a maximum of 4GB of Physical RAM). It does not indicate any issue with the VAS. It should be noted in a 64-bit OS windows 7 itself can access several terabytes of VAS and so is unlikely to interfere with the FSX VAS.

So something running side by side with FSX - another exe/dll file(s) may be depleting the Physical RAM - the message tells you that the system is now probably accessing the paging file and needs you to turn something off or down in order to conserve physical RAM and performance.

You may want to try a clean boot (google to see what I mean) and then see if the figures change when you run FSX.

Regards

pH

 

When I bootup and I see Available memory is clsoe to 5GB.. and then when I load FSX, it kind of remains at 4GB and then after a few hrs, its down to like 1600.

 

So not sure what is happening

 

I see this comment in the old Phil Taylor's blog

 

"

Games under 64 bit Windows would only run into this issue if they use the IMAGE_FILE_LARGE_ADDRESS_AWARE flag. 32 bit executables with this flag get 4GB address space in Win64, while those without the flag continue to have only 2GB.

 

If the game is 64 bit it would be linked against the 64 bit D3DX which"

 

 

http://blogs.msdn.co...ress-space.aspx

We really don't know who authored that comment on Phil's site. Plus pretty old info. Memory management has become much better since the early days of Vista. I heard Windows 7, 64 bit can manage memory better than in previous systems. I personally keep my virtual memory (page file) setting to 'System Managed Size' instead of setting up your own. This has fixed a lot of problems some people have experienced with 64 bit OOM's. Your settings are too high too. There are some memory eaters in the FSX.cfg like Autogen, Aircraft AI, Cars, and Ships. FSX is an old 32 bit application and I think is having issues rendering with these really fast systems. Microsoft Flight runs much better with max settings on a 64 bit system. Those are my settings for Flight and so far I have had no problems. Perhaps Prepar3D folks who have the FSX code can make it better. You might be having issues too with the frequency, timings, and voltages for your memory. I have also seen crashes like this with too high CPU voltages. Hope you can find a solution Manny!

 

Best regards,

Jim

Hi Jim.

I have also seen crashes like this with too high CPU voltages. Hope you can find a solution Manny!

 

Hi Jim.

 

My memory is GSkill Trident 2400 but its running sub 2000. It would not boot if I increase the freq any further. But since I have my IB Processor OC to 4.5 at 1.25v I am ok with it.

 

One thing I need to mention is, the aircraft that I had was the F1 Coolsky MD80. I love this aircraft (in the sim for hand flying and landing. I remember 3 or 4 years ago that this aircraft had some texture overuse of memory? or some issue. So today I plan to try to do the same thing but use another aurcraft to see if I have memory issue

 

Manny

I get OOM's @ KLAX + NGX all the time... never sure of the reason other than virtual memory..

That's weird. I flew in and out of KLAX with NGX couple of times, my LOD is 6.5, never seen an OOM.

 

I would suggest using Process Explorer to view the Virtual Size of the FSX, thus really seeing what's going on, if it's really a classic OOM.

Does keeping a browser like Google Chrome open create problems. I noticed when I kill the Chrome, I get back memory into the "Available" bucket. I thought it shouldn't/

 

Manny

Word Not Allowed

This is not a typical VAS OOM issue , Manny is actually using all of his physical RAM for some reason.

I haven't got a clue why that is happening but you are right ProcMon and Process Explorer (and even PERFMON - built in win 7) could tell you what is causing the issue.

If it was a VAS OOM - FSX ONLY would crash but this is a System wide issue

To start in Perfmon I would look at:

PERFMON and Memory Leakage

 

If you ran PERFMON with the following performance counters for the application ie FSX as above:

Note: Perfmon is not the easiest of MS apps to run or interpret)

Counter: Process/Private Bytes,

Counter: .NET CLR Memory/# Bytes in All Heaps, and

Counter: .NET CLR LocksAndThreads/# of current logical Threads.

Performance Object: Memory

Counter: Pool Non-paged Allocs

Counter: Pool Non-paged Bytes

Counter: Pool Paged Allocs

Counter: Pool Paged Bytes

 

In the case of a memory leak you would see:

If an application's logical thread count is increasing unexpectedly, thread stacks are leaking.

If Private Bytes is increasing, but # Bytes in All Heaps remains stable, unmanaged memory is leaking.

If both counters are increasing, memory in the managed heaps is building up.

If it is not due these then you would then have to look at other counters to see what is going on.

Beyond that it is a steep learning curve to see what is actually going on and even with XPERF it is sometimes difficult to pin down the cause of an issue like this.

I have written a small paper on how to use PERFMON and one day I'll get around to finishing it

Regards

pH

It looks to me like an FSX specific crash Peter. Look at the box: "[...] Please restart Flight Simulator and select different graphics, scenery or traffic settings"

Besides, there are 1404MB of available RAM there plus the paging file to allocate physical memory

 

Does keeping a browser like Google Chrome open create problems. I noticed when I kill the Chrome, I get back memory into the "Available" bucket. I thought it shouldn't/

 

Manny

 

When you close an application, it's allocated RAM goes to the Available bucket, meaning that the data is still there, but those pages are available to other apps that might need it. If you opened Chrome again, those pages would be already in memory and wouldn't need to be loaded again