• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Q6600 voltage?

M

Monkeypillow

Gawd
Joined
Aug 30, 2006
Messages
880
I'm looking to get my Q6600 to 3.6GHz, but I'm not sure how far to start.

I'm completely stable at 3.0GHz on stock voltage (1.275V).
 
Max recommended voltage is 1.5V.
Max recommended temp is 65C to 70C under load

So you still have plenty of headroom to hit 3.6Ghz.. So just increase the voltage little by little till you finally hit 3.2Ghz, 3.4Ghz, and 3.6Ghz.
 
It's a 65nm chip so as Danny Bui said, try not to go over 1.5 volts. Increase at increments and find what others are setting their ICH/MCH voltages to.
 
Alright, I'm on a Gigabyte P35-DS3L. What voltages should I be using for the ICH/MCH and northbridge?
 
DeadSkull said:
Are you sure? I though by intel spec max safe temp under load was below 80C.
Click to expand...

Maximum safe temp and maximum recommended temp are two different things. If your CPU is exceeding 75C regularly, then it isn't being cooled properly.
 
My vid is 1.325 my oc is in my sig it took 1.49v to get there, solid as a rock with 8 gigs of ram. temps never see over 48c on full load, xigmatek cooler.
 
Monkeypillow said:
I got this one a while back. Any way I can check the date?
Click to expand...
If you still have the box it came in, there's a way to find out the week of manufacture from the code printed on the side.
Monkeypillow said:
:eek: Ah yes, that would be 1.328.
Click to expand...
Silly question, but have you tried raising it to around 1.5V? Since it's stable at 3.4GHz with fairly little voltage, maybe the only thing you need to push it higher is simply more volts.
 
Mine wont even do 3.2. 3 is easy at almost stock voltage, but I just cannot get even 3.2 stable at 1.5V.
 
Zero82z said:
If you still have the box it came in, there's a way to find out the week of manufacture from the code printed on the side.

Silly question, but have you tried raising it to around 1.5V? Since it's stable at 3.4GHz with fairly little voltage, maybe the only thing you need to push it higher is simply more volts.
Click to expand...

^ this... if you can already hit 3.4 with that voltage then i don't see why it wouldn't hit 3.6 with a bit more juice.
 
why cant mine do 3.2 even with 1.5v, and run perfectly 3.0 with almost stock voltage?
 
Boostage said:
My vid is 1.325 my oc is in my sig it took 1.49v to get there, solid as a rock with 8 gigs of ram. temps never see over 48c on full load, xigmatek cooler.
Click to expand...

I'm jealous. What do you use for a full load?

My temps are too high, so I think I may have mounted the water block incorrectly, but the top left screw just won't go as far as the others. Any ideas?
 
Zero82z said:
If you still have the box it came in, there's a way to find out the week of manufacture from the code printed on the side.

Silly question, but have you tried raising it to around 1.5V? Since it's stable at 3.4GHz with fairly little voltage, maybe the only thing you need to push it higher is simply more volts.
Click to expand...

If I have to go that much higher for 200MHz, I'm fine with 3.4GHz. :)
 
Kryogen said:
Mine wont even do 3.2. 3 is easy at almost stock voltage, but I just cannot get even 3.2 stable at 1.5V.
Click to expand...

Try 8*400 = 3.2

That did it for me, and I am at stock volts @ 1.225

That's my VID too.

:D
 
Kryogen said:
why cant mine do 3.2 even with 1.5v, and run perfectly 3.0 with almost stock voltage?
Click to expand...

my buddy had that problem, was his mobo,once he got a new board it was on like donkey kong, had that bitch firing at 3.6.... if you've tried different boards then you have a VERY homo chip lol... maybe try different multi / fsb ratios ?
 
Kryogen said:
why cant mine do 3.2 even with 1.5v, and run perfectly 3.0 with almost stock voltage?
Click to expand...

You probably need to tweak your other voltages as well. Try raising your CPU PLL, FSB Termination, and NB voltages slightly.
 
