F5F Stay Refreshed Power Users Overclocking Motherboard Overclocking Ram

Motherboard Overclocking Ram

Motherboard Overclocking Ram

A
AGamingManiac
Junior Member
Find
6
06-30-2016, 09:20 AM
#1
I received a new memory yesterday, the HyperX Red Fury 8 GB RAM Memory Kit (2 x 4 GB) DDR3 1333Mhz CL9 Dimm Red. However, I'm experiencing problems. After installing the four sticks, my system still won't boot and only displays 'Windows Is Loading Files'. Please refrain from any further actions. In my BIOS, it shows that all memory is being read, with a frequency of 3201.06 MHz, a total size of 16384 MB, a voltage of 1.584V. There appears to be an issue with the System Memory Multiplier (SPD) [Auto], indicating an improper memory clock could cause the system to fail to boot. I also checked my PCI Express connection, but it didn't resolve the problem. I removed my graphics card in hopes it might be causing the conflict, but it didn't help. I wasn't expecting this issue and was confident it would work properly. I'm seeking a straightforward solution. I hope this assists... My setup includes Windows 7 Ultimate 64-bit SP1, an Intel Core i3 550 @ 3.20GHz, Gigabyte H55M-UD2H (Socket 1156), and the HyperX Red Fury 8 GB RAM kit (2 x 4 GB) totaling 16GB. The graphics card is an Acer K272HL (1360x768@60Hz) with an ATI AMD Radeon HD 5450 (XFX Pine Group). Regards, Malcolm
Reply
Reply
A
AGamingManiac
06-30-2016, 09:20 AM #1

I received a new memory yesterday, the HyperX Red Fury 8 GB RAM Memory Kit (2 x 4 GB) DDR3 1333Mhz CL9 Dimm Red. However, I'm experiencing problems. After installing the four sticks, my system still won't boot and only displays 'Windows Is Loading Files'. Please refrain from any further actions. In my BIOS, it shows that all memory is being read, with a frequency of 3201.06 MHz, a total size of 16384 MB, a voltage of 1.584V. There appears to be an issue with the System Memory Multiplier (SPD) [Auto], indicating an improper memory clock could cause the system to fail to boot. I also checked my PCI Express connection, but it didn't resolve the problem. I removed my graphics card in hopes it might be causing the conflict, but it didn't help. I wasn't expecting this issue and was confident it would work properly. I'm seeking a straightforward solution. I hope this assists... My setup includes Windows 7 Ultimate 64-bit SP1, an Intel Core i3 550 @ 3.20GHz, Gigabyte H55M-UD2H (Socket 1156), and the HyperX Red Fury 8 GB RAM kit (2 x 4 GB) totaling 16GB. The graphics card is an Acer K272HL (1360x768@60Hz) with an ATI AMD Radeon HD 5450 (XFX Pine Group). Regards, Malcolm

Reply
Reply
V
Vlad1576
Junior Member
Find
6
06-30-2016, 11:49 PM
#2
The Fury line isn't compatible with older rigs before the 1155 (P67) chipset. These units are high density and function via PnP—requiring low density and (for 1600 or above) standard XMP based drives, which isn't suitable in this case.
Reply
Reply
V
Vlad1576
06-30-2016, 11:49 PM #2

The Fury line isn't compatible with older rigs before the 1155 (P67) chipset. These units are high density and function via PnP—requiring low density and (for 1600 or above) standard XMP based drives, which isn't suitable in this case.

Reply
Reply
W
wANHEiZER
Member
Find
158
07-04-2016, 01:14 PM
#3
The Fury line isn't compatible with older rigs before the 1155 (P67) chipset. These units are high density and function via PnP—requiring low density and (for 1600 or above) standard XMP based drives, which isn't suitable in this case.
Reply
Reply
W
wANHEiZER
07-04-2016, 01:14 PM #3

The Fury line isn't compatible with older rigs before the 1155 (P67) chipset. These units are high density and function via PnP—requiring low density and (for 1600 or above) standard XMP based drives, which isn't suitable in this case.

Reply
Reply