Sign in with
Sign up | Sign in
Your question

Recommend me e6600 voltages please!

Last response: in Overclocking
Share
May 22, 2007 4:56:47 PM

I am trying to reach 3.3-3.5ghz with my new e6600 processor. Here are some of my hardware specs to help you help me :wink:

e6600 SL9ZL http://processorfinder.intel.com/details.aspx?sspec=sl9... (NOT ---> http://processorfinder.intel.com/details.aspx?sspec=sl9...

eVGA NF68-A1 680i SLI (P28 bios)

2gb OCZ Platinum Rev.2 DDR2-800mhz 4-4-4-15 1.9v-2.1v

Zalman 9700 1300-2800rpm

Antec900 Case

----------------------------------------------------------------------------------
I have already gone into the bios and did all the "tidying up the bios" parts as dictated by the c2d overclocking guide. I am currently running at 2997mhz (ram 666mhz) with the voltage page as follows, and it is acceptably stable, but I would like to see what changes you guys recommend to push it a little further...

CPU Core: 1.43125v (1.41v in windows)(1.38v Vdroop)
CPU FSB: 1.4v
Memory: 2.0v (4-4-4-15 666mhz)
nForce SPP: 1.3v
nForce MCP: 1.55v
HT nForce SPP<->MCP: AUTO
------------------------------------------------------------------------------------

Orthos Temps (10minutes only) when stock bios: 42 Tcase/57-57 Tjunction

Orthos Temps (15minutes only) @2997 now: 48 Tcase/65-65 Tjunction
May 22, 2007 7:40:27 PM

you should not be over 1.35V for the Vcore at tha clock speed, most Core2 processors go there at 1.2V.
May 23, 2007 11:57:18 AM

Nothing over 1.500v on air. Even that is a little rich for my blood unless I am benching. My X6800 is at 1.4750v running 24/7 3811MHz. I bench it with 1.500v on 3900MHz (air) but I have seen 4200MHz on 1.58v with chilled water. (The lower the temo, the better the performance)
Related resources
May 25, 2007 5:35:10 PM

Only changes I tried doing were...Everything else the same...

I just tried 1.45v vcore bios (1.40v vdroop)
3087mhz
1372 fsb
676mhz ram

and it crashed after 2.5 minutes of Orthos.

the Temperatures were 51celcius Tcase, and 67-67 Tjunction.

Im sure im doing something wrong, can someone make me any suggestions please? I doubt the cpu wall @3.0?
May 25, 2007 6:34:32 PM

Quote:
Only changes I tried doing were...Everything else the same...

I just tried 1.45v vcore bios (1.40v vdroop)
3087mhz
1372 fsb
676mhz ram

and it crashed after 2.5 minutes of Orthos.

the Temperatures were 51celcius Tcase, and 67-67 Tjunction.

Im sure im doing something wrong, can someone make me any suggestions please? I doubt the cpu wall @3.0?


The t-junction sounds low but the rest sounds about right for 1.45, maybe a little high.I would recomend that you keep the multi on 9 and raise the FSB since the most common wall is the FSB wall. Maybe try 1.5.
May 26, 2007 4:27:46 PM

Am I needing such high vcore because my other voltages are too low? Is my vfsb, nForce spp voltages too low? Is it a bad idea to have HT nForce SPP<->MCP: on AUTO?

Quote:
I suggest you read this: Core 2 Duo Overclocking Guide


I already mentioned in my first post that I was inspired by the c2d guide.
May 26, 2007 5:18:51 PM

Quote:
Am I needing such high vcore because my other voltages are too low? Is my vfsb, nForce spp voltages too low? Is it a bad idea to have HT nForce SPP<->MCP: on AUTO?

I suggest you read this: Core 2 Duo Overclocking Guide


I already mentioned in my first post that I was inspired by the c2d guide.

My bad. I missed the part where you read the guide. I assume "inspired" means you've read it thoroughly and configured all the bios setting as recommended. Try running Memtest86 to rule out the RAM causing errors. Also, your temps are pretty high, but probably not what's causing errors. I assume you're using stock cooling. If the RAM is good and you've followed the C2D guide exactly, then maybe you just got unlucky and got a bum overclocking chip. GL
May 28, 2007 8:27:38 AM

I keep my E6600 at 3.3 GHz (9x multiplier) at 1.45V (1.42 in windows)...I succesfully ran Orthos for 17 hours. Temps are 55-56 degrees full load. But if I set VCore to anything less than 1.45V it crashes after one hout runnin' Orthos...
a b à CPUs
a b K Overclocking
May 28, 2007 8:52:39 AM

Um set your memory to 2.1V see if that helps.
May 28, 2007 10:20:56 AM

http://download.intel.com/design/processor/designex/315...

See page 31

