HOWTO: Minimizing Vcores and Operating Temps-must read

This is the place to discuss the latest computer hardware issues and technology. Please keep the discussion ON TOPIC!
Post Reply
graysky
Legit Aficionado
Legit Aficionado
Posts: 83
Joined: Wed Nov 09, 2005 3:03 pm

HOWTO: Minimizing Vcores and Operating Temps-must read

Post by graysky » Sun May 04, 2008 5:05 pm

Well, guys I wrote up this procedure I used to minimize my vcores on my new x3360/P35-based system, and I thought I'd share it with folks. It's a systematic method anyone can use to arrive at a minimized set of vcores for a given multiplier and FSB value. The examples I present in this post are using my X3360/P35-based system. The data aren’t made-up or fictitious for the examples; they are the real data I used to arrive at the stable system.

Also, anyone can use this method - even if not overclocking their system - to lower their respective CPU and MB temps. I should say that I also incorporated this into my C2D/C2Q Overclocking Guide as well, but I felt it could also be useful to folks as a stand-alone post/guide.

The goal of stress testing is two fold:
1) To arrive at a stress test stable system (>24 hours with no prime95 errors).
2) To minimize your vcores and thus minimize heat product both on your CPU but also on your NB/SB and other MB components.

Prime95 will run and every now and then it will check the values it’s calculating using your processor to its internal standards since its torture testing using known values. Assuming you enable error checking, you’ll be notified if your values differ indicating an instability. This is why it is IMPERATIVE that you enable error checking within Prime95; again, if you don’t enable it, you WILL NOT be notified of errors!

Do so simply by going to the “Advanced” menu and enabling “Round off Checking.” If the system isn’t stable, it will report an error and stop stressing the core that gave the error.

Image

Now that you picked your operating condition (i.e. 9x333 or 8.5x400, etc.) let’s stabilize the system through stressing it with prime95. Just so you get an idea what to look for, Coretemp as well as Prime95 (double-check that you enabled round off error checking) and run the Torture Test>Large FFTs. You’ll wanna keep an eye on your system temps to make sure they don’t exceed the redline so the chip doesn’t get throttled (assuming you have thermal management enabled in your BIOS). All your cores should get stressed equally (look in the task manager to verify):

Image

For your reference, here’s what an error from within prime95 looks like:

Image

When/if you get an error (and you will), you’ll need to either back off on the operating conditions (FSB or multiplier) or add some voltage to your vcores. Therein lies the challenge. Since you have four different vcores to select from, how do you know which one or which ones to adjust?

It’s now time to minimize your vcore settings. Reboot and go into the BIOS’ section where you can control your CPU and MB voltages. Remember, different motherboard will call these variables different terms. The pic below is right out of my BIOS so you can see what DFI calls them, and what they mean:

CPU VID Control – The processor vcore, I’m not sure why DFI calls it “CPU VID Control” but whatever. From here on out, I’m going to call it Vcc since technically, the term VID is an entirely different concept (see this document, page 14 for more if you have an interest).
DRAM – The memory vcore.
SBCore – Southbridge vcore (might be called ICH in your board).
NBCore – Northbridge vcore (might be called MCH in your board).
VTT – Reference voltage (might be called FSB Termination voltage in your board). It’s used to terminate data lines between the MCH and CPU.

Image

Some motherboards give the option for GLT reference controls. If you enable this you’re adding three additional variables to the mix and making your life more complicated. Unless you’re an extreme overclocker wanting to squeeze every single MHz out of your system, my advice is not to enable the GLT options. I’d also caution you not to enable this option since there is tons of misinformation out there about these undocumented features.

If you must, here a few links that might help you understand how it works and give you some starting points, but I won’t be using them in this guide:

Adjusting [Advanced] Gunning Transceiver Logic (A/GTL+) Voltage Levels for Increased Front Side Bus (FSB) Signaling Margins and Overclocking.

DFI UT P35-T2R: Tweakers Rejoice!

Good thread (kinda long) but good info.

There are several approaches you can use to arrive at a stable, minimized set of vcores. I recommend that you start with lower vcore values and work your way up. Lower values will fail much faster than higher values thus making the process a bit quicker for you.

To start with, select a set of vcores that are kinda low and see if you can POST. How do you know where to start? Use trial and error at this point unless you know someone else’s settings to use as starting points. When in doubt, I’d recommend that you start near the bottom of the scale. Here are some rough guidelines for setting your VTT:

