at first it was 1.375v, but then the BSOD kept appear when i run the SuperPI 32M, so i rebooted, and pump 1.4v to the proc, and then no more instability issue such as BSOD..i passed the SuperPI 32M

@dblooi

Ok, I lowered the vcore a bit. But got BSOD when using 1.30v. Now I using 1.35v. This midnight I want to orthos priming for several hours, after tinkering with OC setup tonight.

My Brisbane proc is ADO3600IAA5DD CAALG 0717EAT

if you don't mind can you upload a screen shot of cpu-z? bcoz it is kinda weird to get BSOD at low frequency + little bit pumped vcore

oh ya, you can try to change the command rate to 2T

some update for all~

45nm js start assembly at Penang last few day ~~

so i think end of July this proc able to launch~ after Sg testing~

If i not see wrong it may be barcelona~

This post has been edited by tachlio: Jul 1 2007, 12:33 AM

WOW, then this should be a good news for AMD fanboys..
Include me


-pWs-

don know what the price also~

badly is Penang don like SG got ES to test~

are you sure that is 45nm?

the amd roadmap shows that amd plan to enter the 45nm industry at 2008 Q4


source: hkepc

This post has been edited by dblooi: Jul 1 2007, 02:58 AM

I don't know why I got BSOD at 1.30v, then I have to pump again the 1.35v vcore, which in CPUZ it's shown as 1.376v

To all, any workaround to get default vcore when clocking at 2.4 GHz (or 2.6 GHz perhaps)?

i dun think its becoz of ur vcore..
since u used 1T command rate, i bet u didnt pump enuff vdimm..
what is ur vdimm anyway?

This post has been edited by kalakatu: Jul 1 2007, 09:38 AM

ya i m sure it is 45nm d die but the time it launch i not sure only coz it is testing at SG.

vdimm is currently 1.95v

I've tried your suggestion: pump vdimm to 2.1v whilst set auto (default vcore) for the cpu but not to avail. I got BSOD afterward..

I think it is weird that I have to use 1.35v to reach 2.477 GHz, but other people such as dblooi just use default vcore to reach 2.8GHz, higher than mine.

Maybe it's RAM limitation, or cpu limitation. Overclocking result is different from a person's experience to other person's experience. Maybe my brisbane proc is not from a good production batch, whilst other are lucky get a better binned cpu?

even if it is not a good batch, i bet you still can oc to at least 2.5GHz with default vcore.
What's the ram that you are using anyway?Try to drop the memory divider into 400 instead of using 533. Have you turn off the CPU spread spectrum in BIOS setting? Try to change the command rate to 2T and see. Most probably there are something wrong with the setting, my prediction

This post has been edited by dblooi: Jul 1 2007, 12:10 PM

try to change to 2T command rate first
and then lower ur vcore, try to oc again form the beginning..

so have u tried my suggestions before?

hye there
i'm using the same board as u
at stock vcore can get up to 2.4ghz
now running @3ghz but need 1.4v

have u disable the CNQ?
also make sure u lower the HT multiplier to 3X or 2X

I just wondering... I saw robyncom selling 3600+ brisbane 65nm 2Ghz in garage sales... I call all lowyat net shops and they told me don't have 2Ghz... Only 1.9Ghz... I blur already...

bro those X2 3600 brisbane core oni 1.9ghz
if u bought the 2.0ghz...then dats the windsor core
not brisbane

Then I guess this guy in garage sales post wrong information?

http://forum.lowyat.net/index.php?act=Atta...=post&id=221109

yes he stated the wrong information
X2 3600 Brisbane's clock is 1.9GHz, not 2.0GHz..but from the screenshot, yes that was a Brisbane core..