• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 112
  • Last Modified:

Windows server 2008 R2 std shows only 24 GB while there are 32 GB installed

We've got Windows server 2008 R2 std physical rig, which shows only 24 GB while there are 32 GB installed.
I've checked and saw that 32GB are the limit for this version of windows, and we need to use all of them.

See screenshot attached.

Please assist :)

Thanks
SAP.jpg
0
IT_Group1
Asked:
IT_Group1
  • 4
  • 3
  • 3
  • +3
3 Solutions
 
Jayaraja JayaramanCommented:
Windows server 2008 R2 supports only 32 gigs of RAM
http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx
0
 
Cliff GaliherCommented:
Losing exactly 8 seems suspicious. I would suspect either a firmware setting reserving memory for the GPU (something I see often with white box "servers" but I see you are running an IBM M4, so this would surprise me a little) or your server has 4-8GB DIMMs and one is bad. That'll usually get logged in the event logs as well.
0
 
dpcsitCommented:
Could part of the memory be mirrored in Bios?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
IT_Group1Author Commented:
dpcsit thanks - how can I check it via Windows?
0
 
Jon1999Commented:
I had it happen in a server that one of the two 4 gig sticks one was bad casing it to lose both. Replaced one bad it is working now
0
 
Seth SimmonsSr. Systems AdministratorCommented:
if one module was bad, it wouldn't detect that it was there; it should throw an error during POST and the OS wouldn't know about it

if the memory was mirrored you wouldn't see the numbers like that; it would be 16gb available, not 24 since you would have 50% overhead and cuts your number in half, not a quarter

how was the memory installed?  was it upgraded after purchase or ordered like that from the factory?  should be either a bios setting or misconfiguration of modules
0
 
dpcsitCommented:
0
 
Cliff GaliherCommented:
I agree on the mirroring. But as far as bad memory, many servers will disable the stick during preboot (POST or UEFI) but still bubble it up to the OS. This is intentional and newer chipset drivers fully support "knowing" that the BIOS disabled memory. The idea behind it is that system management software such as SCOM can have management packs can query the is, the OS will report when memory fails, and SCOM can generate an alert for replacement. It isn't at all uncommon anymore. And it isn't limited to memory. Bad disks in a RAID array can notify the OS so you no longer need to log into an out-of-band interface or reboot. Bad power supplies (useful if you have a server with redundant supplies that can be hot swapped.) OS level reporting on hot-swappable hardware has come a long ways. And yes, windows will display those as X memory and y usable where y=x-bad.
0
 
dpcsitCommented:
I agree on the bad stick causing issues! Removing the memory and adding it back might fix it if a stick is not in the slot properly.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
another thing to look at...
if you run msconfig, click the boot tab and advanced options button, check if maximum memory is specified.  if a user-imposed memory limit was in place for windows it would show that (32 total, 24 usable) in the system properties
0
 
IT_Group1Author Commented:
Guys,

IBM have checked the server, the DIMM's are misplaced...

Thanks all
0
 
IT_Group1Author Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for IT_Group1's comment #a40498878

for the following reason:

Other solutions were good, but not correct.
Thanks all
0
 
Seth SimmonsSr. Systems AdministratorCommented:
i said earlier a possibility was a misconfiguration of modules
0
 
IT_Group1Author Commented:
2 (!) modules were bad.
Thanks guys
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
  • 3
  • 3
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now