Overclock.net banner
1 - 20 of 87 Posts

·
Premium Member
Joined
·
12,928 Posts
Discussion Starter · #1 ·
I'm not usually one for finding amazingly fast 24/7 clocks but in light of mass pm bombardment over the last year or so I figured I would put a quicky together and show you how I do it. This is just how I've been going about things, I know it's not perfect it's just quick and easy


Go here for more guides http://www.overclock.net/amd-general...edge-base.html

You will need the following software.

Prime 95. This stress test really throws a spanner in the works of amd systems, I can't recommend using any other over this.
http://www.softpedia.com/progDownloa...oad-76537.html

AMD Overdrive. Windows overclocking utility, temp monitoring, the works.
http://game.amd.com/us-en/drivers_overdrive.aspx

CPUID HW monitor and cpu-z, the name says it all.
http://www.cpuid.com/

Whatever OC utility came with your motherboard.

I'm putting a few bios pictures up, I can't cater for every board because 1; I don't have that many
and 2; I don't have all day. If you don't know your way around a bios or know what you are doing then you shouldn't really be prating about doing this so stop reading now if this is you
Take the advice lightly because this is just how I do things personally, quick and dirty
I'm not going to take responsibility for you breaking any hardware so don't go being silly now and don't take this as gospel.

Step One
As with any system the first thing you should be doing is disabling all the stuff you do not need.




If you aren't using it turn it off, it's not doing any good


Throughout this entire process you are going to be messing about in the bios a lot So it's handy to save the profiles under a different name every time you make some progress in case something goes wrong so you can just revert back. Trust me it will save you some time and headaches.





Step 2 The system limits.

Now for the boring part.. Finding the systems limits.
First call of order is the memory. We are getting this out of the way first as it's one of the more difficult parts and if you don't do it now you are not going to be having a good time and will probably fail every stress test from here on in.

Find a safe voltage for your ram kit or more importantly IC's and make sure you don't go over that. We are trying to find a safe OC, nothing ground breaking here so if you don't want degradation then don't do it. While you are doing your ram research you can find what settings others are using to give you a ballpark idea of what to expect. No 2 kits are the same so you will have to find out yourself.

I use super pi 32m for finding that ram limits as it often finds errors memtest misses especially with AMD systems




This particular motherboard above had issues going above 1640mhz on the ram at these settings. I know these timings offer optimum performance from previous testing and 1632mhz was memtest and super pi 32m stable so 1600 cas6 up to around 1632 is well within the realms of stability so that's the margin we have to play with. Basically if we stay within those clock speeds then we know that ram is not the issue from now on.

It's worth trying different dividers and timmings/speeds to see which offers the best performance for your system, find stable clocks now and fine tune later when you have your northbridge and cpu overclocks fine tune to offer maximum throughput so you know the exact performance increases. This is something to come back to.

Northbridge voltage is known to help ram stability in some cases. Under 1.2v is the safe limit on most motherboards so I don't recommend going over that here.

CPU nb voltage Can also help a tad, more so with nortbridge frequency. This is the most important voltage on an amd setup. AMD recommend a max safe limit of 1.55 but there is no way in hell you are going to take advantage of that kind of voltage on air so keep it below 1.4 for this next part as I doubt you will see scaling past that point and it's not worth a damaged IMC.

NORTHBRIDGE FREQUENCY

If you have a locked multiplier Thuban then you are going to have to go to the HTT limits step first as AMD in their infinite system decided to lock out this multiplier
Not very nice


On air you could find your limit anywhere between 2600 and 3100mhz so set it in the bios. Boot into windows and run prime blend for as long as you see fit. As with all of this go as far as you can with as low a voltage as you can. Lower voltage = less heat and less degradation so keep it low.
Keep going up until you find that limit where you can't go any higher without passing 1.4v, find the minimum voltage, save and move on


Teaser shot


Damn I'm such a bad example


HTT limits *snores*

