oc = 1.4v
default = 1.25v
EE = 1.1v stock clock..

i don't really care about the temp.. normally software reports incorrectly..
but it should around 50C on load..
maybe should try thermal sensor later..

so many rig u got ar???
from AMD to Intel...
then get AMD again...

Great proc! I guess with such a low temp, going +0.15v on vcore should be no problem.

For my toledo core, going +0.05v already cause the core temp to jump up to 55-56'c!!

windsor also like that.. i even tried untill 70C... on stock cooler..
i most prefer core temp.. below 60C shouldn't be a problem...

70'c!!!

Ya, I guess below 60'c should be ok. Just that to me, the increase in vcore and temperature for that 50-100 Mhz gain is not justified. Well, at least for my proc anyway, need to pump in a lot of vcore to get a slight increase in OC....

Some forumers told me could be because of my mobo or PSU......

maybe becoz of ram? DDR and DDR2 quite different on voltage supply and heat disipation... case ventilation also another caused..

2.7 for toledo 4200+ seems ok... my previous windsor 3800+ also like that... but need to supply until 1.5v...

brisbane is different from those two... 65W, 65nm, less default voltage..



as u see.. even brisbane can achieve 3ghz.. still less Thermal Design Power (TDP) draw... thus less heat..

I see what you mean. Wished I was on the AM2 platform.... Then can get a brisbane....

Anyway, aiming for a q6600 in the near future....

Thx for the info!

Ermm I have a Q. What if SP2004 crashes after OCed, but still stable in windows and games like FEAR?

That probably means that the OC is not stable.

SP2004 will fully stress your proc where in games, the proc is usually not stress 100%.....

Yours is a single core?

Nope, 3600+ Brisbane

dual core have to use orthos ma.... unless you're running 2 instances of sp2004?

This post has been edited by kmarc: Jun 18 2007, 09:19 PM

Actually this isn't very accurate, as the TDP is only vaguely accurate for the highest speed chip for that particular TDP. Lower speed chips will definitely have significantly lower TDP. For AM2 chips, the TDP is probably close to accurate only for chips at 2.6GHz and above.

Thanks for the info. Still learning, hope you guys can guide me

Orthos will 100% stress my cpu, but what if I don't need 100% cpu stress. Just enough for my windows, games and app to load faster, does that means considered ok already?

You need to stress your OC at 100% to make sure that your rig is 100% stable.

This is because you can't be sure that your rig won't run at 100% at certain times.

In addition, let's say you are running at 50% most of the time, then there is no point overclocking as the reason for overclocking is to get more than what your stock CPU can provide. Do you know what I mean?

Yes, understand that. Thanks a lot. Will try to reach 3.0GHz, and stable

i heard 3.0GHz is quite easy for Brisbane..
why dun u break the boundary by surpassing it..maybe 3.2GHz or 3.3GHz
of course, need a good combination of mobo, ram and cooling system as well

anyway, good luck then..
dun forget to paste the screenshot here, together with Orthos and SuperPI 32M

This post has been edited by kalakatu: Jun 18 2007, 10:16 PM

i'm using micron d9gkx.

i'm using 300HT. 1 more wierd thing..why i can't set the divider to 533 / 667/ 800 but if set to AUTO.pc will set the ram to 800 @ actual speed 1080MHz and it can boot to windows but not stable enough to run STRESS test

If its not 100% stable, your system will crash/hang every now and then, though that might be fine with you (I'm not sure about you, but for me having games hang when I'm just about to finish a particularly hard campaign/mission is one of the biggest disappointments ever ). Also, there is a risk of data errors-files which you write to disk end up being full of rubbish.

Although its quite easy to reach 3.0GHz on brisbane, its very very hard to go higher than that. From what I've heard, even 3.2Ghz is a hard struggle despite using water cooling.

O ok. So when is it the best time to run Orthos? Is it ok to just leave it running while I'm asleep for example? If Orthos stopped while I didn't monitor it and it has stopped for a while, does it affect my system?

Quite easy to reach 3.0GHz with Brisbane? Quite hard for me though with stock cooler Have been adjusting several stuff and now running at 2.9

This post has been edited by afosz: Jun 18 2007, 11:06 PM

Yeah, that would be a good time. Usually I first do a quick stress test about 10-20 minutes, if its not stable I either tweak around a bit more or lower the overclock if there's nothing I can do to make it stable. Often, if the system is quite unstable errors will appear in less than 20mins-which means if you tried to run something under those conditions it would most likely hang/crash in less than half an hour. Once I've achieved a stable enough overclock to last 20 minutes of stress test I will leave the system to stress test overnight, if its not 100% stable but 99.99% stable, then there most likely will be an error and I'll have to make some adjustments and leave it to stress test another night. Usually it takes me 3 days of tweaking to get a 100% stable overclock; possible to do faster by stress testing during the day as well, but means I can't use the PC.