1.2-1.3V - for a FSB of ~400 MHz.
1.4-1.5V – for a FSB of ~420-440 MHz (exceed 1.4V at your own risk with a 45nm chip)!
1.6V – for a FSB of ~440-475 MHz - use at your own risk with a 45nm chip!

You should be aware that newer 45nm fab chips are MUCH less tolerant toward high VTT than their 65nm predecessors. Anantech published their experience frying a QX9650 with high VTT’s as an example.

Vcc – Initially, set within 200-400 mV of where the auto setting used (remember that you need a little more in the BIOS compared to what CPU-Z told you). Remember to consult Intel’s processor finder to know where the upper-end of safety is for your processor (I believe the figures there correspond to the values CPU-Z is displaying, not what you set in the BIOS.).

DRAM – What ever the RAM manufacture recommends is a good starting point. Unless you’re really overdriving them, they shouldn’t need more.

SBCore – I’ve always used the lowest setting, but I typically don’t push my systems that hard (20-25 %). You’re on your own here.

NBCore – Start off low, 1.33 or 1.37 and see if you need more. Also, a little bit can go a long way. My system is unstable @ 1.330V here but stable @ 1.370V which is a difference of only 40 mV (0.04V).

Here are the levels my Q6600 @ 9x333 uses to run stable:

Code: Select all

Memory Voltage=2.100V
CPU VCore=1.2625V
FSB Termination=1.200V
NB Vcore=1.25V
SB Vcore=1.50V
ICH Chipset=1.057V
Here are the levels my X3360 @ 8.5x400 uses to run stable:

Code: Select all

Vcc=1.12500V
SB 1.05V=1.070V
NB Core=1.370V
SB Core/CPU PLL=1.550V
CPU VTT=1.310V
I show those only to give you an idea, not all hardware is the same, and really, those values are personal to my chip, RAM (and RAM settings), MB, etc.!

Once you select a baseline set, that will complete a POST, you’ll want to start a more vigorous evaluation by changing the MB vcores one-at-a-time moving forward. If you change too many variables at once, you’ll never be able to arrive at the stable settings. Confused? Don’t be, just read on and after you see the examples, I think the process will seem clearer to you.

The basic process is to try different Vcc values keeping the other vcores constant. Run p95 at a given Vcc and record what happens after an arbitrary time point (10 to 15 min is good to start with). If Vcc level is stable for 15 min of p95, reboot and lower it a little and repeat. The goal is to find the minimum level that gives errors, then increase it until it’s stable, then extend that time out to say 2-4 h. If it’s still stable, further extend it to 10-14 h. You can probably call it “stable” if you can run p95 for 24 h. If a setting fails after 4 h, increase it one notch or so and repeat until it’s stable out to 24 h. You can then come back knowing this Vcc and try to lower one of the other vcores repeating the process. Yes, it’s time consuming and yes, it’s tedious, and yes, that’s a ****load of rebooting, but it works.

The key to this process is keeping a detailed record to help you achieve a stable system and troubleshoot which vcore to change – p95 errors are NOT always the fault of a low Vcc! Without these data, you’ll have a tough time. So what do you keep track of here?

1) The MB vcores you’re using
2) The Vcc values you’re testing
3) Which core failed (prime95 tells you) and how long it took to fail
4) Any observations or comments you want to record for yourself

Here is an example minimizing vcores using my X3360/P35-based system. The data presented aren’t fabricated to help illustrate the method; rather, they are the real data I used to arrive at the stable system.

Hardware specs for your reference:
X3360 running @ 8.5x400, DFI LT P35-T2R (BIOS 3/17/2008), Ultra-120 Extreme, Corsair TWIN2X4096-8500C5DF 2x2 GB @5-5-5-15 running @ 960 MHz (5:6), 620HX power supply.
Before we dig into the examples, know that to really really do this right, you’d need to do several runs at the various levels; doing it just once as I am is the quick ‘n dirty approach and can cause you to draw an incorrect conclusion or two as you will see.

On to it: in my first try, I set up my MB vcores and began testing Vcc starting low (I chose 1.12500V somewhat arbitrarily).

