3200 MB instead of 4 GB?

[AKA_RA]

I just put in the 3rd and 4th sticks into my roomies motherboard today, and its being weird. The motherboard (supposedly)supports 4 gigs of dual-channel DDR667. The BIOS is showing 3200 MB of RAM with 896 MB appropriated(for what I don't know).

The motherboard is an ASUS P5LD2 rev.2 with newest BIOS update running a C2D e6750 and 4 gigs of Supertalent cheap-o DDR667.

Anyone seen this before or know what its doing?

[crenn]

It's possible that one stick is faulty.

[Luke122]

Try swapping out the sticks, booting it up with one at a time in the first slot to make sure they all are recognized... that will tell you if it's a faulty stick or not.

Does the mobo support 4gb?

[NightrainSrt4]

I can't definitively say what the problem is but check out these links as they have the same issue as yours:

896Mb ram appropriated on Asus P5L-VM

Discussed intermittenly here on Asus P5L DH mobo

P5W DH appropriated memory issue

Seems if your motherboard has a memory remapping feature, and if you enable it, it will take care of the issue. You will still be limited to ~3.2Gb in Windows XP 32-bit as the memory your bios is telling you it is appropriating is being used for memory addressing. Memory remapping should let the bios see the whole 4gb, but you will still be limited to the amount you saw while in windows.

[haha49]

turn memory overlap on in the bois

[The boy 4rm oz]

If it is a 32bit OS then it can only see about 3.5GB of RAM.

[NightrainSrt4]

If it is a 32bit OS then it can only see about 3.5GB of RAM.

I already answered what he was looking for, the memory is all there. The bios is just showing that it is appropriating the other ram for pci lane addressing and such. Memory remapping enabled and it should show it as the full 4Gb.

I also went over the whole 32-bit OS/4GB issue in another thread and you still propagate the misconception that a 32-bit OS can only see/use 3.2-3.5Gb. Yes windows 32bit won't be able to use the memory that is used for addressing for other processes.

The issue at hand really doesn't have to do with the OS anyway, as people were getting this issue before an OS was EVEN INSTALLED.

Edit: Sorry if this post seems blunt, I am dead tired. I just don't see how that explanation really has bearing on the question asked when this issue can occur before the computer is even given an OS.

[Fuganater]

If it is a 32bit OS then it can only see about 3.5GB of RAM.

Beat me to it. I thought this would be the first response.

Unless hes running Vista SP1, then you can see 4 GB. Vista/XP 32-bit can only see "3.5"GB, usually its just shy of 3GB.

[NightrainSrt4]

Beat me to it. I thought this would be the first response.

Unless hes running Vista SP1, then you can see 4 GB. Vista/XP 32-bit can only see "3.5"GB, usually its just shy of 3GB.

Again I will point out that that series of boards have been seen to do that on a virgin drive, as in no OS ever graced those platters, so I don't understand why that is such a common response.