it may cause by system not stable then mobo BIOS setting reset to default, not necessary caused by low CMOS battery.

This post has been edited by ongbs: Dec 15 2007, 04:10 PM

If you happy with this mobo and only limit by the Vdimm, kasi Vdimm mod then...

Even Abit AN9 32X fata1ily max Vdimm around 2.35 - 2.4V, i Vmod it till 2.65V b4

This post has been edited by ongbs: Dec 15 2007, 04:20 PM

lohwenli, thanks again for the explanation.

i've switched off the Cool & Quiet features. and its now stable. this is my current setting,

Speed = 2.5Ghz with 1.35v
FSB = 240Mhz
Multiplier = x10.5
RAM speed = 533 with 2.15v

As stated in the ss below, for 2 hours, test it with Orthos, everything's fine. Temp at most is at 58C and lowest is at 56C during the test.



And i think, im not gonna push it more as im still using stock cooler for the proc and using only valueram.

huhu, forgot you are diehard OCer
make sure u won't Vmod the Vdimm till 3V or else....kaboom...asap keluar!

buy new then

the most thing i want learn.. how to vmod ????

i think Vmod or hardmod need us to properly study the electronic layout of our mobo.
then have to be good in soldering skill too.and the most improtant thing, u know what u do..

Here's how..but must be rajin..go download the datasheets for the ICs near the voltage regulator modules and read though them..from there you need to find the line where the IC reads the voltage of the component in question (vCore, vDimm, vNB, ect) then start making small adjustments to the resistors on that line (and I mean small, like less than 10 ohm at a time-digital multimeter is compulsory). Then check and see if there's any difference to the voltage. The whole idea is to fool the regulator IC to think the voltage is lower than it really is, so it will push up the actual voltage to compensate.

Be warned-voltmodding is not for the faint hearted or those with shaky hands. Messing around with solder, pencil mods or even just measuring voltages on tiny board components with a multimeter takes a steady hand. I've already messed up a few times myself, I'll post my story on the POC thread when I can.

Bro, are u using the automatic oc features ?

And 1.35v for only 2.5ghz seems too high. Me and bro nadeng1987 can get 2.8ghz with stock vcore 1.23v.

dun let me claim and return your board with human damage ler.. =P

Hello guys.
im noob here and i need your help guys.
cud sumbody help me here?
I just learnt how to overclock.
i managed to overclock my amd 4200+ till 2.6Ghz. and use this speed daily.But eventually my hard disc tetiba kong. Is this bcoz of overclocking? I post how to lock sata port here but nobody really answered that question.
Please help guys.

overclock won't kill da harddisk...

want to share only.. different when u just play simple timing(in column timing at memset) or with tweak other timing..
speed= 3.3ghz, HTL 1650mhz using single channel 1gb crucial 10th

the result faster 0.391s after tweak..

[attachmentid=360822]
using 5-4-4-3-11-2T

[attachmentid=360823]
with some tweaking other timing

so, do play other timing to join here:

DDR2 challenge

hope many ppl can join it.. i use single stick, so for dual channel, sure no prob at all rite

This post has been edited by xixo_12: Dec 16 2007, 10:09 AM

[attachmentid=360825]

finally enter 23s zone

bro, tu pki WC ke on air jek

Then what killed my harddisk bro?

hardware can damage ... normal use won't damage it unless u go hit/smack it when it is running... or not running ...
send warranty for it

Tapirus, you've been warned..do hard-modding at your own risk..any hard modding project, you better consider first if you can accept accidentally frying something..

Overclocking won't kill your HDD directly, but possible for it to kill it indirectly. If your PSU can't handle the overclocking and blows up, it can also take out some of your hardware. Theoretically, its impossible to kill a hard disk via the data lines as long as the power is stable, but I had a similar experience to yours which left me confounded-I was using a reliable PSU (which rules out the PSU blowing up scenario) and I was trying to find my max overclock when I forgot to turn down the HT multiplier, after that windows got corrupted and then the hard disk would experience errors every now and then, enough to make windows crash consistently at boot after about a week or 2 or usage. I checked the hard disk and it turned out to be suffering from read errors, fortunately almost all of my data could still be copied out. Sent the HDD directly back to seagate for RMA and got back a replacement unit a few days later, by then I bought another HDD and sold the Seagate to verz84.

I'm completely at a loss to describe how that HDD failed, it was never allowed to overheat and until the overclocking incident it had passed all HDD tests with no problems. The only explaination that I found reasonable is that is happened by sheer coincidence, after all hard disks fail eventually, some earlier and some later.

my PSU is silverstone strider 560W. So it's not psu problem la. What happened to you sama mcm what happen to me bro. I forgot to change HT link as well. Since then, HD becomes pelik. It crashes and gave BSOD. And everytime i format, it only lasts a week or two then it crashes again. I used this hd for 2 years (western digital btw) no more warranty.

This post has been edited by mod99: Dec 16 2007, 12:39 PM

Nope. I used manual OC in the BIOS..

can I get 2.8ghz speed with my stock cooler,stock vcore and also valueram? please advise me...if can,i'll try it.

im using this setting as advised by mr. ^666^

This post has been edited by naz: Dec 16 2007, 01:04 PM