Keeping the motherboard vcores constant, I varied the Vcc starting out low and working up high. You may or may not get a stable system on your first set of iterations (probably not actually). If you do, you’ll probably want to repeat keeping your stable Vcc but optimizing (minimizing) for one of the other vcores such as NB or VTT, etc.

Code: Select all

Overclocking log, Iteration Set 1
Comments: Initial try

DRAM	2.100V
SBCore	1.55V
NBCore	1.37V
VTT	1.200V

Vcc/Prime95 success or failure
1.12500V	Failed on core 3 ~ 5 min
1.13750V	Failed on core 0 ~ 28 min
1.15000V	Failed on core 2 ~1 h 18 min
1.16250V	Failed on core 1 ~ 4 h 4 min
Looking at the data, we see there that multiple cores have failed as I increased the Vcc. That’s suggestive of one of the other voltages lacking and thus needing to be increased. There are two likely causes for my instability: NBCore and VTT. In my next Iteration set (below), I chose to raise the NBCore several notches keeping the rest of the MB vcores constant.

For discussion’s sake, let’s say the same core failed repeatedly. This scenario is likely caused by a low Vcc (although it doesn’t have to be). For you quad core users, cores 0/1 and cores 2/3 should be treated the same, so if you get some core 0 and core 1 failures, treat them like a single core failure as you consider this analysis.

So, I increased the NBCore a few notches and tried a few higher Vcc settings just to see if it was enough:

Code: Select all

Overclocking log, Iteration Set 2
Comments: Added some NBCore

DRAM	2.100V
SBCore	1.55V
[b]NBCore	1.41V[/b]
VTT	1.200V

Vcc/Prime95 success or failure
1.16250V	Failed on core 2 ~2 min
1.17500V 	Failed on core 1 ~3 min
Again, I got two quick failures across the entire chip. Ideally, you might want to collect more data points, but I took a hunch that 1.45V should be plenty for 8.5x400, and next added some VTT keeping the newer, higher NBCore constant – remember to only change one of them per iteration set!

Code: Select all

Overclocking log, Iteration Set 3
Comments: Added some VTT and kept the higher NBCore

DRAM	2.100V
SBCore	1.55V
NBCore	1.41V
[b]VTT	1.310V[/b]

Vcc/Prime95 success or failure
1.17500V	STABLE 15 min
1.16250V	STABLE 15 min
1.15000V	STABLE 15 min 
Now, with the higher VTT, I didn’t get a single failure for at least 15 min at the three Vcc values I ran. I concluded that the VTT gave me the stability. To test this hypothesis, I kept the higher VTT, but lowered the NBCore back to 1.37 and repeated in the 4th iteration:

Code: Select all

Overclocking log, Iteration Set 4
Comments: Kept the VTT, lowered the NBCore

DRAM	2.100V
SBCore	1.55V
[b]NBCore	1.37V[/b]
VTT	1.310V

Vcc/Prime95 success or failure
1.15000V	STABLE 2 h
1.13750V	STABLE 30 min
1.12500V	STABLE 1 h
1.07500V	crashed p95 (n=2)
1.09375V	crashed p95 (n=1)
1.10625V	BSoD after 1+h
1.11875V	STABLE 11 h
1.11250V	Failed on core 0 ~ 1 h 8 min
Now I got some stable runs. After evaluating the data, I was able to nail down both my NB and VTT in only 3 iteration sets, arriving at what I thought was the stable Vcc in the 4th (I was later wrong).

It’s a little easier to visualize if you sort the Vcc from low to high. If you keep your log in a spreadsheet, you can easily sort them, here are the same data sorted by Vcc:

Code: Select all

Overclocking log, Iteration Set 4
Comments: Kept the VTT, lowered the NBCore

DRAM	2.100V
SBCore	1.55V
[b]NBCore	1.37V[/b]
VTT	1.310V

Vcc/Prime95 success or failure
1.07500V	crashed p95-program exited (n=2)
1.09375V	crashed p95-program exited (n=1)
1.10625V	BSoD after 1 h
1.11250V	Failed on core 0 ~ 1 h 8 min
1.11875V	STABLE 11 h
1.12500V	STABLE 1 h
1.13750V	STABLE 30 min
1.15000V	STABLE 2 h
It would seem as though 1.11875V was the winner. I could have stopped right here and repeated extending the time out to 24+ h with these settings, but I elected to further optimize and targeted the VTT since I thought I could do better having jumped from 1.20 to 1.31 and skipping 5 sub levels in the process. This time through, I held the Vcc constant and varied, VTT:

Code: Select all

Overclocking log, Iteration Set 5
Comments: 1.11875V seemed stable, minimizing VTT

DRAM	2.100V
SBCore	1.55V
NBCore	1.37V
[b]Vcc	1.11875V[/b]

VTT/Prime95 success or failure
1.250V	Failed on core 0 ~ 2 h
1.260V	Failed on core 2 ~ 1 h 20 min
1.280V	Failed on core 0 ~ 18 h 22 min
1.310V	Failed on core 1 ~ 1 h 20 min
This one is a little puzzling since the 3rd run (VTT=1.280V) lasted for over 18 h, yet the 4th run with a higher VTT died in under 1-1/2 h. My thinking was that VTT wasn’t the problem, and that I had been mislead on the Vcc. I was also getting a little anxious for this to be finished and I broke my own cardinal rule for the next iteration set by upping two variables at once: Vcc to 1.12500V and VTT to 1.310V.

Code: Select all

Overclocking log, Iteration Set 6
Comments: 1.11875V seemed flaky, so upped the Vcc and kept the higher VTT.

DRAM	2.100V
SBCore	1.55V
NBCore	1.37V
[b]VTT	1.310V[/b]

Vcc/Prime95 success or failure
[b]1.125000V[/b]	Stable 21 h 34 min
Image

Okay! So maybe it was the Vcc after all since it ran for over 21-1/2 h before I stopped it. You could argue that there’s no difference between 18-1/2 h and 21-1/2 h and you would have a valid argument. This underscores the need to collect multiple data point per level as I mentioned in the beginning of this section (I told you it was quick ‘n dirty)!

Finally, I set out to essentially repeat my Iteration Set 5 minimizing the VTT with the slightly higher Vcc.

Code: Select all

Overclocking log, Iteration Set 7
Comments: 1.12500V seemed stable, minimizing VTT

DRAM	2.100V
SBCore	1.55V
NBCore	1.37V
Vcc	1.12500V

VTT/Prime95 success or failure
1.250V	Failed on core 0 ~ 1 h 3 min
1.280V	Failed on core 1 ~ 1 h 0 min
1.310V	STABLE 34 h 41 min
Apparently VTT needs to be 1.310V on this system. In any case, those examples should serve to illustrate the method you need to use to attack the task.

To summarize, using a stepwise approach and documenting your runs, you should be able to arrive at a stable system (assuming your hardware can operate at the level you choice). It probably goes without saying that you will need to repeat this process if change your operating conditions (multiplier and FSB).
http://encoding.n3.net <--- for all your DVD and audio CD backup needs!

Image

User avatar
stev
Legit Extremist
Legit Extremist
Posts: 1507
Joined: Thu Feb 16, 2006 7:29 am
Location: Nashville, TN suburbs
Contact:

Re: HOWTO: Minimizing Vcores and Operating Temps-must read

Post by stev » Sun May 04, 2008 5:55 pm

Thanks! A good read indeed. :)
AMD X2 TK-57 1.90Ghz | F700 Quanta | PC2-5300 DDR2 2Gb | GeForce 7000M | DVDRAM GSA-T40N | HP LaserJet 1018
My Stats http://folding.extremeoverclocking.com/ ... =&u=303718
Image
http://www.eff.org - Electronic Frontier Foundation - working to protect your digital rights

User avatar
martini161
Mr Awesome
Mr Awesome
Posts: 3185
Joined: Sat Sep 08, 2007 8:27 pm
Location: Cherry Hill, New Jersey
Contact:

Re: HOWTO: Minimizing Vcores and Operating Temps-must read

Post by martini161 » Sun May 04, 2008 5:58 pm

nice work. i can see an info mercial with billy mays selling your overclocking guide, but with as one of those "but wait, THERES MORE!!!!!!11" kinda things :rolleyes:

graysky
Legit Aficionado
Legit Aficionado
Posts: 83
Joined: Wed Nov 09, 2005 3:03 pm

Re: HOWTO: Minimizing Vcores and Operating Temps-must read

Post by graysky » Sun May 04, 2008 6:02 pm

ahahah! enjoy!
http://encoding.n3.net <--- for all your DVD and audio CD backup needs!

