Originally Posted by neurotix
Getting a good, stable overclock on these chips with low heat requires massive cooling as they run hot as hell and a board with good loadline calibration.
My Crosshair has DIGI+ VRMs that are heatsinked. I looked up your board and it says it has DIGI+ Power Phase design. So, you might have some of the options I do for power phase adjustment. It looks like your board has heatsinked VRMs so you should be good with these settings. Some of them might be missing, just mimic it as much as you can. Getting these settings right made the difference between having a 5ghz system and a 4.7ghz system.
I got these settings from Krusher33 who used to fold for Dark Predators on a 5ghz 8350 on custom water.
Mine are set thusly:
CPU Loadline Calibration: High (Don't set these any higher than high. You will have some vdroop under load with these settings but that's normal for these chips. If you set them to extreme you will get more voltage on the CPU under load than what you set for CPU VID. This will make the chip run much hotter.)
CPU/NB Loadline Calibration: High
CPU Overcurrent Protection: Disabled (We disable this because sometimes overclocking makes the temp sensors on the chip a little screwy. Sometimes they will read insane values over 90C for a split second when stress testing. This is erroneous. However, if you're running Prime on an overclocked chip and your system shuts off completely, make sure this is disabled and it will fix it.)
CPU/NB Overcurrent Protection: 130%
CPU PWM Phase Control: Extreme
VRM Fixed Frequency Mode: 550khz
Additionally, I can do 4.7ghz at 1.4875v and it passes an hour of Prime95 with temps around 52C. An H80 isn't going to cool as effectively. I can run 5ghz at 1.575v (yikes) and it will be stable in folding@home but fail Prime95 almost instantly on one of the cores. The temps also exceed 60C in Prime. However, web browsing and gaming at 5ghz don't put anywhere near that kind of load on the chip, and are totally stable. For everyday use I can run 5ghz and the only issue is coming back to a frozen mouse cursor, requiring a system reboot, every few days.
Additionally, leave your CPU-NB and HyperTransport Link at stock, which should be 2200mhz for both. I had to raise my CPU-NB to 2400mhz because I run my RAM at 2400mhz. The CPU-NB frequency needs to match that of the RAM. Unlike with Phenom IIs, raising the CPU-NB frequency doesn't provide a linear increase in RAM and cache bandwidth with FX chips.
Good luck, I hope this helps.