I don't know what you want to call it. Ratio clock, FSB, HTT, base clock.... It's that number that's 200 and makes things go faster
This is the key clock to your entire system and the limit can be found anywhere. Leaving our ram, cpu and northbirdge clocks low we can boot into windows fire up prime blend and find a rough limit. I often do this as a time saving measure.
Start prime blend, open a windows overclocking utility and see how far you can go on the htt before crashing so you know where your ceiling is. Run a series of longer stress tests to hone in on that limit and then you can move on to the exciting part without worrying about ALL of the above
It's worth setting the final round of clocks from the bios as I've seen a good few boards with a stable limit far past where they can boot to windows.

I haven't mentioned the hyper transport or pci clocks as they are going to have a minimal effect on system performance but it's nice to see a boost in loading times so those limits are to be found after wards so you don't sacrifice any of the other more important clocks. Same process of trial and error for those also. HT voltage can help with both your max htt and ht clocks but it's a particularly dangerous voltage to play with so leave it stock


CPU

Once we have tried all those clocks together and made sure it's running sweet as a nut we can get to the fun part. The number everyone wants to see


Only now can we start playing here. We know the limits of our IMC NB and HTT so as of now the system is happy. It should be working in perfect unison, if not stop being lazy and go back up there ^^.

CPU VOLTAGES

We've a tried and tested limit of 1.55vcore for Deneb based phenom II's and Athlon II's. It's a safe limit and you don't see much scaling past that so this is you


Thubans are a different story. We've heard from reliable sources that past 1.475 is the danger zone. Much past that and heat is going to become an issue anyway. If your on a Thuban on ambient then this is you.

We know our voltage limits and the maximum operating temperature is 62C. More often than not going near this limit is going to negate stability so keep well under that. You be the judge.

CPU overclocking

Again I am lazy
You will need to use a temp monitoring program. I've linked a bunch of freeware at the top. Find which one you like best and open it now. REMEMBER, under 60C!

Fire up prime blend with all of the known stable overclocks we've got so far along with your overclocking utilities and start moving the multiplier up slowly. After each bump in clock speed leave it a good 20 minutes before moving on. ( We aren't looking for 100% stability yet, just a rough idea of what this cpu can do ) Once you start getting stop errors, blue screens or black outs then you need to fix something. Set voltages from the bios, go up in small increments on you vcore each time and stabilize the point you last crashed at and move on up again.

(1055t owners. If this guide isn't much help to you I'm sorry
If you have found your max htt and you are still disappointed in overall core speed see if your motherboard allows you to manipulate turbo core and use that as you would a normal unlocked cpu in combination with 3 instances of prime blend and setting which cores are to be boosted in amd od along with affinity to the boosted cores. This will ensure turbo stability and a higher 3 threaded clock )

Blue screens; get the number and Google it
I usually put these down to RAM or NB instability but it can be anything so check if you are unsure.

Black screen; Any other crazy colour screen can be put down to cpu frequency most of the time but black is the fault of Vcore. Too much or too little, that's your job to find out.

Freezing; RAM or IMC again.. Fix it.

Once you have reached a wall where you can't use another multiplier use the last stable frequency and test for a good 3-10 hours or more. If it's stable go on to use a different combination of htt clocks and cpu multipliers. See how many more mhz you can squeeze out while you're on the edge


Remember always keep an eye on that all important temperature. Don't go cheating and setting your stable clocks on a cold day because you know a heatwave will come and ruin everything for you.

The best part, 3d stability. On rare occasions your overclock will pass all the stress tests you can throw at it but fail your favorite game
Fire it up and kill some zombies for a good 10 hours straight to ensure your zombie killing abilities will not be hampered. This is the most rewarding part, seeing increases from your stock benchmarks up to your fullly tweaked monster spi times and fps numbers


FINNALY Post your stable settings in some threads on here and brag about how awesome you are and how much Redhat_Ownage sucks. Congratulations you are now a Gappo
 

