OverdriveNTool - tool for AMD GPUs

Discussion in 'Videocards - AMD Radeon' started by tede, Aug 6, 2017.

  1. Poisson

    Poisson Member

    Messages:
    38
    Likes Received:
    15
    GPU:
    RX 590 Nitro+
    Hi I have added some new features to ONT, it seem that acording to the first post them could work fot AMD OverdriveN API so supported GPUs could be "(currently 290, 290x, 380, 380x, 390, 390x, Fury, Fury X, Nano, 4xx, 5xx series, Vega 56, Vega 64)". But I have tested it only on my rx 590, nobody else have tested it, so if some thing goes worng when you test it is not my responsibility, sorry.

    [​IMG]

    Like you see at the image there are four options:

    - Power efficiency by activity and power: this option is working for auto and manual mode, it increase or decrease the clocks by activity and power (obviously xD), you can select your gpu wattage. It is not changing its power limit. Its at 178w by default, you have to change it to your W an every use, I don't know how to save it at a profile, sorry. The gpu load taken into account is the one you can see at hwinfo64 named as GPU utlization, it's AMD's gpu measurement, i think it's not working so great... I think that the hwinfo64 name GPU D3D usage measuremt one is better, but it is not at AMD's API.

    - Up to -50mv by temperature and wattage: it's working only for manual mode, it increase or decrease the voltage for the used dpm depending on temp and W. You can select the max drooped mv form 0 to 50 mv The max temp is 74º.

    - Up to +40 Mhz and +50 mv more by temperature, load and Wattage: with it the setted P7 clock could go up to 40mhz more and 50mv more depending on temp, gpu load and W. The max temp is also 74º.

    -Voltage fix: it's onlly for polaris gpus. Some of them cames with lower dpms with higher voltages than the P7 one with manual mode. So it can cause stability problem. With it you can fix the voltages selecting your asic quality and your polaris gpu. I can't know if the new setted voltages are going a be stable for your gpu so the range of the voltage diference by asic is 37mv, not to wide to be sure it could work. So you will have to ajust it.

    To set the first option you, and not getting error popups, you have set your profile and apply it with the auto or manual button. Set the W, check it and click apply auto or manual.

    To set the second and third option, and not getting error popups, you have set your profile and apply it with the manual button. Set the W at the first option (you can check or not the first option) and the mv at the second option, check it and click apply auto or manual.

    To set the third option: Set first the W at the first option (you can check or not the first option).

    If you want to change W or mvs option you have to click reset button. But you can check or uncheck the option without clicking apply button if you don't change the W ot mvs.

    For the voltage fix is better to set the parameters click to apply manual, save the profile, and then click two times at reset button.

    The first three options are working better with vsync, a framerate limit and maybe freesync but I can't test it.

    I aslo have setted a voltage limit of 1.3v and it can go up to 1.35v with the third option.

    Thanks to tede for doing this amazing tool.

    Also thanks to BromoL the WattTool creator, the voltage, wattage and temp monitoring is adapted from his code.

    Special thanks to hellm.

    Old release:

    Release

    New releases:

    Versions. V1.1 is the first version with some fixes to some errors I saw at my code. And V2.1 is downvolting more by temperatures DPMs 1 to 6.

    V1.1

    V2.1

    About V2.2.5. Tede updated my version to his 0.3.0 beta version, and solved some problems he saw and I also have solved another ones he saw. He also suggested to implement changes at the apply button when an option is runing.
    With this new version for manual options, you have to set a profile first to get the starting values or unlock dpms when an option is checked/uncheked, or if you change from manual to auto and to manual again. The apply captions ar changing from apply to apply the profile or values, start to start the options to work when an option is checked, or apply/start if an option is checked but the profile isn't loaded and stop.
    Nobody than me have tested this version, seems to work for me. Let me know if you see some problem. Hope it works four you.

    You can see with this gif how it is working

    [​IMG]

    V2.2.5
     
    Last edited: Sep 18, 2020
    Dekaohtoura, OnnA, chispy and 2 others like this.
  2. OnnA

    OnnA Ancient Guru

    Messages:
    11,859
    Likes Received:
    2,767
    GPU:
    Vega XTX LiQuiD
  3. Poisson

    Poisson Member

    Messages:
    38
    Likes Received:
    15
    GPU:
    RX 590 Nitro+
    You are welcome. Is it working for Vega?. Afaik Vega have none constat voltages per clock and very variable clocks, at least at auto mode. I don't know if with manual mode is the same. So maybe this tool is not needed for it or could cause problems.
     
  4. OnnA

    OnnA Ancient Guru

    Messages:
    11,859
    Likes Received:
    2,767
    GPU:
    Vega XTX LiQuiD
    I have (now) 0.2.8 with PP_Table
    IMO it will work NP with Vega.

    Note:
    Please change Version into 0.2.9 ;)

    Note 2:
    Fan settings not working, it's all greyed out.
     
    Last edited: Mar 19, 2020

  5. Poisson

    Poisson Member

    Messages:
    38
    Likes Received:
    15
    GPU:
    RX 590 Nitro+
    As is not my tool I prefer to not to change the version to don't have misunderstandings. But maybe I would have to add some thing at the verison, I don't know. I pmed tede like a mounth ago, but I didn't had response.

    Yes, fan settings is not working because for polaris is not working ok, for my, and I don't know how to solve it. So is greyed out by default with FanDeactivatedGpus=0 at the ini file. But you can use it clicking on it with crtl pressed.
     
  6. OnnA

    OnnA Ancient Guru

    Messages:
    11,859
    Likes Received:
    2,767
    GPU:
    Vega XTX LiQuiD
  7. Poisson

    Poisson Member

    Messages:
    38
    Likes Received:
    15
    GPU:
    RX 590 Nitro+
    Hi, I have done today some fixes to my ONT version. I have added to its name R.B.R.T Edition, to don't have misunderstandings with tede's version, and I have fixed some minor errors I saw at my code.
    Also I am going to post two versions. V1.1 that is the first version with some fixes to some errors I saw at my code. And V2.1 that is downvolting more by temperatures DPMs 1 to 6.

    V1.1

    V2.1
     
    OnnA likes this.
  8. ht_addict

    ht_addict Active Member

    Messages:
    68
    Likes Received:
    11
    GPU:
    Asus Vega64(CF)
    Think I found my happy settings. No issues playing Gears 5 and Doom Eternal @ 4K with highest settings.
     

    Attached Files:

    OnnA likes this.
  9. danske

    danske New Member

    Messages:
    3
    Likes Received:
    0
    GPU:
    Rx 570
    Hey, is there a fix for this? Whenever i set the values for these and click apply, they reset. I want to atleast lock the p0 voltage and core clock so i would have less fluctuation.
     

    Attached Files:

  10. Poisson

    Poisson Member

    Messages:
    38
    Likes Received:
    15
    GPU:
    RX 590 Nitro+
    Those values are locked by the driver and can't be edited, I have tested to try to enable them at ONT but I didn't had success. But you can edit them at the ONT registry PPtable editor.

    Also you can disable/enable those P stateas as is said by tede at the first post:

    "-It's possible to disable/enable each P state. To do this click on P0, P1.. etc. label. If P state is disabled it will not be used by GPU."
     
    OnnA likes this.

  11. danske

    danske New Member

    Messages:
    3
    Likes Received:
    0
    GPU:
    Rx 570
    Thank you so much! Disabling P0 state worked for me. I cant believe how much time i've spent around this thing, and yet that the solution was so simple.. Thank you so much again!
     
  12. Rev_Night

    Rev_Night New Member

    Messages:
    1
    Likes Received:
    0
    GPU:
    Sapphire Pulse 5700
    Hi! I too am finding Wattman buggy and I want to use this tool. However, I have a 5700XT. Is this supported? I created the Windows Schedule and it just says 'Running', and its been a few minutes. Shouldn't this be relatively instant if no other tasks are running?

    Arguements:
    • -r0 -p0"5700XT F Drive"
     
  13. shotgunhobo

    shotgunhobo New Member

    Messages:
    1
    Likes Received:
    0
    GPU:
    Vega64 Nitro+
    Hi. Your tool is working great with my Vega64. Now I can use manual fan curve with ZeroRPM. That is not possible with Wattman.

    Can you explain me, what is Acoustic Limit (Mhz)?

    Thank you for this great tool!
     
  14. Shonk

    Shonk Member

    Messages:
    11
    Likes Received:
    2
    GPU:
    Sapphire RX Vega 64

    Maybe check this chief
    it resets vega 64 voltages badly
    leaving them broken until the adapter is removed from control panel

    https://forums.guru3d.com/threads/overdriventool-tool-for-amd-gpus.416116/page-27#post-5769431

    if you want a manual fan curve with zero rpm edit amd settings xml file for wattman

    here's one of mine for as an example

    1672 1045 10pl.xml
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <GPU DevID="687F" RevID="C1">
        <PPW Value="3"/>
        <FEATURE ID="4" Enabled="False">
            <STATES>
                <STATE ID="0" Enabled="True" Value="852"/>
                <STATE ID="1" Enabled="True" Value="991"/>
                <STATE ID="2" Enabled="True" Value="1084"/>
                <STATE ID="3" Enabled="True" Value="1138"/>
                <STATE ID="4" Enabled="True" Value="1200"/>
                <STATE ID="5" Enabled="True" Value="1401"/>
                <STATE ID="6" Enabled="True" Value="1536"/>
                <STATE ID="7" Enabled="True" Value="1672"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="12" Enabled="False">
            <STATES>
                <STATE ID="0" Enabled="True" Value="800"/>
                <STATE ID="1" Enabled="True" Value="900"/>
                <STATE ID="2" Enabled="True" Value="950"/>
                <STATE ID="3" Enabled="True" Value="1000"/>
                <STATE ID="4" Enabled="True" Value="1050"/>
                <STATE ID="5" Enabled="True" Value="1100"/>
                <STATE ID="6" Enabled="True" Value="1150"/>
                <STATE ID="7" Enabled="True" Value="1200"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="5" Enabled="True">
            <STATES>
                <STATE ID="0" Enabled="False" Value="167"/>
                <STATE ID="1" Enabled="False" Value="500"/>
                <STATE ID="2" Enabled="True" Value="800"/>
                <STATE ID="3" Enabled="True" Value="1045"/>
                <STATE ID="4" Enabled="False" Value="0"/>
                <STATE ID="5" Enabled="False" Value="0"/>
                <STATE ID="6" Enabled="False" Value="0"/>
                <STATE ID="7" Enabled="False" Value="0"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="13" Enabled="False">
            <STATES>
                <STATE ID="0" Enabled="False" Value="800"/>
                <STATE ID="1" Enabled="False" Value="800"/>
                <STATE ID="2" Enabled="True" Value="950"/>
                <STATE ID="3" Enabled="True" Value="1100"/>
                <STATE ID="4" Enabled="False" Value="0"/>
                <STATE ID="5" Enabled="False" Value="0"/>
                <STATE ID="6" Enabled="False" Value="0"/>
                <STATE ID="7" Enabled="False" Value="0"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="9" Enabled="False">
            <STATES>
                <STATE ID="0" Enabled="False" Value="0"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="8" Enabled="False">
            <STATES>
                <STATE ID="0" Enabled="True" Value="0"/>
                <STATE ID="1" Enabled="True" Value="0"/>
                <STATE ID="2" Enabled="True" Value="10"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="17" Enabled="False">
            <STATES>
                <STATE ID="0" Enabled="True" Value="2"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="18" Enabled="True">
            <STATES>
                <STATE ID="0" Enabled="False" Value="0"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="19" Enabled="False">
            <STATES>
                <STATE ID="0" Enabled="False" Value="0"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="20" Enabled="False">
            <STATES>
                <STATE ID="0" Enabled="False" Value="0"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="21" Enabled="False">
            <STATES>
                <STATE ID="0" Enabled="False" Value="0"/>
            </STATES>
        </FEATURE>
        <FEATURE ID="22" Enabled="True">
            <STATES>
                <STATE ID="0" Enabled="True" Value="30"/>
                <STATE ID="1" Enabled="True" Value="30"/>
                <STATE ID="2" Enabled="True" Value="50"/>
                <STATE ID="3" Enabled="True" Value="33"/>
                <STATE ID="4" Enabled="True" Value="56"/>
                <STATE ID="5" Enabled="True" Value="43"/>
                <STATE ID="6" Enabled="True" Value="59"/>
                <STATE ID="7" Enabled="True" Value="54"/>
                <STATE ID="8" Enabled="True" Value="62"/>
                <STATE ID="9" Enabled="True" Value="58"/>
            </STATES>
        </FEATURE>
    </GPU>
    
     
    Last edited: May 22, 2020
  15. The_Amazing_X

    The_Amazing_X Master Guru

    Messages:
    555
    Likes Received:
    188
    GPU:
    Red Devil V64
    On my Vega 64 works great.

    I even have PPT to 150% so my vega is going to 1750mhz at 1.1mv

    P71666mhz
     

  16. davido6

    davido6 Maha Guru

    Messages:
    1,431
    Likes Received:
    9
    GPU:
    Rx5700xt
    Very interesting this useing rx5700xt and love just how much control you can have with th fan curve
     
  17. davido6

    davido6 Maha Guru

    Messages:
    1,431
    Likes Received:
    9
    GPU:
    Rx5700xt
    interesting first version on first post lets me change all fans but v1.1 and 1.2 are greyed out ?
     
  18. davido6

    davido6 Maha Guru

    Messages:
    1,431
    Likes Received:
    9
    GPU:
    Rx5700xt
  19. davido6

    davido6 Maha Guru

    Messages:
    1,431
    Likes Received:
    9
    GPU:
    Rx5700xt
    sorted works perfect
     
  20. Poisson

    Poisson Member

    Messages:
    38
    Likes Received:
    15
    GPU:
    RX 590 Nitro+
    My new options of my ONT version are not compatible and are not working for navi gpus that uses Overdrive8 API. The up to 40 Mhz should not be seen for your gpu, I must have done something wrong.

    The fan section is greyed out at my version becase I had some problems with my rx 590 fans when applying a config. Even not changin any thing at fan section, fans where behaving diferent than at stock. So I let it greyed out for caution. I don't know if it's only a problem caused by some specific drives or if it's solved now by a new driver. But I don't know how to solve it at ONT code or if the problem can be solved at it.
     

Share This Page