F5F Stay Refreshed Power Users Overclocking Issue with XMP on AB350 Pro4 resolved

Issue with XMP on AB350 Pro4 resolved

Issue with XMP on AB350 Pro4 resolved

F
Flikaflare
Junior Member
17
09-17-2019, 02:16 PM
#1
CPU: Ryzen 5 3600
Motherboard: AsRock AB350 Pro4
Bios Version: P5.80
Memory: G.Skill Aegis 3200 MHz ram (F4-3200C16D-16GIS)
Slots available: 2 & 4
Problem: Using XMP profile causes the system to fail to boot, but resetting via BIOS works. Adjusting RAM speed to below 3000 MHz resolves audio issues, though crashes persist after a few minutes regardless of speed.
* Crashing means the computer either freezes completely or shuts down abruptly, with static audio being a recurring issue. What exactly is happening? I need to maximize my RAM performance.
F
Flikaflare
09-17-2019, 02:16 PM #1

CPU: Ryzen 5 3600
Motherboard: AsRock AB350 Pro4
Bios Version: P5.80
Memory: G.Skill Aegis 3200 MHz ram (F4-3200C16D-16GIS)
Slots available: 2 & 4
Problem: Using XMP profile causes the system to fail to boot, but resetting via BIOS works. Adjusting RAM speed to below 3000 MHz resolves audio issues, though crashes persist after a few minutes regardless of speed.
* Crashing means the computer either freezes completely or shuts down abruptly, with static audio being a recurring issue. What exactly is happening? I need to maximize my RAM performance.

C
CookieKinq
Junior Member
37
09-18-2019, 11:45 PM
#2
Hey there,
The issue comes from the constraints of your motherboard. 1st Gen Ryzen cards and CPUs usually cap at around 2933mhz, sometimes even lower. They work okay at the default settings, but XMP might lead to the crashes you mentioned. When you say you've set them manually, clarify what adjustments you made—specifically voltage and primary timings. If you skip both, crashes are likely. Ensure your RAM is placed in the proper slots. Refer to your motherboard manual or search online for details.
C
CookieKinq
09-18-2019, 11:45 PM #2

Hey there,
The issue comes from the constraints of your motherboard. 1st Gen Ryzen cards and CPUs usually cap at around 2933mhz, sometimes even lower. They work okay at the default settings, but XMP might lead to the crashes you mentioned. When you say you've set them manually, clarify what adjustments you made—specifically voltage and primary timings. If you skip both, crashes are likely. Ensure your RAM is placed in the proper slots. Refer to your motherboard manual or search online for details.

S
SirKumsishon
Senior Member
257
09-19-2019, 01:14 AM
#3
I checked online and confirmed I have the RAM in the right slots. I plan to gradually increase the RAM speed, but I’m unsure how much to adjust the voltage per 100 MHz. Also, I’m not sure what changes to make to the timings—I thought it was optional and didn’t know where to start.
S
SirKumsishon
09-19-2019, 01:14 AM #3

I checked online and confirmed I have the RAM in the right slots. I plan to gradually increase the RAM speed, but I’m unsure how much to adjust the voltage per 100 MHz. Also, I’m not sure what changes to make to the timings—I thought it was optional and didn’t know where to start.

W
WaZtoX
Member
115
09-19-2019, 06:11 AM
#4
There isn't a straightforward voltage-to-frequency link—it forms a curve where voltage rises more rapidly as frequency increases. DDR4 memory remains stable up to 1.5V. When facing XMP stability issues, manually adjusting the voltage to around 1.45V can help. If the system starts and runs fine, gradually lowering the voltage may restore stability. Adjusting timing settings is complex due to numerous interrelated parameters; a Ryzen DRAM Calculator might be useful for those who are serious about tuning.
W
WaZtoX
09-19-2019, 06:11 AM #4

There isn't a straightforward voltage-to-frequency link—it forms a curve where voltage rises more rapidly as frequency increases. DDR4 memory remains stable up to 1.5V. When facing XMP stability issues, manually adjusting the voltage to around 1.45V can help. If the system starts and runs fine, gradually lowering the voltage may restore stability. Adjusting timing settings is complex due to numerous interrelated parameters; a Ryzen DRAM Calculator might be useful for those who are serious about tuning.

J
JebThePleb
Posting Freak
898
09-20-2019, 06:47 PM
#5
I do agree with everything you've said, except the ram voltage. There is simply no need to have it set as high as 1.45. It should run at 1.35v and work as expected. There is no reason other than OC further beyond XMP to increase voltage to 1.45v.
J
JebThePleb
09-20-2019, 06:47 PM #5

I do agree with everything you've said, except the ram voltage. There is simply no need to have it set as high as 1.45. It should run at 1.35v and work as expected. There is no reason other than OC further beyond XMP to increase voltage to 1.45v.

2
20Jacobs
Junior Member
13
09-22-2019, 03:21 AM
#6
1.45 serves as a basic reference, aiming to reduce voltage until stability is lost. It's completely safe because every DDR4 RAM must function at 1.5V. The goal is usually around 1.35, though that's not always achievable. On a less-than-perfect motherboard—especially one that inaccurately shows VRM voltage—it could deviate significantly, possibly even drop further.
2
20Jacobs
09-22-2019, 03:21 AM #6

1.45 serves as a basic reference, aiming to reduce voltage until stability is lost. It's completely safe because every DDR4 RAM must function at 1.5V. The goal is usually around 1.35, though that's not always achievable. On a less-than-perfect motherboard—especially one that inaccurately shows VRM voltage—it could deviate significantly, possibly even drop further.

T
trj55
Member
175
09-26-2019, 06:05 AM
#7
The Ryzen DRAM calculator requests the memory type, but when using Thaiphoon burner, it only displays the manufacturer as Samsung "1 die" without more details.
T
trj55
09-26-2019, 06:05 AM #7

The Ryzen DRAM calculator requests the memory type, but when using Thaiphoon burner, it only displays the manufacturer as Samsung "1 die" without more details.

S
Smeden01
Junior Member
12
09-27-2019, 04:09 PM
#8
It was a bit frustrating... I experienced the same issue with my SKHynix, only displaying part of the die type. In your case, you can likely eliminate Samsung B-Die, especially if all the package timings aren't unusually low—such as 14 or less for the first three or four.
I generated a profile for each Hynix memory type. I started with the one having the most flexible timings and it worked well. Then I tested tighter primary timings from other profiles.
The key points to focus on are the Termination Block settings: ProcODT, RTT_NOM, _WR and _PARK, plus the additional settings like Power Down mode, Gear Down mode, BGS /ALT, and Command Rate.
S
Smeden01
09-27-2019, 04:09 PM #8

It was a bit frustrating... I experienced the same issue with my SKHynix, only displaying part of the die type. In your case, you can likely eliminate Samsung B-Die, especially if all the package timings aren't unusually low—such as 14 or less for the first three or four.
I generated a profile for each Hynix memory type. I started with the one having the most flexible timings and it worked well. Then I tested tighter primary timings from other profiles.
The key points to focus on are the Termination Block settings: ProcODT, RTT_NOM, _WR and _PARK, plus the additional settings like Power Down mode, Gear Down mode, BGS /ALT, and Command Rate.