AMD 64 3000+ (reached max OC?)

[Dreadd]

This is my first OC experience. I wont even pretend to be an expert at OCing or even fluent with the lingo! I spent numerous hours reading threads on this forum. So much time my eyes bleed and my brain turned to mush after hours of acronyms, etc..

 

My signature is accurate except im using an IDE drive for OCing, SATA drive is not physicall connected at all.

 

*edit

Temps are all under 40 celcius except for chipset which sometimes goes into the 40's *

 

I do realize i do not have a recommended PSU (see what happens when you don't FULLY do your research? Anyone want to trade for a OCZ600? LoL!) I have tested rails on PSU under POST, idle and FULL load. I used a multimeter, not an application. Tested each for approx 20 mins. Results appeared to be acceptable. 12v fluxuated from 12.10 to 12.14 for example. 3.3v and 5v where about the same results!

 

CPU specs (CPU-Z);

 

AMD Athlon 64 3000+, Winchester, Brand ID 4, Technology 90 nm, Family F, Model F, Stepping 0, Ext. Family F, Ext. Model 1F, Revision DH8-DO

 

RAM;

 

Currently set for; 100=RAM / FSB:01/02. If i understand correctly, with a 1/2 devider this elimates my RAM from causing stability allowing me to determine and reach max CPU OC.

 

BIOS config;

 

FSB Bus Frequency: 248

LDT/FSB Frequency Ratio: 3x

LDT Bus Transfer Width: 16 x 16

CPU/FSB Frequency Ratio: 9x

PCI-E Frequency: default (100)

Cool `n Quiet: disabled

CPU VID Startup voltage: default

CPU VID Control: default (1.375v)

Chipset Voltage Control: default (1.6)

DRAM Voltage Control: default (2.6)

 

Im 100% stable under this config. This includes overnight memtest, prime95 (8 hour), OCCT, 3dmark05, and super_pi 1.5(32M). With DRAM devider 1/1 im also 100% stable under same tests.

 

(DRAM Devider at 1/2)

If i raise my FSB Bus Frequency to 249 I fail prime95 after about 56~58 mins. (hardware failure i believe is the error). I did not run any other tests beyond this (I started and stopped at prime95 since it produced an error).

 

FSB Bus Frequency at 249; I then adjusted CPU VID Control to 1.4 and still error out in Prime95 within an hour. I adjusted CPU VID Control to 1.425, same results in prime95.

 

Next I lowered CPU VID Control to 1.4v and raised Chipset Voltage Control to 1.7v. Still producing error in Prime95. Not even sure if Chipset Voltage is relevant.

 

So, have i conclusively reached my maximum OC? I feel like there is a good chance im overlooking something and thats why I have turned to YOU for advice! Hopefully I haven't left out any chunks of useful info.

 

Thanks folks, great forum btw!

 

 

*Edit* I'm trying to obtain max CPU clock before i overwhelm myself with DRAM overclocking! I'm even more confused with DRAM vrs CPU when it comes to OCing!

[ebdoradz]

http://www.dfi-street.com/forum/showpost.p...542&postcount=3

[Dreadd]

I notice you have a Venice core where as I have a Winchester core. I realize OCing even if the exact same setup can vary.

 

Perhaps the Winchester core in general is not as tolerant of OCing as the Venice?

 

I did mess around with vcore as mentioned in my post but i did not change the 104%, etc.. setting where as im not sure when / why it's applicable.

 

I also tried with a x8 mulitplier, got clock up around 2120 (HTT around 267 i believe) and it was unstable.

 

So perhaps i should try raising FSB / HTT to 249 with default Vcore but change (dont remember name) to 104% (i do know this ups vcore slightly)

 

Still feel like im overlooking something - perhaps not, maybe I have reached my max OC for cpu!

[boo_masters]

Hey congrats on getting to where you are!

 

Just some tips on Vcores and cooling. You should be careful about the max VCore you use for air. Nominally it is around 1.45 for air cooling, possibly 1.5-1.55 for excellent air cooling. With h2o you can obviously get higher with 1.6 and even 1.7 for those risk takers.

 

Basically you are at 1.425 now and if your temps are good there you probably have good air cooling. I personally (if it were me) would't go higher than 1.6 without major testing and temp monitoring. But then I would get h2o on it too so that would raise my theoretical threshold

 

good luck

 

boo

[Dreadd]

Thanks for the tips!

 

Thus far i have not had any temp issues, including when i had vcore up to 1.425 (according to BIOS, MBM5 and smartguardian). But i will be cautious about raising vcore.

 

I have pretty good cooling setup, 2 intakes on front of case, one intake on side panel (almost inline with CPU). Then i have 2 exausts in back of case and 1 blowhole on top. Also using non stock heatsink fan that is posted in my sig. I used AS5 for TIM on chipset and CPU. Hardware side i feel more confident in. I have moded multiple cases, etc.. the overclocking, however, is new territory to me.

 

Looks like prices tumbled on AMD processors. Im almost tempted to splurge for an upgrade - thanks DFI, this 'tweaking' crap is addictive....

[Guest BFG]

Try bumping your vcore up a little bit. Just make sure the temps are in check and you should be able to get a higher overclock. And if you do decide to upgrade and still stay single core then IMO you should get a 3700 San Diego.

[n_w95482]

Perhaps the Winchester core in general is not as tolerant of OCing as the Venice?

That's correct. To be more technical, the Venice/other E rev. CPU's cores are made with an additional metal layer versus the Winchesters, which makes them better clocking chips. The same thing happened with the Athlon XP Thoroughbred A and B cores. The A's were nothing special, but the additional metal layer of the B's made them exceptional overclockers.

[farksy]

I always put at least 1.5V into my chip when clocking =X. lol.

[Dreadd]

Try bumping your vcore up a little bit. Just make sure the temps are in check and you should be able to get a higher overclock. And if you do decide to upgrade and still stay single core then IMO you should get a 3700 San Diego.

 

Thanks for that advice - it appears that CPU is only $99 at the egg. I might be looking to spend more than that. I have heard various opinions on dual cores chipsets so im going to do my research - if i decide to stay single core i'll pickup that chip.

[Dreadd]

I always put at least 1.5V into my chip when clocking =X. lol.

 

I will try that. I only went as high as 1.425.

[ebdoradz]

my venice is runnign a 1.46V (bios) 1.44( MBM5)

 

and ive reach 2.4Ghz

 

maybe a little 0.02V can give you 2.4Ghz too

[Dreadd]

Placed DRAM back onto a devider, upped vcore to 1.50v. Increased HTT / FSB to 255. Super_pi 32m, passed. 3 hours prime95, zero errors. Temps on torture test peaked at 40c. Have yet to run OCCT. I think im back on track - thanks for the tips!