·
Premium Member
Joined
·
8,652 Posts
Shoulda made that guide when you still could be repped


Thanks! nice info all in one place
and what's with the redhat hate lol?
 

·
Premium Member
Joined
·
12,928 Posts
Discussion Starter · #4 ·
Quote:

Originally Posted by thiru View Post
Shoulda made that guide when you still could be repped


Thanks! nice info all in one place
and what's with the redhat hate lol?
Cheers fellas

We're all a bit sick of redhat talking about overclocking and benchmarking all the time and never doing anything so we are trying to give him a kick start

http://www.overclock.net/off-topic/7...-agp-dell.html

Got to be cruel to be kind


And LOL to whoever gave me that sneaky rep
 

·
Premium Member
Joined
·
8,652 Posts
Quote:

Originally Posted by el gappo View Post
Cheers fellas

We're all a bit sick of redhat talking about overclocking and benchmarking all the time and never doing anything so we are trying to give him a kick start

http://www.overclock.net/off-topic/7...-agp-dell.html

Got to be cruel to be kind


And LOL to whoever gave me that sneaky rep

[email protected], maybe a bit harsh


edit:
 

·
Premium Member
Joined
·
6,404 Posts
Nice guide, repped

Now if you could give us a guide on how to fix the 3d gaming dying problems, I'd be... urm.. much obliged

My unlocked x2 555 is fine, for everything, until I play 3d games, and TF2 keeps dying randomly with the Nvidia driver failing. I'm not sure this card likes running 2 displays.
 

·
Premium Member
Joined
·
12,928 Posts
Discussion Starter · #11 ·
Could be many things
Does it do it wit the 7600? if it does I would give that cpu some more juice.

More than likely bloody drivers tho...
 

·
Premium Member
Joined
·
6,404 Posts
The 7600 is pci-e x1 modded, I doubt it has the bandwidth to game with. I even took it out to see if that helped stop the crashes.
My chip has a 1.275v VID (nice and low I think) and is at 1.425v with all cores unlocked, and at 3.8GHz. It's OCCT and OCCT Linpack stable, plus I ran prime95 over it for a while, no errors. The Occt gpu memtest came back ok as well... Maybe it's time to strip my GPU down and replace the TIM.
 

·
Premium Member
Joined
·
12,928 Posts
Discussion Starter · #14 ·
Quote:

Originally Posted by UnAimed View Post
Why are you using win 2000?
1. That's server 2008

2. Because it's a far superior os
 

·
Premium Member
Joined
·
36,139 Posts
Quote:

Originally Posted by UnAimed View Post
Why are you using win 2000?
It's called Classic Theme. You can make XP, Vista, 7, Server 08, and just about any Windows OS look like that.
 

·
Premium Member
Joined
·
10,197 Posts
Thanks for this, it's helped me, definitely. But let me ask you a question, with all of your infinite CPU intelligences, if you don't mind!

On my 1055T, I'm aiming for 3.7 @ 1.435v w/ NB @ 2650 (my multipliers are locked) and RAM running at 1400~. Now, the CPU is good w/ 1.435v but I can't get the NB to get me into windows. I can get into windows and Prime with NB @ 2360 (or whatever the number is) at the same vcore.

I've tried upping the CPU/NB for 2600+ to 1.375 and it still won't boot into windows. I went up to 1.4 and still Windows loading froze. Motherboard is M4A78T-E, any ideas?
 

·
Premium Member
Joined
·
12,928 Posts
Discussion Starter · #18 ·
More voltage is your only option I guess. It will continue to scale with voltage but I don't know an actual safe limit because I've never noticed degradation but I do run 1.475 for 3ghz NB on my setup.
 

·
Premium Member
Joined
·
10,197 Posts
Is that VCORE or CPU/NB? Both?

Currently:

VCORE @ 1.4350
CPU/NB @ 1.2250 (Stable @ 2400) [Aiming for the next up which is 2600~]
 
1 - 20 of 87 Posts
Top