My AMD E6 3500+ SUCKS for OC'ing

[Accipiter22]

it fails to boot with the FSB at 210!! WTF?? My old 3500 Newcastle I had the FSB at 245. Thanks AMD.

 

[atybimf]

yes, it does. should've gone with the E3.

 

[imported_michaelpatrick33]

Originally posted by: Accipiter22
it fails to boot with the FSB at 210!! WTF?? My old 3500 Newcastle I had the FSB at 245. Thanks AMD.

You're angry at AMD for a processor that doesn't run over its rated speed?

Have you examined all the other possibilities? I seriously doubt you are only getting a 110 megahertz overclock. 210 sounds suspiciously like memory or motherboard lock issues etc.

Stock HSF? Bios updated? Memory timings relaxed? HTT set properly? Memroy dividers used? Have you done all the things to ensure that it isn't something else? Do you have AGP/PCI and are they locked after putting in the new processor (if the same motherboard). How about the hard-drive(s)?

 

[Accipiter22]

I couldn't buy the E3, they rma'd me this e6 to replace my newcastle.


It is the stock HSF, my bios is the most recent edition, memory timings are relaxed...my HTT is at 1000 like always....I've never used memory dividers before, I guess I could do that...I just need to know what they are.

 

[n7]

*sigh*

Lemme guess...you're not usign a RAM divider.
Or maybe you didn't lower the HT multi.

Maybe you should let us know what you've tried before claiming your CPU sucks.

Oh, & also, yeah...you paid for a 3500+ (11x200)
Anything more is just a bonus.

 

[n7]

ROFL so you haven't lowered the HT multi/LDT & used a RAM divider, & it's the CPU's fault :roll:

Start reading. http://forums.anandtech.com/messageview.aspx?catid=28&threadid=1497607

I have no patience for people that spread FUD around.

 

[grant2]

He implies the rest of his system worked just fine at 245 with a different CPU.

If it suddenly only works at 210, and the only thing changed is the CPU... then guess where the problem is!

 

[n7]

Originally posted by: grant2
He implies the rest of his system worked just fine at 245 with a different CPU.

If it suddenly only works at 210, and the only thing changed is the CPU... then guess where the problem is!

Not necessarily.

The memory controller on A64 really varies in terms of overclockability, which means adding a new CPU = retesting everything to find max capabilites again.

 

[t3h l337 n3wb]

Yeah, the E6's shouldn't be THIS bad at overclocking right?

 

[imported_michaelpatrick33]

Also, when the new processor was put in we don't know if the BIOS setting all defaulted back and he forgot to switch a setting. He isn't using a divider and we don't know what his memory is. Maybe he set a memory divider before and forgot and now he is trying to get 1:1 settings. Who knows without much more information.

 

[Nocturnal]

What you need to do is sell that chip and get an Opteron.

 

[Makaveli]

He need to learn how to overclock before selling anything.

 

[P0ldy]

Cool n Quiet on?

 

[leigh6]

So you rma'd your working 3500 Newcastle so you could get a Venice core 3500? HMMMMMMMMMM. YGWYD

 

[Accipiter22]

Originally posted by: n7
ROFL so you haven't lowered the HT multi/LDT & used a RAM divider, & it's the CPU's fault :roll:

Start reading. http://forums.anandtech.com/messageview.aspx?catid=28&threadid=1497607

I have no patience for people that spread FUD around.

i already read that guide, that's how I got it at 245 with a newcastle. I changed the cpu and now I can't get past 210. I did the exact same thing I did when I got it to 245, and I can't even get past 210 on step 2 of the guide.

 

[Accipiter22]

Originally posted by: leigh6
So you rma'd your working 3500 Newcastle so you could get a Venice core 3500? HMMMMMMMMMM. YGWYD

uuuuuuuuuuugh I can't spell this out any simpler.

1. newcastle 3500 works fine, lightening strike overloads surge supressor, newcastle gets toasted.
2. I get e6. I do the same thing as last time for OC'ing, can't get past 210 for FSB.

For the record, I AM using the quick & dirty oc'ing guide. I get to the 2nd step in it, where you leave the multiplier up, take memory out of the equation, and see how high you can set the FSB. I can't get it past 210 without the boot completely failing on me.

 

[Accipiter22]

Originally posted by: michaelpatrick33
Also, when the new processor was put in we don't know if the BIOS setting all defaulted back and he forgot to switch a setting. He isn't using a divider and we don't know what his memory is. Maybe he set a memory divider before and forgot and now he is trying to get 1:1 settings. Who knows without much more information.

it's generic corsair valueram.

 

[Macro2]

RE:"lightening strike overloads surge supressor, newcastle gets toasted.
2. I get e6. I do the same thing as last time for OC'ing, can't get past 210 for FSB."

Surges can semi toast other things you know. Often you have nagging problems after that.

 

[KoolDrew]

Originally posted by: Accipiter22

Originally posted by: michaelpatrick33
Also, when the new processor was put in we don't know if the BIOS setting all defaulted back and he forgot to switch a setting. He isn't using a divider and we don't know what his memory is. Maybe he set a memory divider before and forgot and now he is trying to get 1:1 settings. Who knows without much more information.

it's generic corsair valueram.

Since when is Corsair RAM generic?

 

[w00t]

ya generic ram doesnt oc well in 1:1 you goign to have to run a divider so its your fault.

 

[Accipiter22]

Originally posted by: w00t
ya generic ram doesnt oc well in 1:1 you goign to have to run a divider so its your fault.

so how did I get my newcastle running at 2.6 ghz?

 

[Accipiter22]

Originally posted by: Macro2
RE:"lightening strike overloads surge supressor, newcastle gets toasted.
2. I get e6. I do the same thing as last time for OC'ing, can't get past 210 for FSB."

Surges can semi toast other things you know. Often you have nagging problems after that.

other stuff's been replaced, but my friends winchester in my setup OC's fine.

 

[cryptonomicon]

well thanks for letting us know

 

[Chaotic42]

I thought my 3700 sucked for not doing over 245.

 

[Dragoon42]

dude, what mobo are you using? powersupply?

It seems like you might have a bad chip. But it also looks like there might be a bad OC'er that's trying to OC. What is your setup?