Ryzen 1700 Literally Won't OC
Ryzen 1700 Literally Won't OC
never handled a gigabyte mb, a valuable lesson for me. Congratulations, Karadjgne.
You can also explore these recommendations, which may assist some users. There are also links to OC guides for the Ryzen 1700.
Here are some alternative phrasings for your text:
My Discoveries:
The Ryzen 5 1600 can easily reach 3800 Mhz with a low Vcore and specific SOC voltage settings.
It needs a bit more voltage above 3800 Mhz to stay stable.
Even after setting the timings to 14-14-14-14-34, my RAM was running at 15-15-15-15-36.
Setting 1.38V on my RAM actually leads to 1.40V consistently throughout the day.
At 3825 Mhz / 1.320V / 1.128V… Idle = 33c / 15W / 1050rpm. Load = 63c / 82W / 1500rpm
My Configuration:
Windows 10 Pro x64 (Most Recent Update)
AMD Ryzen Chipset Drivers Download Here
AMD Ryzen Balanced Performance Plan Download Here
Game Mode turned off (Windows)
Core Performance Boost turned off (Bios > Advanced CPU Core Settings)
Global C-state Control turned off (Bios > Advanced CPU Core Settings)
Windows HPET turned off (Bios > Power)
Extreme Memory Profile disabled
My Overclocking:
AMD Ryzen 5 1600 @ x38.25 / 3825 Mhz
Dynamic Vcore (DVID) offset +0.078V (1.332V HWMonitor)
Dynamic VCORE SOC (DVID) offset +0.258V (1.116V HWMonitor)
DRAM Voltage (CH A/B) @ 1.380V
DRAM Memory Frequency @ x32.00 / 3200 Mhz
DRAM Memory Sub Timings @ 15-15-15-15-36
Turn off core performance enhancement
Disable global c-state
Turn off Windows HPET
Disable XMP
Please try the VCore and SOC voltage settings above
I've already tried all these options and still can't get it to work.
I submitted a ticket with Gigabyte for a board RMA.
I don't have any other ideas left! Thanks for your assistance
It's strange... Gigabyte seems tricky... MSI is a lot easier, I just adjusted a couple of settings, really.
It's really strange... Gigabyte seems tricky... MSI is a lot easier, I just adjusted two settings, basically... So did I do it the first time? Changed multiplier and vcore voltage. That's what's getting me frustrated but I'm leaning towards a motherboard problem.