First off I have to say now that I have seen it first hand I am not impressed at all....I had access to both systems simultaneously with a switch of the KVM monitor switch. IMO the AMD X2 system was noticeably faster with multiple programs (and/or any program that held 100% load) running...The Intel chip felt lethargic. So I decided to investigate and what I found was a bit surprising...
Let me also state right off hand, that the X2 system is at the disadvantage when it comes to cooling...It has only 1 case fan (not including the PSU) and a smaller XP90 (aluminum) with smaller 92mm fan. At full load running S&M 1.73 the heatsink was at 54c load on average an almost unnoticeable to the notch for heat. It also has a disadvantage in that it is running on a 380watt antec while the Intel system uses a Fortron 450 watter....
On the other hand the INtel system has 2 case fans, one frekkin behemoth of a heatsink (typhoon) and a massive 120mm fan....The heat around it as soon as you stuck your hand near it was noticeably verm warm. The heatpipes actually were burning hot.....
Initially Mark had the beast at 3.5ghz, w/ 1.45v...At that speed it had ran apps fine for 2 days including dual instances of F&H....As soon as I started messing with it I loaded it with 2 instance of FFT Prime95 and it froze within 5 minutes though heat only reached like 58-60c. Temp shutoff is 70c and we verified that to work later.....
The board after reboot clears out all settings so I set it to same vcore to lower speed of 245fsb for 3430mhz....It subsequently ran 2 instances of prime for 37minutes so power definitely seemed like an issue at 3.5ghz. Especially since I saw a max temp of 64c doing it and it did not freeze....
Now for the interesting part....
I decided to run S&M 1.73...It is the program that spanks prime95's arse when it comes to stress of heat and power....especially when you focus on the cpu (FPU) portion of the test. Now S&M is dual core setup so 1 instances is all it takes to load both cores. It also has tabs for each core....It was during running this that I noticed that...
THE P-D was THROTTLING!!!!!
At 55c the cpu being reported by the S&M for core1 starting dropping from 3430mhz.....By the time we hit 60c the speed was listed about 100mhz lower then core 0 and set speed.....When we hit 64c the speed was over 400 mhz and actually dipped below 3ghz. To verify this was temp related we removed the side of the case and subsequently the temps fell to around 56c and the cpu mhzz of core 1 climbed back to within 20mhz of core 0....Place the side back on and the temps rise and cpu1 drops again back to 400+ mhz lower.....
We at the same time ran this on the X2 3800+ oc'd to 2.55ghz at 1.475v and noiticed max temp of 56c and no differnece greater then 1-3mhz of reported speeds between core 0 and core 1....It is clearly just a P-D thing here...
Ultimately we decided to see how high it would go. Using the long test, 100% load and using the cpu (fpu) test about 29 minutes into the test we hit 69c and the chip had throttled a whopping 800mhz....that is right!!! we then watched slowly as it creep to 69.2, 69.3, 69.4, etc....Finally the system rebooted but this time did not clear the settings...it was strictly the thermal safety setting in the bios that shut it down....
I then remember the stuff Stevty was talking about, the higher the vcore the lower the throttle point. I decided to prove that theory....and I did....Setting the cpu volts to 1.4v in the bios and dropping the cpu speed now to 240 for 3360mhz I then restarted S&M and the same cpu (fpu) test....Once it rose to 55c (rather quickly too) I checked the cores and no throttling...checked at 57c....checked at 59c and was starting to get iffy, and then finally at 60c the cpu speed of core 1 dropped more then 10mhz below the other....The temps slowly rised over time until it reach 64c and it was about 70mhz lower clock speed then core 0. Bottom line was the throttle temp point defintiely had changed.
At 64-65c and removing the side of case the heatpipes we so damn hot holding your figure there too long was uncomfortable....
THIS THING IS A BEAST...
My best guesses is that 3.5ghz will not be stable. 1 cause it needs more power and 2 unless mark wants to run with case side off he will likley throttle quicker then current 55c. Even with case side off I was able to get it to throttle with 2 instance of prime95 running as it hit 58c....
3.43ghz likely can work with case side off and folding at home but it may just crosss into slight throttling evry now and then when the room gets a bit warmer....room temp was 76f but he did have a window open and it is like 48-50f at the time outside.
Most likely to insure no throttling 1.4v might be the max vcore to use and a speed of about 3360mhz....If you can keep vcore low you can OC these chips but temps will be likely still high....
The sad thing is, that HSF is the best damn air cooling you can buy and it doesn't muster it at these rather conservative levels....IMHO...
PS.
Guys run S&M and if anything just launch the app and use its monitoring of temps and core speeds...you dont have to run the app but can use it to do those 2 things and is far more effective then cpu_z was...
EDIT 1:
let me clarify 1.45v was what was set in the bios...It actually was undervolted a bit from that but the surprising thing may be more related to this mobo but the droop under load was tremendous. I have heard reportes from other boards for these chips similar stories of undervolting a drooping...In this case it didn't affect ocing and did't seem to help the temps either...
Let me also state right off hand, that the X2 system is at the disadvantage when it comes to cooling...It has only 1 case fan (not including the PSU) and a smaller XP90 (aluminum) with smaller 92mm fan. At full load running S&M 1.73 the heatsink was at 54c load on average an almost unnoticeable to the notch for heat. It also has a disadvantage in that it is running on a 380watt antec while the Intel system uses a Fortron 450 watter....
On the other hand the INtel system has 2 case fans, one frekkin behemoth of a heatsink (typhoon) and a massive 120mm fan....The heat around it as soon as you stuck your hand near it was noticeably verm warm. The heatpipes actually were burning hot.....
Initially Mark had the beast at 3.5ghz, w/ 1.45v...At that speed it had ran apps fine for 2 days including dual instances of F&H....As soon as I started messing with it I loaded it with 2 instance of FFT Prime95 and it froze within 5 minutes though heat only reached like 58-60c. Temp shutoff is 70c and we verified that to work later.....
The board after reboot clears out all settings so I set it to same vcore to lower speed of 245fsb for 3430mhz....It subsequently ran 2 instances of prime for 37minutes so power definitely seemed like an issue at 3.5ghz. Especially since I saw a max temp of 64c doing it and it did not freeze....
Now for the interesting part....
I decided to run S&M 1.73...It is the program that spanks prime95's arse when it comes to stress of heat and power....especially when you focus on the cpu (FPU) portion of the test. Now S&M is dual core setup so 1 instances is all it takes to load both cores. It also has tabs for each core....It was during running this that I noticed that...
THE P-D was THROTTLING!!!!!
At 55c the cpu being reported by the S&M for core1 starting dropping from 3430mhz.....By the time we hit 60c the speed was listed about 100mhz lower then core 0 and set speed.....When we hit 64c the speed was over 400 mhz and actually dipped below 3ghz. To verify this was temp related we removed the side of the case and subsequently the temps fell to around 56c and the cpu mhzz of core 1 climbed back to within 20mhz of core 0....Place the side back on and the temps rise and cpu1 drops again back to 400+ mhz lower.....
We at the same time ran this on the X2 3800+ oc'd to 2.55ghz at 1.475v and noiticed max temp of 56c and no differnece greater then 1-3mhz of reported speeds between core 0 and core 1....It is clearly just a P-D thing here...
Ultimately we decided to see how high it would go. Using the long test, 100% load and using the cpu (fpu) test about 29 minutes into the test we hit 69c and the chip had throttled a whopping 800mhz....that is right!!! we then watched slowly as it creep to 69.2, 69.3, 69.4, etc....Finally the system rebooted but this time did not clear the settings...it was strictly the thermal safety setting in the bios that shut it down....
I then remember the stuff Stevty was talking about, the higher the vcore the lower the throttle point. I decided to prove that theory....and I did....Setting the cpu volts to 1.4v in the bios and dropping the cpu speed now to 240 for 3360mhz I then restarted S&M and the same cpu (fpu) test....Once it rose to 55c (rather quickly too) I checked the cores and no throttling...checked at 57c....checked at 59c and was starting to get iffy, and then finally at 60c the cpu speed of core 1 dropped more then 10mhz below the other....The temps slowly rised over time until it reach 64c and it was about 70mhz lower clock speed then core 0. Bottom line was the throttle temp point defintiely had changed.
At 64-65c and removing the side of case the heatpipes we so damn hot holding your figure there too long was uncomfortable....
THIS THING IS A BEAST...
My best guesses is that 3.5ghz will not be stable. 1 cause it needs more power and 2 unless mark wants to run with case side off he will likley throttle quicker then current 55c. Even with case side off I was able to get it to throttle with 2 instance of prime95 running as it hit 58c....
3.43ghz likely can work with case side off and folding at home but it may just crosss into slight throttling evry now and then when the room gets a bit warmer....room temp was 76f but he did have a window open and it is like 48-50f at the time outside.
Most likely to insure no throttling 1.4v might be the max vcore to use and a speed of about 3360mhz....If you can keep vcore low you can OC these chips but temps will be likely still high....
The sad thing is, that HSF is the best damn air cooling you can buy and it doesn't muster it at these rather conservative levels....IMHO...
PS.
Guys run S&M and if anything just launch the app and use its monitoring of temps and core speeds...you dont have to run the app but can use it to do those 2 things and is far more effective then cpu_z was...
EDIT 1:
let me clarify 1.45v was what was set in the bios...It actually was undervolted a bit from that but the surprising thing may be more related to this mobo but the droop under load was tremendous. I have heard reportes from other boards for these chips similar stories of undervolting a drooping...In this case it didn't affect ocing and did't seem to help the temps either...
