I forgot one point.

for those whom asked about Windows Home Server 2011

't's based upon Windows Server 2008 R2 Foundation with the same processor, memory and other hardware limitations

http://technet.microsoft.com/en-us/library/dd744832(v=ws.10).aspx

the maximum supported memory you see listed above for 64-bit Windows 7 Ultimate\Enterprise\Professional, Vista Ultimate\Enterprise\Business, Server 2008\R2 Datacenter\Enterprise and others represent how much physical main memory had been tested by Microsoft in their labs prior to RTM [Release To Manufacturing] (which for Windows 7 and 2008 R2 occurred in summer 2009 which is different from the GA [General Availability] also called retail release informally between halloween and thanksgiving 2009 in the USA)

any unlimited/non-hard-coded 64-bit OS if properly architected (which includes basically all modern BSD or Linux distros and Windows releases; yes I left a major OS out for a reason; sorry fans) can fully support an entire 64-bit address-space of 2^64 bytes of physical main memory or 64 EXAbytes ...and that's with a flat memory mapping ...all modern OS platforms have used VMM [Virtual Memory Managers] for a decade or longer now, which alows multiple concurrent/simultaneous address-spaces

VMM in combination with certain other hardware technologies i.e. NUMA is why some unices and certain legacy editions of 32-bit windows server were able to address 8GB or more despite the 32-bit addressing limitation of 4GB (the driver model legacy API support and poor coding practices amongst many of microsoft's partners are why this can't be done on the client)

also for those whom brought it up below ReadyBoost is no different from your pagefile   ...'t's a seperate virtual memory mapped address-space residing in your storage subsystem that sits between the pagefile on your fixed disk(s) and main memory itself

so to recap.

Professional and higher client ediitons (including Vista business) don't have an upper limit of what can be addressed and used just an upper limit of what microsoft will guarantee and support (same goes for Server Datacenter or Enterprise editions)

ReadyBoost and PageFile don't count against your maximum addressable main mmeory but have an equivalent upper limit (i.e. Home Premium can't use more than 32GB of virtual memory effectively or @ all)

questions?

whr203@email.vccs.edu

for some advanced reading

http://blogs.technet.com/b/markrussinovich/archive/2008/07/21/3092070.aspx

 - Will

The top end of the new Xeon E5-26xx workstations (HP Z820 and Dell Precision T7600) claim to support up to 512 GiB of memory with Windows 7 Professional. How can this be? Microsoft says that Win7 Professional only goes up to 192 GiB...

I don't see the max. amount of supported memory for Windows home server 2011.

But the amount of memory that the current 64-bit processor from Intel is only 32GB. I hope that Intel makes processors for desktop to support over 128GB.

Lets say we have home basic version of windows 7.The max RAM is 8Gb(x64).Lats say our computer has 2 gb and readyboost we has 16gb,can we use all the 16 gb,or only 6Gb of the flash drive?

I don't understand this silly old fashion Windows Small Business Server 2011 32GB limit (based on "standard" windows 2008R2 It sounds like the old 16GB limit on the older Exchange 2003 databases. They allow now up to 75GB. Please remove this very old fashion 32GB limit, modern servers have 48 or 96 and more memory "standard" installed. The hardware should make the limt, not the software, for software the 'clouded' sky should be the limit! Luc Vinck , Vinck &;; Thys Systems

The limit for 64-bit XP is given as 128 GB, while on the support site, http://support.microsoft.com/kb/283247/en-us, it is given as 16 GB!

What is correct, 16 GB or 128 GB?

Some customers have been reported problems with running 64-bit XP on 32 GB RAM. Can you clarify if 32 Gb RAM is supported and if so, what was the purpose of information in KB 283247

I running windwos Vista 64-bit with 8-GB of ram. Most of my applications are 32-bit applications. How much RAM can VISTA dedicates to 32-bit application?

cs

This document is out of date as it doesn't include the limitations of Windows 2008 and Windows 7. For example, non-paged pool, page pool and system cache are not listed.

