F5F Stay Refreshed Hardware Desktop No, it doesn't fit the usual OC profile.

No, it doesn't fit the usual OC profile.

No, it doesn't fit the usual OC profile.

O
Ozwego
Member
191
12-16-2019, 01:08 PM
#1
Hi everyone. With the example you shared—having a motherboard supporting up to 4133MHz (OC), a DDR4 kit at 3000MHz, and a Ryzen 5 3600 at 3200MHz—setting RAM via XMP, it runs smoothly at 3000MHz with 1.35V—does that mean it’s considered OC? I was under the impression OC refers to exceeding the system’s supported limits. Thanks for clarifying!
O
Ozwego
12-16-2019, 01:08 PM #1

Hi everyone. With the example you shared—having a motherboard supporting up to 4133MHz (OC), a DDR4 kit at 3000MHz, and a Ryzen 5 3600 at 3200MHz—setting RAM via XMP, it runs smoothly at 3000MHz with 1.35V—does that mean it’s considered OC? I was under the impression OC refers to exceeding the system’s supported limits. Thanks for clarifying!

J
juri1990
Senior Member
441
12-23-2019, 04:21 PM
#2
Technically it's viewed as overclocking due to XMP support. The RAM package you possess is likely 3000MHz CL15 or 3000MHz CL16, offering tighter clock speeds than JEDEC standards (around 3000MHz CL20). Adjusting settings falls under OC classification. It's only a minor OC since it stays within the hardware's rated limits, but it remains technically an overclock.
J
juri1990
12-23-2019, 04:21 PM #2

Technically it's viewed as overclocking due to XMP support. The RAM package you possess is likely 3000MHz CL15 or 3000MHz CL16, offering tighter clock speeds than JEDEC standards (around 3000MHz CL20). Adjusting settings falls under OC classification. It's only a minor OC since it stays within the hardware's rated limits, but it remains technically an overclock.

G
grisou47
Member
133
12-23-2019, 04:45 PM
#3
The main distinction is likely whether it can damage the hardware or not.
G
grisou47
12-23-2019, 04:45 PM #3

The main distinction is likely whether it can damage the hardware or not.