F5F Stay Refreshed Power Users Overclocking A suggested oc is provided for this.

A suggested oc is provided for this.

A suggested oc is provided for this.

Pages (2): 1 2 Next
D
ddawgz01
Junior Member
10
10-31-2016, 06:52 AM
#1
Your current setup includes an Asus Z170 pro gaming rig with an Intel i5 6600K processor and a Hyper TX3 EVO cooler. A suitable overclocking capacity would be considered.
D
ddawgz01
10-31-2016, 06:52 AM #1

Your current setup includes an Asus Z170 pro gaming rig with an Intel i5 6600K processor and a Hyper TX3 EVO cooler. A suitable overclocking capacity would be considered.

S
STEVEJasonson
Member
171
11-16-2016, 02:00 AM
#2
Their settings are flexible based on the chip, as each one varies in performance. Begin with low temperatures; the tx3 isn't an excellent cooler. Install OCCT, test the system, and verify if the cooler can handle the demands for overclocking.
S
STEVEJasonson
11-16-2016, 02:00 AM #2

Their settings are flexible based on the chip, as each one varies in performance. Begin with low temperatures; the tx3 isn't an excellent cooler. Install OCCT, test the system, and verify if the cooler can handle the demands for overclocking.

X
Xx_LifeShot_xX
Junior Member
3
11-16-2016, 10:52 AM
#3
Their settings are flexible based on the chip, as each one varies in performance. Begin with low temperatures; the TX3 isn't particularly effective as a cooler. Install OCCT, test the system, and verify if the cooler can support overclocking.
X
Xx_LifeShot_xX
11-16-2016, 10:52 AM #3

Their settings are flexible based on the chip, as each one varies in performance. Begin with low temperatures; the TX3 isn't particularly effective as a cooler. Install OCCT, test the system, and verify if the cooler can support overclocking.

D
darksoup
Member
127
12-07-2016, 08:00 AM
#4
Their performance really depends on the chip they received, as everyone overclocks differently. Start with something small; the tx3 isn't a great cooler. Try downloading OCCT and see how your temperatures look—check if it's enough to even push it overclock. I know the tx3 isn't the top choice, but I believe a decent cooler could be around 3.9 or 4.2, and my temps are about 52 while playing BF1 at full speed.
D
darksoup
12-07-2016, 08:00 AM #4

Their performance really depends on the chip they received, as everyone overclocks differently. Start with something small; the tx3 isn't a great cooler. Try downloading OCCT and see how your temperatures look—check if it's enough to even push it overclock. I know the tx3 isn't the top choice, but I believe a decent cooler could be around 3.9 or 4.2, and my temps are about 52 while playing BF1 at full speed.

_
_FireDragon_
Junior Member
13
12-07-2016, 12:38 PM
#5
Verify the temperatures during the stress test, not while playing.
_
_FireDragon_
12-07-2016, 12:38 PM #5

Verify the temperatures during the stress test, not while playing.

C
Chibiknight25
Junior Member
7
12-07-2016, 11:43 PM
#6
removed duplicate
C
Chibiknight25
12-07-2016, 11:43 PM #6

removed duplicate

I
iiSweeTzz
Posting Freak
862
12-12-2016, 11:59 AM
#7
Your current build includes an Asus Z170 pro gaming rig, an Intel i5 6600K processor, and a Hyper TX3 EVO cooler. What overclocking settings would be suitable for this configuration?
It largely depends on your specific CPU and system, but you should be able to achieve around 4.2GHz.
Install CPU-Z to verify BIOS configurations and monitor Vcore readings.
Use HWMonitor to track core temperatures continuously.
Run OCCT for stability and maximum temperature checks.
Disable turbo, EIST, and all energy-saving modes during overclocking.
Set the Vcore to 1.35V.
Adjust your multiplier to 42 and execute OCCT-Small Blocks for 30 minutes, observing temperatures. If they stay below 80°C, increase the multiplier to 43 and repeat. Continue this process until temperatures exceed 80°C (or you encounter a blue screen or error in OCCT). Then reduce the multiplier by one and retest.
While testing, keep an eye on Vcore via CPU-Z; if it remains at 0.01V or higher than your BIOS setting, it indicates Vdroop. Apply some LLC to mitigate this. Aim for sufficient LLC to limit Vdroop without causing Vboost (excessive voltage spikes).
Once stable, proceed with OCCT-Large for 3 hours to confirm stability. If you encounter crashes or errors, decrease the multiplier by one and retry. Continue until a stable multiplier is identified, allowing OCCT-Large to run smoothly for 3 hours.
After reaching a stable setting with temperatures under 80°C, gradually lower Vcore in increments of 0.01V while re-running OCCT-Large. Stop when stable operation is achieved with minimal voltage fluctuations.
At this stage, you should determine the highest multiplier that maintains stability and keeps temperatures below 80°C, achieving the lowest possible Vcore. This defines your maximum overclock level.
Finally, consider re-enabling EIST and possibly C-1E c-state for further optimization.
I
iiSweeTzz
12-12-2016, 11:59 AM #7

