But why oh why turn up the settings everytime there´s new hardware on the block, then you´ll just "elevate" the problem, right?

Strangely enough, yes... We're already running FSX with tweaks that weren't supposed to be possible. We're going outside the normal operating limits. There are some addons made per the SDK, but many newer ones stray far from it and use their own methods. I believe that's where the trouble starts coming from. In the meantime, I've simply created a saved .cfg file to load when in operating near big cities in Orbxland.

Based on ongoing OOM, BSOD, CTD's ...whatever, I digged in to the past posts and gave it a try to get the events visibleRead the full story and (my) resolution HERE

Yes OOM is about virtual memory, not RAM. You can't use the task manager to monitor it. Try Process Explorer and compare

I'v got process explorer finally and what value describes virtual memory?

Set it up like this: EDIT: Dario, I notice you are using "virtual memory" for your explanations of virtual space or virtual size in PE (or VAS even). While I know what you're talking about, I think others are misunderstanding you. Or not? We are both trying often very hard to explain the difference between virtual memory and VAS.

Just my 2 cents here, one thing I found out about screwing FSX up or getting OOM is (in my case ) due to tweaking, I am as guilty as all of you as far as trying to find the right tweak, I tried this and that + other stuff, I am now running on W7 64-bit with no tweak what so ever in fsx.CFG but TBM at 120 and that's it, I am also maxing out the scenery and use some good payware plane like the Carenado CT 120M Centurion. I have not had any error or problems since then, I stoped tweaking, I should mention that I am also flying using DX10 only, here... I just made a small vid. just to show how far one can push the scenery (in this case maxed out) with a good payware plane, no ENB as it does not work in DX10 and no FPS limiter (placebo IMO) just REX and Orbx scenery, FPS at unlimited and Lignt bloom enable... I know it's a sacrilege but the flying is so much more fun...

So IMHO, if you want problems with FSX you start tweaking the fsx.CFG...

Alain, while I can only congrat you, you must bear in mind that what you are running here is so called low and slow.Ryan is running NGX, which is FAR more commanding on the computer than Carenado's Centurion.Also when you climb out more, say some 10,000ft and above, and you see the scenery with LOD 4.5, it is starting to get ugly.For your needs, it's definitely enough. And no, OOM has nothing to do with tweaking, ONLY with FSX using more memory than on default. It's using more if you tell it. And the only tweak telling it that is LOD.Other parts are heavy scenery, aircraft, AI etc... or a faulty installation.

You are right Word Not Allowed, raising the LOD will make the scenery look sharper at high altitude but how far and sharp can you see in real life flying....the other side of the coin is that with a high LOD you'll get more blurries at low altiture, I tried it, you can push the LOD up to 9.5 if you want to but the hardware "aint gonna follow" and that's the problem.

Set it up like this: EDIT: Dario, I notice you are using "virtual memory" for your explanations of virtual space or virtual size in PE (or VAS even). While I know what you're talking about, I think others are misunderstanding you. Or not? We are both trying often very hard to explain the difference between virtual memory and VAS.

Not sure what you mean I just said that OOMs are related to virtual memory as opposed to physical memory. The amount of virtual memory used by a certain process is shown in that "virtual size" column, yes

You are right Word Not Allowed, raising the LOD will make the scenery look sharper at high altitude but how far and sharp can you see in real life flying....the other side of the coin is that with a high LOD you'll get more blurries at low altiture, I tried it, you can push the LOD up to 9.5 if you want to but the hardware "aint gonna follow" and that's the problem.

Sure, going 9.5 is going to make FSX crazy. But I found out that 6.5-7.5 gives very nice results, both keeping my FSX under the OOM limit (6.5 is any case, and 7.5 is pushing it a bit, my setting btw) while having really way better graphics in FSX than on default. IMO MS should have set 6.5 as high setting.And I know, there is more haze in real world, but something FSX can't really display. Thus the only way is keeping it sharp, as it is on really clear day up there - oh btw. one flight I did, it was really clear, I was amazed.

I just said that OOMs are related to virtual memory as opposed to physical memory.

Now you are up. Am I misunderstanding you and understanding that you mean windows virtual memory (aka swap) has something to do with VAS and has nothing to do with physical memory?

Am I misunderstanding you and understanding that you mean windows virtual memory (aka swap) has something to do with VAS and has nothing to do with physical memory?

But virtual memory is the general concept, swap space (page file-s) is the portion of the disk where the pages go when the Virtual Memory Manager pages out, or swaps out an entire processVirtual Address Space is the same as Virtual Memory Size (of a process, the whole system, etc...)

Rather than continuous explaining, read the full articles about How memory is managed in OS and what to do to prevent OOM Measuring is knowing, when you know what you measure... so select Start type "reliab" (without quotes) in the Search program and files field, enter and be amazed which disasters passed your system the last days or weeks..

That's not necessarily going to stop OOMs. Your page file size should be around 1.5x the amount of your RAM. You can still get OOM errors, even with a 9GB pagefile.

Rather than continuous explaining, read the full articles about How memory is managed in OS and what to do to prevent OOM Measuring is knowing, when you know what you measure... so select Start type "reliab" (without quotes) in the Search program and files field, enter and be amazed which disasters passed your system the last days or weeks..

Jan, you may want to reconsider your link to advancepctweaking tool from your website as it is banned by my Eset anti virus for being a dangersous site. You may also wish to consider commenting directly on these forums with your personal experiences and advices. A large part of our interaction here carries a social as well as a technical component. Your self promotion to your website is becoming distracting and boarders spam. A nice website by the way, some parts are interesting while others I consider pure hogwash.

But virtual memory is the general concept, swap space (page file-s) is the portion of the disk where the pages go when the Virtual Memory Manager pages out, or swaps out an entire processVirtual Address Space is the same as Virtual Memory Size (of a process, the whole system, etc...)

As I understand it:Physical memory is used by OS, which also extends onto disk if you don't have enough RAM. The reason also why you can get away without swap if you have enough physical memory.VAS is a process memory. The >virtual< space used by an application.OS uses the physical memory to map data from files to VAS.A page table is kept as a reference for data to translate their virtual addresses into physical addresses.Concerning Virtual Memory Manager, yes, it's there so the physical memory doesn't get filled with junk, as I understand it. I think we both know our homework

Yes, that's how I understand it too. It's just that sometimes the page file - swap space is incorrectly refered to as virtual memory