E8400, Can't overclock or UNDERCLOCK!

Scrooge2

Senior member
Jul 18, 2000
856
0
0
I got a e8400, upgraded from e6320. I KNOW my mobo and memory could handle overclocking cause I was doing 430 FSB and 1000+ mhz for my ram. I ran my 1.86 e6320 at 3.0ghz for almost a year without problems.

Then comes my new e8400 at 333x9=3ghtz. I CAN'T OVERCLOCK IT! Freezes at bios startup at 9x400. Freezes at 9x380, freezes at 9x350.

But here's the kicker. I tried to see if it was the mobo by UNDERCLOCKING it at multipliers 8, 7, 6, and it froze at bios start up! What the heck? I can't seem to underclock the darn thing either!

Anybody have this problem too? Any ideas?

e8400
GA-p965 DS3
Crucial 2x1gb ddr2 800
WinXp 32bit

Thanks!
 

LOUISSSSS

Diamond Member
Dec 5, 2005
8,771
54
91
are you sure you've read that overclocking guide at the top of this forum?


have u tested ur crucial ram with memtest86+ for 24 hours each dimm?
 

geokilla

Platinum Member
Oct 14, 2006
2,012
3
81
You're using P965 chipset. They might not support 45nm processors. Check Gigabyte's site.
 

Scrooge2

Senior member
Jul 18, 2000
856
0
0
Yes! I've Oc'ed processors before. The same ram and mobo have been at 400mhtz for my e6320 for months until my e8400. The ram definitely works! The only thing I've upgraded is the processor!
 

Scrooge2

Senior member
Jul 18, 2000
856
0
0
The 965P has "non official" support with the latest bios from Gigabyte. I mean my motherboard clearly works with it as I am on it right now!
 

BonzaiDuck

Lifer
Jun 30, 2004
15,732
1,459
126
You're swapping out processors and changing clock settings.

Did you clear the CMOS before you swapped hardware components?

I posted a thread about myself and another forum member who'd experienced this problem just by changing to OC and back to stock again.

Consider resetting the CMOS, rebooting and entering BIOS Setup, and re-flashing the current BIOS again -- if the BIOS has that built-in flashing feature. If not, clear the CMOS and flash it using the floppy-disk utility.
 

Scrooge2

Senior member
Jul 18, 2000
856
0
0
I already reflashed the bios, I was not aware that I needed to change the CMOS, never had this issue again, but I'll try it!