I've been looking into overclocking my Cpu and I have come across some questions that I can't find definitive answers to on Google. Little background on my system first:
Cpu: i5 7600k
Mobo: Msi Z270 Sli plus
Current cooler: hyper 212 Evo, but I'll be putting a DH-15 on this afternoon.
I am shooting for 4.5 - 4.6 GHz, is that gain worth it over the 4.2GHz boost clock that the 7600k achieves? I mostly play Wow and Overwatch with a 144Hz 1080p monitor, so rather cpu bound games. But is a 400MHz overclock even worth the hassle?
If so, what is the best vcore method to use? Some people swear by the manual method, but that forces constant voltage even when idle. So is adaptive the best? Also when using adaptive vcore, is Llc required?
Last night I decided to push the core multiplier up to 4.5ghz just to see if the hyper 212 could handle it. I set the vcore to adaptive and put the max at 1.15volts. I then did a simple 5 min stress test in XTU. CPU-z said that the vcore was 1.16v or so and the system passed. But when I ran the XTU benchmark, vcore went up to 1.20v. Is that a side effect of adaptive vcore, or is that LLC coming into play?
Cpu: i5 7600k
Mobo: Msi Z270 Sli plus
Current cooler: hyper 212 Evo, but I'll be putting a DH-15 on this afternoon.
I am shooting for 4.5 - 4.6 GHz, is that gain worth it over the 4.2GHz boost clock that the 7600k achieves? I mostly play Wow and Overwatch with a 144Hz 1080p monitor, so rather cpu bound games. But is a 400MHz overclock even worth the hassle?
If so, what is the best vcore method to use? Some people swear by the manual method, but that forces constant voltage even when idle. So is adaptive the best? Also when using adaptive vcore, is Llc required?
Last night I decided to push the core multiplier up to 4.5ghz just to see if the hyper 212 could handle it. I set the vcore to adaptive and put the max at 1.15volts. I then did a simple 5 min stress test in XTU. CPU-z said that the vcore was 1.16v or so and the system passed. But when I ran the XTU benchmark, vcore went up to 1.20v. Is that a side effect of adaptive vcore, or is that LLC coming into play?