F5F Stay Refreshed Hardware Desktop Command speed for RAM remains locked at 2N setting.

Command speed for RAM remains locked at 2N setting.

Command speed for RAM remains locked at 2N setting.

B
bordbeinsvein
Member
70
02-07-2016, 09:57 PM
#1
You've adjusted the timing settings and noticed improved performance, but the command rate remains on 2N despite having 2TB RAM. The issue might be related to how the system interprets your configuration. Try verifying the exact values in BIOS or through a different method to ensure consistency. It could also help checking if the CPU model supports the intended settings. As for the hardware, your setup looks solid with the i5-10400F and HyperX components.
B
bordbeinsvein
02-07-2016, 09:57 PM #1

You've adjusted the timing settings and noticed improved performance, but the command rate remains on 2N despite having 2TB RAM. The issue might be related to how the system interprets your configuration. Try verifying the exact values in BIOS or through a different method to ensure consistency. It could also help checking if the CPU model supports the intended settings. As for the hardware, your setup looks solid with the i5-10400F and HyperX components.

M
94
02-08-2016, 06:27 AM
#2
A few bits work better with a 2T command speed. It doesn’t affect performance enough to cause concern.
M
morganmerlin31
02-08-2016, 06:27 AM #2

A few bits work better with a 2T command speed. It doesn’t affect performance enough to cause concern.

C
Cl0ud_Client
Member
169
02-09-2016, 11:34 AM
#3
Your RAM module is labeled for 3200 MHz but only accepts 2666 MHz, and your command rate is stuck at 2N. This might limit performance because the actual speed is constrained by the hardware. It seems the system is preventing you from reaching the full potential due to these restrictions. Also, there doesn’t appear to be an XMP profile configured in your BIOS, which could explain why it isn’t being optimized.
C
Cl0ud_Client
02-09-2016, 11:34 AM #3

Your RAM module is labeled for 3200 MHz but only accepts 2666 MHz, and your command rate is stuck at 2N. This might limit performance because the actual speed is constrained by the hardware. It seems the system is preventing you from reaching the full potential due to these restrictions. Also, there doesn’t appear to be an XMP profile configured in your BIOS, which could explain why it isn’t being optimized.

M
Mummy_Man23
Member
58
02-11-2016, 12:03 AM
#4
2T and 2N is nearly the same thing. No worries there. No, I don't think that command rate is holding back the frequency. I would need to know specifically the rigs hardware specs, or we'd be just guessing.
M
Mummy_Man23
02-11-2016, 12:03 AM #4

2T and 2N is nearly the same thing. No worries there. No, I don't think that command rate is holding back the frequency. I would need to know specifically the rigs hardware specs, or we'd be just guessing.

A
Avidelux
Junior Member
42
02-19-2016, 12:24 PM
#5
What processor and motherboard are you using? If Intel, you should use B560, H570, Z590 or Z490 to exceed the CPU limit. On a 400 board without Z490, an i5 or lower will cap at 2666, while an i7 or i9 on that board will run at 2933.
A
Avidelux
02-19-2016, 12:24 PM #5

What processor and motherboard are you using? If Intel, you should use B560, H570, Z590 or Z490 to exceed the CPU limit. On a 400 board without Z490, an i5 or lower will cap at 2666, while an i7 or i9 on that board will run at 2933.

X
226
02-19-2016, 09:25 PM
#6
command speed 1 versus 2. My old OEM board has very limited BIOS support. With two 8GB sticks I see a command rate drop to 1, and adding more than two causes it to fall to 2. Basically, each memory access adds one to timing. This is done for stability to prevent BSODs. On some boards, using more sticks reduces the maximum clock speed. A command rate of 2 only shows up as a small -1% to -2% drop in synthetic tests.
X
X_Impossible_X
02-19-2016, 09:25 PM #6

command speed 1 versus 2. My old OEM board has very limited BIOS support. With two 8GB sticks I see a command rate drop to 1, and adding more than two causes it to fall to 2. Basically, each memory access adds one to timing. This is done for stability to prevent BSODs. On some boards, using more sticks reduces the maximum clock speed. A command rate of 2 only shows up as a small -1% to -2% drop in synthetic tests.