
Originally Posted by
Tristicus
Well, I just got 4gb of RAM (4x1gb) from Silicon Assets. Coming from 1gb (512mbx2), which was high density. The new stuff is low latency (4-4-4-12), and low density, and double sided. Well, I installed them in Vista Ultimate x64, and only 2814 show up.
I go in the BIOS, and everything shows as 4gb, the PCI-E is limited to 512mb (because thats how much it takes iteself), and everything was set.
Well, in CPU-Z it also tells me I have 4gb of RAM.
When I used the MEM-TEST LiveCD, it said I had 2815 again, same as Vista.
I removed all the RAM and tested them one by one, and all showed up in the Bios correctly. I then put in 3 sticks so they aren't in dual and that only 3gb is there, and the same: 2815 even after scanning and everything.
I am completely lost on what to do.......
Specs:
Newegg.com - Foxconn 915A01-P-8EKRS2 LGA 775 Intel 915P ATX Intel Motherboard - Retail
4gb of RAM (Avant it says on the stick).
Ati Radeon x1650 Pro 512mb
P4 3.4ghz with HT Technology
500gb SATA HDD (Maxtor)
DVD-+RW Drive (Samsung)
680W PSU
First off, I'm guessing you're using onboard graphics, else you would not be able to adjust the memory allocated to the display, correct?
4GB (4096MB) - 512MB = 3584MB
Now, if you take into account the usual deficit of "lost" memory of about 600MB used by other devices on a hardware-level, such as USB controller, LAN adapters, IDE/SATA controllers, etc., then the remaining memory is available to the system. In your case, 2815MB sounds about right.
You can perhaps increase the available system memory by decreasing the amount allocated to your on-board graphics. By installing a dedicated graphics card that uses it's own memory, you can reclaim the full 512MB back, and bring your system memory up to 3327MB, which is the usual for a 4GB system.
This is a hardware issue, and will remain so for as long as any attached devices (both on-board and add-on) use a 32-Bit memory addressing scheme. It has never been a problem before, because up until now, computers with 4GB of RAM where unheard of. Only when all hardware devices use 64-bit addressing on the hardware level will this issue go away.
Sorry I don't have any better news for you....