8gb Installed 3.92GB Usable

Kiakri · Sep 20, 2013

Hi

Basically my computer is saying i have 8GB installed and 3.92Gb Usable

I am using windows 7 64BIt

I have tried changing the maximum memory in msconfig in the advanced boot options, however when i do it just reset to 0 when resetting

CPUID is showing 8GB installed. and also showing the memory in slots 1 & 3 both with 4gb

Current built

Sabertooth 990fx r2 (newest bios)
XMP Beast Series 8GB 1866MHz
AMD Athlon Dual core 265 3.58ghz (replacement for a broken processor at this time)
GTX 670 EVGA FTW
Corsair HX850 Hybrid modular 850watt PSU

wondered if anybody had a solution as I've searched around the general fixes do not work

mactronix · Sep 20, 2013

Don't worry its not a real issue its just that the system is reserving some. Its perfectly normal.
The amount that is being reserved is not physically cut off from the rest of the system and will be used inf needed.

Here read this.

http://support.microsoft.com/kb/978610

Mactronix

Kiakri · Sep 20, 2013

Ahh i see thanks for the quickly reply

Kiakri · Sep 20, 2013

Out of curiosity is there a way to actually remove so nothing is reserved?

Also that websites says about .9 GB while im losing about 4.08GB

Pinhedd · Sep 20, 2013

Kiakri :

This is a common problem with some chipsets that have legacy PCI slots such as yours. The PCI bus uses a 32 bit physical address space. For compatibility with legacy operating systems the system firmware will often limit the physical address space to 32 bits to ensure that PCI peripherals have access to the entire physical memory space. Newer operating systems with improved memory management and PAE awareness do not have this compatibility requirement which allows the full physical memory space to be used.

In your system settings under "North Bridge Configuration" set "Memory Hole Remapping" to "Enabled" and reboot.

Kiakri · Sep 20, 2013

Pinhedd :

Kiakri :

This is a common problem with some chipsets that have legacy PCI slots such as yours. The PCI bus uses a 32 bit physical address space. For compatibility with legacy operating systems the system firmware will often limit the physical address space to 32 bits to ensure that PCI peripherals have access to the entire physical memory space. Newer operating systems with improved memory management and PAE awareness do not have this compatibility requirement which allows the full physical memory space to be used.

In your system settings under "North Bridge Configuration" set "Memory Hole Remapping" to "Enabled" and reboot.

So assuming i i got a newer cpu that would get rid of that problem?

You mean change the north bridge configuration in the bios right?

Pinhedd · Sep 20, 2013

Kiakri :

The CPU has nothing to do with it. Your motherboard has a PCI slot (not a PCIe slot) which has direct access to the system memory. PCI is extremely old and due to its parallel signal nature was stuck with a 32 bit physical address space long after other standards had moved on. The physical address space of the entire system is larger than 32 bits, between 36 and 52 bits. This means that physical addresses above the 32 bit barrier would be wholly inaccessible to anything connected over PCI. Most operating systems work around this, but some do not. Since most address mapping is handled by the firmware before any operating system is loaded, it's necessary to have an option to ensure that the entire physical address space is constrained to 32 bits in order to ensure that PCI works correctly in the event that an operating system isn't designed with a physical address space larger than 32 bits in mind.

When memory hole remapping is disabled, the entire physical memory space is constrained to 32 bits and memory addresses are allocated from this space only. If the combination of IO addresses and DRAM addresses exceeds the 32 bit address space, the DRAM gets chopped off as the IO devices take precedence.

When memory hole remapping is enabled, DRAM is mapped into physical addresses above the 32 bit barrier, which leaves plenty of space below the barrier for devices that aren't compatible with the the larger address space.

Consumer versions of 32 bit Windows have memory remapping disabled at the software level even if it is enabled at the hardware level. Server versions of 32 bit Windows have it enabled, which allows for support for more than 4GiB of DRAM dating all the way back to Windows 2000. If it is disabled at the hardware level, the same constraint will impact both 32 bit and 64 bit operating systems.