Zero82z said:
You probably need to tweak your other voltages as well. Try raising your CPU PLL, FSB Termination, and NB voltages slightly.
Click to expand...


I agree, try these things, just no way a q6600 is stuck at 3.2 unless its a b3 on a 965 chipset.
 
I was able to boot into windows at 3.6, but it promptly crashed under Intel burn test.

For some reason, when I manually set voltages in my BIOS, CPU-Z reports them considerably lower.
 
Monkeypillow said:
I was able to boot into windows at 3.6, but it promptly crashed under Intel burn test.

For some reason, when I manually set voltages in my BIOS, CPU-Z reports them considerably lower.
Click to expand...

Yup, it's called vdroop. Most motherboards have it. Some have options to significantly reduce it. I have to set my vcore to 1.54v in BIOS to see 1.49v in CPUz at idle. Then I lose almost .1v at load.
 
What are you guys setting your NB voltage to? For 3.6ghz I'm running about 1.44V for the NB without messing too much with CPU Vtt or SB voltages. In my experience with my previous Abit iP35 Pro board (for P35 reference), I could run 360x10 @ 1.51V vcore and 1.44V nb, whereas I always needed to bump the nb voltage up to 1.48V for 400x9 to work. But that board had alot of vdrop & vdroop. In your cases ... you'd be trying 400 x 9 or 450 x 8 right? Why not experiment ...400x9, 1.5V (bios) and 1.5V NB (bios). And if that works, turn the nb voltage down. And if that doesn't help then maybe work backwards speedwise. Considering the known safe voltage wall, maybe that way is easier?

Also, I'd check what your vdrop is like (idle voltage in Windows) and then what your vdroop is under load. Who knows, you may be setting 1.5V in the bios and only be getting 1.47 or 1.48 in actuality.

I had to set 1.565V on the P35 board to get 1.5-1.51V idle in Windows - and then during prime95, that voltage would drop to 1.47 under load. So for me it was the only way to get it stable.

Anyway that's just my experience. Thankfully this Asus Maximus II board has negligible vdrop (load line calibration in bios) and zero vdroop so I can run 400x9 @ 1.48V and it never drops below that.

Monkeypillow - is the waterblock not on flat on socket? Do the individual core temps vary alot? I know my Cores 0,2 are always 2-3C less than Cores 1,3. But it may just be how the thermal paste spread (I mounted the waterblock last while the comp was standing up).
 
prasvt said:
What are you guys setting your NB voltage to? For 3.6ghz I'm running about 1.44V for the NB without messing too much with CPU Vtt or SB voltages. In my experience with my previous Abit iP35 Pro board (for P35 reference), I could run 360x10 @ 1.51V vcore and 1.44V nb, whereas I always needed to bump the nb voltage up to 1.48V for 400x9 to work. But that board had alot of vdrop & vdroop. In your cases ... you'd be trying 400 x 9 or 450 x 8 right? Why not experiment ...400x9, 1.5V (bios) and 1.5V NB (bios). And if that works, turn the nb voltage down. And if that doesn't help then maybe work backwards speedwise. Considering the known safe voltage wall, maybe that way is easier?

Also, I'd check what your vdrop is like (idle voltage in Windows) and then what your vdroop is under load. Who knows, you may be setting 1.5V in the bios and only be getting 1.47 or 1.48 in actuality.

I had to set 1.565V on the P35 board to get 1.5-1.51V idle in Windows - and then during prime95, that voltage would drop to 1.47 under load. So for me it was the only way to get it stable.

Anyway that's just my experience. Thankfully this Asus Maximus II board has negligible vdrop (load line calibration in bios) and zero vdroop so I can run 400x9 @ 1.48V and it never drops below that.

Monkeypillow - is the waterblock not on flat on socket? Do the individual core temps vary alot? I know my Cores 0,2 are always 2-3C less than Cores 1,3. But it may just be how the thermal paste spread (I mounted the waterblock last while the comp was standing up).
Click to expand...
For 3.8 ghz i needed the following voltages.

