RX Vega Owners Thread, Tests, Mods, BIOS & Tweaks ! (cont.)

Discussion in 'Videocards - AMD Radeon' started by Glidefan, Mar 31, 2019.

  1. geronimo666

    geronimo666 Member Guru

    Messages:
    116
    Likes Received:
    9
    GPU:
    MSI RX Vega 56 AB
    you do it from win10? I have both win7 and win10.
    I don't know if it matters but I have seen some complaining that it doesn't work under w10. maybe they didn't use run as admin...
    I'll try it tonight again from win7.
    thanks for all the info.
    I'll let everyone know of the result.
     
  2. MerolaC

    MerolaC Ancient Guru

    Messages:
    3,314
    Likes Received:
    230
    GPU:
    RX VEGA 56
    Windows 10 here.
     
    geronimo666 likes this.
  3. geronimo666

    geronimo666 Member Guru

    Messages:
    116
    Likes Received:
    9
    GPU:
    MSI RX Vega 56 AB
  4. MerolaC

    MerolaC Ancient Guru

    Messages:
    3,314
    Likes Received:
    230
    GPU:
    RX VEGA 56
    geronimo666 likes this.

  5. geronimo666

    geronimo666 Member Guru

    Messages:
    116
    Likes Received:
    9
    GPU:
    MSI RX Vega 56 AB
    tried it. it doesn't work :-(.
    I get:

    Old SSID: 3681
    New SSID: 3680
    SSID mismatched
    ERROR: 0FL01
     
  6. MerolaC

    MerolaC Ancient Guru

    Messages:
    3,314
    Likes Received:
    230
    GPU:
    RX VEGA 56
    Oh, I forgot, you have to force the flash, because of the SSID missmatch.
    run the command with -f added
    amdvbflash.exe -p 0 -f V64.rom
     
    geronimo666 and OnnA like this.
  7. geronimo666

    geronimo666 Member Guru

    Messages:
    116
    Likes Received:
    9
    GPU:
    MSI RX Vega 56 AB
  8. The_Amazing_X

    The_Amazing_X Master Guru

    Messages:
    470
    Likes Received:
    155
    GPU:
    Red Devil V64
    easy tunning.

    radeon driver set max gpu oc click. gives you a value. for me 1715mhz do the same for vram for me 1175mhz, drop -25 in voltage, 50% power.

    Not a single error or drop. clock near 1700mhz my vega is crap but works well. lol
     
  9. Mr. Sunshine

    Mr. Sunshine Master Guru

    Messages:
    216
    Likes Received:
    67
    GPU:
    SapphireNitro V64
    Is this in lastest drivers?
     
  10. geronimo666

    geronimo666 Member Guru

    Messages:
    116
    Likes Received:
    9
    GPU:
    MSI RX Vega 56 AB
    I must say I'm not very happy with this v64 flash. Can't get HBM above 1070mhz. before I was able to get to 970 stable :-(. the temps are not the problem.
    bigger problem is I can't get the timings good. I don't get how come I can't get at least vega56 default timings with this if I use identical GPU/HBM clocks/voltages, except HBM which is now 1.35mV instead of 1.25mV and what I wanted in the first place cos I expected higher clocks on the HBM.
    advice?
    thx
     

  11. OnnA

    OnnA Ancient Guru

    Messages:
    11,025
    Likes Received:
    2,448
    GPU:
    Vega 64 XTX LiQuiD
    That's because V56 HBM is different than this on V64.
    Just make new Default OC for V64 -> Try similar to mine ;)

    Adjust one option, test -> then rest follows.

    Restart driver = ctrl+shift+Win+B

    [​IMG]
     
    Last edited: Dec 14, 2019
  12. geronimo666

    geronimo666 Member Guru

    Messages:
    116
    Likes Received:
    9
    GPU:
    MSI RX Vega 56 AB
    What do you mean different? It's the same card. You mean it works somehow different, maybe A.I. or algos or something?
    I'll try. thanks OnnA.
    BTW is there any way to reload adrenalin/AMD driver without restart after it crashes?

    edit: I still don't understand the reason why using ODNT together with amd tweak memory when I can do the same things in only AMD tweak mem. Is there something I don't know?

    edit2: tried your sett. it crashes in Tom Raider DOX in a few minutes :-(.
    these are the settings:

    https://i.**********/XGhFZtRM/z-Vega64-cst-fan-T4-0perc-Onn-A-crash.jpg

    wich setting to try raising/lowering first now?
     
    Last edited: Dec 14, 2019
  13. OnnA

    OnnA Ancient Guru

    Messages:
    11,025
    Likes Received:
    2,448
    GPU:
    Vega 64 XTX LiQuiD
  14. Undying

    Undying Ancient Guru

    Messages:
    12,960
    Likes Received:
    2,242
    GPU:
    Aorus RX580 XTR 8GB
    Detroit does not run well for a vulkan game.
     
    apple020997 likes this.
  15. OnnA

    OnnA Ancient Guru

    Messages:
    11,025
    Likes Received:
    2,448
    GPU:
    Vega 64 XTX LiQuiD
    Ultra ;)
     

  16. geronimo666

    geronimo666 Member Guru

    Messages:
    116
    Likes Received:
    9
    GPU:
    MSI RX Vega 56 AB
    these are my latest stable settings for my vega56@64 on 1050mhz HBM after spending much of a weekend on tweaking:
    https://i.**********/5XR6nhG0/v64-last.jpg

    Is there some limit to tREF that I shoudn't go over, or should I just try raising more before crashing (I think I read somewhere that tREF raises HBM temp)? the temps you see on the photo are more or less max (room 21-23c).
    with these above settings I'm barely touching results from benches/tests on default v56 bios:
    https://i.**********/qhdBF4Gk/v56-last.jpg

    btw are there any good specific HBM quick tests/benches available similar to poclmembench?

    thx
     
  17. stevin48

    stevin48 Member

    Messages:
    11
    Likes Received:
    0
    GPU:
    asus ares 5870x2
    sapphire nitro+ vega 64 does not like newer driver or mine dont the 19 .12.2 my core clocks dropped as have been each newer update the 19.12.2 my clocks were down avg 1100 mhz to 1300 mhz and mem dropping while temp only 63 c . and could not get to undervolt . uninstalled went back few drivers and got it up to 1500 mhz turbo . went back to amd driver 18.5.2 and on turbo my clocks tun above 1600 mhz again ITS THE DRIVERS amd wants us to upgrade our cards. sapphire is core clock of 1630 mhz . the 18.5.2 driver you wont see mem bouncing up and down or the gpu core clock lowered . its rock solid . watch memory clock while bench using msi afterburner on the newer driver it dives as low as 500 mhz causing frame drops and studder on newer drivers
     
  18. stevin48

    stevin48 Member

    Messages:
    11
    Likes Received:
    0
    GPU:
    asus ares 5870x2
    sapphire nitro+ vega 64 does not like newer driver or mine dont the 19 .12.2 my core clocks dropped as have been each newer update the 19.12.2 my clocks were down avg 1100 mhz to 1300 mhz and mem dropping while temp only 63 c . and could not get to undervolt . uninstalled went back few drivers and got it up to 1500 mhz turbo . went back to amd driver 18.5.2 and on turbo my clocks tun above 1600 mhz again ITS THE DRIVERS amd wants us to upgrade our cards. sapphire is core clock of 1630 mhz . the 18.5.2 driver you wont see mem bouncing up and down or the gpu core clock lowered . its rock solid . watch memory clock while bench using msi afterburner on the newer driver it dives as low as 500 mhz causing frame drops and studder on newer drivers
     
  19. stevin48

    stevin48 Member

    Messages:
    11
    Likes Received:
    0
    GPU:
    asus ares 5870x2
    sapphire nitro+ vega 64 does not like newer driver or mine dont the 19 .12.2 my core clocks dropped as have been each newer update the 19.12.2 my clocks were down avg 1100 mhz to 1300 mhz and mem dropping while temp only 63 c . and could not get to undervolt . uninstalled went back few drivers and got it up to 1500 mhz turbo . went back to amd driver 18.5.2 and on turbo my clocks tun above 1600 mhz again ITS THE DRIVERS amd wants us to upgrade our cards. sapphire is core clock of 1630 mhz . the 18.5.2 driver you wont see mem bouncing up and down or the gpu core clock lowered . its rock solid . watch memory clock while bench using msi afterburner on the newer driver it dives as low as 500 mhz causing frame drops and studder on newer drivers
     
  20. Morax

    Morax Member Guru

    Messages:
    108
    Likes Received:
    25
    GPU:
    Asus RX Vega 64
    Is there a way in the new 19.12.2 drivers to alter the Min/Max of the P-states like it used to be possible within Wattman?

    I'm trying to play Transport Fever 2, but since it's yet another one of those not-that-well-optimised games without Exclusive Fullscreen support, and not even Vulkan, the Core and Memory speeds are yet again being mismanaged by this dynamic powerstate control thing (is it still called Powerplay?), resulting in unreasonably poor performance.
     

Share This Page