• 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.

AMD® Athlon™ II Overclocking Thread

Seraph . . . did you read much of this thread? :)

There is only 223 posts so far which in terms of thread size is "tiny" :D

Loads of info (inc BIOS shots) to help you on your way . . . sounds like your processor needs more juice. . . my chip needs approx 1.4000vCore to break 3.5GHz and I've used up to 1.600vCore for testing up to 3.8GHz . . . check out post #130 :cool:
 
Hey jmp_78,

just looking at your AMD® Athlon™ II X2 245 @ 3654MHz (1.376v) overclock in post #221 . . . look decent enough :)

I think if you wanted too there is scope to crank a bit more from that chip . . . 266 x 14.5 = 3857MHz . . . would obviously need a bit more juice? . . . what cooling do you have on that chip?

Also if you submit any more screenies make sure you include the [Memory] tab from CPU-z so we can see the RAM MHz/Timings and also your CPU-NB clock . . . you also may find HWMonitor useful for showing the CPU temps!

Good luck! :cool:
 
Hey Fonz-Valo,

just looking at your AMD® Athlon™ II X3 435 @ 3625MHz (1.392v) overclock in post #225 . . . looks pretty nippy to me! :)

I noticed you had the HT Link and CPU-NB running the [x8] multi along with a 250MHz HT ref.Clock for a total of 2GHz a piece? . . . did you experiment with letting the clutch out on both of those? . . . pretty sure both of those would both run fine using the [x10] multi for a total speed of 2.5GHz . . . may be worth a shot or?
 
Hey Seraph,

just looking at your AMD® Athlon™ II X4 635 @ 3335MHz (1.250v) overclock in post #226 . . . seems like the "Brave Pills" are working although I think you may need to up the dose a bit more . . . looking good! :D

Your sig states you are using "4Gb DDR3 1066" yet in the screenie your memory seems to be running at DDR3-1226? . . . overclocked or incorrect sig specs?

You mention about CPU-z showing you the [VID] which isn't the correct term . . . what CPU-z is showing you is vCore . . . as frozennova mentioned [VID] is the voltage deemed by AMD that the chips needs to run stably and is kinda "stamped" on the CPU . . . when the CPU is plugged into the mobo the boards checks what voltage the CPU requires by reading the [VID] info :) . . . for the record on every chip I have tested the [VID] level is wayy higher than what the processor actually needs to run stably at stock speeds . . .

As you adjust the CPU voltage (vCore) up and down using either the BIOS or Turbo V the [VID] is unaffacted . . . if you got decent cooling I would say you can pump up to 1.500vCore to 1.550vCore into that Propus without taking too many "Brave Pills" :p . . . looks like a nice chip you have there . . . may be good for up to 3.8GHz if you can keep it cool enough! :cool:
 
Last edited:
@ jmp_78: Yeah the cold weather is great for clocking and temps! :D . . . use HWMonitor to read the socket temps (TMPI) . . .

@ Fonz-Valo: Let them out one at a time and bit by bit starting with CPU-NB i.e:

Day 1: CPU-NB X9
Day 3: CPU-NB X10
Day 5: HT-Link X9
Day 7: HT-Link X10
 
Hi Seraph,

I'm not familiar with Turbo v and mostly do overclocking via the BIOS . . . when you say you set 1.45vCore but CPU-z reports 1.150v that's either a bug with Turbo v not setting the voltage properly or you must have Cool n Quiet enabled and the computer is dropping the CPU speed? . . . if its not that then you have the worst vDroop in the history of mankind! :p

It should be really easy to clock that chip, would you feel comfy using the BIOS? . . . also can you list your mobo and memory again please! . . .
 
Hi Betamax,

3.5GHz is better! :D . . . as you have such a "premium" motherboard I dare say you could push that chip even further if you wanted . . . temps look good and you got some more headroom to add voltage? . . . can you include the CPU-z [Memory] tab as well please so we can see how the CPU-NB and memory is set-up! :)
 
Looks decent burrell :)

270MHz Ht ref.Clock is nice . . . 2.7GHz CPU-NB is very high indeed! :D