Your current build includes an Asus Z170 pro gaming rig, an Intel i5 6600K processor, and a Hyper TX3 EVO cooler. What overclocking settings would be suitable for this configuration?
It largely depends on your specific CPU and system, but you should be able to achieve around 4.2GHz.
Install CPU-Z to verify BIOS configurations and monitor Vcore readings.
Use HWMonitor to track core temperatures continuously.
Run OCCT for stability and maximum temperature checks.
Disable turbo, EIST, and all energy-saving modes during overclocking.
Set the Vcore to 1.35V.
Adjust your multiplier to 42 and execute OCCT-Small Blocks for 30 minutes, observing temperatures. If they stay below 80°C, increase the multiplier to 43 and repeat. Continue this process until temperatures exceed 80°C (or you encounter a blue screen or error in OCCT). Then reduce the multiplier by one and retest.
While testing, keep an eye on Vcore via CPU-Z; if it remains at 0.01V or higher than your BIOS setting, it indicates Vdroop. Apply some LLC to mitigate this. Aim for sufficient LLC to limit Vdroop without causing Vboost (excessive voltage spikes).
Once stable, proceed with OCCT-Large for 3 hours to confirm stability. If you encounter crashes or errors, decrease the multiplier by one and retry. Continue until a stable multiplier is identified, allowing OCCT-Large to run smoothly for 3 hours.
After reaching a stable setting with temperatures under 80°C, gradually lower Vcore in increments of 0.01V while re-running OCCT-Large. Stop when stable operation is achieved with minimal voltage fluctuations.
At this stage, you should determine the highest multiplier that maintains stability and keeps temperatures below 80°C, achieving the lowest possible Vcore. This defines your maximum overclock level.
Finally, consider re-enabling EIST and possibly C-1E c-state for further optimization.

J
jkgaga15
Member
234
12-12-2016, 01:50 PM
#8
1.35 is quite too aggressive for that cooler or simply for a 4.2 overclock.
J
jkgaga15
12-12-2016, 01:50 PM #8

1.35 is quite too aggressive for that cooler or simply for a 4.2 overclock.

E
Egg_
Junior Member
40
12-12-2016, 02:07 PM
#9
removed duplicate
E
Egg_
12-12-2016, 02:07 PM #9

removed duplicate

G
234
12-16-2016, 12:04 AM
#10
Zerk2012 shared their experience on the topic. They found that 1.35 is quite aggressive, possibly just for a 4.2 overclock. A 1.35V setting is safe for the CPU. Their approach involves adjusting the Vcore to the highest comfortable level for their CPU, gradually increasing the multiplier while watching temperatures, and then slightly reducing it if stability is maintained. They prefer starting with the maximum known stable Vcore before tweaking. For their EVO212 model, they initially set 1.35 at 4.4GHz but faced blue screens at higher speeds, leading them to lower it to 1.36 briefly before reverting to 1.35 and 4.6G. They tested various values down to 1.28 before encountering core errors during OCCT, then settled back to 1.29V and 4.6G after running stability checks. They also mentioned using EIST and c-states with these changes, re-enabling them once stable.
G
ghostghillie07
12-16-2016, 12:04 AM #10

Zerk2012 shared their experience on the topic. They found that 1.35 is quite aggressive, possibly just for a 4.2 overclock. A 1.35V setting is safe for the CPU. Their approach involves adjusting the Vcore to the highest comfortable level for their CPU, gradually increasing the multiplier while watching temperatures, and then slightly reducing it if stability is maintained. They prefer starting with the maximum known stable Vcore before tweaking. For their EVO212 model, they initially set 1.35 at 4.4GHz but faced blue screens at higher speeds, leading them to lower it to 1.36 briefly before reverting to 1.35 and 4.6G. They tested various values down to 1.28 before encountering core errors during OCCT, then settled back to 1.29V and 4.6G after running stability checks. They also mentioned using EIST and c-states with these changes, re-enabling them once stable.

Pages (2): 1 2 Next