Quote (Ghot @ Oct 22 2013 06:32pm)
1. click the tiny auto button to turn it off.
2. turn the fan speed up to about 40-50%
3. click apply overclocking at system startup
4. then the hard part ...move the core clock slider to the right ONLY 5-10Mhz.
5. Repeat step #3 and reboot comp.
6. Run Unigine Valley benchmark to see if you get any artifacts or screen tearing etc. If you do, lower the core clock a bit. If you don't repeat steps 4 and 5.
7. when you get to the highest core clock you can w/o tearing or artifacts...and reasonable temps...then the only way to go higher is to add core voltage...VERY slowly..like .05mv at a time.
8. You can then do the same with memory clock as you did with the Core Clock
Don't add more than .2 mv w/o more expert help
That's the general idea.
1. This isnt a neccesity<- fuck spelling. Typically they do fine on auto. And if anything if you're worried i'd put it to 80%~
2. same as #1
3. Yes.
4. Eh i usually do 20-50mhz depending. Helps get a general idea of where its unstable at, Then fine tune. Saves a bit of time.
5. Why restart? You don't have to restart to OC.
6. OCCT is another good prog, They have an automatic error test. Usually errors instantly if its even slightly unstable. And takes less time to do then a full benchmark.
7. Agree.
8. True, But memory OC generally doesnt do all that much. And memory gets hot pretty quick
