Overclocking E6600 Core 2 Duo issues

Intel Core 2 duo e6600 dual core process...
August 3, 2009 at 15:40:51
Specs: Linux i686, Intel Core 2 Duo E6600, Corsair XMS2 DDR2 800MHz
I have an Intel Core 2 Duo E6600, an asus p5b deluxe wifi-ap edition motherboard, 2GB of Corsair XMS2 DDR2 800MHz and an nvidia 8800GT 512 MB. I am new to overclocking but as I understand it it basically involves increasing the speed of the front side bus and perhaps messing with the VCore voltage and the RAM votlage.

The other day I booted into the bootup menu and increased my CPU frequency from 266 to 333 MHz. I hit F10 to save and the computer turned off, turned back on, then turned off and then turned back on again, this time staying on. However, the PC was not sending a signal to the monitor. I was worried that I destroyed something so I opened up my computer to be sure. I unscrewed the video card, took it out, blew some dust off of it and stuck it back in there. Then I tested the monitor and it worked. When it was booting up I got a message that said overclocking failed and it told me to hit F1 or F2. Then I manually set my CPU VCore voltage (the RAM had been set at 2.1) tried 300 and it worked. Then I tried 333. That worked. Then I tried 370. That worked. Then I tried 390 (I wasn't sure if having my RAM go above the 800MHz mark would damage it). I saved the settings, powered down and then turned it on again.

All the fans and everything started whirring but again, no signal to the monitor (actually I really don't remember, it might not have booted at all).

Regardless, the motherboard temp averages around 36C while the CPU at normal 2.4GHz runs about the same. Right now I have it overclocked to 3.0 GHz and the temperature is averaging about 45C I think (although I haven't been monitoring it for long periods of time but when I was in XP and booted up PCProbe II while running just firefox and something else it was about that.

So, why is it messing up it I go over 370MHz if the CPU temp is only 45C? Also, should I set my RAM so it is a 1:1 ratio with the CPU frequency (same thing as FSB right?) or should I try and overclock it? Like written before it is Corsair XMS2 DDR2 800MHz RAM running in dual channel interleaved mode.

Here are my current settings (seems to be working):
CPU Frequency 333
DRAM Frequency DDR2-667
PCIE Frequency 110
PCI Clock Synchronization 33.33MHz
Spread Spectrum Disabled
Memory Voltage 2.1V
VCore 1.3375V
FSB Termination Voltage Auto
NB VCore Auto
SB VCore Auto
ICH Chipset Voltage Auto

Memory Remap disabled
RAM timing by SPD off
CAS latency 4
RAS to CAS delay 4
RAS Precharge 4
RAS Activate to Precharge 12
DRAM Write recovery 6 DRAM clocks
DRAM TRFC 42 DRAM clocks

CPU configuration:
Frequency 3.01 GHz
FSB 1332MHz
L1 Cache 32 KB
L2 Cache 4096KB
Ratio Status: Unlocked
Max Value: 9 Min Value: 6
Actual Ratio Value: 9
Modify Ratio Support Disabled
C1E enabled
Max CPUID value limit disabled
CPU TM function enabled
execute disable bit enabled
PECI off

Could any please help me with this? If you post the settings I should try could you tell explain to me why those settings need to be that way? Also, what if I want to try and clock my RAM over 800MHz and try to overclock my 8800GT 512MB? Do I need to check anything other than temperature; do I just check the temperature of the video card and RAM by touching them (grounded) or does that take a fair bit of experience (knowing what is too hot).

Thank you.

See More: Overclocking E6600 Core 2 Duo issues

Report •

August 3, 2009 at 18:46:51
Your problem is probably not due to overheating. You should lock the PCI-E frequency at 100-if you don't do that, the PCI-E frequency increases because of the other overclock. Which corsair RAM do you have, C4 ?
2.1 volts should be sufficient. You should increase the FSB frequency at smaller increments(20 MhZ, say) until you reach a point where it fails or is unstable. When you say "CPU VCore voltage-...tried 300-that's the FSB, not the voltage. What voltage did you set the cpu at ? You should be able to increase the RAM to DDR2 800 MhZ and set it at a 1:1 ratio with the CPU frequency-that is, the cpu would be set at 400 MhZ.

Report •

August 3, 2009 at 22:38:18
Yeah, I meant that I changed the FSB to those values. The CPU VCore is 1.3375V. My RAM is this in dual channel interleaved: http://www.newegg.com/Product/Produ...

Do you think I could go any higher than 400MHz and overclock the RAM too? What about my 8800GT? I thought that overclocking was just limited be heat, which me only being at 45C for the CPU at 333MHz I should be able to get at least 3.5GHz I am thinking. That is, of course, if the RAM will allow it right?

Report •

August 4, 2009 at 06:31:59
Personally I've never overclocked RAM-you would have to worry about the RAM voltage then, perhaps. Heat is not the only issue with overclocking. Why don't you try first to see if you can get the RAM to DDR2 800 MhZ and the CPU frequency set at 400 MhZ. If you overclock the RAM and keep the CPU frequency set at 400 MhZ, it will no longer be in a 1:1 ratio. I see that you have the RAM voltage set higher than is necessary, which shouldn't hurt the overclock, but might make the RAM not last quite as long.

Report •

Related Solutions

August 4, 2009 at 07:10:05
There's no reason to overclock the RAM. You should be maintaining a CPU:DRAM frequency ratio of 1:1. That means with the CPU at 1333MHz FSB (333MHz freq), the RAM should be configured to run as DDR2-667 (333MHz freq).

If you want to take full advantage of your RAM, lower the CPU multiplier to 8x, set the FSB at 1600MHz (400MHz freq) & set the RAM to run in sync as DDR2-800 (400MHz freq). Do NOT overclock the PCI-e bus....lock it at 100MHz.

Report •

August 4, 2009 at 12:18:12
Well as far as I have tried the thing won't run right over about 370. I have no idea why. Regardless, I have a bigger issue now. I had the settings the same as above and was wondering i f setting DRAM Frequency to auto would be any faster (it was set at 667). Now I just get the multiple boot thing where all the fans start going but nothing is receiving signal (monitor, flash drive, etc.)

I tried taking the graphics card out, turning Psu off and on, taking the CMOS battery out, running with 1 stick of RAM, taking Cmos out and moving jumper, and taking the CPU out and back in. Right now I have unplugged the power connector to the MB, taken all RAM out and graphics card. I took the CMOS battery out, moved the jumper and moved it back. Then I put the RAM and graphics card back in. The gpu isn't connected to PSU either. Iam going to leave it like that for a couple hours and come back and try again.

Report •

August 4, 2009 at 12:26:13
I should have paid closer attention to which board you're working with. It's based on the old (but good) P965 chipset. I doubt you'll hit 400MHz with it...from what I've read, about 370-380MHz is the limit. Make sure you have the latest BIOS.

Report •

August 4, 2009 at 12:26:36
I'll come back and report what happens. Really though, what is going on? I thought thE BIOS settings were stored in CMOS.

I knew I shouldn't have started screwing around with overclocking, now this is going on. Doesn't OC'ing make the hardware fail faster anyway?

If I get it working again I kind of just want to leave it alone unless someone has the correct settings. I spent way too much on this for it to mess up, especially since I have basically no money now (this PC was built 3 years ago).

Report •

August 4, 2009 at 14:55:31
"I thought thE BIOS settings were stored in CMOS"

They are. And the battery was what keeps them stored in CMOS memory. Remove the battery, lose the settings.

"Doesn't OC'ing make the hardware fail faster anyway?"

Not if you know what you're doing.

"If I get it working again I kind of just want to leave it alone unless someone has the correct settings"

There are no "correct settings". It's always trial & error, but you need to understand the basics of what you're doing.

I believe your CPU default settings are 9 x 266MHz (2.4GHz), right? Let's say you want to run it at 3.0GHz. All you need to do is set AI Tuning to manual, increase the CPU freq from 266MHz to 333MHz, set the RAM to DDR2-533, lock the PCI-e at 100MHz, lock the PCI at 33.33MHz, disable any/all Spread Spectrum settings & disable EIST (aka SpeedStep).

You may or may not have to play with the voltage settings....that is where a lot of the trial & error (& experience) comes into play.

Report •

August 4, 2009 at 15:23:11
"Doesn't OC'ing make the hardware fail faster anyway?"
That might be true, but with the overclock you would be doing, it's probably not going to make the hardware fail that much faster. Also, that's why I suggested setting the RAM voltage lower-1.9 volts should be sufficient for your RAM, especially if you underclock the RAM as jam suggested.

Report •

August 4, 2009 at 23:26:53
I just came back after 8 hours and tried turning it on and it booted up with default settings. I had turned off the power supply, unplugged it and unplugged the 4pin power connector tot he motherboard (I forgot to unplug the 24 pin; by the way would there be any reason why I would have a 4 pin connector hooked up instead of the 8 pin power connector cable that is right next to it??)

I still have no clue why the initial pulling out of the CMOS battery and the clearing of the CMOS using the jumper didn't allow me to do a normal boot initially. Regardless, it booted.

I have the settings back at default except for the RAM timings which I set to 4-4-4-12. I set the JMicron controller to ACHI mode as well as the hard drive and tried booting into Windows but got a blue screen. I switched it back to IDE and it worked fine. I thought ACHI was meant to run the hard drive as SATA (which my drive is) and I definitely don't want to be running at IDE speeds (will bottleneck my system). Could it have been that the JMicron controller controls the DVD drive and since that is actually IDE it didn't like it? Would setting it to RAID allow me to use SATA speeds and still boot Windows?

Anyway, back on track with overclocking. After that awful experience I don't want that to happen again. I'll make a personal note to never turn the RAM to auto when trying to overclock (unless I want to have an unbootable machine for the next 8-10 hours or worse, screw the CMOS stuff up and have to buy a new motherboard; I probably ruined any warranty I may have had left overclocking).

I checked my BIOS version and it is version 1101. That is the latest non-beta version. However, there are 9 newer BIOS versions that are in beta (doesn't appear to say how far along in beta as far as I can tell). If you go to Asus support and put in motherboard> socket 775 > and choose P5b Deluxe/Wifi-AP you can see all the BIOS. I would link it but so many sites use flash for this stuff now...
I am going to go ahead and download the BIOS versions and make a bootable flash disk. I will wait to flash the BIOS until I get a response however.

I want to be able to get the most performance out of the current computer I have without significantly decreasing the time my hardware has to live (after all I am overclocking stuff to prolong this computer's use as a gaming PC) and obviously not making it unbootable/unstable or the worst that could happen: having to buy a new motherboard or possibly other parts (I am broke now).

Report •

August 5, 2009 at 02:23:51
Depending upon the cpu you only need the 8 pin cpu connection for more powerful wattage cpus. Anything over 130 watts would require an 8pin cpu connection. Your processor only draws 65 watts so there isn't a need for the 8pin cpu connection for your cpu.

Well it seems to me based on what i just read that you are going to need a better motherboard to get the most out of that processor. I guess you are just going to have to deal with the limitations that you have on that motherboard until you get some extra cash and save up for a better overclocking motherboard. You pretty much hit your limit with that motherboard.

Iron Sharpens Iron.

Report •

August 5, 2009 at 03:45:42
Thanks for your help. However, I need help with the actual BIOS settings. I also need to know if I should flash my BIOS with the latest beta one. One of the beta ones says something about better RAM support for 1333MHz mode, maybe that would help me.

Could someone clarify the ACHI, RAID and IDE setting for me as well?


Report •

August 5, 2009 at 07:53:01
"Would setting it to RAID allow me to use SATA speeds and still boot Windows?" This tells you how to do it by modifying the registry. I would back up the registry first if you are going to try it.

Report •

August 5, 2009 at 11:24:49
I really want to know if it is a good idea to flash with the latest beta BIOS and I need help on the settings. I jsut tried turning spread spectrum off, setting RAM voltage at 1.9V, CPU VCore at 1.3375 or so and moved the FSB up to 333. Windows wouldn't even boot, at all. It would get to about the point where it should go to the main screen then it rebooted. So, just leaving the other setting the same and upping the FSB isn't going to work apparently. I already have NTFS filesystem errors from blue screens.

Report •

August 5, 2009 at 11:31:08
Did you lock the PCI-e at 100MHz ? Try setting the timings back to 5-5-5-18

Report •

August 5, 2009 at 12:26:34
"One of the beta ones says something about better RAM support for 1333MHz mode, maybe that would help me"

I don't think you understand how it works. When you run the CPU at 1333MHz FSB (QDR), you should be running the RAM at 667MHz (DDR). Maintaining a 1:1 ratio is important if you want optimal performance. And that ratio is based on frequency, not the bogus QDR & DDR ratings. And just in case you're not familiar with with Intel's QDR ratings:

800MHz FSB = 200MHz frequency
1066MHz FSB = 266MHz frequency
1333MHz FSB = 333MHz frequency
1600MHz FSB = 400MHz frequency

Memory DDR ratings:

DDR2-400 = 200MHz frequency
DDR2-533 = 266MHz frequency
DDR2-667 = 333MHz frequency
DDR2-800 = 400MHz frequency
DDR2-1066 = 533MHz frequency
DDR2-1200 = 600MHz frequency

Report •

August 7, 2009 at 15:49:41
My RAM says its timing are 4-4-4-12. Yes I understand the FSB to RAM ratio, but I can't over what seems like 333-350 without it not working. That isn't much of an overclock considering the CPU is only running 42-43 C overclocked from 2.4 to 3.05.

Report •

August 7, 2009 at 17:39:34
2.4 to 3.05 is about a 25% overclock. I wouldn't measure how good an overclock is by how much increase in temperature there is. According to the link you gave on newegg, the default timings of your RAM are 5-5-5-18. Your RAM might be capable of 4-4-4-12, but if that doesn't work, you should perhaps go back to the default timings.

Report •

August 7, 2009 at 17:54:16

It says 4-4-4-12 right there. Am I looking at the wrong thing?

I posted this elsewhere but does any of this have to do with me having a seemingly random system beep that happens every so often (notice it using WIndows XP SP3 but it might do it on other things)? It is just a single beep that lasts a very short time. It is almost unnoticeable. Also, when I load into XP I get the "installing device" sound every single time. Is that possibly related?

Report •

August 7, 2009 at 18:22:16
"I understand the FSB to RAM ratio, but I can't over what seems like 333-350 without it not working"

So that means you're running the RAM at 667-700MHz, right? You're not trying to run it at 800MHz? Because if you're starting off with the CPU at 1066MHz FSB & RAM at 800MHz, the ratio is 2:3. So if you increase the FSB to 1333MHz, the RAM speed will increase to approx 1000MHz.

Report •

August 7, 2009 at 18:53:30
It says OVERCLOCKABLE to 4-4-4-12-under specifications it's listed as 5-5-5-18. But, according to jam's response, that might not be your problem.

Report •

August 9, 2009 at 16:56:52
Yeah I have had the timings at 4-4-4-12 and the voltage at 2.1V for about 2 years now. Only changing the CPU stuff gave me a lot of problems.

Report •

August 21, 2009 at 14:59:52
tightening down RAM latency timings (lower numbers) can theoretically increase performance, but i doubt it's an increase that a human can detect. Tightening down the timings can also seriously decrease stability, which you definitely WILL detect.

the faster timing settings may have worked fine for years, but then you started changing the default frequency of the RAM. If you're increasing your **RAM frequency** and lose some stability, loosening up the **latency timings** could increase stability and allow you to hit the CPU/RAM frequencies you were shooting for.

Report •

August 24, 2009 at 11:16:49
Thanks. That is a nice bit of info to know. I had always just assumed the latency timings were defaulted to 4-4-4-12.

Report •

Ask Question