Intel Processors Overclock Database

[CrashG]

EDIT: Sorry I forgot some information before. It won't let me edit my last post.

Intel Core 2 Duo E4500 @ 2.9 GHz

D Stepping

1.38 V-Core (Set to Auto in Bios because it isn't stable for some reason if it isn't)

Stock Intel Box Cooler (Air)

Gigabyte P35-DS3L Rev. 2.0 With F7 Bios

Windows Vista Business x64

Kingston KVR667D2K2/2GR (2GB of RAM) and Kingston KVR667D2N5K2/2G (Other 2GB of RAM)

Both 2GB Kits of RAM are 667MHz (PC2 5300)

The stock latencies are 5-5-5-15, but I have them running at 5-4-4-15 at 792MHz

Stable with prime95 for 12 hours. The temps hover around 60 degrees celsius when running prime 95 after a couple of hours, so I think I'm ok temperature-wise. I don't have screenshots for the prime95 because it was done a while back and didn't think to take screenshots when I did it.

That'll work. :)

I've heard/read that anything 20-30c under tjunction max is safe, of course cooler is always better. I believe that the max temps should be the same for all conroes (95c). I'm sure that Gwai Lo will add you to the list.

Thanks for contributing to the list. (Y)

I see we are the only ones "crazy" enough to run stock coolers. :laugh:

[Impact]

Stock coolers actually seem to be fine for me lol. They're pretty quiet and keep it within safe temps, so why buy some other cooler? lol

I'm currently in the process of testing with a lower v-core to see if it works.

[CrashG]

Stock coolers actually seem to be fine for me lol. They're pretty quiet and keep it within safe temps, so why buy some other cooler? lol

I'm currently in the process of testing with a lower v-core to see if it works.

My thinking exactly. That's how I got my temps down to 57-58c after 11+ hours of Orthos. It kept bouncing from one to the other every few seconds. Which to some are high, but still well in the "safe zone".

[gwai lo]

Well I'll add it, but I just wanted to comment that it may not be the best demonstration of your setup. You're having the board auto overvolt to the overclocking and they *always* overvolt too much, software can't predict stability. Anyway, updated.

[Impact]

I actually updated the bios to the F8F beta bios now, so that can be updated. I was actually kinda scared because the first bios flash didn't flash correctly so my motherboard basically didn't have a bios on it and when I turned my PC on, it said "searching hard disk for bios." I was really scared! I inserted the CD that came with the motherboard into the CD drive just to check if it would work and it reloaded the bios (thank God!). I then flashed it to the latest successfully (F8F) and I also set the v-core to 1.4 volts (instead of auto). This bios doesn't seem to have as horrible v-droop as the F7 because with the F7, I had it set to 1.4125 volts and CPU-Z was reporting 1.344 volts idle and less if under load (it would drop to 1.311 volts and crash, which is why I had it set to auto). Now, with this bios I have the v-core set at 1.4 volts in the bios and CPU-Z is reporting 1.36 volts idle and 1.344 volts under load. I am stress testing with orthos right now to see if its stable, so I'll update you on how it's doing. Also, is CPU-Z very reliable for reporting the v-core? The reason I ask is because in the bios it says that it's really 1.38 volts when I look at the monitoring, but CPU-Z says it's 1.36 volts idle.

[+shift. MVC]

The Wolfdale stock cooler seems to be better than the ones provided before on the Conroe and before.

[gwai lo]

I haven't heard of issues with vcore reporting really, but I could just be completely in the dark about the issue.

[Impact]

Cool. Well, it's been stable for 45 minutes so far, but I'm gonna leave it running overnight just to be safe.

[CrashG]

My bios says Vcore1.212, CPUz says 1.192. Go figure. I'm also testing my machine right now @1.192, going fine so far (a little over 1.5 hours). If all goes well overnight I'll post the results.

[Impact]

How can you guys all run you Vcore at like 1.2 volts? What's the standard Vcore for those processors, because the motherboard detected mine as 1.325 volts and that's the minimum ammount of volts I can run it stably at with stock speeds even.

[gwai lo]

The newer chips have lower VIDs and most boards will let you undervolt. Overclocking and overvolting is done because your processor is underbinned for its speed...and it works both ways. To run at stock, some times people drop the vcore.

[+shift. MVC]

Motherboard and Processor lists have been updated as of 10:11PM June 19, 2008.

CHANGES: Added everyone to motherboard's page, added Obi Wong and Citrusleak to Processor's list. Fixed some formatting issues.

NOTES: If possible please only take a screenshot of the CPU-Z window that you want to post instead of a shot of the entire desktop. Makes it easier for gwai lo and I to update.

Refer to CrashGordon's post if there are any questions as to how your submission should be formatted. :)

Edited June 20, 2008 by -SHiFT-

[+shift. MVC]

The following is how a submission into the database should be made.

It would be ideal if a 8hr+ ORTHOS or Prime95 screenshot was provided. But not mandatory for your submission to be entered into the database.

Processor Core2Duo E6550 @ 2.8GHz

Stepping B