There is PCI hole for MMIO between 3 and 4 gb which size differs from 512 to 1024Mb depends on installed pci and video cards. So part or RAM is "shadowed" by MMIO.

Some BIOS may remap MMIO beyond the 4Gb (to be accessed from 32bit mode with PAE) but windows 7 (and other "desktop systems" from Microsoft) do not support it because (according to Russsinovich) they do not want drivers to work with 64bit pointers (which is required to address memory > 4Gb).

Please fix your documentation. It is technically impossible to force windows 7 32bits to access 4Gb ram.

Shouldn't the chipset dictate how much memory the system can handle, I believe the current limit is 2.81474977 × 10¹⁴ byte of memory. which is 2^48, at least this is what Linux currently supports, i would think a big complex, expensive system like Windows would at least match the world best Operating System.

Answer:
There is more to memory limits that what is physically or even theoretically available. Generally, you can't advertise your product supports something unless you have actually tested it. So a lot of these limits aren't based on science, theory, or competence. If you don't have a system large enough to support (at the time of Windows 7, the largest machine tested was a 2TB HP machine, also known as the Superdome) more than 2TB, Microsoft can't advertise that.

I find myself in need of Windows 7 or greater 32 bit with more than 4GB ram. x64 fails due to backwards comparability (a few old programs) and Windows Vista failed an accessibility test that is important to me (which 7 passed).

[tfl] In general, you can not have a 32-bit OS with more than 4GB of RAM. My advice: accept the inevitable and move to 64-bit OSs.

i've updated my overview of the memory sizes of windows using the information above

it can be retrieved via:

http://roadbiker.student.utwente.nl/Memory_sizes_of_Windows_OS.doc

I found out yesterday something that is not listed in any online store selling Windows 7 (even Microsoft) or any comparison charts. Windows 7 Home Premium 64bit has a memory limit of 16GB, Professional and Ultimate have 192GB. I would have liked to have known this prior to makin purchasing decision. Comparison charts at Microsoft store have no mention of memory limits, anyway....

This 'Physical Memory' limit of 16GB, does that also include VRAM? If I install 4 sticks of 4GB Ram, and have 2 x 1.5GB Video Cards (as home enthusiasts may have, probably more-so than a professional guy in an office using Excel), does this count as 16GB physical RAM (4 x 4GB RAM) or 19GB physical RAM (4 x 4GB RAM + 2 x 1.5GB VRAM)?

Thanks.

Answer (Gaidheal):

No, as I mentioned in my comment below, no video card is going to map all of its own physical memory into your system's virtual address space and the installed physical system memory is nothing at all to do with any physical memory on an expansion card.  In other words, just as you don't see memory from soundcards and network adapters (both do have memory, of course) you don't see the memory belonging to your video card, except those ports it explicitly maps.

Okay, time to spear a few myths.  The 4 GiB physical memory limit on 32 bit Windows is a licensing limitation not a hardware limitation; in most cases it is not even a software limitation and the OS version has code capable of enumerating memory beyond 4 GiB but Microsoft choose not to enable it on your licence.

PAE stands for Physical Address Extension, is not a 'Microsoft thing' and has nothing to do with virtual memory or paging; the hint is in the name.  It's a chipset standard that means there are more address lines available, increasing the amount of memory that can be installed on the system.  Windows needed a patch to make use of the increased physical address space and so properly enumerate all system memory and handle the processors which can use these 'extra' address lines.

Virtual address =/= physical address.  Your virtual address space is theoretically unlimited, you simply need to use pointers large enough to handle the maximum desired value; a 32 bit pointer allows a virtual address space of 4 GiB (Gibibyte - 2^30) {this is where the confusion comes in, probably} for example, a 64 bit pointer allows 16 EiB (Exbibyte - 2^60).  The physical memory that this will be mapped onto is utterly irrelevant - it could be a hard disk, flash disk or SDRAM installed as system memory.

