F5F Stay Refreshed Hardware Desktop Does your memory issue stem from RAM problems or a motherboard fault? (LED indicates higher frequency)

Does your memory issue stem from RAM problems or a motherboard fault? (LED indicates higher frequency)

Does your memory issue stem from RAM problems or a motherboard fault? (LED indicates higher frequency)

Pages (2): 1 2 Next
R
RobertXDB
Junior Member
38
12-15-2019, 08:32 PM
#1
I recently assembled a black/white themed PC and encountered issues with the motherboard or RAM. My memory is set at 2x 8GB GSKill TridentZ Neo DDR4-3600MHz CL16-19-19-39, matching the specifications on the box. When I enable XMP on my Asus Prime X570 Pro with a Ryzen 7 3700X, it boots intermittently—about two-thirds of the time. When it fails, the memory debug LED illuminates but doesn’t turn off. Adjusting XMP settings changes the timings to 16-19-19-39 and frequency to 3600, yet it still works up to around 3200. I’ve also tried manually setting it to 16-19-19-39 with a starting frequency of 3000MHz, which functions properly until 3200. I’m certain the kit was correct and the package lists compatibility with this board. Asus claims the 3600 TridentZ Neo model supports it. Could there be an error in my configuration or missing components? I built it about a week ago using the latest BIOS (version 1407). The build details include: Ryzen 7 3700X, Asus Prime X570 Pro, GSKill kit, MSI RTX 2070 Super Gaming, Corsair RM650. Note: DOCP adjustment also lowers voltage to 1.35.
R
RobertXDB
12-15-2019, 08:32 PM #1

I recently assembled a black/white themed PC and encountered issues with the motherboard or RAM. My memory is set at 2x 8GB GSKill TridentZ Neo DDR4-3600MHz CL16-19-19-39, matching the specifications on the box. When I enable XMP on my Asus Prime X570 Pro with a Ryzen 7 3700X, it boots intermittently—about two-thirds of the time. When it fails, the memory debug LED illuminates but doesn’t turn off. Adjusting XMP settings changes the timings to 16-19-19-39 and frequency to 3600, yet it still works up to around 3200. I’ve also tried manually setting it to 16-19-19-39 with a starting frequency of 3000MHz, which functions properly until 3200. I’m certain the kit was correct and the package lists compatibility with this board. Asus claims the 3600 TridentZ Neo model supports it. Could there be an error in my configuration or missing components? I built it about a week ago using the latest BIOS (version 1407). The build details include: Ryzen 7 3700X, Asus Prime X570 Pro, GSKill kit, MSI RTX 2070 Super Gaming, Corsair RM650. Note: DOCP adjustment also lowers voltage to 1.35.

P
pinkwolf_pvp
Member
144
12-17-2019, 04:37 AM
#2
Do you have the most recent bios ready? It looks like the installation should be solid, given that Zen 2 offers a decent option.
P
pinkwolf_pvp
12-17-2019, 04:37 AM #2

Do you have the most recent bios ready? It looks like the installation should be solid, given that Zen 2 offers a decent option.

F
FloryJumper
Member
61
12-18-2019, 03:47 PM
#3
The current BIOS version is 1407. The previous one was 1405, and updating it didn’t resolve the issue.
F
FloryJumper
12-18-2019, 03:47 PM #3

The current BIOS version is 1407. The previous one was 1405, and updating it didn’t resolve the issue.

I
iiSweeTzz
Posting Freak
862
12-18-2019, 10:00 PM
#4
Do you have RAM in slots 2 and 4? Activate XMP, set frequency to 3600, boost DRAM voltage to 1.37 and SOC voltage to 1.05.
I
iiSweeTzz
12-18-2019, 10:00 PM #4

Do you have RAM in slots 2 and 4? Activate XMP, set frequency to 3600, boost DRAM voltage to 1.37 and SOC voltage to 1.05.

X
xRedxNightx
Member
176
12-19-2019, 10:29 PM
#5
Competitively challenge him!
X
xRedxNightx
12-19-2019, 10:29 PM #5

Competitively challenge him!

3
3gilad3
Senior Member
735
12-19-2019, 10:48 PM
#6
Dims are located in slots B2 and A2, according to the guide. I could attempt increasing the voltage, perhaps it would assist.
3
3gilad3
12-19-2019, 10:48 PM #6

Dims are located in slots B2 and A2, according to the guide. I could attempt increasing the voltage, perhaps it would assist.

P
Pancake109953
Junior Member
45
01-10-2020, 08:02 PM
#7
Increasing the voltage from 1.350 to 1.370 appeared effective. Turning off the device, shutting down the power supply, and restarting didn't trigger the debug LED. I'll monitor the situation over the coming days. Thanks!
P
Pancake109953
01-10-2020, 08:02 PM #7

Increasing the voltage from 1.350 to 1.370 appeared effective. Turning off the device, shutting down the power supply, and restarting didn't trigger the debug LED. I'll monitor the situation over the coming days. Thanks!

B
blue10x
Member
74
01-25-2020, 05:49 AM
#8
If the problem repeats, slightly increase the SOC voltage
B
blue10x
01-25-2020, 05:49 AM #8

If the problem repeats, slightly increase the SOC voltage

K
KungJoel
Junior Member
48
01-25-2020, 09:58 AM
#9
The situation appears to occur less often now. You increased the DRAM voltage and checked the SOC voltage. The listed value is around 1.1V (auto), matching the standard 1.36xxV specification by the CPU. Consider adjusting it slightly higher if needed.
K
KungJoel
01-25-2020, 09:58 AM #9

The situation appears to occur less often now. You increased the DRAM voltage and checked the SOC voltage. The listed value is around 1.1V (auto), matching the standard 1.36xxV specification by the CPU. Consider adjusting it slightly higher if needed.

O
OceanBear
Member
103
01-27-2020, 01:13 AM
#10
I reset the tRC timing to automatic and it worked again. I set it to 58, but the issues returned. The DOCP remains fixed at 85 in the BIOS, while XMP still shows 58.
O
OceanBear
01-27-2020, 01:13 AM #10

I reset the tRC timing to automatic and it worked again. I set it to 58, but the issues returned. The DOCP remains fixed at 85 in the BIOS, while XMP still shows 58.

Pages (2): 1 2 Next