E6600 Vcore help

CPU-Zebra

CPU-Zebra

CPU-Zebra

Associate
Joined
18 Aug 2007
Posts
45
Location
W. Sussex
This is my first time overclocking my CPU. I've got it up to 2.95 odd but getting to 3.0ghz on boot up when it shows the Windows XP welcome screen it freezes. My setup is Core 2 Duo E6600 - Asus P5N-E - Hiper 580W - Arctic Cooling Freezer 7 Pro. I have the Vcore at stock and haven't been OCing my memory. I did 2 hours of prime95 with no errors or the such at 2.9ghz, and as I understand the Core2s get to 3ghz quite easily. Now I am unsure if firstly it is the voltage that needs increasing, and then if so what to. I understand my mobo has bad Vcore drop when under load. In Cpu-Z I get 1.344V idle and clocked at 2.9ghz it drops to 1.266V under load. Finally, what is the true setting of my Vcore in my BIOS, Cpu-Z gives me 1.344 (which I guess is a read out of the actual Vcore going through the chip) and in CoreTemp it says VID is 1.3250 (is this Vcore or some power saving thing?). If I look in my BIOS it's set to auto so I have no point to start from. So, is Vcore the problem, and if so what should I set it to and start from. Thanks.
 
Last edited:
Ok thanks. I'm just wondering (because I'm going to restart and continue Ocing in a few mins) how much Vcore affects temp? And when does Vcore get dangerous to the chip? Thanks.
 
Theorectically the more voltage you put through the chip, the hotter it will be.

Well I had my E6600 at 1.55Vcore which was OC'd to 3.6GHz for a long time and I've had no symptons because of this, probably just try and put no more than 1.55 and you should be fine.
 
Voltage can only really damage the chip in that it causes more heat.

Ie. Putting more voltage through the chip won't cause any damage in itself, but the resultant heat can.

So as long as you keep an eye on the temps and make sure they're within a safe range, you should be OK :)

Obviously this is only true up to a point - you can't go sticking 1.8v through that E6600 and expect it to live for too long ;)

Jon
 
Ok thanks. I was just wondering if Vcore can damage the chip past the temp, say the temps are fine but it still may be causing damage, like you say not to go over 1.6 really. I'll pick up where I left off Ocing tomorrow, thanks. Oh and as this is my first time OCing, I was wondering how does say a 3.4ghz OC on an E6600 reduce it's lifespan if it is running at or below stock temps? Thanks.
 
Last edited:
If it's running at or below stock temps, the lifespan should be almost the same as it would be running at stock.

It might be a tad shorter, but the lifespans of modern CPUs are so great, they are replaced long before they die in 99 out of 100 cases.

Jon
 
Ok, when I put my FSB up to 1,333mhz to get 3,006mhz my PC freezes at the windows startup screen still. I got the Vcore on 1.3750 in the BIOS and it reads as 1.392V in CPU-Z. I ran a 30 minute test at 2.99ghz in prime95 and it was fine, but at 1,333mhz FSB it freezes on startup. It runs fine at 1,332mhz FSB but when I knock it to 1,333 it won't boot into windows. Vcore is up by .05V and won't boot. What's going on?
 
I have the same going from 359 to 360 mhz. I guess i was lucky, ive been quite happily running it at 3.15 at stock vcore. Try knocking down you multiplier and then upping the fsb to give you the same speed. Thats what im doing. Currently at 420mhz with a 8x multi. To give 3.35ghz on a tuniq. Currently running orthos to test. Oh, and im at 1.4v
 
Ok, I'll try the multiplier. How does this affect the CPU anyway? Is there any difference in say an 8x clocked to 3.4 or a 9x clocked to 3.4?
 
CPU-Zebra said:
How does this affect the CPU anyway? Is there any difference in say an 8x clocked to 3.4 or a 9x clocked to 3.4?
Click to expand...

The actual CPU "speed" will be the same. It's running at the same core clock so it processes the same amount of data per unit time.

However running with a lower multi means the FSB has to be higher which increases ths speed of the memory and other system components.

I suppose an 8x clocked to 3.4 would be a slightly faster system than a 9x clocked to 3.4. However with a higher multi, you might have to stick a divider on the RAM which lowers its speed if it cannot run that fast, which slightly negates the advantage of a higher FSB/lower multi.

Overall, doesn't make a massive amount of difference :)

Jon
 
Ok, it has booted into windows on an 8x multi and FSB 1,333mhz. This gives me 2.66ghz in CPU-Z, but Coretemp gives it as 3ghz (375x8) I've heard changing the multiplier can make some programs give the wrong CPU clock speeds. Now what is the next step? Should I work my way back up to where I was testing it everytime, or should I just put it back up to where I was on a 9x multi and continue from there? And also, what can putting the FSB really high do to the mobo, does it damage the NB or can it damage other parts of the board or other components (I worry a lot). BTW I'm only OCing my CPU for now, my RAM is running unlinked to the FSB and is being kept around stock speeds or less. Thanks a lot.
 
Hit a wall again! I lowered the multiplier to 8 which got me past 1,333mhz FSB, but now it won't boot at anything past 1,370mhz FSB (2.74ghz). I managed to get 2.99ghz with a 9x multiplier and stock volts. Even with 1.392 Vcore it wouldn't get past 1,333mhz FSB on 9x and with 1.392V it won't get past 1,370mhz on 8x (which is a lower clock speed than I got on 9x multiplier before I hit the wall). The memory is running unlinked and has stayed at around it's stock 800mhz all the time. Everything else is untouched. What should I do :confused: ?
 
You must log in or register to reply here.
Back
Top Bottom