2

I'm currently running Windows 7 Professional 32-bit with 6 GB of RAM.

I use a PAE patch to enable use of more than 3.5 GB of RAM in 32-bit Windows. A similar discussion took place here: How can I enable PAE on Windows 7 (32-bit) to support more than 3.5 GB of RAM?

The link to the patch for Win7 SP1 is here: https://wj32.wordpress.com/2011/02/23/pae-patch-updated-for-windows-7-sp1/

Anyway, long story short, I have the patch installed, but if any of you have played Skyrim may be aware of, the latest version of Skyrim (1.3.10) has the Large Address Aware flag enabled by default to allow it to use up to 3 GB of memory in 32-bit Windows and 4 GB of memory in 64-bit Windows. Of course, to take advantage of this, you also have to set a user environment variable in your BCD entry (userva=3072) to allow the application to use the full 3 GB in 32-bit Windows.

Here's the question: From my understanding from a friend of mine, the 32-bit Windows kernel can only address up to 2 GB of memory for itself. With the PAE patch enabled and using a LAA-enabled application such as Skyrim, would the 32-bit Windows kernel have any problems properly taking advantage of the extra memory available (for example, would it still only be able to address 1 GB because of the original 4 GB limit) or would Windows be able to properly allocate enough memory for itself so that the kernel can use up to the 2GB necessary? Remember, I have 6 GB in my original configuration.

From what I can tell, even if applications aren't designed to work with PAE, one application can still use up to 2 GB before it hits its "limit", so in theory, I can have up to 3 applications using up 2 GB each (pretending Windows isn't taking up any memory, but just a theoretical scenario) and I'd still be fine since Windows is handling where in the memory space these applications are in.

Please feel free to correct me if I'm wrong - I'm not a programmer but I'm kind of curious as to what sort of possible ceilings or walls I'll run into using this configuration.

Community
  • 1
White Phoenix
  • 1,381

2 Answers2

4

The physical memory limits and the virtual memory limits are entirely unrelated. One has nothing to do with the other. PAE removes the 4GB limit on physical memory. It has no connection whatsoever on the 3GB/LAA issues that involve virtual memory.

There is one nasty problem though. With 3GB mode enabled, the kernel only has 1GB of address space available. Certain system entries, including entries to track the usage and mapping of physical memory and the entire non-paged pool, must live in that address space. So your OS may be address space constrained. This can cause problems for 32-bit operating systems, especially when other things consume lots of address space, such as high-end video cards.

If this is affecting you, the first symptom will be networking mysteriously failing with odd errors. See, for example, this Microsoft thread.

You never mentioned you're using /3GB. Without it, LAA processes are still limited to 2GB.

From what I can tell, even if applications aren't designed to work with PAE, one application can still use up to 2 GB before it hits its "limit", so in theory, I can have up to 3 applications using up 2 GB each (pretending Windows isn't taking up any memory, but just a theoretical scenario) and I'd still be fine since Windows is handling where in the memory space these applications are in.

No! The 2GB limit is on virtual memory. You have 6GB of physical memory. You can have 50 processes each using 2GB and you won't hit any limit except the per-process limit on each of those 50 processes.

David Schwartz
  • 62,365
2

The 32-bit Windows kernel can only address up to 2 GB of memory for itself.

Yes -- the kernel won't take more than the upper 2 GB from a program's 4 GB of virtual address space (or more than 1 GB, if you have the /3GB flag and the program is large-address aware). So each app is guaranteed the lower 2 GB of virtual memory (or 3 GB in the latter case).

With PAE, the kernel can use up to 64 GB of physical memory. But each program still has a 4 GB virtual address space. You can't get around this in any way other than by upgrading to a 64-bit system.

From what I can tell, even if applications aren't designed to work with PAE, one application can still use up to 2 GB before it hits its "limit", so in theory, I can have up to 3 applications using up 2 GB each (pretending Windows isn't taking up any memory, but just a theoretical scenario) and I'd still be fine since Windows is handling where in the memory space these applications are in.

Yup.

If an application needs more than 2 GB of physical memory, it must use AWE, but I seriously doubt that the game does this (it's not easy to program for it).

user541686
  • 23,629