Quote:
An increase in processor operating frequency not only increases system performance, but also increases the processor power dissipation. The relationship between frequency and power is generalized in the following equation: P = CV^2F (where P = power, C = capacitance, V = voltage, F = frequency). From this equation, it is evident that power increases linearly with frequency and with the square of voltage.


Temp and frequency have a linear relationship; temp and voltage have an exponential relationship... conclusion: minimize voltage.

Same thing holds true for speed in a car: energy = 0.5mv^2 where m is mass and v is velocity. This is the basis of the old expression, "speed kills."
May 28, 2007 11:33:23 AM

I can only speak from my own experience.

I am stable at 3.2 with 1.3125. I've played around with 3.6 but at 1.45 I still was not stable. I've not really played with speeds in between yet.


Here are some numbers for reference at Extreme Overclockers.
May 28, 2007 11:44:17 AM

2.0v :lol: 
a c 172 à CPUs
a c 197 K Overclocking
May 28, 2007 12:45:56 PM

There are a couple of 680i specific OC guides out there. Google something like "680i overclock guide".

Mayouuu is right. You should be able to reach 3.0 GHz on 1.25 volts or less.

I can run at 3.4 GHz on 1.45 volts.

Zalmans sure are neat looking, but there are other HSF's that work as well for less money or better for the same price. If I could find one cheap - like off eBay, I'd buy one for my knick-knack shelf. :D 
May 28, 2007 5:00:41 PM

http://www.evga.com/community/messageboard/topic.asp?TO...

I am going to try this guide next. He unorthodoxingly recommends All Voltages set to Auto, Ram: Linked + Synced. Also he mentions disabling Linkboost/Smart Fan, which I am unsure if I have done that.

Using those techniques, Should I try 299fsb first, and see what auto-voltages/temps that gives me, or go straight to 333fsb and compare apples to apples?

What do you guys think about his recommendations?
May 28, 2007 10:42:02 PM



I got the overclock a little higher today so im pleased with that. While running Orthos, the CPU temp reached a maximum 51, but the airconditioner in my room was running :lol: . Im expecting a worst case scenario of ~53 when the AC isnt running. Now the C2D sticky temperature guide, says that cpu temp shouldnt exceed 55 during orthos testing, does this means I still have a tiny bit of headroom for uping the vcore even a little further, for 3150-3300mhz? Room for vcore 1.46875 <---> 1.475

dont forget that my cpu is a super new batch of e6600 and they are apparantly more power hungry then the older batches when overclocking.

So can 1.46875 <---> 1.475 damage my cpu, or is the only cause for damage from the heat? Cause the heat levels right now, lead me to believe that I have a bit of headroom left.
a b à CPUs
a b K Overclocking
May 29, 2007 5:47:19 AM

SET YOUR RAM TO 2.1V!!!

It is rated to run at that voltage so set it up there. It will help with stability when OCing (although it shouldnt be necessary for stability atm as the RAM is at 667mhz)
June 3, 2007 5:07:35 AM

Okay, different reply but I wanted to warn you ahead of time so you don't think you screwed something up. The 680i mobos appear to have a major flaw and only now are popping up. EVGA is one of a few manufacturers that have their own forums and I suggest you take a look at them. I have no idea when you built this rig but the issue is people are starting to see their system (RAM specifically) all of a sudden dying. Not all are OCing their systems but most are using the newer RAM (8000 and 8500) and upping their voltages. The spec is still 1.8volts and anything over this is playing russian roulette. To make this issue worse is not everyone with failing ram has voltages higher than 1.9 volts. Some have even monitored their temps on RAM and nada.

If your system is working fine now and has been for a while, I wouldn't tempt fate. There is a growing number of users on ASUS and other vendors about this issue and no one has an answer yet. Just food for thought and good luck!!
June 3, 2007 7:10:48 PM

Try 1.42. I wouldnt honestly go over 1.45ish.
June 3, 2007 7:16:50 PM

1.4625v for stable 3100mhz, and 1.4875v for stable 3200mhz :cry: . HUGE jump in vcore for only 100mhz? whats going on?

Are the current e6700s this bad also?
June 3, 2007 7:36:05 PM

Quote:
1.4625v for stable 3100mhz, and 1.4875v for stable 3200mhz :cry: . HUGE jump in vcore for only 100mhz? whats going on?

Are the current e6700s this bad also?


Eeep. I have no idea. 1.48 for only 3200 is not that good.

Mine is 1.45 and runs very stable @ 3.4 I actually ran it for 12 hours with 1.45 @ 3.5 but then had some weirdness... is the best way to describe it actually.

All CPU's OC very differently. Can you RMA your CPU and get another one? My friend had to exchange his E6600 twice before he could get it to run at 3.4. He is also using 1.45. (Or maybe slightly lower?)
Thankfully mine OC'd well right out of the box.
!