F5F Stay Refreshed Hardware Desktop RAM cannot be overclocked.

RAM cannot be overclocked.

RAM cannot be overclocked.

O
olivia9652
Junior Member
Find
18
06-07-2019, 02:01 AM
#1
I’m working on assembling my first dedicated gaming build, which includes pushing components beyond their standard limits. This means experimenting with various parts and even some unconventional adjustments. As a beginner, I’m also making mistakes and will share some challenges soon. My main concern right now is my RAM setup. I purchased a 2x16GB G.Skill Trident Z Neo module rated for speeds of 16-16-16-36 at 3600 compute units. I’m using it with an ASRock Phantom Gaming Z390/itx motherboard and an i9-9900K processor. Initially, I tried the XMP profile but it didn’t work. Then I slowly increased the speed and fine-tuned the timings, hoping to hit the official ratings. So far, I reached 22-22-22-56 at 3200 compute units before the system crashes and starts looping until I reset the UEFI. I’m pretty sure something is wrong, but I want to confirm my assumptions before returning it. I’m not familiar with many of these settings, and I don’t know all the BIOS details, so I’m trying to avoid making further errors. Could you advise me on whether adjusting subtimings would help or if I should stick with what I have?
Reply
Reply
O
olivia9652
06-07-2019, 02:01 AM #1

I’m working on assembling my first dedicated gaming build, which includes pushing components beyond their standard limits. This means experimenting with various parts and even some unconventional adjustments. As a beginner, I’m also making mistakes and will share some challenges soon. My main concern right now is my RAM setup. I purchased a 2x16GB G.Skill Trident Z Neo module rated for speeds of 16-16-16-36 at 3600 compute units. I’m using it with an ASRock Phantom Gaming Z390/itx motherboard and an i9-9900K processor. Initially, I tried the XMP profile but it didn’t work. Then I slowly increased the speed and fine-tuned the timings, hoping to hit the official ratings. So far, I reached 22-22-22-56 at 3200 compute units before the system crashes and starts looping until I reset the UEFI. I’m pretty sure something is wrong, but I want to confirm my assumptions before returning it. I’m not familiar with many of these settings, and I don’t know all the BIOS details, so I’m trying to avoid making further errors. Could you advise me on whether adjusting subtimings would help or if I should stick with what I have?

Reply
Reply
S
sopispink
Member
Find
217
06-07-2019, 03:08 AM
#2
No, there isn't a RAM listed for the QVL.
Reply
Reply
S
sopispink
06-07-2019, 03:08 AM #2

No, there isn't a RAM listed for the QVL.

Reply
Reply
T
T4K3N
Junior Member
Find
1
06-12-2019, 04:22 PM
#3
I didn't consider it at first. I'll verify it now. None of the Trident Z Neo sets are included.
Reply
Reply
T
T4K3N
06-12-2019, 04:22 PM #3

I didn't consider it at first. I'll verify it now. None of the Trident Z Neo sets are included.

Reply
Reply
D
djepinio
Member
Find
67
06-13-2019, 11:43 AM
#4
Check if the memory voltage is correctly configured at 1.35V. If not, increase it to 1.5V VCCSA and VCCIO, adjusting SA to 1.3V and IO to 1.2V as needed.
Reply
Reply
D
djepinio
06-13-2019, 11:43 AM #4

Check if the memory voltage is correctly configured at 1.35V. If not, increase it to 1.5V VCCSA and VCCIO, adjusting SA to 1.3V and IO to 1.2V as needed.

Reply
Reply
1
111carys111
Posting Freak
Find
832
06-13-2019, 08:36 PM
#5
I kept the voltage steady at 1.35V. I'll adjust it slightly and check if performance gets better.
Reply
Reply
1
111carys111
06-13-2019, 08:36 PM #5

I kept the voltage steady at 1.35V. I'll adjust it slightly and check if performance gets better.

Reply
Reply
P
Persiphany
Member
Find
159
06-13-2019, 09:10 PM
#6
I'm back in the situation! I adjusted the VCCSA, VCCIO, and RAM voltage settings, set the BIOS from 1.30 to 1.60, and tried updating it. It seems the memory support might help, but I still can't get 17-17-17-39 at 3200 or 3300. Since the motherboard doesn't support my kit, I haven't checked yet, and I'm hoping ASRock will release a compatible BIOS or I'll need to find another supported setup.
Reply
Reply
P
Persiphany
06-13-2019, 09:10 PM #6

I'm back in the situation! I adjusted the VCCSA, VCCIO, and RAM voltage settings, set the BIOS from 1.30 to 1.60, and tried updating it. It seems the memory support might help, but I still can't get 17-17-17-39 at 3200 or 3300. Since the motherboard doesn't support my kit, I haven't checked yet, and I'm hoping ASRock will release a compatible BIOS or I'll need to find another supported setup.

Reply
Reply
J
JoshA2006
Junior Member
Find
5
06-16-2019, 07:52 AM
#7
I managed to replace the Trident Z Neo package with a standard 32 GB Trident Z 3600 model, which fits the 17-19-19-39 timings and is available on ASRocks QVL. I reached 3200 compute units before hitting the same performance ceiling as before. The XMP profile didn’t help, but it seems I was surprised it would work. Now I’m not sure if the issue lies with the motherboard, the RAM itself, or something else entirely.
Reply
Reply
J
JoshA2006
06-16-2019, 07:52 AM #7

I managed to replace the Trident Z Neo package with a standard 32 GB Trident Z 3600 model, which fits the 17-19-19-39 timings and is available on ASRocks QVL. I reached 3200 compute units before hitting the same performance ceiling as before. The XMP profile didn’t help, but it seems I was surprised it would work. Now I’m not sure if the issue lies with the motherboard, the RAM itself, or something else entirely.

Reply
Reply