- Joined
- Dec 14, 2010
Going into this one I wasn't exactly sure what to expect.
My experience with socket 939 AMD dual cores is somewhat limited since the only overclocking and benchmarking I've done has been with the Athlon 64 X2 4200+ Manchester (E4) and Toledo (E6). I knew the Manchester topped out at 2.8GHz with about 1.6V going to the CPU, but wasn't fully stable at that speed. The Athlon 64 X2 4200+ Toledo (E6) on the other hand reached its limit at 3.1GHz with 1.62V, this chip is a great overclocker and runs nice and stable at 3GHz with a relatively low voltage of 1.5V
So, I did know that the Toledo was a good performer in the 4200+ rated CPU. I hoped this would hold true with the Athlon 64 X2 4400+ Toledo as well and I could get some good results.
I figured I would give the CPU an easy task first and so I started my testing by raising the FSB to set the CPU speed to 2.6GHz and bumped up the vCore to 1.375V to give me right around 1.34-1.35V after Vdroop so that I'd be at the stock voltage. So, I booted the system up and got right into the OS without any problems. Ran some tests with PiFast, SuperPi 1m, UCBench 2011, and wPrime 32m, and it completed all tests without any problems. Then I did a 15-20 minute run of Prime95, which it completed without any errors or warnings.
Next stop was 2.7GHz at the same settings, again there were no problems.
Finally, I decided to go for 2.8GHz while still at the stock voltage, I figured if any speed wouldn't be able to run on stock voltage with a 2.2GHz chip this would be it. I went into the bios, increased the FSB, lowered the memory multiplier, and rebooted. Much to my amazement as well as to my delight the system booted into the OS without any problems. So I fired up HWMonitor to go check the temps, they were still around 23-27°C. Then I ran SuperPi 1m, since usually if an overclock is unstable this program is the quickest to bring the problem to the surface. It completed without any issue, so I moved on to the rest of my chosen benchmarks, PiFast, UCBench 2011, and wPrime 32m, all of which were completed without any errors of any kind. After this, I moved on to a run of Prime95 for another 15-20 minutes, and again it completed without any errors or warnings.
I have encountered one peculiar issue though, Core 0 runs much hotter than Core 1. Under load Core 0 hits 48-52°C while Core 1 is at 36-39°C. I'm not sure if this is due to a bad mount, variances between the cores that are there due to a design flaw in the attachment of the IHS, or perhaps the heatsink I am using is not completely flat.
This is as far as my testing has gotten so far.
My experience with socket 939 AMD dual cores is somewhat limited since the only overclocking and benchmarking I've done has been with the Athlon 64 X2 4200+ Manchester (E4) and Toledo (E6). I knew the Manchester topped out at 2.8GHz with about 1.6V going to the CPU, but wasn't fully stable at that speed. The Athlon 64 X2 4200+ Toledo (E6) on the other hand reached its limit at 3.1GHz with 1.62V, this chip is a great overclocker and runs nice and stable at 3GHz with a relatively low voltage of 1.5V
So, I did know that the Toledo was a good performer in the 4200+ rated CPU. I hoped this would hold true with the Athlon 64 X2 4400+ Toledo as well and I could get some good results.
I figured I would give the CPU an easy task first and so I started my testing by raising the FSB to set the CPU speed to 2.6GHz and bumped up the vCore to 1.375V to give me right around 1.34-1.35V after Vdroop so that I'd be at the stock voltage. So, I booted the system up and got right into the OS without any problems. Ran some tests with PiFast, SuperPi 1m, UCBench 2011, and wPrime 32m, and it completed all tests without any problems. Then I did a 15-20 minute run of Prime95, which it completed without any errors or warnings.
Next stop was 2.7GHz at the same settings, again there were no problems.
Finally, I decided to go for 2.8GHz while still at the stock voltage, I figured if any speed wouldn't be able to run on stock voltage with a 2.2GHz chip this would be it. I went into the bios, increased the FSB, lowered the memory multiplier, and rebooted. Much to my amazement as well as to my delight the system booted into the OS without any problems. So I fired up HWMonitor to go check the temps, they were still around 23-27°C. Then I ran SuperPi 1m, since usually if an overclock is unstable this program is the quickest to bring the problem to the surface. It completed without any issue, so I moved on to the rest of my chosen benchmarks, PiFast, UCBench 2011, and wPrime 32m, all of which were completed without any errors of any kind. After this, I moved on to a run of Prime95 for another 15-20 minutes, and again it completed without any errors or warnings.
I have encountered one peculiar issue though, Core 0 runs much hotter than Core 1. Under load Core 0 hits 48-52°C while Core 1 is at 36-39°C. I'm not sure if this is due to a bad mount, variances between the cores that are there due to a design flaw in the attachment of the IHS, or perhaps the heatsink I am using is not completely flat.
This is as far as my testing has gotten so far.
I normaly do and the 939's are pretty good at holding the vcore 
