Tuesday, July 23rd 2019
CCX Overclocking Tool for AMD CPUs Updated With New Features
Today an overclocking utility for AMD Ryzen CPUs called "Work Tool" has been updated with new features. The tool enables per-CCX overclocking, which is said to enable additional overclocking performance if one CCX is more capable than the other, so the whole CPU doesn't have to run at the speed of a slower CCX to be stable. The tool has been released by user shamino1978 on Overclock.net forums.
The reason for overclocking Ryzen CPUs on per CCX basis is because if you want to overclock a single core inside a CCX, the second core must run at a 1 GHz difference, meaning that if one core is OC'd to 4.5 GHz, the second core must run at 3.5 GHz. Such design is to be blamed on CPU's internal clock divider. However, you can use the Work Tool to do individual CCX overclocking and gain additional performance. Additionally, the tool has been updated to support tweaking of voltage aka VID. There are two versions of the tool, one which is smaller and has less features and one which can tweak the voltages. The smaller version is available here, while the bigger, more capable version is available here.
Source:
r/AMD
The reason for overclocking Ryzen CPUs on per CCX basis is because if you want to overclock a single core inside a CCX, the second core must run at a 1 GHz difference, meaning that if one core is OC'd to 4.5 GHz, the second core must run at 3.5 GHz. Such design is to be blamed on CPU's internal clock divider. However, you can use the Work Tool to do individual CCX overclocking and gain additional performance. Additionally, the tool has been updated to support tweaking of voltage aka VID. There are two versions of the tool, one which is smaller and has less features and one which can tweak the voltages. The smaller version is available here, while the bigger, more capable version is available here.
64 Comments on CCX Overclocking Tool for AMD CPUs Updated With New Features
Ouch. THE Shamino is a renowned overclocker of many years in the scene and multiple WR holder.
This is hacking FIT limits, the last line of protection for the processor
If anyone in the world outside AMD engineers knows something about the inner workings of AMD CPU's, that's 1usmus.
I totally trust his judgment and certainly don't want to burn my CPU for no good reason.
p.s.
@1usmus any ETA on the memory tool updated for Matisse ?
forums.guru3d.com/threads/ryzen-dram-calculator-1-5-1-release-overclocking-dram-on-am4.422224/
Not sure what kind of magic he used to get those numbers out, but they work ! Removes most of the guesswork from timings tightening and memory overclocking.
Love it !
So he clearly knows more than us about those CPUs.... heck, he might even secretly be an AMD employee ;)
P.s. I checked the words of this respected user (The Stilt)
www.overclock.net/forum/28055052-post324.html
My advice is to wait and see - dont start screwing around with this unless you're willing to risk your CPU and your board.
I will make an announcement in the middle of the week
This is false for both Intel and AMD.
As usual all overclocking are done on your own risk. This does not change no matter what tool you are using.
with all the hype for amd and heckling for intel's 14++++++++, zen 3000 topped 100mhz over zen 2000 so he's abolutely right.
sorry if that hurts you in a personal way.
amd never said they were gonna stomp intel like ppl like you on forums argued.
they released a very good family of cpus,most of them better value than intel counterparts,but the thing about amd smashing intel was due to internet hypeboys.
and this is mostly on people who hyped zen 2 on froums,not amd themselves.amd never promised anything remotely close to what people kept insisting zen 2 would be.
using a dangerous tool to prove a point that ryzen can do 4.5ghz is silly,just enjoy zen 3000 for what is,an excellent all round cpu with great energy efficiency.don't ruin it with a stupid tool.
Also remember that overclocking could include all types of hacks, your own risk if you decide to use it.
Also I wasn't aware AMD was unstable. You're trying way too hard.