Image

User avatar
DaIceMan
Legit Extremist
Legit Extremist
Posts: 1599
Joined: Tue Jul 18, 2006 10:31 pm
Location: Springfield-ish, Missouri
Contact:

Re: HOWTO: Minimizing Vcores and Operating Temps-must read

Post by DaIceMan » Sun May 04, 2008 9:43 pm

in for later... I'm WAAAAY too ADD right now to read that. If it's anything like the OC Guide, I'm sure I'll be reading it over and over.

Thanks!!
Gamer - Thermaltake Element S | PC Power & Cooling Silencer 750 Black | Gigabyte GA-EP45-DS3L | Intel E8400 | Arctic Cooling Freezer 7 Pro | 4GB OCZ Reaper Ram | XFX 8800GTX | Creative X-Fi XtremeGamer | Seagate 7200.10 320GB

HTPC / Folder - Palit 9600GT 1GB Sonic | AMD Phenom 9600 | Corsair DHX 4GB | ECS GF8200A | OCZ StealthXStream 500
Thanks to Palit, AMD, Corsair and ECS for sponsoring the 2008 Folding Give-away!

Image

JustSomeone
Legit User
Legit User
Posts: 14
Joined: Wed Jan 30, 2008 9:31 am

Re: HOWTO: Minimizing Vcores and Operating Temps-must read

Post by JustSomeone » Mon May 05, 2008 4:12 pm

=D> Nice job. I plan on using this info this weekend when I have a little more time to do all the rebooting. :P

User avatar
bobletman
Legit Aficionado
Legit Aficionado
Posts: 98
Joined: Mon Nov 12, 2007 9:40 pm

Re: HOWTO: Minimizing Vcores and Operating Temps-must read

Post by bobletman » Mon May 05, 2008 4:15 pm

wow thanks this will definately help I cant wait to use this info, thanks again.
Q6600 Core 2 quad @ 3.0Ghz
2gb of patriot ram reduced latency.
500GB 7200 rpm Seagate (baracuda)
BFG nvidia 8800 GTS 512 MB G92 core
Zalman CNPS9700 LED CPU fan
Ultra X-Blaster computer case
P5K-E Wifi edition MOBO
G15 keyboard and G7 mouse
22 inch widescreen samsung
Z5300e speaker system
3Dmark06 score 15K

bandieramonte
Legit Fanatic
Legit Fanatic
Posts: 200
Joined: Sat Dec 08, 2007 4:30 pm
Location: Caracas, Venezuela

Re: HOWTO: Minimizing Vcores and Operating Temps-must read

Post by bandieramonte » Wed May 07, 2008 8:45 am

Incredible, I will overclock my Q6600 very soon and this guide will really prove useful for me, even though it seems it will take a huge amount of time rebooting and testing prime95 to accomplish this objective.

graysky
Legit Aficionado
Legit Aficionado
Posts: 83
Joined: Wed Nov 09, 2005 3:03 pm

Re: HOWTO: Minimizing Vcores and Operating Temps-must read

Post by graysky » Wed May 07, 2008 11:38 am

Thanks for the kind words, all. Be sure to report your success in the thread :)

@bandieramonte - yeah, it does take some time and reboots, but I honestly don't see that you have another option... who wants to run a PC that uses power and generates heat needlessly afterall? You might find the info in my overclocking guide useful as well. This minimizing vcore guide is containing within the larger guide. I wrote it (I tried to write it) at a newbie level to attract more new folks. Enjoy!
http://encoding.n3.net <--- for all your DVD and audio CD backup needs!

Image

bandieramonte
Legit Fanatic
Legit Fanatic
Posts: 200
Joined: Sat Dec 08, 2007 4:30 pm
Location: Caracas, Venezuela

Re: HOWTO: Minimizing Vcores and Operating Temps-must read

Post by bandieramonte » Wed May 07, 2008 2:36 pm

You are right, there is no other way to have the 4 voltages at the minimum possible stable level without having to dedicate many days of testing. At the end, this job will really provide helpful for one's system because it will ensure operation at lower temps which means more life span for a system.
This guide will come in handy for me when I overclock my Q6600 and try to lower the voltages of my NB and SB, because the Nforce 680 is a hot motherboard! and I want to try to lower its temps.

Thanks for the info.

Post Reply