If you want to isolate testing on the CPU then drop the CPU-NB multi down from [x10] to [x9] or [x8] . . . if you don;t want to dop the CPU-NB multi then your gonna need to hit it with bigger volts to get past 2.7GHz!

Also, in HWMonitor use the TMPIN sensors to get a more accurate reading of CPU temps . . . there are one or two TMPIN sensors so spend a moment working out whhich is which . . .

Off Topic CPU screenie but it shows you which sensors I'm talking about . . . TMPIN0 is the CPU and TMPIN1 is the motherboard in the system I am using . . . yours may be different . . .



The greyed out sensors are not accurate . . . use the TMPIN sensors instead . . .
 
Hey Betamax,

I'm just looking at your clock in post #241 and the CPU-z [Memory] tab in post #247 and can see you didn't quite get your head around the memory multipliers yet so I thought I would make this post to help you (and any other padawans) get the memory stuff straightened out! :)

Most people seem to understand how the CPU Multi and HT ref.Clock works but didn't quite yet see the connection between the HT ref.Clock and the memory speed . . .

AMD® Athlon™ II X2 240
  • Processor Frequency = 2.8GHz
  • HT ref.Clock = 200MHz
  • CPU Multiplier = x14
So 200MHz HT ref.Clock multiplied by 14 gives a total processor frequency of 2800MHz (14x200=2800) . . . nice and easy and 99% of people understand that . . . so what if we wanted to overclock the CPU frequency to 3.5GHz? . . . just take the end frequency you want and divide it by the CPU multiplier to get the HT ref.Clock speed you would need . . . i.e

  • Desired Processor Frequency = 3500MHz
  • 3500 divided by 14 = 250
So to get the AMD® Athlon™ II X2 240 running at 3.5GHz we would need a 250MHz HT ref.Clock . . .

  • 14 x 250 = 3500MHz
So far so good and I'm sure 99% of people who have overclocked before understand everything up to this point . . . now we get to the bit that seems to be causing a few folks some head scratching . . .

Memory Multipliers

Starting from a non-overclocked stock system we know the HT ref.Clock runs at 200MHz . . . this is the base frequency that everything else is connected to . . . on most modern AMD® AM3 systems the user has the choice of running these three memory speeds along with their "stock" system

  • DDR3-1066 (533MHz)*
  • DDR3-1333 (666MHz)*
  • DDR3-1600 (800MHz)*
Base memory speed as seen in CPU-z [Memory] tab . .

So how does the system control what speed the memory runs at? . . . as already mentioned the system has a base clock of 200MHz so to get the DDR3 memory running at any of the speeds above it employs a system of memory multipliers that look like this:

am3stockmemory.gif

if you look in the above image at the FSB : DRAM field you can see these three different memory multipliers

  • 3:8 DDR3-1066
  • 3:10 DDR3-1333
  • 1:4 DDR3-1600
So starting with DDR3-1066, all you do is take your HT ref.Clock and divide by the first number than multiply by the second number i.e

200 divide by 3 then multiplied by 8 equals = 533
200/3x8=533

If your **** at maths like me then get a calculator and do the maths

200
divide by 3
Multiplied by 8
Equals 533

Its easy really . . . and the basic maths doesnt change when you consider the other memory multipliers

200
divide by 3
Multiplied by 10
Equals 666

200
divide by 1
Multiplied by 4
Equals 800

The figure that we can change in all the above is the HT ref.Clock . . . so going back to the beginning of this post . . what happens when we want to overclock the AMD® Athlon™ II X2 240 up to 3.5GHz . . the answer is we bump up the Ht ref.clock from 200MHz to 250MHz . . . but as we discussed above the memory speed is directly attached to this base clock so as we boost that we are also changing the memory speed . . . assuming we had been using a base clock of 200MHz along with the [3:10] memory multiplier which had been running the memory at DDR3-1333 look what happens when we boost the HT ref.Clock from 200 to 250:

AMD® Athlon™ II X2 240 @ Stock
  • Processor Frequency = 2.8GHz
  • HT ref.Clock = 200MHz
  • CPU Multiplier = x14
  • Memory Multi = 3:10
  • Memory Speed = 666MHz (DDR3-1333)