Your expansion cards, whether video cards, network adaptors, sound cards or anything else are also utterly irrelevant to your installed physical memory;  their onboard memory is visible only to them and nothing whatsoever to do with your 'RAM' (physical system memory).  Of course, they can make this memory visible to other device by mapping it into the virtual address space and various ports will also take up some of the address space BUT no video card I know of (and I use the 'big boys') maps anything approaching its entire onboard physical memory into the virtual address space.  Installing a "1 GB video card" will not take 1 GiB away from your available virtual memory.

http://www.geoffchappell.com/viewer.htm?doc=notes/windows/license/memory.htm may be of some interest to readers and covers some of what I have stated here.

Windows 7 Pro: 192 Gb - Windows 2008R2 standard (= windows 7 server): 32 Gb, so the client version can address 6 times the memory of the server version
Windows Vista Business x64: 128 Gb - Windows 2008 x64 standard (= windows vista server): 32 Gb, so the client version can address 4 times the memory of the server version

Strange; when you pay more, you get less?
A server should alway be equal or more powerfull than a client!
 
So please, releas a fix that changes max memory of the server versions to (minimal) match the max memory of the client versions.

Hardware drivers need to use memory too. Your requirement to make all RAM usable for software requires a machine with no hardware, I don't think Windows can install on such a machine as it cannot have hard disk, monitor mouse or keyboard.

This web site is for software developers to look up information that help them to write software, so you are not going to the traffic that Microsoft forums usually get. There just way too many pages in this web site here (millions of pages) so traffic to individual pages are minimal. I don't suggest anyone to ask question here and expect timely answers.

Imagine someone who need urgent help in writting software, land on a MSDN page during research, somehow decided to answer your question instead of working on his/hers own problem... how often does that happen?

Ultimate OS wich should support more then 3gbs of RAM but it doesnt.
I have 2x 2gbs od ddr2 RAM, but only 3.12gb is usable, 897mb is hardware reserved.
There is nothing I can do to make all of RAM usable. I tried every tweak but nothing helped me.
I think that M$ should fix this, I did not buy x64 version to have only 3gbs of RAM.

I have Windows 7 x64 Ultimate OS wich should support more then 3gbs of RAM but it doesnt.
I have 2x 2gbs od ddr2 RAM, but only 3.12gb is usable, 897mb is hardware reserved.
There is nothing I can do to make all of RAM usable. I tried every tweak but nothing helped me.
I think that M$ should fix this, I did not buy x64 version to have only 3gbs of RAM.

http://...

The above link describes how to set up PAE (Physical Address Extension) on Vista 32 bits (It can be done in other 32 bits Windows), so that it can make use of 4GB RAM, not just ~3.5GB.

To authors of this message: Please, read how PAE works.

We have bought a Windows 2008 R2 64bit standard edition.. our machine have a memory capacity of 36 GB..

But this server only can handle 32 GB !?

And a client OS alike Win7 pro 192 GB??

Why / what is this?

We have bought a Windows 2008 R2 64bit standard edition.. our machine have a memory capacity of 36 GB..

But this server only can handle 32 GB !?

And a client OS alike Win7 pro 192 GB??



Why / what is this?

• A 32 bit OS can only use 4GB of memory total, that means if you have 4GB of ram and your graphic card has 1GB of ram, you have a total of 5GB of memory.

• Out of that 5GB of memory, you can only use 4GB total. 1GB the graphic card will take up, so now the 32bit OS can only use 3GB.

• Enabling PAE, will limit to the OS to 2GB total. What PAE does is dedicate 2GB to OS and the other 2GB to anything other then the OS. Apparently some people don't understand how PAE works and think that some how it can magically make a 32bit XP use more then 4GB, which is impossible, so after noticing my explanation is not getting through, I thought a visual from MS itself might help sink it in, you can see it here: http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx
  • The 'fact' above is the perfect example of this misunderstanding. PAE has nothing to do with the user and kernel pool being seperated.
  • Many confuse virtual memory with physical memory. All requests for memory by applications; that is running processes, such as explorer.exe, wmplayer.exe, dwm.exe, iexplore.exe, etc; are furfilled using virtual memory. Virtual memory is just an abstraction which includes physical memory and your pagefile(s). Yes, virtual memory includes physical memory!

