Associate
just managed to get mine to 3.5ghz.... been stuck on 3.1ghz for awhile.. had a fiddle around and dropped the multiplier... my first proper o/c 
-
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
- Thread starter Big.Wayne
- Start date
Man of Honour
VDDA is the voltage supplied to the clock generator (PLL) on the board as found here, at a guess I would say this is helpful for working against FSB walls
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!
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! . . .
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!
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! . . . 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! 
3.5GHz is better!
. . . 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! 
12 hour stable with Prime 95, on watercooling, got a 360 rad and a 120 with just the cpu and NB in the loop.
What you think?
When i try anything higher on restart i just get a power saving mode on my screen and i have to restart to see "Overcloking failed, enter bios to reset blah blah blah"
Also i set the voltage to 1.5 in the BIOS but cpu-z only shows 1.4
What you think?
When i try anything higher on restart i just get a power saving mode on my screen and i have to restart to see "Overcloking failed, enter bios to reset blah blah blah"
Also i set the voltage to 1.5 in the BIOS but cpu-z only shows 1.4
Last edited:
Looks decent burrell
270MHz Ht ref.Clock is nice . . . 2.7GHz CPU-NB is very high indeed!
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 . . .
270MHz Ht ref.Clock is nice . . . 2.7GHz CPU-NB is very high indeed!
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 . . .
Associate
thanks.. I bought the board with the intent on o/c but i am a still trying to work out what to do lol. thanks for starting this thread though, its been a great help looking at other peoples setups.
I did an intel burn test and failed at 3.5ghz so dropped fsb down to 255 and seems stable at 3442mhz on standard test.
heres my mem info..
I think I could play around at the voltages but im not entirely sure what im doing, ill have a read up on the link frozennova posted.
I did an intel burn test and failed at 3.5ghz so dropped fsb down to 255 and seems stable at 3442mhz on standard test.
heres my mem info..
I think I could play around at the voltages but im not entirely sure what im doing, ill have a read up on the link frozennova posted.
Last edited:
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!
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! . . .
hey big wayne,
not sure about Turbo V it might be a bug but i dont know lol
cool and quiet is definitely turned off
i would be happy with the bios but theres a lot more options then i had on my old GA board lol
i know where to up the clck speed and the voltage, only thing thats really phasing me is manually setting the voltage, how far along should i go
i've googled bits and bobs but cant find a definitive answer, have seen 1 review screen showing something like 1.5000v,
should i basically enter the voltage as it looks in Turbo V, so 1.450? how many zeros on the end are safe, i know it sounds daft but i worry about silly things like that lol
Board is Asus M4A79XTD Evo
Memory currently is 3Gb Crucial Ballistix PC3-10700 with 1Gb unbranded PC3-8500
I've got some Corsair xms3 CL9 2x2Gb DDR3 on order, should be here by the end of the week weather permitting, i'm guessing the ram should help somewhat?
Here are my current ram timings at stock
Ram Timings with cpu at 229 clock ( as far as it will go without upping the voltage )
Last edited:
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
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
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:
if you look in the above image at the FSB : DRAM field you can see these three different memory multipliers
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
. . . 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
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
- Desired Processor Frequency = 3500MHz
- 3500 divided by 14 = 250
- 14 x 250 = 3500MHz
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)*
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:
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
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)
- Processor Frequency = 3.5GHz
- HT ref.Clock = 250MHz
- CPU Multiplier = x14
- Memory Multi = 3:10
- Memory Speed = 833MHz (DDR3-1666)
. . . 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)
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
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:
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
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!
HT-Link & CPU-NB
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
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
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!
hey Big wayne
ok i got over my bios problem lol
however, it dont seem to have sorted anything.
i changed the voltage in bios, from 1.275 ( auto ) to 1.4000 and the clock upto 230.
It boots fine, but cpu-z is still showing 1.100v core vid
cpu-id Hardware monitor is properly showing cpu vcore as 1.41V at max and 1.40v minimum
cpu id version is 1.56, would it be worth trying an older version to see if it shows the same?
ok downloaded Version 1.54 and guess what lol
wonder whats going on eh lol new program has a bug, guess turbo V was working correctly then
ok another *edit*
just been stressing with IBT and coretemp and cpu-z open trying to find out why my vcore is all over the place
heres a screen at full load look at the cpu-z vcore info, the vcore incidentally is set to 1.4V in bios
and notice the VID in coretemp, another thing i dont have a screen for is HWmonitor cpu vcore seems to mirror the changes in vcore that cpu-z reports, two programs reading wrong? at the same time? not sure
and after completing the test, computer basically idling
ok i got over my bios problem lol
however, it dont seem to have sorted anything.
i changed the voltage in bios, from 1.275 ( auto ) to 1.4000 and the clock upto 230.
It boots fine, but cpu-z is still showing 1.100v core vid
cpu-id Hardware monitor is properly showing cpu vcore as 1.41V at max and 1.40v minimum
cpu id version is 1.56, would it be worth trying an older version to see if it shows the same?
ok downloaded Version 1.54 and guess what lol
wonder whats going on eh lol new program has a bug, guess turbo V was working correctly then
ok another *edit*
just been stressing with IBT and coretemp and cpu-z open trying to find out why my vcore is all over the place
heres a screen at full load look at the cpu-z vcore info, the vcore incidentally is set to 1.4V in bios
and notice the VID in coretemp, another thing i dont have a screen for is HWmonitor cpu vcore seems to mirror the changes in vcore that cpu-z reports, two programs reading wrong? at the same time? not sure
and after completing the test, computer basically idling
Last edited:
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!
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!
Associate
Big Wayne,
Thanks for your response..
I kind of get what you mean about memory multipliers.. but still a bit hazy...
My memory should run at 1600mhz which is 200/1*4... but now the FSB is 250, I had to lower this to a ratio of 3:10. If I ran it at the normal ratio of 1:4 my system wouldnt boot because it would try and clock the memory to 2000mhz, which is 250/1*4 (could this be where more mem voltage comes into play???).
Are you saying that I should be running this at the ratio of 1:4? At 3:10 its currently sitting around 1700mhz which is still more than the stock level...
Apologies If I have completely misunderstood your post, I am still learning..
Cheers
Thanks for your response..
I kind of get what you mean about memory multipliers.. but still a bit hazy...
My memory should run at 1600mhz which is 200/1*4... but now the FSB is 250, I had to lower this to a ratio of 3:10. If I ran it at the normal ratio of 1:4 my system wouldnt boot because it would try and clock the memory to 2000mhz, which is 250/1*4 (could this be where more mem voltage comes into play???).
Are you saying that I should be running this at the ratio of 1:4? At 3:10 its currently sitting around 1700mhz which is still more than the stock level...
Apologies If I have completely misunderstood your post, I am still learning..
Cheers
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!
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
Once you got the maths and BIOS settings sorted, run a few hours of Prime95 >> Torture Test >> Blend . . . look forward to your results!
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!
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)
Once you got the maths and BIOS settings sorted, run a few hours of Prime95 >> Torture Test >> Blend . . . look forward to your results!
Last edited:
hey big wayne, thanks for that info.
i updated to the latest Bios all fine
restored the bios settings to stock, so everything, stock clock is 200x14.5
stock vcore 1.275v
ran the prime95 torture blend test for an hour
heres my screen running at stock, computer idling
after half an hour under prime95 blend
and after an hour full load
i updated to the latest Bios all fine
restored the bios settings to stock, so everything, stock clock is 200x14.5
stock vcore 1.275v
ran the prime95 torture blend test for an hour
heres my screen running at stock, computer idling
after half an hour under prime95 blend
and after an hour full load
Associate
ok I have run the config as stated, here are my results...
seems pretty stable...
im thinking the next step is to up the clock, maybe push the vcore to isolate the cpu limit and then work on the memory??
seems pretty stable...
im thinking the next step is to up the clock, maybe push the vcore to isolate the cpu limit and then work on the memory??
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! . . .
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! . . . 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
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!
. . .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!
. . . 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"
see if you can figure out this next clock!
AMD® Athlon™ II X2 240
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"
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)
Hey Big Wayne,
thanks for the screenie info, wasn't sure what to include so
i'm pretty sure HWmonitor shows TMPIN0 to be my cpu chip
and TMPIN1 the motherboard,
cpu cooler is Arctic cooling freezer 7 pro
it usually idles cooler, got the central heating roasting the front room lol
as for the clock
the clock would be 224
Vcore would be stock 1.275V
as for the memory, if the Memory is DDR3-1333
Memory multiplyer would be 3/10
giving a memory speed of 747Mhz?
^^ was worked out using examples from your post above
and i cant find any options in my mobo's bios for fiddling the memory multi, or in it's user guide or on the asus support pages :S
*edit*
removed cheap pc3-8500 stick of ram and presto
shot shows cpu running at 235clock with 1.4V vcore
think i'll just run it like this for now, still have dual channel despite 3 sticks lol and better speeds
thanks for the screenie info, wasn't sure what to include so
i'm pretty sure HWmonitor shows TMPIN0 to be my cpu chip
and TMPIN1 the motherboard,
cpu cooler is Arctic cooling freezer 7 pro
it usually idles cooler, got the central heating roasting the front room lol
as for the clock
the clock would be 224
Vcore would be stock 1.275V
as for the memory, if the Memory is DDR3-1333
Memory multiplyer would be 3/10
giving a memory speed of 747Mhz?
^^ was worked out using examples from your post above
and i cant find any options in my mobo's bios for fiddling the memory multi, or in it's user guide or on the asus support pages :S
*edit*
removed cheap pc3-8500 stick of ram and presto
shot shows cpu running at 235clock with 1.4V vcore
think i'll just run it like this for now, still have dual channel despite 3 sticks lol and better speeds
Last edited: