The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    AMD Griffin CPU UnderVolting Guide (QL/RM/SI/ZM)

    Discussion in 'Hardware Components and Aftermarket Upgrades' started by weinter, Jul 7, 2009.

  1. weinter

    weinter /dev/null

    Reputations:
    596
    Messages:
    2,798
    Likes Received:
    1
    Trophy Points:
    56
    Original Guide here

    Firstly download K10STAT from here.
    I Extracted it to C:\Program Files\K10STAT

    Configure K10STAT

    [​IMG]

    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 or 3 P-state which 2 are identical.

    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 P-State.(Try to set this to 100ms (lower better) so it will ramp up performance quickly when you need it so less time lag)

    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)

    After you have set suitable values (-0.05 recommended).

    [​IMG]

    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.

    Setting K10STAT for StartUp

    Open >> Start Menu\All Programs\Accessories\System Tools\Task Scheduler

    Create a Task

    [​IMG]

    [​IMG]

    [​IMG]

    [​IMG]
    The following arguments are available (Source: http://dsus4.blog126.fc2.com)
    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 same clock.
    -StayOnTray - use this option with -nw for Clock Control Mode.
    e.g.Target:
    "C:\Program Files\K10stat\K10STAT.exe" -lp:1 -ClkCtrl:2 -StayOnTray -nw

    [​IMG]

    [​IMG]

    Finally you can Control your CPU using the K10STAT Systray if you enabled -StayOnTray .

    [​IMG]

    -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.
     
  2. Snowm0bile

    Snowm0bile Starcraftologist

    Reputations:
    265
    Messages:
    1,142
    Likes Received:
    0
    Trophy Points:
    55
    Nice guide buddy.

    +props
     
  3. exercise

    exercise Notebook Consultant

    Reputations:
    3
    Messages:
    170
    Likes Received:
    0
    Trophy Points:
    30
    Hi!
    I'm trying hard to get K10STAT to load at startup.
    I followed the guide "by the numbers", and in the task manager, it says that the application loads at startup (in the task log). In reality, it doesn't show in tray and I have to manually run another instance and click OK for the set voltages to be applied.

    Any help would be appreciated!
     
  4. exercise

    exercise Notebook Consultant

    Reputations:
    3
    Messages:
    170
    Likes Received:
    0
    Trophy Points:
    30
    EDIT:

    Ok I found out. You have to find the K10STAT.dat file, erase it and the next time it loads, it will use the specified settings!