AMD® Athlon™ II X2 240 @ 3.5GHz
  • Processor Frequency = 3.5GHz
  • HT ref.Clock = 250MHz
  • CPU Multiplier = x14
  • Memory Multi = 3:10
  • Memory Speed = 833MHz (DDR3-1666)
That's right folks . . . we just blown the memory frequency sky high . . . if using DDR3-1333 designed to run at 666MHz we almost certainly got a no boot situation . . . very little chance sticks meant to run at 666MHz will boot up the PC running at 833MHz! :D . . . some people at this point will curse their bad luck and pour scorn on their weak processor or puny motherboard but really the problem is simple rOOkie overclocker error and is quite easy to fix . . .

All you would need to do in the above scenario is firstly drop the memory multiplier from [3:10] down to the lower [3:8] and that will put the memory frequency back down to stock . . i.e

AMD® Athlon™ II X2 240 @ 3.5GHz
  • Processor Frequency = 3.5GHz
  • HT ref.Clock = 250MHz
  • CPU Multiplier = x14
  • Memory Multi = 3:8
  • Memory Speed = 666MHz (DDR3-1333)
If some of this post has gone over anyone’s head I suggest you read it again and again until it sinks in . . . you need to know exactly what speed your memory is designed to run at and you need to find the memory multiplier adjustment in the BIOS . . . once you know what speed memory you have, how to adjust the memory multi, how to adjust the Ht ref.Clock and adding vCore for the processor your on the way to getting better overclocks from your AMD® Athlon™ II . . . but were not quite done yet! ;)
 
so in the previous post we have discussed the basics of adjusting the Ht ref.clock to boost the processor speed, and we discussed the basics of how the memory multipliers work and how to adjust them to keep the memory running in specs as the Ht ref.Clock gets adjusted upwards . . . there is another fairly important factor to consider and one that if not understood will prevent anyone getting the best processor clocks . .

HT-Link & CPU-NB

htlinkcpunb.gif


so above is a screenie from my home server as it is running atm . . . undervolted processor with a little overclock on the CPU and a bit bigger overclock on the HT-Link & CPU-NB (highlighted in orange) . . .

Now as we discussed in the previous post nearly all the different buses and their clocks on the AMD® platform are tied into the HT ref.Clock (aka base clock or FSB) . . . at standard this is meant to run at 200MHz and as this base clock speed gets raised so does all the other buses and clocks including the HT-Link & CPU-NB . . . by default on the modern AMD® systems both of the latter buses are meant to run at 2GHz . . . this speed is worked out simply like so:

  • HT-Link = [HT-ref.Clock] x10 = 2000MHz
  • CPU-NB = [HT-ref.Clock] x10 = 2000MHz
as you can see both the HT-Link & CPU-NB have their own Multiplier . . . on the AMD® Athlon™ II platform this is a maximum of [x10] and can be reduced much lower . . . I think the CPU-NB can go as low as [x5] and the HT-Link can go all the way to [x2] . . . the HT-Link speed can never be greater than the CPU-NB speed . . .

In the screenie above you can see both the HT-Link & CPU-NB are running at 2.5GHz . . . this is 25% above defaults speed and is starting to put a lot of pressure of both the buses . . . if I was to raise the Ht ref.clock trying much more I'm pretty sure the system would crash without me adding more voltage to either of these buses . . . for the moment and without making this explanation too complicated the easiest thing to do would be do lower the multipliers so their speeds were closer to stock . . . like so

  • HT-Link = [HT-ref.Clock] x8 = 2000MHz
  • CPU-NB = [HT-ref.Clock] x8 = 2000MHz
Out of the two buses the main advantage in terms of added speed comes from overclocking the CPU-NB . . . the CPU-NB is the memory controller that is built into the processor . . . the faster it is running the quicker it can deal with shovelling heaps of memory data through your system and the lower latency the system becomes . . . its definitely worth overclocking the CPU-NB but that comes later in the overclocking process after you have finished tinkering with your processor clocks . . . to begin with its best to drop both the HT-Link & CPU-NB multis as you adjust the HT ref.Clock upwards to keep them both as close as possible to 2GHz . . . a few MHz extra isn't going to cause you any problems but if you leave them both at default [x10] multi its makes it harder to trouble-shoot any issue that pops up when you crank the HT ref.Clock trying to max your CPU overclock . . . once you max your processor clocks your ready to start tweaking both the HT-Link & CPU-NB clocks . . .