Kiakri · Sep 20, 2013

Pinhedd :

Kiakri :

The CPU has nothing to do with it. Your motherboard has a PCI slot (not a PCIe slot) which has direct access to the system memory. PCI is extremely old and due to its parallel signal nature was stuck with a 32 bit physical address space long after other standards had moved on. The physical address space of the entire system is larger than 32 bits, between 36 and 52 bits. This means that physical addresses above the 32 bit barrier would be wholly inaccessible to anything connected over PCI. Most operating systems work around this, but some do not. Since most address mapping is handled by the firmware before any operating system is loaded, it's necessary to have an option to ensure that the entire physical address space is constrained to 32 bits in order to ensure that PCI works correctly in the event that an operating system isn't designed with a physical address space larger than 32 bits in mind.

When memory hole remapping is disabled, the entire physical memory space is constrained to 32 bits and memory addresses are allocated from this space only. If the combination of IO addresses and DRAM addresses exceeds the 32 bit address space, the DRAM gets chopped off as the IO devices take precedence.

When memory hole remapping is enabled, DRAM is mapped into physical addresses above the 32 bit barrier, which leaves plenty of space below the barrier for devices that aren't compatible with the the larger address space.

Consumer versions of 32 bit Windows have memory remapping disabled at the software level even if it is enabled at the hardware level. Server versions of 32 bit Windows have it enabled, which allows for support for more than 4GiB of DRAM dating all the way back to Windows 2000. If it is disabled at the hardware level, the same constraint will impact both 32 bit and 64 bit operating systems.

Just checked the north bridge config on the bios and memory hole remapping is already enabled

Pinhedd · Sep 20, 2013

Kiakri :

Pinhedd :

Kiakri :

The CPU has nothing to do with it. Your motherboard has a PCI slot (not a PCIe slot) which has direct access to the system memory. PCI is extremely old and due to its parallel signal nature was stuck with a 32 bit physical address space long after other standards had moved on. The physical address space of the entire system is larger than 32 bits, between 36 and 52 bits. This means that physical addresses above the 32 bit barrier would be wholly inaccessible to anything connected over PCI. Most operating systems work around this, but some do not. Since most address mapping is handled by the firmware before any operating system is loaded, it's necessary to have an option to ensure that the entire physical address space is constrained to 32 bits in order to ensure that PCI works correctly in the event that an operating system isn't designed with a physical address space larger than 32 bits in mind.

When memory hole remapping is disabled, the entire physical memory space is constrained to 32 bits and memory addresses are allocated from this space only. If the combination of IO addresses and DRAM addresses exceeds the 32 bit address space, the DRAM gets chopped off as the IO devices take precedence.

When memory hole remapping is enabled, DRAM is mapped into physical addresses above the 32 bit barrier, which leaves plenty of space below the barrier for devices that aren't compatible with the the larger address space.

Consumer versions of 32 bit Windows have memory remapping disabled at the software level even if it is enabled at the hardware level. Server versions of 32 bit Windows have it enabled, which allows for support for more than 4GiB of DRAM dating all the way back to Windows 2000. If it is disabled at the hardware level, the same constraint will impact both 32 bit and 64 bit operating systems.

Just checked the north bridge config on the bios and memory hole remapping is already enabled

If that's the case, one of your DIMMs or one of your DIMM slots may be damaged. Take one of the modules out and boot it up. Repeat with the other module. If both modules work, try them in the second slot. Sometimes just reseating the modules is enough to fix it.

Kiakri · Sep 21, 2013

Pinhedd :

Kiakri :

Pinhedd :

Kiakri :

