E6600 Vcore help

CPU-Zebra · 18 Aug 2007 at 23:23

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.

CPU-Zebra · 18 Aug 2007 at 23:51

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.

CPU-Zebra · 19 Aug 2007 at 00:58

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.

CPU-Zebra · 19 Aug 2007 at 01:25

Ok. Thanks a lot everyone.

CPU-Zebra · 20 Aug 2007 at 17:32

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?

CPU-Zebra · 20 Aug 2007 at 17:49

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 · 20 Aug 2007 at 18:46

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.

CPU-Zebra · 20 Aug 2007 at 23:34

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:

?