• Vista 32bit can see only 3.5GB of ram total. The new sp1 only reports how much memory you have installed, not how much memory you can use.

Whomever wrote this ^.

You should actually read the article you posted a link to. I quote:
"

Introduction

PAE is an Intel-provided memory address extension that enables support of greater than 4 GB of physical memory for most 32-bit (IA-32) Intel Pentium Pro and later platforms. This article provides information to help device driver developers implement Windows drivers that support PAE."

Sounds to me like your FACTS, might not be FACTS?

AH! I was going to post these 'inconvenient facts' myself. the 'PAE' (please READ about your acronyms, people!) means 'Physical Address Extension'
Why is that important? the last word, really. 'Extension'. this does NOT enable you to use more than 4GB ram. Face facts people. This is a form of some memory management features,
more than anything else. This isn't even a 'Microsoft thing'. it's a 32-bit computing limitation. the 'Microsoft thing' part comes in because they've somehow given people
the idea that using this boot flag can somehow magically let your computer address more ram than any 32-bit OS is capable of.
I blame their marketing department. Stupid buggers.
And yes, there's a page on microsoft that DOES say that it allows you to use more than 4GB ram. THAT's where people got this idea.

If you want and bought more than 4GB of ram. suck it up and get a real 64-bit OS already.
You could afford the RAM, so go do it. If it's the cost of windows 64-bit that's stopping you,
go download the 64-bit version of ubuntu or something it's free. And if you hate MS, you should want to do that anyway.
But above all, quit ranting. MS isn't going to 'fix' anything because the users rant. This should be painfully obvious to us all by now.
I mean jesus, just look at IIS if you hope that they will one day 'fix' thier OS....

This isn't even a 'Microsoft thing'. ?

But yes, this is a Microsoft thing.
Linux PAE kernel supports 64 GB RAM, because how old 32 bit CPU-s work, and address the memory.
Intel 32 bit CPU-s (and AMD as well) uses Segment:Index addressing where the Segment is 20 bit wide, and the Index is 32 bit wide. However this doesn't mean an 56 bit wide memory address, just 36 bit, and as a result a single byte in memory can be addressed several ways.
Example
- segment:index: 0000:000000001 this is the second byte in the memory (technically, the :00000000 is the first)
- segment:index: 0000:000000010 this is the 17 byte in the memory, however this can alternatively be addressed by this: 0001:00000000
This is because the Segment part overlaps the Index part. Increasing the Segment part by 1 can be an alternative $10 (or decimal 16) increase in the Index side.
It is just the Windows operating system, that runs in protected mode where the Segment is not usable (they are pointers) and addresses the whole memory only by Index, which is a maximum of 4 GB.
The total addressable memory is exactly 4 GB multiplied by that Segment-Index relation - which is 16 - therefore it is 64 GB.
You can do the math for the 64 bit CPU, knowing that Segment size did not change (16 bit), but Index was increased to 64 bit, so the total addressable space is 2^68 = 256 exabytes.

Check the advanced boot options.

Go to Start, in the search bar type msconfig and press enter
System Configuration window will open on the screen
Click on tab named "boot"
Click on "Advanced Options" and uncheck the box for "Maximum Memory"

12 GB (7.99 usable) is displayed under computer properties / system / installed memory (RAM). How do i get the all 12 GB working??

Specs.-OS Windows 7 Home Premium 64 bit
Intel i7 950
evga x58 sli classified
12 GB corsair DDR3 xms3 platinum series

Fact. The only reason why the x32 version of Windows will not see anything past 3.1gig (in some versions) is not a hardware issue. The majority of x32 Intel processors beginning with the Pentium PRO in 1995 have been able to able to support the addressing for up to 64gig of RAM. And while the limit for 32 bits is calculated to 2 to the 32nd (32bit) power or 4 gig, 2 to the 16th (16bit) power is 64k. 16bit MSDOS was designed to use 640k of RAM on an old 8086. A little higher than the "limitation" indicated by math.

