• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

**LETS SEE YOUR PILEDRIVER OVERCLOCKS - LET ME START WITH 5GHz+!!**

I've been trying out nkata's high fsb OC, he's seen my screenies on OC.net. It's going OK so far, it's stable at 306x16 for 4.9Ghz and has given me my best Cinebench score to date. :)

Now I'm working on the other advise floating around of linking the HT, NB and RAM speeds to reduce stress and enable lower voltages. I'm sceptical tbh but it's worth a try. Going OK so far though, I've backed off the bus speed to 300 so that I can link them all at 2400Mhz. Pretty pleased with my 30nm RAM doing 2400Mhz, although I've backed the timings off to 12-12-12-30 so I'll see if I can get that back to CL11 later.

Edit, nope RAM maybe not stable needs more work! :p
 
Last edited:
Pretty pleased with my 30nm RAM doing 2400Mhz, although I've backed the timings off to 12-12-12-30 so I'll see if I can get that back to CL11 later.

Edit, nope RAM maybe not stable needs more work! :p

Maximum I've seen on the patriot 2133 is about 2100MHz at CL11 at 1.65V so I cannot see me syncing all the busses at that. I cannot see the validity of syncing memory with HT and NB. It may work or be sensible but I am currently only syncing HT and NB at 2400-2500MHz.

In the thoroughbred / barton days it used to be that you did sync the fsb and memory bus ie 200/200 or 166/166 however things have changed a bit since then

Another Saturday coming up playing around with voltages I think. Will look at IBT stability this time with max ram, not max gflops though. Just 1 hour stable runs.

EDIT:

Phanteks are really good IMO, I have not had major cooling issues with CPU or VRM provided I keep it fairly sensible.
 
Last edited:
OK so I am going to try watercooling an 8350.

Being a bit cheap and a skinflint, I have so far acquired

Used XSPC delta 2 universal CPU block
New 2m of tubing and 6 monsoon fittings
Used EK 2.2 pump and combo tube res.
for £35
Used EK supreme universal CPU block + 1366 CPU block for £12
An offer of a brand new 240mm rad for £20

So a current total outlay of £67 with a choice of two possible CPU blocks to suit AMD.

Being a complete noob in this area, it may take me some time to get it right but I think I have enough for a basic loop to experiment with.

I have also resurrected this thread for what it is worth.
 
After many posts, and a significant number of tests my experiences overclocking an 8350 are as follows.

The key difference is what stress testing application I use as this greatly differs what overclock I am both capable of, and happy with. It is worth noting from the outset 4.8 seemed stable using AIDA (at a very respectable 1.46125) until I noticed during an encode using handbrake temps soared to 70 degrees, Prime and OCCT would require 1.5125v to achive 4.8 stable, but temps sky rocket at this, that said I must have had nearly 2 weeks usage stable before I noticed this (and often temps didn't exceed 47 when gaming), I also experienced no crashes throughout even with the high temps, but maybe the CPU was throttling as CnQ was enabled when I initially did this.

I am using a Phanteks PH-TC14PE air cooler, with 3 140mm fans, temperatures up to and including 4.6 are good in Prime95, and I am stable for 24 hours using 1.45v (27.9), temps hit a maximum of 57 on the core but typically sit around 54 which I like as it keeps the fan profile silent, jumping to 4.7 requires 1.49325v, and temps hit circa 62 on the core, and rarely dip below 58. Clearly 4.6 is my sweet spot. Reading many many threads and posts by other users, it's quite clear 4.5-4.7 seems to be a consensus for air cooling.

For 4.6, I have adjusted a few other variables, firstly I found the same stability but lower temps (circa 5 degrees) by using a lower CPU/NB of 1.375, I also lowered the CPU VDDA down to 2.2 down from the default 2.5.

On my 990FX Sabertooth (R1) board, I have set CPU LLC at Ultra High, CPU/NB on high to counteract droop, and CPU current capacity & CPU/NB current capability at 130% with the intention of allowing the board to use 143A & stop overvolting.

Finally I have locked HT at 2600, CPU/NB at 2200 and DRAM at 1600 manually, disabled spread spectrum but left all power saving features active with the exception of CnQ which I have set to "disabled by CPU", although I may revert this back. I just wanted to ensure no throttling was taking place.

System power draw with monitors on standby under full load 362W (Prime95 blend).
 
Last edited:
Chris*
Your experience mirrors mine almost exactly. For day to day usage, I am at 4.675GHz with vcore set at 1.48. I have reduced LLC by a notch less than yours although I used the same as you have posted here when I was benching at 5GHz. Aida 64 runs at 5GHz, as does x264 FHD and a couple of other encoding benches and within spec. temps on the Phanteks. I have memory at 2GHz, HT and NB at 2400MHz 24/7. I use power saving as well. I am hitting 350W on prime at the wall but as someone pointed out to me that could be 20% less due to efficiency of the PSU ie 280W system load.

This cpu has made me think of watercooling it which I have never done on any other system. We will see if I can do that and also mod some motherboard cooling as well.
 
I found the same as both of you.
4.6Ghz is the highest stable frequency i could mange.
NB at 2,2 or 2.4, 2.6 kinda works but needs lots of extra NB volts and isn't really stable when stressed.
Getting prime stable above 4.6 needs high vcore >1.5 on load and the thermal output is too great to maintain load for very long.
The big fft's pass easy enough it is the small fft's where the heat and power consumption go north.
A t 4.6 Hgz running prime AVX large fft's i was pulling about 360w from the wall, with the small ftt's 8k's and 12k's around 420w.
 
Last edited:
nice to see you guys posting your actual use speed of 4.5-4.6 like i said would be months ago :D

5 ghz is too much for these and gibbo you naughty boy :p bit of a false sales pitch tbh. but i guess it shifted a lot of pd chips :)
 
nice to see you guys posting your actual use speed of 4.5-4.6 like i said would be months ago :D

5 ghz is too much for these and gibbo you naughty boy :p bit of a false sales pitch tbh. but i guess it shifted a lot of pd chips :)

4.7GHz is probably the max on air with eight workers prime stable 24/7. 5Ghz is easily achievable if you do not prime on more than four workers.

I am looking to watercool to try for 5GHz prime stable, but in comparison with 2500/2700 most of which seem to be overclocked at 4.4-4.5GHz it is still a very good CPU for all uses.
 
Dg
Most folks didn't think these chips could run at 5Ghz under any significant load.
Experience with BD had already taught us that.

Granted there were a few drum bangers trying to create that impression.
 
You need proper water cooling for higher 24/7 clocks with these, then it's very possible to achieve 5ghz. But it also depends on the chip you get and the board you've got. I got a stinker, on a decent board, and still manage 4.9ghz 24/7.

You'd be lucky to get 4.7ghz on air.
 
You need proper water cooling for higher 24/7 clocks with these, then it's very possible to achieve 5ghz. But it also depends on the chip you get and the board you've got. I got a stinker, on a decent board, and still manage 4.9ghz 24/7.

You'd be lucky to get 4.7ghz on air.
This. I did get 4.8GHz with my silver arrow but my temps were too high. Core temps read 65 degrees during an hour and a half 1080p encode in Handbrake. Was a bit nervewracking. I'll see if I can dial down the voltage a bit and maintain the speed but I can run 24/7 at4.6-4.7 with temps in the high 50's only under heavy load. I won't get 5Ghz without a custom water rig. Might have to wait until next septembers OU grant and get a bigger case and the gubbins to try it. Still, more than happy with the performance I've got now.
 
Back
Top Bottom