F5F Stay Refreshed Hardware Desktop System halts upon startup after attempting to utilize the appropriate RAM rate

System halts upon startup after attempting to utilize the appropriate RAM rate

System halts upon startup after attempting to utilize the appropriate RAM rate

R
RoawZ
Junior Member
15
12-04-2016, 06:21 PM
#1
Hey! Your system is running at 2133MHz, which is below the expected 3200MHz for your setup. You might need to enable XMP profiles or adjust the memory settings manually. Also, ensure your BIOS supports higher speeds and check if the RAM is properly seated. Consider using a compatible overclocking tool or contacting Corsair for further assistance.
R
RoawZ
12-04-2016, 06:21 PM #1

Hey! Your system is running at 2133MHz, which is below the expected 3200MHz for your setup. You might need to enable XMP profiles or adjust the memory settings manually. Also, ensure your BIOS supports higher speeds and check if the RAM is properly seated. Consider using a compatible overclocking tool or contacting Corsair for further assistance.

X
Xerion2015
Member
73
12-17-2016, 07:02 PM
#2
It’s clear your system isn’t receptive to this memory kit. Turn on XMP and adjust the frequency manually—start around 2933mt/s, then increase gradually.
X
Xerion2015
12-17-2016, 07:02 PM #2

It’s clear your system isn’t receptive to this memory kit. Turn on XMP and adjust the frequency manually—start around 2933mt/s, then increase gradually.

N
Nero12321
Posting Freak
858
12-18-2016, 04:43 PM
#3
How do i enable XMP and choose the frequency myself?
N
Nero12321
12-18-2016, 04:43 PM #3

How do i enable XMP and choose the frequency myself?

K
koolman788
Junior Member
42
12-20-2016, 08:19 AM
#4
In the bios, choose the Tweaker option. XMP is referred to as DOCP—it's identical. Under that configuration, you can pick the DRAM frequency.
K
koolman788
12-20-2016, 08:19 AM #4

In the bios, choose the Tweaker option. XMP is referred to as DOCP—it's identical. Under that configuration, you can pick the DRAM frequency.

P
pyrote
Senior Member
407
12-20-2016, 09:50 AM
#5
I identified the issue. The BIOS wasn't current.
P
pyrote
12-20-2016, 09:50 AM #5

I identified the issue. The BIOS wasn't current.