The CPU has nothing to do with it. Your motherboard has a PCI slot (not a PCIe slot) which has direct access to the system memory. PCI is extremely old and due to its parallel signal nature was stuck with a 32 bit physical address space long after other standards had moved on. The physical address space of the entire system is larger than 32 bits, between 36 and 52 bits. This means that physical addresses above the 32 bit barrier would be wholly inaccessible to anything connected over PCI. Most operating systems work around this, but some do not. Since most address mapping is handled by the firmware before any operating system is loaded, it's necessary to have an option to ensure that the entire physical address space is constrained to 32 bits in order to ensure that PCI works correctly in the event that an operating system isn't designed with a physical address space larger than 32 bits in mind.

When memory hole remapping is disabled, the entire physical memory space is constrained to 32 bits and memory addresses are allocated from this space only. If the combination of IO addresses and DRAM addresses exceeds the 32 bit address space, the DRAM gets chopped off as the IO devices take precedence.

When memory hole remapping is enabled, DRAM is mapped into physical addresses above the 32 bit barrier, which leaves plenty of space below the barrier for devices that aren't compatible with the the larger address space.

Consumer versions of 32 bit Windows have memory remapping disabled at the software level even if it is enabled at the hardware level. Server versions of 32 bit Windows have it enabled, which allows for support for more than 4GiB of DRAM dating all the way back to Windows 2000. If it is disabled at the hardware level, the same constraint will impact both 32 bit and 64 bit operating systems.

Just checked the north bridge config on the bios and memory hole remapping is already enabled

If that's the case, one of your DIMMs or one of your DIMM slots may be damaged. Take one of the modules out and boot it up. Repeat with the other module. If both modules work, try them in the second slot. Sometimes just reseating the modules is enough to fix it.

Sadly for some reason if i try run with one slot of ram it just doesn't boot DRAM led light up, and even if i press the memo ok button nothing happens.

Anyways tried another type of ram in two different channels.
and well same problem 4GB installed 1.92 Usable

Im assuming that puts its down to motherboard problem?

Pinhedd · Sep 21, 2013

Kiakri :

Pinhedd :

Kiakri :

Pinhedd :

Just checked the north bridge config on the bios and memory hole remapping is already enabled

If that's the case, one of your DIMMs or one of your DIMM slots may be damaged. Take one of the modules out and boot it up. Repeat with the other module. If both modules work, try them in the second slot. Sometimes just reseating the modules is enough to fix it.

Sadly for some reason if i try run with one slot of ram it just doesn't boot DRAM led light up, and even if i press the memo ok button nothing happens.

Anyways tried another type of ram in two different channels.
and well same problem 4GB installed 1.92 Usable

Im assuming that puts its down to motherboard problem?

If it doesn't boot at all with a single DIMM installed, it's time to RMA the motherboard

Kiakri · Sep 21, 2013

Pinhedd :

Will double check tonight with two different ram types just to make sure.

Lets hope replacemrnt motherboard fixes all this and thanks for all your help

Kiakri · Sep 21, 2013

So update, i basically tried one ram into each channel slot and its works in channel so i decided to add another ram to channel 4, and all my problem are solved, However with one ram slot in the channel one and two is fails to boot, Motherboard will be replaced it seems. running 8gb Usable 7.42

Pinhedd · Sep 21, 2013

Kiakri :

Okay, sounds good

Kiakri · Sep 21, 2013

Pinhedd :

Thanks for all the help

Pinhedd · Sep 21, 2013

Kiakri :

Pinhedd :

Thanks for all the help

you're most welcome

drkarasheed · Sep 23, 2013

Kiakri :

You seems to have got the needed answer
But have you identified who (I mean what all hard wares) is taking away the hidden portion of the RAM ??

Kiakri · Sep 23, 2013

drkarasheed :

Hardware wasn't taking away from it was due to fault channels im not bac to to 8gb installed and 7.42 usable.

The .58 ram im assuming is used by windows

8gb Installed 3.92GB Usable

Honorable

Judicious

Honorable

Honorable

Champion

Honorable

Champion

Honorable

Champion

Honorable

Champion

Honorable

Honorable

Champion

Honorable

Champion

Distinguished

Honorable

Share this page