Commentary

Dave Methvin
 

Windows Memory Has Physical, Design, and Marketing Limitations

Mark Russinovich is one of Microsoft's best technical people, and he shows that every time he makes a blog post. This week he has a great post about the maximum supported memory in different versions of Windows. I thought I knew this story pretty well by now, but learned several new things about the limits--and the interesting reasons behind them.

Mark Russinovich is one of Microsoft's best technical people, and he shows that every time he makes a blog post. This week he has a great post about the maximum supported memory in different versions of Windows. I thought I knew this story pretty well by now, but learned several new things about the limits--and the interesting reasons behind them.The blog points to an MSDN article on memory limits, which does have a few quirks. As the commenter on that page points out, why should 64-bit Windows Vista Business (a desktop OS) allow 128 GB of RAM, but 64-bit Windows Server 2008 Standard top out at 32 GB? These are not limits born of technical reasons, but simply put there by the marketing department to convince one group or the other to pony up more money for what is essentially the same OS.

There is a way for 32-bit Windows to access memory using a technology called Physical Address Extensions (PAE). However, Microsoft intentionally limited desktop XP and Vista to 4 GB of RAM because many third-party drivers did not work properly when trying to access a memory address above 4 GB. Rather than risk crashes and system problems, Microsoft made it impossible to do.


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

This issue is compounded by hardware, particularly video boards, that map some of their memory into the 4 GB address space. Windows can do that fine, but in the process it maps some real RAM into the space above 4 GB where it won't be accessed by either applications or the operating system itself. That's why you'll often see Windows use much less than 4 GB RAM on 32-bit XP or Vista, even if you've installed 4 GB of physical memory.

I completely understand why Microsoft instituted the 4-GB limit for 32-bit desktop operating systems by default, but the finality of the implementation leaves something to be desired. Since this was ostensibly a patch to work around bad device drivers, it would have been good to have perhaps a boot.ini option that technical users could use to regain their missing memory. If I have well-behaved drivers, I should be able to use them with more than 4 GB on 32-bit Window -- or at the very least, get a full usable 4 GB of RAM.

One point that Russinovich didn't emphasize, perhaps because it's a hardware problem and not a Microsoft problem: many Pentium 4 northbridge chipsets for portables and desktops were limited until recently to addressing 4 GB of RAM. Even if you install a 64-bit version of Windows on these systems, you won't be able to install more than 4 GB of RAM, so it doesn't help much. Server chipsets allow a more generous helping of RAM as you might expect.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links