Configure K10STAT: 0 Performance Handicap With Less Heat Issues and Longer Battery Life!!
Configure K10STAT: 0 Performance Handicap With Less Heat Issues and Longer Battery Life!!
Because if a lower voltage can sustain your clockspeed undervolting preserve battery life and reduce heat generated without affecting your CPU performance at all!!
0 performance handicap with less heat issues and longer battery life!! If it is so great why manufacturers don't undervolt?
Because they create processors in bulk you can't expect them to test & undervolt every single processor! So they simply take the a slightly higher approximate stable voltage and burn the same value into every chip of the same family!
Configure K10STAT
When you run K10STAT you should see the menu above. You can set a maximium of 5 Profiles. FID: The multiplier for the Processor (NOTE: FID doesn't work in AMD Mobile Processors) DID: The P-State of the Processor. ZM/RM has 3 P-State, P0,P1,P2 while QL/SI should only have 2 P-State. CPU-Voltage that is what we are interested in. To set the voltage for P0 simply Select P0 and select the corresponding voltage and apply. Remember: Min 0.75 V Max 1.2 V! For me I tested -0.05 is the Max Stable voltage for each default state any higher it BSOD! Up%: This is the amount of CPU load before the processor changes P-State. Currently it is set at 60% meaning it will switch from P2 to P1 when processor detect 60% load and the same applies from switching from P1 to P0. Down%:It is basically the opposite of Up%. Up(ms):It is the time the processor takes to switch from one P-State to the next higher PState.(Try to set this to 100ms (lower better) so it will ramp up performance quickly when you need it so less time lag however setting this low will cause higher temperatures)
Down(ms):It is basically the opposite of Up(ms).(Try to set this to 100ms (lower better) so it will ramp down performance quickly when you don't need it so more power save; less heat produced however setting this low will cause higher temperatures) After you have set suitable values (-0.05 recommended).
Use Vista Processor Power Management to test different levels. To test simply click on the core of the P-State immediate the Processor will assume the P-State. Test each P-State by running Intel Burn In or any suitable CPU loading tool. You should have 4 Windows Open to control and test each p-state as shown above. Finally I had time to do a Full LinPack Test. The voltages that passed are 1.075V, 0.900V and 0.750V. At 1.025V it BSOD after 2 mins. At 1.0372V it produce the wrong result. To pass LinPack the result calculated by the CPU must be consistent.
Command Line Option -lp:#(1-5) - load profile#(1-5) and write to MSR. -nw - Start K10stat with NoWindow. -ClkCtrl:#(0-4) - Enable Clock Control by K10stat. 0:No Control 1:Control clock of each core. 2:Control clock of all cores together (Criterion is most loaded core). 3:Control clock of all cores together (Criterion is average of all cores). 4:Control clock of all cores together (Criterion is least loaded core). It is recommended that you set -ClkCtrl:2 for faster setting. Because Windows proceed on the assumption that cores are default unganged. -StayOnTray - use this option with -nw for Clock Control Mode.
Finally you can Control your CPU using the K10STAT Systray if you enabled -
-ClkCtrl:#(0-4) - Enable Clock Control by K10stat (Refer to above). 0:No Control 1:Control clock of each core. UnGanged means each CPU Core #0 & #1 operates independently of each other so at any one time their frequency and DID could be different.(This is the original intent of the design of the Turion Chips as they are given different power planes.) 2:Control clock of all cores together (Criterion is most loaded core). This means the CPU will raise/drop the DID of Core #0 & #1 together when it detects the one of higher Core has reached the criteria for a Frequency boost/Throttle Down. 3:Control clock of all cores together (Criterion is average of all cores). This means the CPU will raise/drop the DID of Core #0 & #1 together when it detects the average of both core has reached the criteria for a Frequency boost/Throttle Down. 4:Control clock of all cores together (Criterion is least loaded core). This means the CPU will raise/drop the DID of Core #0 & #1 together when it detects the one of lowest Core has reached the criteria for a Frequency boost/Throttle Down.