Installed Memory vs RAM Usable by Windows

jmke · 15th June 2010, 12:21

Most PC users are familiar with the 4GB system memory limitation of 32-bit Windows Operating Systems, which is why 64-bit computing has become the standard for computer enthusiasts. Occasionally though, a computer system will not report the correct amount of RAM installed. In this article, our 64-bit Windows 7 test system had 6.00 GB of installed memory but indicates only 4.00 GB usable RAM available. While some may dismiss this as a case of defective RAM, you might be surprised by the culprit.

http://benchmarkreviews.com/index.ph...sk=view&id=541

thorgal · 15th June 2010, 20:08

This happens to me too from time to time. What you need to do in most cases is reseat the CPU, not replace it.

15th June 2010, 20:14

Agreed. Damaged socket, mis-aligned CPU, or even overly aggressive RAM settings. I can't imagine the CPU controller being "bad" unless a memory controller was degraded through overclocking?

jmke · 15th June 2010, 22:21

Quote:

Originally Posted by thorgal

This happens to me too from time to time. What you need to do in most cases is reseat the CPU, not replace it.

had this happen too; culprit turned out to be the motherboard

15th June 2010, 12:21	#1
jmke Madshrimp Join Date: May 2002 Location: 7090/Belgium Posts: 79,021	Installed Memory vs RAM Usable by Windows Most PC users are familiar with the 4GB system memory limitation of 32-bit Windows Operating Systems, which is why 64-bit computing has become the standard for computer enthusiasts. Occasionally though, a computer system will not report the correct amount of RAM installed. In this article, our 64-bit Windows 7 test system had 6.00 GB of installed memory but indicates only 4.00 GB usable RAM available. While some may dismiss this as a case of defective RAM, you might be surprised by the culprit. http://benchmarkreviews.com/index.ph...sk=view&id=541 __________________

15th June 2010, 20:08	#2
thorgal [M] Reviewer Join Date: Sep 2005 Posts: 1,887	This happens to me too from time to time. What you need to do in most cases is reseat the CPU, not replace it. __________________

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Microsoft Patch Tuesday: 5 Criticals, 2 Important, 1 Moderate Patch	jmke	WebNews	0	14th April 2009 18:47
Microsoft Security Bulletin Summary for September 2008	jmke	WebNews	0	9th September 2008 19:20
Microsoft Security Bulletin Summary for August 2007	jmke	WebNews	0	14th August 2007 22:21
INFO: RAM List: What Chips on what Memory	jmke	FAQ / INFO / HOW-TO	3	23rd April 2005 17:13
List of fixes included in Windows XP Service Pack 2	jmke	WebNews	1	17th August 2004 15:03

15th June 2010, 20:14	#3
Kougar Posts: n/a	Agreed. Damaged socket, mis-aligned CPU, or even overly aggressive RAM settings. I can't imagine the CPU controller being "bad" unless a memory controller was degraded through overclocking?