emm...any idea wad`s wrong with it??i can log in windows and benchmark it with sissandra but when running 3dmark05,it will hang and then blackout.
wad`s the recomemded vcore for it @ tat speed?i set it at 1.5+vcore.enuff?
ram i set it @ 166mhz so after ocing d proc,i think only 200-220mhz??forgot liaw...shouldnt b this problem rite?

if @ 2.6x+ghz,it wouldnt have tat problem,but havent test it`s stability cause still wanna c whether it can go any higher or nt.


This post has been edited by Koroshiwa: Mar 27 2006, 04:14 PM

dun straightaway bump it up to 2.7ghz and test it.....should do it slowly to determine the max possible speed with stock vcore....try increasing 10mhz at a time...

yup.. you should not straight away push it..btw..try to increase ur vcore..

hahaa.. u should refer to the pinned OC tread. there have been alot discussion regarding troble-shooting for overclocking setup.

btw, i believe the vcore aint enuff & tat y windowz crash if u try running heavy apps

every 10mhz i should prime it or just c whether it can pass the sis benchmark and 3dmark then pump it until it can`t pass these benchie then i`ll need to add vcore?
if every 10mhz i should prime it,omfg...waste a lot of time eh

btw,wad`s the highest recomemded vcore for it?


i had c the pinned oc thread but i don understand eh..just a little bit nia.
so i need guide from u guys.

This post has been edited by Koroshiwa: Mar 27 2006, 04:35 PM

then, if u kinda lazy, juzz put ur vcore to 1.55v > 1.6v

if still kenot stable, forget to OC

what ram u using?

check htt multiplier..

w00ps.. u already got it running, try updating chipset driver.

This post has been edited by DaEMoNteNTAcLe: Mar 27 2006, 05:25 PM

lor so malas to test ur own proc..and then how u will know ur prob?

I had the 3500+ and it hits a limit at 2.63ghz only even if pumped with 1.55 to 1.6V. HTT multipler set at 4 and memory set at DDR400. Use my results as benchmark to gauge your OC limit.

If your system is not prime stable for at least 6 hours... don't complain if you cannot run games or 3dmark.

To get a quick test out of everything setting change, just try use SuperPi 32M. The test wont take too long. If you can finish it, then you can try increasing you speed. Probably when you are satisfied anough with the overclocked speed, then you can run Prime95 custom test with 8-512K in-place FFT for about 12hours.

If no problem, then your system confirm quite stable.

Don't underestimate the efficiency of Prime stress.

haha.....i dun think 6 hours is enough....last time when i prime my system....prime went pass the 8th hour...but by the time it reach the 9th hour, the thing returns an error...speaking bout priming for at least 6 hours...

For cpu with 256KB L2 cache..... like the Sempron for example, 8 hours should be enough. If you get error after 8 hours, most probably there is a spike in your power which affects the cpu voltage fluctuation.... thus producing error during prime.]

For Athlon64...... the prime should be longer.... probably 16 hours to finish 1 round of prime stress with in place FFT

wut ur suggestion time to prime for opty ?

running 2 SuperPi in once wif custom setting each. 1024kb for each cores & mebe 20hrs atleast

perghh..20 hours... or may be a one solid day

This post has been edited by kulus: Mar 29 2006, 05:00 PM

id agree with soulfy, pi 32 can quickly show whether the cpu / ram is stable at that speed or not, although they may pass pi 1m, but 32 easily stops with error at slight instability. still prime is worth the trouble, especially for the long hours in max cpu temps.