I'm new to the actual act of oc'ing in newer boards but not the idea. i used to oc my p3 but those were the sdram days. i've researched extensively and thats the reason for the post. too much conflicitng info and varying opinions for me.
specs first: msi k7n2-delta2-lsr motherboard
amd athlon xp 2500+ barton week 55 i think
dual channel kit pqi turbo memory 2 modules of 256 pc3200
antec fan/heatsink combo rated to 3200+ Xp
antec slk1650 solution series with smart power supply
ati radeon 9600xt 128mb agp 8x
windows xp pro
first i noticed if i install and try to overclock using the corecenter application it will turn my processor fan off completely. anyone else have this problem its aggravating and if i uninstall no problems.. scary really...
also, my ram never runs at the stock 2.5 cas it automatically sits at 2.0 of course i should factor in the fact that the ram states it's good for overclocking and at stock i'm running it low at the stock 333 or pc2700 specs. it's just weird.
secondly i know the chip is locked, and during inital and early research i uppd the fsb to 200 and got a blue screen of death before getting anywhere near into windows. i usually run about 33 to 35 degrees celcius when at stock everything.
i see alot of ppl say dont let it over 50 celcius or even 60 celcius. amd states 85 celcius although i am aware that should be A> under full load and b> the highest maximum and anything near it will surely halflife the cpu lifespan.
after alot more research i went ahead an uppd the fsb to 200 and the vcore to 1.6 in the bios and i came into windows fine at 2.2ghz... to slightly test these settings i ran sandra and did a multimedia benchmark and simultaneously checked temps they went to 49 celcius at highest during this benchmark. i also realize this benchmark is probably not stressing the system that hard but i experienced no real problems as far as that goes. i used the sandra because i dont trust the msi software or the pchealth bios readouts.
so what i'm worried about is temp and monitoring during a game or say a prime95 test. i dont want to waste the money i spent obviously but i still want what i know i can squeeze out of it. it's my understanding wrong or right that the 2500+ barton is no, or barely different than the 3200+, that the 3200 just has different locked multiplier and fsb as well as vcore much like the pentium 90s of days past they were really 133's running at lower clocks. am i wrong? it seems not even by amd's own words. but amd doesnt exactly suport oc'ing hehehe.
so i ask the gurus here, whats at stake? what are the real word numbers on temps with this chip? i need a final answer, cause the variances of opinions is vast and not exacty confidence inspiring. i see alotof people get away with this on one hand, on the second i would rather seem dense and be overly cautious and paranoid than simply run out and blindly jack everything up like alot of other people i've seen. i've read about every faq and guide i can and still have a few unanswered questions and whatnot. i know alot of it will be minutely changing this and that until i can get as stable as possible. but it's the hardware limits, and real world experience i cant seem to get solid info on.
urville
specs first: msi k7n2-delta2-lsr motherboard
amd athlon xp 2500+ barton week 55 i think
dual channel kit pqi turbo memory 2 modules of 256 pc3200
antec fan/heatsink combo rated to 3200+ Xp
antec slk1650 solution series with smart power supply
ati radeon 9600xt 128mb agp 8x
windows xp pro
first i noticed if i install and try to overclock using the corecenter application it will turn my processor fan off completely. anyone else have this problem its aggravating and if i uninstall no problems.. scary really...
also, my ram never runs at the stock 2.5 cas it automatically sits at 2.0 of course i should factor in the fact that the ram states it's good for overclocking and at stock i'm running it low at the stock 333 or pc2700 specs. it's just weird.
secondly i know the chip is locked, and during inital and early research i uppd the fsb to 200 and got a blue screen of death before getting anywhere near into windows. i usually run about 33 to 35 degrees celcius when at stock everything.
i see alot of ppl say dont let it over 50 celcius or even 60 celcius. amd states 85 celcius although i am aware that should be A> under full load and b> the highest maximum and anything near it will surely halflife the cpu lifespan.
after alot more research i went ahead an uppd the fsb to 200 and the vcore to 1.6 in the bios and i came into windows fine at 2.2ghz... to slightly test these settings i ran sandra and did a multimedia benchmark and simultaneously checked temps they went to 49 celcius at highest during this benchmark. i also realize this benchmark is probably not stressing the system that hard but i experienced no real problems as far as that goes. i used the sandra because i dont trust the msi software or the pchealth bios readouts.
so what i'm worried about is temp and monitoring during a game or say a prime95 test. i dont want to waste the money i spent obviously but i still want what i know i can squeeze out of it. it's my understanding wrong or right that the 2500+ barton is no, or barely different than the 3200+, that the 3200 just has different locked multiplier and fsb as well as vcore much like the pentium 90s of days past they were really 133's running at lower clocks. am i wrong? it seems not even by amd's own words. but amd doesnt exactly suport oc'ing hehehe.
so i ask the gurus here, whats at stake? what are the real word numbers on temps with this chip? i need a final answer, cause the variances of opinions is vast and not exacty confidence inspiring. i see alotof people get away with this on one hand, on the second i would rather seem dense and be overly cautious and paranoid than simply run out and blindly jack everything up like alot of other people i've seen. i've read about every faq and guide i can and still have a few unanswered questions and whatnot. i know alot of it will be minutely changing this and that until i can get as stable as possible. but it's the hardware limits, and real world experience i cant seem to get solid info on.
urville