vcore, 1.50625 (1.512@load, LLC enabled)
pll, 1.6v
nb, 1.3
fsb-term, 1.34
v-dimm, 2.02, 5-5-5-18
Clocked using 9x422, ram @844mhz
Full spec in sig.
 
prasvt said:
What are you guys setting your NB voltage to? For 3.6ghz I'm running about 1.44V for the NB without messing too much with CPU Vtt or SB voltages. In my experience with my previous Abit iP35 Pro board (for P35 reference), I could run 360x10 @ 1.51V vcore and 1.44V nb, whereas I always needed to bump the nb voltage up to 1.48V for 400x9 to work. But that board had alot of vdrop & vdroop. In your cases ... you'd be trying 400 x 9 or 450 x 8 right? Why not experiment ...400x9, 1.5V (bios) and 1.5V NB (bios). And if that works, turn the nb voltage down. And if that doesn't help then maybe work backwards speedwise. Considering the known safe voltage wall, maybe that way is easier?

Also, I'd check what your vdrop is like (idle voltage in Windows) and then what your vdroop is under load. Who knows, you may be setting 1.5V in the bios and only be getting 1.47 or 1.48 in actuality.

I had to set 1.565V on the P35 board to get 1.5-1.51V idle in Windows - and then during prime95, that voltage would drop to 1.47 under load. So for me it was the only way to get it stable.

Anyway that's just my experience. Thankfully this Asus Maximus II board has negligible vdrop (load line calibration in bios) and zero vdroop so I can run 400x9 @ 1.48V and it never drops below that.

Monkeypillow - is the waterblock not on flat on socket? Do the individual core temps vary alot? I know my Cores 0,2 are always 2-3C less than Cores 1,3. But it may just be how the thermal paste spread (I mounted the waterblock last while the comp was standing up).
Click to expand...

My motherboard doesn't actually tell me the voltages I'm using; it only gives me the option of adding .1, .2, and .3 volts to the northbridge.

No, I don't believe the water block is mounted evenly. My temps vary by 10C at times, and the top left screw won't tighten as far as the rest.
 
This wasn't stable, but if I'm booting, I've got to be close, right? :)

3175818784_f07cf8b3ed.jpg
 
Monkeypillow said:
I'm jealous. What do you use for a full load?

My temps are too high, so I think I may have mounted the water block incorrectly, but the top left screw just won't go as far as the others. Any ideas?
Click to expand...

Sounds like a cap is under the block. :eek:
 
I need 1.41 vcore and slightly boosted northbridge just to reach 3.2ghz stably, and almost 1.5 vcore to reach 3.5ghz.
 
3.6ghz @ v1.4125 in the early to mid 30's. I'm watercooling so that's what I expected it to be. I know I can boot into 3.8ghz, but I really have to push voltage to 1.5+ and I just don't want to do that. Also, memory is sitting at 1.92 volts, nb is 1.15 and the rest is auto. I'm still screwing around with fsb strap and stuff like that to see which is the best for the overclock.
 
i am only able to hit 3.352ghz on 1.408v idle (droop to 1.36/1.376 load)...8x419 - G0 1.325vid

temps idle around 20's and load depends on what i run...burntest takes them to 50c after about an hour of loops...

i tried for 3.4...but i keep hitting a wall a little higher than this...voltage needs to go way up for a very nominal gain...

i suppose with a bit more tweaking i could get it stable...but the additional power/heat for another 100 or 150mhz? not worth it really...
 
Methadras said:
3.6ghz @ v1.4125 in the early to mid 30's. I'm watercooling so that's what I expected it to be. I know I can boot into 3.8ghz, but I really have to push voltage to 1.5+ and I just don't want to do that. Also, memory is sitting at 1.92 volts, nb is 1.15 and the rest is auto. I'm still screwing around with fsb strap and stuff like that to see which is the best for the overclock.
Click to expand...

What's your loop like? I'm seeing temps up to 42 on the hottest core, but I think that's the fault of a mismount.
 
You must log in or register to reply here.
Back
Top