Anyone that is familiar with AMD® Athlon™ II overclocking will pretty much know and be familiar with everything I've run through in the last two posts but if your new to overclocking then all this info may blow your mind . . . don't sweat it . . just remember Coruscant wasn't built in a day and neither is anyone’s understand of overclocking . . . just take your time, read this posts again and again and again until you get the hang of it . . . do some simple testing yourself adjusting the various multipliers up and down along with the Ht ref.Clock etc . . .

Once you think you have understood most of this "theory" I suggest you read this thread from the very beginning here and by the time you get back to this post the AMD® Athlon™ II "force" will most definitely be with you . . . good luck! :cool:

wewantbetterdesignpleas.jpg
 
Hi Seraph,

really not sure what is going on at your end . . . deffo some strange things happening and its hard to say what is the cause . . .

I would suggest you uninstall Turbo-V for the moment, check you have the latest BIOS for your motherboard (if not update to it) . . . I would then fully reset BIOS and start again with a stock system . .

Use just these bits of software for the moment please:

Leave the system at stock . . . run HWMonitor then CPU-z . . . leave for a few minutes and watch the temps & vCore in both apps . . . then load up Prime95 and select Torture Test >>> Blend Test . . .

Out of all the apps I'm finding Prime Blend Test quite effective at detecting errors, LinX, Intel Burn Test etc and all nice apps but I can get cleans passes with the latter while Prime Blend find errors?

Anyway run an hour of Blending, take some notes of how the vCore is acting and how the temps are etc . . . then start doing some basic clocking using the BIOS . . . lets see if anything changes . . . good luck! :cool:
 
Hi Betamax,

glad to see some of that info has sunk in . . . I totally understand you are new and that there is a lot of "theory" to get your head round but it worth putting some time aside to get the maths sorted out as once you really understand this part of overclocking you will spend less time stumbling around in the dark wondering why your overclock has failed and more time achieving great overclocking results! :D

The fact you have one of the best AMD® overclocking boards in the world kinda offsets the fact that you are new . . . so with a little bit of knowledge we all expect Stella results from you! ;)

Right so in your previous post you mentioned that if you ran a 250MHz Ht ref.Clock and left the memory running on the [1:4] memory multiplier this would push your ram up to 1000MHz (DDR3-2000) which obviously is way past spec so you then said you "had to lower this to a ratio of 3:10" which still would push your memory to 833MHz (DDR3-1666) which is again higher than its official spec . . . I think what you was meaning to say was that if running a 250MHz Ht ref.Clock and wanting to keep your memory in spec and not overclocked you would need to use the [3:8] memory multiplier

Examples:

250
divide by 1
Multiplied by 4
Equals 1000 (DDR3-2000)


250
divide by 3
Multiplied by 10
Equals 833 (DDR3-1666)


250
divide by 3
Multiplied by 8
Equals 666 (DDR3-1333)


Your memory may well be able to run higher than 800MHz (DDR3-1600) but at this early stage its better to concentrate on just your CPU overclocking and remove the memory from the equation i.e set a lower memory multiplier to keep your memory within spec so that if you hit a snag you can be 99.9% sure the issue is not caused by the memory . . .

As well as taking the strain off the memory you need to also take the strain off the HT-Link & CPU-NB clocks by reducing their multipliers as well . . . at this early stage you just want to be concentrating on raising the HT ref.Clock and adding vCore to the CPU . . . the higher the base clock gets raised the faster the processor will run and the more voltage it will need . . .

So to demonstrate that you have taken all this theory in . . the practical test will be to publish some Prime95 Blend stability screen shots using the following config

AMD® Athlon™ II X2 240
  • Processor Frequency = 3.5GHz
  • HT-Link = 2.0GHz
  • CPU-NB = 2.0GHz
  • Memory Speed = 666MHz (DDR3-1333)
I want to see a screenshot using these apps