Revision G0

Vcore 1.232v

Method of cooling and make and model of cooler Air, Stock

Make and model of motherboard with BIOS version Asus P5K-e 1013

OS version Vista Ultimate 32bit w/SP1

RAM brand, model number, frequency (actual not effective), and latencies G.Skill, F2-6400CL4-1GBHK, 400MHz, 4-4-3-5 2T @ 2.1v

It is perfectly stable running Orthos for 8 hours, I've had it at these speeds for around 2 months and just didn't save a screenshot of it at the time because I didn't ever think I'd need one. :p It's only a minor OC, and I haven't tried to push it any farther.

[+shift. MVC]

Another update, fixed Obi Wong's database entry. I had his cooling as "Stock" when it was supposed to be either Air or Water.

[CrashG]

Ok, ran Orthos all night testing 1.192 Vcore. Stable, so at this OC it looks like that's as low as I can go. Temps look good at 37/57c (min/max). If someone can update my Vcore to the new value. Nothing else has changed as far as settings go, just the voltage.

Also on a side note, the easy way to get all three CPUz screens in one shot is to just open CPUz three times and set it on a different tab. :)

[+shift. MVC]

Updated as of June 20th, 2008 10:17AM PST

CHANGES: Updated CrashGordon's Vcore value.

[utdarkviper]

Processor Q6600

Stepping B3

Vcore 1.2625

Method of cooling and make and model of cooler air - ZEROtherm Nirvana NV120

Make and model of motherboard with BIOS version ASUS P5K-E Wifi/AP BIOS 1012

OS version Vista Ultimate x64

RAM brand, model number, frequency (actual not effective), and latencies

G.Skill DDR2-800 F2-6400CL5-2GBPQ 334MHz 5-5-5-15

Note: have not tested stability with Orthos, but have played CoD4 for ~8hrs just fine :p

Edited June 20, 2008 by utdarkviper

[+shift. MVC]

Latest version as of June 20th, 2008 12:42PM

Updated with your info. :)

CHANGES: Modified motherboard database such that it is in descending order in terms of FSB. Will probably make it easier to make comparisons between processors.

Edited June 20, 2008 by -SHiFT-

[marc2003]

can we have some clarification on the vcore entry? i assumed you'd want the value it's set to in the bios - while others are posting what cpu-z is showing in windows. and to confuse things even further, some people are posting their cpu-z value while running prime.......these values can vary wildly with vdroop.

for example with my entry i submitted 1.4625v - that's what i have set in the bios. when idling in windows cpu-z shows 1.40v. and you can see from my prime screenshot (on page 1), it's showing 1.36v under load. obviously in a database, saying my cpu can do 3.4ghz with 1.36v looks better than 1.4625. can the OP be updated with the vcore value (bios, windows idle or windows load) that everybody should use.

[+shift. MVC]

I will ask gwai lo when he gets on. so we can determine a set of criteria for Vcore.

[CrashG]

can we have some clarification on the vcore entry? i assumed you'd want the value it's set to in the bios - while others are posting what cpu-z is showing in windows. and to confuse things even further, some people are posting their cpu-z value while running prime.......these values can vary wildly with vdroop.

for example with my entry i submitted 1.4625v - that's what i have set in the bios. when idling in windows cpu-z shows 1.40v. and you can see from my prime screenshot (on page 1), it's showing 1.36v under load. obviously in a database, saying my cpu can do 3.4ghz with 1.36v looks better than 1.4625. can the OP be updated with the vcore value (bios, windows idle or windows load) that everybody should use.

I also thought about that too. My BIOS setting is 1.2125, but CPU-z reports it as 1.192 although it does not drop while running Orthos.

[utdarkviper]

The value I posted is what is set in my BIOS, which I assumed was the standard.

[Impact]

I think CPU-Z while not running orthos should be the standard, because I notice that even my bios says that my v-core isn't running as high as I have it set in the bios settings. It probably drops further when windows boots just like it drops when maxed out running prime 95 or orthos.

[+shift. MVC]

Usually, Vcore is reported as the value in CPU-Z while the computer is at idle, as most motherboards have vdroop which would lower the voltage at load.

Again I will discuss this with gwai lo and adjust as neccessary. :)

[gwai lo]

can we have some clarification on the vcore entry? i assumed you'd want the value it's set to in the bios - while others are posting what cpu-z is showing in windows. and to confuse things even further, some people are posting their cpu-z value while running prime.......these values can vary wildly with vdroop.

for example with my entry i submitted 1.4625v - that's what i have set in the bios. when idling in windows cpu-z shows 1.40v. and you can see from my prime screenshot (on page 1), it's showing 1.36v under load. obviously in a database, saying my cpu can do 3.4ghz with 1.36v looks better than 1.4625. can the OP be updated with the vcore value (bios, windows idle or windows load) that everybody should use.

Sorry, I guess I should've clarified...I kind of assumed everyone was doing the BIOS vcore because that's what I've been used to on other forums. So here it is and I'll update the first post:

Post the BIOS vcore, the sole reason being vdroop.