Ram Installed Isn't Reported to OS

Discussion in 'Server Setup' started by Doug A., May 5, 2005.

  1. Doug A.

    Doug A. Guest

    I've been running the OS for about two months now - 3GB
    ram was installed in the motherboard, but yesterday I
    upgraded to 4GB. Motherboard POST reports 4GB but
    Windows Server 2003 Standard SP1 reports only the
    original 3GB from when the OS was installed and
    configured.
    This is the first time any Windows OS hasn't "updated"
    itself to match the hardware installed in my extensive
    pre-Windows 3.1 days to present. Bug? Is there a way to
    force the OS to "rescan" the total ram installed and make
    it available for use? Thanks for your assistance in
    advance.

    Configuration: Supermicro X6DAE-G2, Dual 3.0G Xeon 64-bit
    (Nocona), 4GB DDRII 400MHz buffered (registered) ECC
    SDRAM 72-bit . . .
     
    Doug A., May 5, 2005
    #1
    1. Advertisements

  2. Hi,

    Add "/PAE" to the Windows Server 2003 line in c:\boot.ini. You may need to
    unmark it as read only first.

    --
    --Jonathan Maltz [Microsoft MVP - Windows Server - IIS, Virtual PC]
    http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
    tutorial site :)
    http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004? Find out
    here
    Only reply by newsgroup. I do not do technical support via email. Any
    emails I have not authorized are deleted before I see them.
     
    Jonathan Maltz [MS-MVP], May 6, 2005
    #2
    1. Advertisements

  3. Doug A.

    Doug A. Guest

    Thank you Sir, problem solved :) The system properties
    window now correctly displays 4.00GB of ram installed
    followed by the words "Physical Address Extension". So
    now that I'm happily running with as much ram as Windows
    Server Standard Edition (SP1) permits, I can now
    concentrate on the finer points of server management ;-)
    Take care.
     
    Doug A., May 6, 2005
    #3
  4. Doug A.

    Guest Guest

    Hello,

    I've seen this issue before (and also used the PAE switch solution). In all
    cases it had to do with the PERD RAID controller in several DELL servers.
    The explanation would be that the raid controller reserves memory (even when
    it has 128 or 256 MB of onbaord memory) and that this only becomes noticable
    when 4GB of RAM are installed. I read (and was told by DELL) that this is a
    hardware/PCI related issue. My question with regards to adding the PEA
    switch: is the memory 4 GB available to windows or not? If not why not? Why
    would a PCI device take a significant amount of RAM when it doesn't need it,
    just to ensure that it is there when needed? And why only when there is
    4GB+ RAM in the server? The solution with the PAE switch is this only a
    cosmetic workaround as we are then fooled into believing we have 4GB
    available when we do not? Like wise, how do tools like permon etc deal with
    this situation what is there perception of how much RAM there is and how
    much there is availabe to the system?

    Thx if you can shed any light on this issue.


     
    Guest, May 7, 2005
    #4
  5. Doug A.

    Robert Moir Guest

    How it works in general is pretty well documented:
    http://blogs.msdn.com/oldnewthing/archive/2004/08/22/218527.aspx

    Obviously the people to ask about any tricks dell are playing would be dell
    themselves.


    --
     
    Robert Moir, May 7, 2005
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.