[Edit: the 8086 had a 20 bit address bus or 1GB addressable RAM limit, but the later 80x86 families could address up to 32 bits in different modes. However the 8086 CPU was always 16bit. Debate also raged at the time over whether the 80x86 families were 16, 20, 24 or 32 bit processors. But the 1Gb 8086 vs 640K MSDOS stupid limit became infamous when Bill Gates stupidly asked in defence of his stupidity "Who needs more than 640K of memory?" (DSR)]

Opinion. The reason x32 Windows will not recognize anything past that is probably market based. 64bit processors came out a couple years after Windows XP. The first true (no I don't consider XP pro x64 version a true 64bit operating system) 64bit operating system to come from MS was Vista. Everyone knows how well that went. People were downgrading, or doing anything they could to stay away from that mess. Businesses couldn't initially justify the cost of the machines to run Vista acceptably amongst other things (reverse compatibility in hardware and software, reliability issues, hardware support, ect) as indicated by Vista's paltry 18% market share at the launch of 7. In order to sell more copies of Vista and throw some business down their partners way they came up with some pretty lame (IMO) excuses to get people to buy new stuff. Thanks to Vistas horrendous overhead the price of memory has dropped creating this little conundrum.

And while I have my opinions as to why Vista was such a train wreck. It has definitely become more refined over time. Windows 7 is hands down, again in my own opinion, the best OS Microsoft has launched to date. And there are definite advantages to 64bit processing. A majority of the software is still written for 32 bit processing negating most of the advantage you would get with using a 64bit operating system. Besides, doesn't seem to matter which computer or what Microsoft OS I jump onto. The closer I get to utilizing 2 gig of RAM, the crappier the computer seems to run. Kind of like a glass wall there.

hello all. thanks for these very useful numbers. now me being a noob, i have a question since i dont really understand the per process thing.

so i wwork with cubase 5 64 bit version on win 7 ulimate 64 bit. no let say i add a kontakt (sampler) 32 bit. cubase 5 is then a host for this konakt. so my question is since it says per process, does kontakt have 4 gb ram and cubase has another 4 gb of ram? or how do i have to understand this per process?


thank you

There seems to be some confusion about memory limits for the kernel and each process on 32-bit systems. I have written several articles that explain all that (and PAE, by the way) in great detail:

http://blogs.sepago.de/helge/2008/01/23/windows-x64-all-the-same-yet-very-different-part-2/

http://blogs.sepago.de/helge/2008/05/25/x64-my-terminal-servers-run-just-fine-with-32-bits-and-81216-gb-ram/

But, fact in the few past.
If talking only by design、 even XP x64 can treats 32TB.
2 socket hardware, such as Opteron 2000 number processor platform had maximum memory 128GB.
Microsoft says support that only what it was possible to prove.

And now, Xeon 5500 number processor platform can support maximum up to 144GB.
Microsoft will do the proof examination of 144GB in the near future.

I need to select an operating system for a server that runs on Xeon 64Bit (5080) platform. I have an application that needs as much memory as possible. Which operating system version setup will provide the maximum memory to this 32 bit application?

"Apparently some people don't understand how PAE works and think that some how it can magically make a 32bit XP use more then 4GB, which is impossible, so after noticing my explanation is not getting through, I thought a visual from MS itself might help sink it in, you can see it here: http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx"


I also mistakenly thought a 32bit operating system could only use 4GB, having only 32 address bits to work with. But as you can see from the tables above, 32bit Windows Server 2008 can use up to 64GB of physical memory. Turning on the PAE feature modifies the virtual address mapping used by the processor hardware. There is a good explanation on Wikipedia:
http://en.wikipedia.org/wiki/Physical_Address_Extension

Very basically, each process is still limited to 4GB because of the 32bit addresses, but the OS can use a processor control register to map that 4GB space above the 4GB. So process "A" might have it's 4GB virtual address space start in physical ram at 8GB, process "B" at 12GB, etc.

Many people will doubt this because of their personal experience with Microsoft 32bit desktop operating systems. Microsoft has specifically limited the desktops to 4GB for driver compatibility reasons.

Correction, read my facts again and you will see I specifically said "XP 32 bit", second I point to ms's own site and you take us to wiki which anybody can edit? since when is wiki's info more reliable then ms's own site when we discussing ms's OS? lol

In short XP 32-bit can't see more then 4GB of ram total no matter what you do, and its clearly stated here by MS:http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx

yes other 32-bit OS-es can use more then 4GB of ram but not XP 32-bit

"I running windwos Vista 64-bit with 8-GB of ram. Most of my applications are 32-bit applications. How much RAM can VISTA dedicates to 32-bit application?"

64 bit editions of Windows can only attribute a total of 4 GiB of RAM to any single 32 bit virtual memory instance (or application), regardless of your total RAM. The reason is simple, 64 bit editions of Desktop Windows run on the x86-64 architecture, which is a processor architecture capable of running both 64 and 32 bit instructions, limiting 32 bit instructions (or applications) to what 32 bit limits them to, thus, 4 GiB of RAM.

Intel and AMD's specification of PAE does support the x86-64 architecture but the software layer of Microsoft's PAE (the API), called AWE, is not supported on 64 bit editions of Windows, so Windows Vista 64 bit cannot attribute more than 4 GiB of RAM for a 32 bit application.

In fact, true 64 bit architectures like the Intel Itanium processor do not support 32 bit applications. The only reason 32 bit applications work on 64 bit editions of desktop Windows is because the very architecture at its core, called x86-64 (often erroneously shortened to x64), is a hybrid architecture capable of running both 32 bit and 64 bit instructions.

It's also the reason why drivers may not work in 32 bit, but applications will, on Windows Vista 64 bit. The Windows Vista 64 bit kernel is written in 64 bit, and thus, drivers must also be written in 64 bit. If Microsoft would have made the kernel in 32 bit, expanded support would have had to rely on PAE, but drivers wouldn't have had to be re-written. In fact, Apple used that strategy with Mac OS X's transition to 64 bit processors and only its future Snow Leopard will have its kernel in 64 bit.



"I also mistakenly thought a 32bit operating system could only use 4GB, having only 32 address bits to work with. But as you can see from the tables above, 32bit Windows Server 2008 can use up to 64GB of physical memory."

Note however that Windows Server 2008 32 bit uses PAE to achieve this.



"The limit for 64-bit XP is given as 128 GB, while on the support site, http://support.microsoft.com/kb/283247/en-us, it is given as 16 GB!
What is correct, 16 GB or 128 GB?"

Short answer is 128 GiB of RAM.
While Windows XP Pro 64 bit can theoretically support 128 GiB of RAM, driver issues, lack of motherboard support and PAE's Intel technical spec limit to 64 GiB can limit this. Very few 32 bit systems will be built to handle 128 GiB of RAM as the use of a 64 bit operating system becomes much more advantageous in this situation.


I have an article on my blog, Pacoup.com, but you'll have to find it yourself as I cannot link to my own articles on MSDN.

WROTE:

XP and Vista can only truly manage ~3GB of Physical RAM. 4GB is misleading.

Quote:

Xp and Vista can truly manage ~4GB of physical RAM, but shows only the "available" ram. If you have a onboard vídeo with 512mb and something else on-board to complete 1gb, your manager will show only 3GB "available".

QUOTE: PP

Xp and Vista can truly manage ~4GB of physical RAM

Well, that's not logical - 64-bit Vista Business can have up to 128GB RAM, while 64-bit Windows Server 2008 Standard can only have 32GB. Standard Edition is expensive enough to justify increasing the limit to 128GB in my opinion. Why should buying the next version up, Enterprise Edition, allow a 64-increase in memory (up to 2TB!) - unless Standard Edition is being gradually phased out? Hopefully this will be done with Windows Server 2008 Service Pack 1? I can understand Web Edition being limited to just 32GB though.

That said, most of the memory limits make sound sense.

There was a Windows 2003 x64 verison i.e. NON R2 so why does it list this as Not applicable ? Should be 32gb for x64 same as R2 version?