Overclocking E6420 problems

kreacher

Member
May 15, 2007
64
0
0
After reading many threads on overclocking the E6420 I tried it on my aging PC.
I just set AI Tuning to Manual and increased the FSB from 266 to 333. After restarting my Avast Home Edition was disabled and when I clicked 'My Computer' the window kept showing the torch and Searching.
Thinking that the system wasn't stable I restarted and set the AI Tuning to Auto. When that didn't fix anything I reset the BIOS to default settings.
When my PC starts it takes a long time to open anything, now I can start 'My Computer' after a long wait but Avast is still disabled.
What do I do?

Configuration:
Core 2 Duo E6420
Asus P5B (BIOS v1803)
4x 1GB Kingston Value RAM DDR2-667

EDIT: Thinking that I had blown a RAM chip I just enabled the memory remap feature and restarted. Suddenly Avast started working and when I restarted with memory remap disabled again it was still working. Weird stuff.

EDIT 2: Can anyone tell me how to get the overclocking right?
 

BonzaiDuck

Lifer
Jun 30, 2004
16,775
2,114
126
Originally posted by: kreacher
After reading many threads on overclocking the E6420 I tried it on my aging PC.
I just set AI Tuning to Manual and increased the FSB from 266 to 333. After restarting my Avast Home Edition was disabled and when I clicked 'My Computer' the window kept showing the torch and Searching.
Thinking that the system wasn't stable I restarted and set the AI Tuning to Auto. When that didn't fix anything I reset the BIOS to default settings.
When my PC starts it takes a long time to open anything, now I can start 'My Computer' after a long wait but Avast is still disabled.
What do I do?

Configuration:
Core 2 Duo E6420
Asus P5B (BIOS v1803)
4x 1GB Kingston Value RAM DDR2-667

EDIT: Thinking that I had blown a RAM chip I just enabled the memory remap feature and restarted. Suddenly Avast started working and when I restarted with memory remap disabled again it was still working. Weird stuff.

EDIT 2: Can anyone tell me how to get the overclocking right?

ASUS makes good motherboards, but if you ask my advice (and other colleagues chime in here) -- do the over-clocking manually. Read Graysky's over-clocking thread. Make sure you start with the RAM set to [DDR]=533, so that OC'ing the FSB from 1066 to 1333 will just push the RAM to their spec.

You're best to make all the settings manually, even if some voltages remain at "auto."

I can't advise on exactly what filling four slots with Value-Ram will do to your over-clocking potential, but they should run at their spec voltage and latency settings at 667 Mhz, even if you've filled four slots with them.
 

fffblackmage

Platinum Member
Dec 28, 2007
2,548
0
76
I was also going to recommend doing overclocking settings manually, but maybe that's because I'm not familiar with the software you're using to overclock.
Reading up on overclocking might be the best start. There are many things other than just simply changing the FSB freq. to consider: memory dividers, voltages (cpu, north bridge), timings, etc etc....

But don't worry, you'll learn quickly. The first time I tried OCing was with my ooold HP computer (Celeron at 400MHz). I tried bumping the FSB and the computer refused to POST. Fortunately, I knew about clearing the CMOS and got the computer booting up again. It scared the hell out of me though.
 

kreacher

Member
May 15, 2007
64
0
0
I thought I did read up on overclocking (graysky's thread too) :)
Specifically for the E6420 I read that just changing the FSB from 266 to 333 MHz will bump it to 2.67GHz without any issues (on stock cooler).
According to graysky' thread here's what I did -
1) CPU multiplier = 8.0 (max) so overclocking option is raising the FSB. Check.
2) I have DDR2-667 so max FSB I should use is 333MHz. Check.
3) Disabled C1E and Speedstep in BIOS settings. Check.
4) Set AI tuning to Manual. Check.
5) Changed CPU frequency to 333 setting divider to 1:1. Check.

After this I left the other settings to Auto because I read everywhere that E6420 can go to 2.6Ghz without any manual VCore bump.
Did I miss something?