barton 2800 @ 2.44!!!

[leeperpsu]

i was able to get my barton 2800 at 2.44GHz
212fsb
mem timing 11,2,2,2

testing for stability now

voltage is 1.9v

 

[lookouthere]

your volt is kind of too high

 

[lookouthere]

unless you have good cooling systerm

 

[Corporate Thug]

i'd be kinda weary about 1.9V as well

 

[drewdogg808]

i don't think 1.9 is too bad.....2.0 and higher is getting toasty. you only live once you'll probably upgrade in a couple years anyway if not sooner.

great job with the barton.

 

[Chumpman]

nice man

 

[WA261]

Should have purchased a 1700

 

[Chumpman]

Originally posted by: WA261
Should have purchased a 1700

thread crap of the day ^^

 

[Corporate Thug]

Originally posted by: WA261
Should have purchased a 1700

the barton at 2.44 is equivilant to something like a tbred 2.6. not too many 1700+ get to 2.6

 

[leeperpsu]

well i can run at 2.44 but when i turn off my computer and unplug it from the wall and then go to boot up again...the computer hangs up at the part during the post that says "verifying DMI pool data"

anyone know what the hell that means and how to fix it

currently i can't go past 2.37GHz
or 215 FSB

 

[leeperpsu]

maybe i should leave it at 2.37 cause i only need 1.800v

my cooling set up is

slk-800
Tt tornado fan

two 80mm intake
two 80mm exhaust
one 80mm on side

two in psu

i'm sure i can do 1.9 volts but i can't figure out the DMI pool data bullshit

 

[Shimmishim]

Originally posted by: leeperpsu
i was able to get my barton 2800 at 2.44GHz
212fsb
mem timing 11,2,2,2

testing for stability now

voltage is 1.9v

if it hangs then it's not stable

anyway... congrats with the o/c... i got my 2500+ to 2.4 ghz (12 x 200) @ 1.9 volts (1.82 actual)....

never tried higher...

 

[Jeff7181]

I got my XP2500 at boot at 2.5 Ghz... but it's not stable at that speed so it doesn't do much good to run it at that speed.

 

[VisableAssassin]

Originally posted by: shady06
i'd be kinda weary about 1.9V as well

why? ive been running 1.975v since i bought my barton.....mine is fromt he FIRST shipment newegg ever had ! and its been runnign that way since then.
besides AMD's tech docs flat out state that the model 10 CPU's (bartons) can handle a MAX of .5v over which means a MAX of 2.15v

but nice OC on that barton man considering that when you hit roughly the 220mhz FSB or so @ 2.3ghz your pretty much faster tan a P4 3.0ghz so enjoy the speed.

 

[bgeh]

you're stuck at the Verifying DMI Pool Data?
then i think you should lower the oc

 

[leeperpsu]

does anyone know why my computer hangs at "verifying DMI pool data"??

i think i'm gonna reflash the bios and maybe install the nforce2 drivers again.

just to vent....this really makes me mad...you try for weeks to get every last drop from your pc. you buy new toys thinking it will fix the problems and its never really fixed. just new problems arrive!! ahhh

 

[VisableAssassin]

Originally posted by: leeperpsu
does anyone know why my computer hangs at "verifying DMI pool data"??

i think i'm gonna reflash the bios and maybe install the nforce2 drivers again.

just to vent....this really makes me mad...you try for weeks to get every last drop from your pc. you buy new toys thinking it will fix the problems and its never really fixed. just new problems arrive!! ahhh

if your hanging there man lower your OC that is the problem. either drop a multiplier down a notch or back off the FSB slightly onec yoru in windows your good to go...somewhat still need to run prime.

 

[lchyi]

I don't know the technical details of the voltage, but I remember like 3 people on this forum frying their chips running at 2.0 vCore in about a week. Honestly, if you can set your voltage to 1.85 like you said at about a few fsb difference, I would settle in there at the risk of your computer screaming at you.

 

[leeperpsu]

dude frying my chip is the LEAST of my worries...

if i wouldn't get these stupid hang ups during verifying dmi poop data screen, i'd be upping it more


1.9v is not that big of a deal

 

[DivideBYZero]

Originally posted by: leeperpsu
dude frying my chip is the LEAST of my worries...

if i wouldn't get these stupid hang ups during verifying dmi poop data screen, i'd be upping it more


1.9v is not that big of a deal

I'd say 2.36Ghz is the stable point and over that you hit the wall. Thats the deal when doing this. Willing it to go faster will not help. Your at the max, no two ways about it.

 

[Jeff7181]

I'd like to know if that 2.36 Ghz can run Prime95 while looping 3DMark for 12 hours without an error.

 

[DivideBYZero]

Originally posted by: Jeff7181
I'd like to know if that 2.36 Ghz can run Prime95 while looping 3DMark for 12 hours without an error.

Me too. And temps, what are your temps?

 

[leeperpsu]

at 2.36 the voltage is only 1.800v

so my temp under loads only 45-47c depending on how hot it is in my room.

i've done a cpu stability test over night i think 3 times and it always made it though.
the utility was from a pcworld cd-rom.
and i've looped 3dmark2001 for a little while.

its definately stable at 2.36 with a fsb of 205mhz.

but anything higher and i don't get crashes or lockups...only when i turn off my computer and unplug it, then turn it back on...it hangs at one part in the boot up and it says "verifying dmi pool data..."

noone has really explained what that is..so feel free to enlighten me. i really think i can go higher but something is messed up....i'm putting in the latest nforce2 drivers and newest bios....if it doesn't work then, well 2.36 its gonna have to be

 

[Cadaver]

I managed to get 2304MHz on my 2600+ (the 266MHz FSB model, not the 333MHz model) at 192MHz x 12. Ran just fine, but to reduce noise I dropped it to 2280MHz @ 190MHz x 12. Even with this slight difference in clock speed I was able to reduce the heat sink fan speed, thus noise, and maintain stability. Anything higher required more cooling... and more noise.

I'd say 2.36GHz is pretty good for an AMD processor.

 

[leeperpsu]

thanks.

well i updated the bios
installed most up to date nvidia drivers
found out that i had a conflict with resources with my stupid sound card (santa cruz)....fixed the conflict
did a complete HD scan and automatic repair
disabled all my onboard B.S....like game port and midi port and parallel port to free up resources
disabled fast write
set my HD to single/master (was on cable select)
set my HD up so theres a 80mm fan blasting cool air on it

i pray to god that the "verifying dmi pool data" crap that happens when i overclock too much goes away!!!

what you guys think?? i was a busy geek today