February 19, 2009, by kike_1974
can get a micro eat less by reducing their frequency and voltage, in fact, consumption is proportional to the square of frequency and operating voltage. You can use different programs (software) to modify the frequency and voltage values \u200b\u200bduring operation of the micro. In this article we will see some of these programs (RMClock, CrystalCPUID) and how they work.
Introduction:
Note: This guide was originally published on 6/2/2008 Noticias3D forum, namely here.
This guide is designed to have a cooler, quieter PC, and incidentally to consume something less. The method of control of voltages and frequencies for software that we will see is exactly the same as that used C & Q and EIST, but in this guide we'll work out a lot more advantage of the opportunities offered by the micro that these two technologies from AMD and INTEL.
One of the key when seeking a quiet PC is to find components with the lowest possible to generate as little heat as possible and easier with fewer cooling fans or fans with fewer turns. Also associated with this lower consumption we associate an energy bill a little smaller.
One component where we can get reduce the heat generated is the microprocessor. The first question is it worth it?. First some accounts:
A kW / h currently costs € 0.092834 (BOE.29-12-07), and that price should apply the electricity duty and VAT. Ie, total taxes are (0.092834 * 1.05113) * 4.864% and VAT, ie the total cost is ((0.092834 * 1.05113) * 1.04864) * 1.16 = 0.1187, or rounding a 12 cents per kW / h . It is indeed impressive (or a shame ...) we pay almost 30% tax on electricity ... but hey, that's another topic ...
For example, a computer to download 24 / 7 to consume about 100W each year consumes about 0.1 * 24 * 365 * 12 = 105 €. If undervolting 20W conseguiéramos down, would be 0.08 * 24 * 365 * 12 = 84 €. Or what is, for every 10W of us to reduce consumption, we save about 10 € a year. Given that the accounts we have made on the assumption that the computer is always on because it is not much. Then
reason to undervolting is not to save, but above all to have better temperatures in the micro and the PC to have more silent, and here it is worth as differences temperature itself that are important to lower voltages. While the small savings we get are also welcome. Previous concepts
:
is important to talk about pre-theoretical concepts to better understand what we do. In addition there are many misconceptions about what a Vcore, which is a VID, etc. Let's start with these concepts:
FSB (Front Side Bus Frequency): The frequency at which the board works. Most components work with the reference speed (micro, memory, etc.). FIDs
(frequency identifiers) : A code encoding different frequency references with respect to the FSB. Usually they are multipliers (x8, x9, etc.). The frequency at which a processor operates depends on the FSB (reference) and FID (multiplier). The IDF are totally dependent on micro, some buses have more FIDs than others. This issue is well known in the field of overclocking so I do not entertain a lot with him. The FID can be set in the BIOS, but everything that interests us is that you can also change the software (eg Cool & Quiet and EIST FIDs change dynamically).
Vcore: is the voltage the motherboard provides the microprocessor. There are plates for fixing this voltage to different values. Normally there is an option "Auto" and other options specific values. These values \u200b\u200bdepend entirely on the motherboard manufacturer and regulators to include. Overclocking is common to increase this voltage to a fixed value greater than the stock voltage to run the micro at higher speeds. You can also decrease, and is a way to undervolting (through the BIOS, but what we want in this guide is to change the software). Has the disadvantage that once set to a value we lose control of the vids (which we discussed what are the next paragraph).
VID: A vid has nothing to do with the Vcore, confused these two concepts is one of the most common mistakes. A VID is a code that encodes a possible values \u200b\u200bof voltage division. Usually taken as the reference voltage of 3.3 V provides the motherboard to the micro. It can be seen as a VID voltage equivalent to the frequency multipliers. The VID are changed by software (eg Cool & Quiet and EIST modify the vids). Depending on the micro can be more or less VIDS available (as happens with multipliers). The problem is that the VID always use a fixed voltage reference that can not be changed, unlike the FSB multiplier used as a reference and it can be modified. There may be a plate that allows a variable voltage reference, but today I know not. As the VID are referenced to a fixed voltage, it is customary to refer to them by their values \u200b\u200b(1.1V VID, VID of 1.16V, etc.) Unlike IDF that having variable reference is better to use relative values \u200b\u200b(x6 , x7, x8, etc.).
In summary, we can change the frequency and voltage to the microphone works by changing the FSB, and then one of two ways: by changing the Vcore and multiplier in the BIOS, or modifying software and vids FIDs. Normally these two forms are mutually exclusive (although there are exceptions). In this mini-guide we will discuss the second form (by software).
Cool & Quiet and EIST : These two technologies do exactly the same (and very similar to what we do ourselves). Both change dynamically depending on VID and FID micro load. For example, an E6600 uses a stock voltage of 1.225V at 2.4GHz, but if the bus is idle ("on idle") is then automatically change its VID and FID to run at 1.6GHz at 1.1V. Logically to operate these technologies need to be configured in the BIOS the voltages on "Auto" and the multipliers also in "Auto" (although there are exceptions as we have said, some boards allow work C & Q and EIST even setting a voltage on the BIOS, but it is not common and not something standard, so that we can not in general use). Change
vids and software FIDs
Well, we know the previous concepts. What are we going to do? Then we will modify the vids and FIDs as C & Q and EIST but we like to find the combination of undervolting / overvolting underclocking / overclocking that we like, and even use profiles.
Advantages:
- Changing Dynamic frequency and voltage dynamically according to load the micro
- If the microphone does nothing consumes much less
- If the microphone is to stop it also consumes less if we put a voltage lower than stock
- We can even overclock dynamically when needed
- We may use and change profiles manually by software Disadvantages
:
- the vids are limited (as multipliers). For example, my E6600 the lowest possible VID is 1.1V and the largest is 1.325V. Thus OC can not do beyond the 1.325V, or lower consumption when the micro does not do anything below 1.1V. Some buses have greater flexibility (my X2 4800 + brisbane allowed from 0.8V to 1.4V). For Otherwise there is no other problem.
- rely on software, and may not be available for all operating systems. I know no equivalent software for Linux for example (although there may be).
programs that can be used to modify dynamically the vids and FIDs are
- RMClock (free, although a fuller version of payment)
- CrystalCPUID (free)
- notebook hardware control (free aimed at laptops.) Search
optimal values \u200b\u200bof frequencies and voltages
Firstbefore configure anything is to know our micro, and learn about all what are the values \u200b\u200bwe want to use.
This is the heaviest part as happens when we seek stable values \u200b\u200bfor OC. We need to find appropriate values \u200b\u200bfor the FSB (the BIOS) and the VID and FID we want to use. Since the FSB is not going to change software but leave a fixed value in the BIOS (which may be the default if you do not want to do OC), omit it to simplify things a bit.
therefore we have to find stable values \u200b\u200bof VID and FID. Each pair VID / FID will call state. It is advisable to have at least 3 states, one with values \u200b\u200bfor maximum operating frequency, one for low and an intermediate. CrystalCPUID can be configured with 3 states, whereas as many as FIDs RMClock exist.
important thing is that values \u200b\u200bare stable. There are many ways to look, here everyone has their method. One option is to start from the stock values \u200b\u200bof micro and start a program that stressed out the microphone and detects errors such as prime95 or orthos. And then go step by step down the voltage, allowing time between 5 and 10 minutes between each step. It is important to check that has really changed the voltage, we can use for this CPU-z. Before reaching a total value inestableorthos usually give errors. In this case we raised the voltage a step to the previous value and so on until no errors. When no errors should leave a few hours on orthos with these values \u200b\u200bto verify that it is stable (12 to 24 hours).
To change the voltage on these steps we can use CrystalCPUID in the Function menu select the option for Intel SpeedStep Enhanted micros intel or AMD K6/K7/K8 Multiplier for AMD (and leave other options for other micros). We will get a screen like this:
we can go in trying different voltages and multipliers. Capture it all together (CrystalCPUID, orthos and cpu-z):
And it's a matter of keep trying. I specifically use this method when it falls into my hands a new micro:
- Using stock FSB, I look for each multiplier (FID) lower VID that is stable.
- If I get something to OC: look for the FSB to which the maximum multiplier (FID) is stable at maximum voltage (VID). Sounds confusing but it is not so;). This is the best OC we can do for software, since we can not put voltages greater than the maximum VID for software. By the way, not to walk continuously rebooting the PC looking for that land value use the program clockgen for changing the FSB via software. And let the FSB, and in the same way as before for each FID seek the lowest VID that is stable.
- Finally I note the table of FID / VIDS obtained for my micro in a file to have the data for the future.
After all this, our data should be prepared.
Examples:
Example 1)
In my E6600 I did these values:
- The FSB with which the multiplier is stable up to the maximum VID 338 I got, so I set this value in the BIOS.
- The table with FID minimum vids that were stable:
- x6 -> 1.132 V (2 GHz approx.)
- x7 -> 1.132 V (2.4 GHz approx.)
- x8 -> 1.132 V (2, 7 GHz approx.)
- x9 -> 1.340 V (3 GHz approx.)
(1,132 V is the lowest VID of this micro, but we could put lower values).
Example 2):
Another example, my Athlon X2 4800 + brisbane:
- I leave the FSB at 200 by default, since this micro does not do anything about OC
- Table of FID / VIDS (3 FIDs calculated only in this case):
- x5 -> 0.8 V (1GHz)
- x8 -> 0.950 V (1.6 GHz) x12.5
- -> 1.2 V (2.5 GHz)
These voltage values \u200b\u200bare very below the values \u200b\u200bthat came from stock (both for idle with C & Q as the maximum value), the temperature dropped considerably.
Once we have calculated the states that we will use the fun begins to set our programs (CrystalCPUID, RMClock) to make the changes automatically. Change
FID / CrystalCPUID automatically VIDS:
With CrystalCPUID is use "multiplier management."
First, to set up, we File menu and select the option management multiplier setting. We will get a screen like this:
can define 3 states: maximum, middle and minimun.
In all three we can see that we can associate a multiplier and VID (must be left button clicked Enable Voltage capture as to change the vids).
value Time Interval is the time it takes to change the multiplier from the last change. It is a security system in case, for not allowing many sudden changes in voltage in a short space of time. We can leave as the default.
values \u200b\u200b Up and Down threshold are those that indicate what charge must have the microphone to the higher state or returning to the bottom.
For example, I in my E6600 I have it configured to pass the maximum state (9x) only if the load is above 90% and only step to that state (which is 3 GHz to 1.32 V) only when really necessary. Typically, the micro moves between states 6x and 8x, both with the minimum voltage of 1.1 V (and the microphone is quite chilly).
Of other options may be interesting:
Trigger Switch: indicated in cases of multiple cores which are considered as micro load: the maximum of any of them, the media, etc. Exit
mode: indicates if we close the program in which state makes the mic.
Up and Down : sequences indicate which states are allowed breaks
Well, CrystalCPUID should be configured to operate automatically. We can only go to the Function menu and select the "Multiplier Management. We will see in the taskbar icon CrystalCPUID the blue when you are in the state minimum, yellow for medium and red for maximum.
Finally, if we always start the CrystalCPUID we get into windows, then we can create a shortcut and add the / HIDE / CQ and add it in our home folder. Change
FID / VIDS automatically and RMClock profiles:
This other program is a bit more intuitive to use and has the advantage that it can use profiles.
There are two versions of the program, a free and a paying. I have no payment and I will discuss only the free version. The fee includes the ability to create custom profiles, but those coming in the free version we can make do quite a bit.
This free version can use these 4 sides
-
- No Power Saving management
-
- Maximun Performance Performance on Demand
The first is simply to disable the operation of the program. The next two are used to associate each of these profiles a single state (VID / FID), normally the maximum and minimum, but we can configure with which we want. And the last to select all states that want between those who want to automatically switch the program.
Configuration is done in two steps. First you tell the program what the IDF and vids of our micro (which we already calculated before.) Is set on the "profiles":
is possible that the names of the vids do not exactly match the names we came out in CrystalCPUID. This is normal because they are simply labels (remember that the vids are not the same as the Vcore).
Once configured, we configure the profiles. Following the example of my E6600:
In this example I have configured the 3 profiles as follows:
- Power Saving: FID: x6 (micro to 2 GHz)
- Max. Performance: FID: x9 (micro to 3GHz)
- Perf. On Demand: Varies between x6 and x8 (mictro between 2 and 2.7 GHz). I typical
Performance on Demand profile by default (at the top of the catch that I have set before the profiles can be set which is the default profile that says "Startup"). So my micro varies between the states of 2 and 2.7 GHz according to the load of the bus, in which matches are to the minimum possible voltage (both).
If I need to leave your PC at night with downloads change the Power Saving profile.
if I need to rock it to the bus, for example to encode a mpeg, then change the profile Max. Performance (micro to 3GHz with mild OC).
profile is changed easily by clicking the left mouse button on the icon in the taskbar RMClock:
The remaining configuration is done in the Settings window, Management and Advanced CPU Settings. The program is fairly intuitive, so I think no need to explain in detail each of the options. Still get a snapshot of these screens if you want to see my settings in case of doubt
0 comments:
Post a Comment