Once you got the maths and BIOS settings sorted, run a few hours of Prime95 >> Torture Test >> Blend . . . look forward to your results! :cool:
 
Last edited:
Hey Seraph,

looks like everything is getting back to normal . . . just for the record you only needed to publish one screenie instead of a blow by blow set of stock results! :p . . .

If you can include CPU-z [CPU] & [Mem] tabs, HWMonitor (close the extra readings by clicking the minus (-) leaving mainly voltages, temperatures, not core temps, Prime95 and optionally Windows task manger that will be fine, try to arrange the windows a little closer together as your last screenie was nearly FullHD sized which is getting a bit big . . . also don't need to see CoreTemp . . .

Ok so looking at your last humungus screenie I'm seeing two TMPIN reading in HWMonitor . . . TMPIN0 is reading 36°C-47°C and TMPIN1 is reading 32°C-33°C . . . do you know which is your CPU temps? . . . its hard to say as 47°C is quite high temps for a stock AMD® Athlon™ II X4 635 at stock 1.2xvCore and 32°C is kinda low! :D . . . what cooler are you using please?

Heres a tester for you . . . . see if you can figure this clock out . . . the only voltage you will need to adjust is vCore . . . the rest is all multpliers! ;)

AMD® Athlon™ II X4 635
  • Processor Frequency = 3.25GHz
  • HT-Link = 2.0GHz
  • CPU-NB = 2.0GHz
  • Memory Speed = 666MHz (DDR3-1333)
 
Hi Betamax :)

Good work . . . seems your getting the hang of things . . . the only point I can pull you on is the size of your screenies . . . maybe I'm getting old but the figures are quite hard to read due to being "shrunk" :D

see if you can figure out this next clock! ;)

AMD® Athlon™ II X2 240
  • Processor Frequency = 3710MHz
  • HT-Link = 2120MHz
  • CPU-NB = 2120MHz
  • Memory Speed = 706MHz (DDR3-1413)
 
Hi burrell, thanks for your kind words! :)

I'm a pretty slow learner myself but having owned an AMD® Athlon™ II system for a year now I managed to get to grips with the basics! . . . still got more to learn but I reckon in another 12 months I will have cracked it! :p

I replied to your post #245 stating your CPU-NB clock was rather high and how to make life simple you should consider dropping the CPU-NB multiplier to see if that solves your clocking problem? . . . 3.5GHz is a decent clock from a AMD® Athlon™ II X4 620 as it only has a [x13] CPU multiplier therefore forcing you to pump the Ht ref.Clock sky high . . . 270MHz is great! :)

Re finding out what the standard voltage is for your processors CPU-NB the only app I know of is Everest which shows you both CPU & CPU-NB [VID]

everest.gif


As you can see on the AMD® Athlon™ II X4 630 I am using the CPU-NB [VID] is 1.175v for operation at the standard 2.0GHz . . . at the moment I'm running it at 2.5GHz but had to manually boost the CPU-NB voltage from 1.175v to 1.225v . . .

If you think your Processor clock is maxed then fair enough go about raising the CPU-NB voltage and see if you can get 2.7GHz stable *but* if your still working out the max CPU clock then drop the CPU-NB multi down to [x8] or [x7] to take the strain off it and allow to to explore the Ht ref.Clock and CPU clocking further . . .

To get your Propus up to about 3.7GHz your gonna need a 285MHz Ht ref.Clock which may or may not be possible depending on the quality of your motherboard and CPU etc . . . for maximum chance of success your gonna need to drop the HT-Link Multi, the CPU-NB multi and the Memory multi . . . if you used the [1:2] memory multi that would still mean your DDR2-1066 ram was being overclocked while using a Ht ref.Clock of 285MHz

  • 285/1*2= 570MHz (DDR2-1140)
There is a bunch of lower memory multipliers on the AM2+/DDR2 platform . . . I think the next lower one is [3:5] which would be the one you wanted if your sticks can't quite reach DDR2-1140 and you wanted to keep them in spec while running a Ht ref.Clock of 285MHz

  • 285/3*5= 475MHz (DDR2-950)
Hope this info helps . . . good luck with the big clocks! :cool:
 
Last edited:
Back
Top Bottom