Why is my 4800+ such a piece?

Gagan

Senior member
Mar 6, 2006
512
0
0
I'm trying to overclock my 4800+ at a 250 FSB and 12 multiplier
It seems to be locked! I know I can do it NP since I"m Watercooling, but what irritates me is the fact that it will not do the Backup CMOS and Verify DMI Pool data, rather it goes to the part where it's supposed to do those steps, and doesnt do them and restarts

I cranked up voltage to 1.45 for the cpu and 2.71 for the ram and STILL no luck w/ the ram at ddr200 or ddr400!

Any advice?
 

KBTuning

Senior member
Mar 22, 2005
357
0
0
go higher w/ the ram.... it could also be that your chip doesnt wanna run at 3GHz... which isnt uncommon... 3ghz seems to be the brick wall and yours might be hitting it slightly before...

whats the highest you've been stable at?
 
S

SlitheryDee

Originally posted by: Gagan
I'm trying to overclock my 4800+ at a 250 FSB and 12 multiplier
It seems to be locked! I know I can do it NP since I"m Watercooling, but what irritates me is the fact that it will not do the Backup CMOS and Verify DMI Pool data, rather it goes to the part where it's supposed to do those steps, and doesnt do them and restarts

I cranked up voltage to 1.45 for the cpu and 2.71 for the ram and STILL no luck w/ the ram at ddr200 or ddr400!

Any advice?

ou're STARTING at a 3ghz overclock? No no my friend you've got it backwards. Start at a moderate overclock and bump it up until your system becomes unstable and then back off a bit. Watercooled or no your processor might not be able to hit 3 ghz.

Quick and dirty A64 clocking guide **UPDATE** X2 OC information!

Read it, learn it, live by it.
 

imported_ST

Senior member
Oct 10, 2004
733
0
0
Originally posted by: Gagan
I'm trying to overclock my 4800+ at a 250 FSB and 12 multiplier
It seems to be locked! I know I can do it NP since I"m Watercooling, but what irritates me is the fact that it will not do the Backup CMOS and Verify DMI Pool data, rather it goes to the part where it's supposed to do those steps, and doesnt do them and restarts

I cranked up voltage to 1.45 for the cpu and 2.71 for the ram and STILL no luck w/ the ram at ddr200 or ddr400!

Any advice?

o_O

/shakes head
/shudders

 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
I love my 4800+, but I'm content to run it at 250HTT w/ 10x mult. at 1.35Vcore. RAM running 1:1, of course, at 2.75V.

My system is hoss of a box as it is. :beer:
 

LittleNemoNES

Diamond Member
Oct 7, 2005
4,142
0
0
SlitheryDee knows what's going on. You have to start low, my friend. Even with my Opteron 170 all I can get is 2.71
 

Gagan

Senior member
Mar 6, 2006
512
0
0
is it usual for one core to fail

one core goes all the way for 8 h ours the other fails in a few mins i dont understand why it's so stupid, it's usually the core that's started 2-3 seconds after since you cannot run em simultaneously.

i'm runnin 250x10

what should id o?
 

svsnow

Member
Feb 8, 2006
90
0
0
sorry for double post but.... make sure ur ram can do 250FSB...
250 is quite a bit for 4 dimms of what u have
 

Gagan

Senior member
Mar 6, 2006
512
0
0
it's at x4 thought you wanted it to be at 1000 for premium or below for near premium
and this ram should not have a problem hitting these speeds.
 

DrMrLordX

Lifer
Apr 27, 2000
22,897
12,957
136
HT speeds of 600-1300 mhz will not affect performance much, it at all. You only see a hit below 600 mhz. So a 3x LDT is just fine.
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Originally posted by: Gagan
is it usual for one core to fail

one core goes all the way for 8 h ours the other fails in a few mins i dont understand why it's so stupid, it's usually the core that's started 2-3 seconds after since you cannot run em simultaneously.

i'm runnin 250x10

what should id o?
I was having that problem when I had 2x1GB of Corsair that was rated for C2. When I ran it at C2 one core would fail Prime95 and the other would just hum along. When I backed CAS down to 2.5 both cores passed Prime95. Perhaps it is your memory. In detail, how do you have your memory set up? Voltage, timings, etc...
 

Gagan

Senior member
Mar 6, 2006
512
0
0
I'm fine with ram at 3-3-3-8
Rated at 2-3-2-5 it will not work I hate OCZ For false advertisement in that regard.
Priming it right now at 220 we'll see what happens!
 

Gagan

Senior member
Mar 6, 2006
512
0
0
Doesn't work
This ram isn't hte issue, it seems that fsb of 220 is making 1 of the cores conk I don't understand what the hell is going on

Anyone who can help?
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Originally posted by: Gagan
I'm fine with ram at 3-3-3-8
Rated at 2-3-2-5 it will not work I hate OCZ For false advertisement in that regard.
Priming it right now at 220 we'll see what happens!
Just to be sure, are you running with a divider on the RAM or is it running at 1:1? Your RAM is only rated to run at DDR400 so there are no guarnantees as to how well your RAM will overclock.

Also, what command rate are you trying to run the memory at? With 4 high density sticks you will have to run at 2T. So, if you are running at 1T that may be your problem.
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Originally posted by: Gagan
I'm fine with ram at 3-3-3-8
Rated at 2-3-2-5 it will not work I hate OCZ For false advertisement in that regard.
Priming it right now at 220 we'll see what happens!
I'm running my 2 x 1GB of OCZ DDR500 (3-4-3-8) at the advertised speed even with 1T command rate. I'm thinking you may be butting up against the onboard memory controller on your X2 chip. It's notorious for not liking 4 DIMMs installed, not with performance timings especially.
 

Gagan

Senior member
Mar 6, 2006
512
0
0
Running @ 2T

2T or 1T man, 2 gigs or 4 gigs, The 2-3-2-5 @ ddr400 works only on 2, i want it on 4.
 

jiffylube1024

Diamond Member
Feb 17, 2002
7,430
0
71
250*12 = 3 Ghz, what do you expect!?!? That chip is 2.4 Ghz stock, start out with 2.6 Ghz and work your way up...
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Originally posted by: Gagan
Running @ 2T

2T or 1T man, 2 gigs or 4 gigs, The 2-3-2-5 @ ddr400 works only on 2, i want it on 4.
I'd say you're probably out of luck then, sorry to be the bearer of bad tidings. :(