1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RX Vega Owners Thread, Tests, Mods, BIOS & Tweaks !

Discussion in 'Videocards - AMD Radeon' started by OnnA, Aug 15, 2017.

  1. PontiacGTX

    PontiacGTX Member

    Messages:
    33
    Likes Received:
    0
    GPU:
    AMD
    I have some doubts for anyone who uses the reference card, is it normal it throttles to 1150mhz?how hot can get the hotspot?
     
    Last edited: Mar 14, 2019
  2. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    15,019
    Likes Received:
    1,128
    GPU:
    Sapphire Vega Pulse
    Hotspot I think is at 105 degrees Celsius though it's possible the GPU might try to throttle or lower clocks before hitting the full temperature limit similar to how the HBM2 memory modules start relaxing their timings around 72 degrees I believe it was in Celsius but it's not critical though it will affect performance a bit.

    EDIT: There's what around 64 some sensors in Radeon VII and probably a similar amount in Vega 10 though with some design differences I would assume though GPU-Z and HWInfo should be able to measure several of these including the little thing simply known as the hotspot sensor.
     
  3. PontiacGTX

    PontiacGTX Member

    Messages:
    33
    Likes Received:
    0
    GPU:
    AMD
    Well mine didnt perform properly in superposition it throttled to 1050/950mhz and I dont know why, It is a MSI Radeon RX Vega 56 8GB reference using 165w bios undervolted -100mV but didnt improve the performance,it just performs close to R9 Fury in superposition(7400 high preset 1080p)

    hotspot reaches 105c,while core reach 78c with fan at 4800RPM, and the memory starts throttling to 700Mhz...

    I am using Windows 10 1809 and 19.3.1 drivers


    Do you believe is there anything I can do aside re-applying thermal compound?
     
  4. The_Amazing_X

    The_Amazing_X Active Member

    Messages:
    52
    Likes Received:
    18
    GPU:
    rx 480 4g
    Yes you need to, put a good amount of it. Also get a Mortheus 2 for a cooler you will get a huge uplift in temps and performance
     

  5. PontiacGTX

    PontiacGTX Member

    Messages:
    33
    Likes Received:
    0
    GPU:
    AMD
    I will see if I can find any morpheus II on the used market,since MSRP seems a bit high for my current budget
     
  6. OnnA

    OnnA Ancient Guru

    Messages:
    7,444
    Likes Received:
    1,098
    GPU:
    Vega 64 XTX LiQuiD
    Vega 56 OC/UV (good cooling)

    [​IMG]

    Vgea 64 XTX 1550MHz 0.900mV

     
  7. Mr. Sunshine

    Mr. Sunshine New Member

    Messages:
    9
    Likes Received:
    2
    GPU:
    Vega 64
    Was hoping for that 1700mhz mark... So went to 1717mhz @1.1mv. Stable for 5hr loop of Heaven with a avg. speed of 1642mhz(max 1662mhz)

    State6- 1650@1050mv
    State7- 1717@1100mv
    Mem-1100@975mv
    PL-20%

    Temp- 59c
    HBM-64c
    HotSpot-75c
    233w
    1.048v

    Wondering if I bump State6 to 1675mhz that it will keep it over 1650mhz stable.
     
  8. Mr. Sunshine

    Mr. Sunshine New Member

    Messages:
    9
    Likes Received:
    2
    GPU:
    Vega 64
    SuperPosition 1080p High- 11411

    Min-65.09
    Avg.-85.35
    Max-102.52
     
  9. OnnA

    OnnA Ancient Guru

    Messages:
    7,444
    Likes Received:
    1,098
    GPU:
    Vega 64 XTX LiQuiD
    Try to keep P6 even lower ;) Don't worry Vega will BoosT if needed.

    Here is my BFV config (BFV is verry unstable if OC is too high -> CPU/RAM or GPU)

    [​IMG]
     
    Last edited: Mar 16, 2019
  10. Mr. Sunshine

    Mr. Sunshine New Member

    Messages:
    9
    Likes Received:
    2
    GPU:
    Vega 64
    I tried bumping 1717mhz to 1722mhz... no go. I get this wierd anomaly at anything over 1717mhz where it will run stable for about an hour or so then it spikes to its max State setting and crashes the driver.

    Ex. State7 @ 1732mhz will peak at 1698mhz during Heaven loop then like two hours in spike at 1732mhz and crash to desktop.
     

  11. Mr. Sunshine

    Mr. Sunshine New Member

    Messages:
    9
    Likes Received:
    2
    GPU:
    Vega 64
    Update:
    Stable at
    State1 -1137mhz@890mv
    State2 -1302mhz@925mv
    State3 -1347mhz@931mv
    State4 -1407mhz@950mv
    State5 -1552mhz@975mv
    State6 -1687mhz@1050mv
    State7 -1717mhz@1120mv

    Mem- 1100mhz@975mv
    Memory timings level1

    All Avg
    1650mhz (1648mhz-1658mhz range)
    1.069v
    249w
    Core 61c
    HBM-66c
    Hot Spot-79c

    If I moved State 6/7 frequency or voltage down it starts dropping steady mhz. The avg. drops about 10mhz and frequency jumps around by like 20-30mhz instead of 10-15mhz.

    I was able to get over 1700mhz(1709mhz avg.)stable but had to go with power table mod(1225mv)(PL 142%)and run fans at 90-100%....load and hot for 50-60mhz. Water would push card to that barrier but not looking to mess with that.
     
  12. Thiago Diniz

    Thiago Diniz Member

    Messages:
    17
    Likes Received:
    11
    GPU:
    RX VEGA 64
    I'm done doing some tests, now all I want is enjoy the card.. In some settings P7 clocks spikes to a higher than value set and driver crashes too.

    And I noticed that depending on the application, clocks may vary for the same settings, like:
    P6: 1647mhz 1106mv
    P7: 1732mhz 1168mv Mem: 1100Mhz 1006mv
    PL: 0
    HWiNFO Max Clocks in:
    - Superposition Extreme: 1499Mhz
    - TimeSpy: 1575Mhz
    - FireStrike: 1555Mhz
    - Metro Exodus Bench DX11: 1584Mhz
    ________________________________
    P6: 1647mhz 1106mv
    P7: 1732mhz 1168mv Mem: 1100Mhz 1006mv
    PL: 15%
    HWiNFO Max Clocks in:
    - Superposition Extreme: 1576Mhz
    - TimeSpy: 1675Mhz
    - FireStrike: 1650Mhz
    - Metro Exodus Bench DX11: 1685Mhz
    _________________________________

    And for now, I'm using:
    P6: 1647mhz 1106mv
    P7: 1717mhz 1137mv Mem: 1100Mhz 1006mv
    PL: 15% (peaks at 250W)

    I didn't do any bench test with these settings, I launched some games (BF1, TombRaider Demo, R6Siege, The Witcher 3) in windowed mode and did some tweaks/settings using overdriveNTool. Each game achieved a different gpu clock, so I guess it depends on the engine (how the game uses the gpu) to achieved a certaing clock
     
  13. OnnA

    OnnA Ancient Guru

    Messages:
    7,444
    Likes Received:
    1,098
    GPU:
    Vega 64 XTX LiQuiD
    Neon Noir by Crytek (This Demo was rendered real-time using single RX Vega 56)

    Crytek has released a new video demonstrating the results of a CRYENGINE research and development project.
    Neon Noir shows how real-time mesh ray-traced reflections and refractions can deliver highly realistic visuals for games.

    According to the press release, the Neon Noir demo was created with the new advanced version of CRYENGINE’s Total Illumination showcasing real time ray tracing.
    This feature will be added to CRYENGINE release roadmap in 2019, enabling developers around the world to build more immersive scenes, more easily, with a production-ready version of the feature.

    Neon Noir follows the journey of a police drone investigating a crime scene.
    As the drone descends into the streets of a futuristic city, illuminated by neon lights, we see its reflection accurately displayed in the windows it passes by,
    or scattered across the shards of a broken mirror while it emits a red and blue lighting routine that will bounce off the different surfaces
    utilizing CRYENGINE’s advanced Total Illumination feature. Demonstrating further how ray tracing can deliver a lifelike environment,
    neon lights are reflected in the puddles below them, street lights flicker on wet surfaces, and windows reflect the scene opposite them accurately.

    Neon Noir was developed on a bespoke version of CRYENGINE 5.5., and the experimental ray tracing feature based on CRYENGINE’s Total Illumination used to create the demo is both API and hardware agnostic,
    enabling ray tracing to run on most mainstream, contemporary AMD and NVIDIA GPUs. However, the future integration of this
    new CRYENGINE technology will be optimized to benefit from performance enhancements delivered by the latest generation of graphics cards and supported APIs like Vulkan and DX12.

    The experimental ray tracing feature simplifies and automates the rendering and content creation process to ensure that animated objects and changes in lighting are correctly reflected with a high level of detail in real-time.
    This eliminates the known limitation of pre-baked cube maps and local screen space reflections when creating smooth surfaces like mirrors, and allows developers to create more realistic, consistent scenes.
    To showcase the benefits of real time ray tracing, screen space reflections were not used in this demo.

    Now we need this new Crysis 4 :D

     
    apple020997 and Jackalito like this.
  14. MerolaC

    MerolaC Ancient Guru

    Messages:
    2,987
    Likes Received:
    82
    GPU:
    RX VEGA 56
    OMG, just ONE RX Vega 56?
    That's impressive!
     
    Jackalito and OnnA like this.
  15. OnnA

    OnnA Ancient Guru

    Messages:
    7,444
    Likes Received:
    1,098
    GPU:
    Vega 64 XTX LiQuiD
    ACE is the Key here :D ( & Compute is the magic word, because Raytrace is a form of Compute)

    So we can have dedicated normal GPU workload + asynchronous raytrace compute at no cost.

    (i told You that in December)
     
    Last edited: Mar 15, 2019

  16. The_Amazing_X

    The_Amazing_X Active Member

    Messages:
    52
    Likes Received:
    18
    GPU:
    rx 480 4g
    This is huge, so all the people that got RTX will get a slap in the face lol
     
    MaestroBayten likes this.
  17. Mr. Sunshine

    Mr. Sunshine New Member

    Messages:
    9
    Likes Received:
    2
    GPU:
    Vega 64
    Glad to see some else having same issue. Must have something to do with voltage spiking while undervolting. I've been trying to track down the cause of it. I set State 5,6,7 to the following:

    S5- 1692mhz 1094mv
    S6- 1702mhz 1100mv
    S7- 1717mhz 1120mv

    Mem- 1100mhz@975mv

    Ran Heaven for about 30sec then spiked to 1742mhz @ 1113mv and crashed driver. But If I run the following:

    S5- 1692mhz 1150mv
    S6- 1702mhz 1180mv
    S7- 1732mhz 1250mv

    Mem- 1100mhz@1100mv

    Stable for over an hour loop of Heaven. But hot:
    Fans 85-90%
    Core- 70-71c
    HBM- 73-75c
    Hot Spot- 92-94c
     
  18. pharma

    pharma Master Guru

    Messages:
    972
    Likes Received:
    86
    GPU:
    Asus Strix GTX 1080
    Voxel ray tracing has been around for quite a while, so nothing new. Not quite the same...
     
  19. Mr. Sunshine

    Mr. Sunshine New Member

    Messages:
    9
    Likes Received:
    2
    GPU:
    Vega 64
    P6: 1675mhz 1075mv
    P7: 1720mhz 1120mv
    PL: 30%
    Mem: 1100Mhz 975mv
    Memory timings level1

    Stable Clocks in:
    Games at 2560x1440
    Doom Nightmare mode: 1651-1662mhz (avg.1655mhz)
    The Division2 Ultra mode: 1651-1655mhz (avg.1653mhz)

    In Game
    Core 57-64c
    HBM-63-66c
    Hot Spot-75-79c
    1.069v avg.
    249-269w

    TimeSpy- Total score-7818/Graphics Score-8010
    Graphics Test 1- 55.78fps 1655-1663mhz (avg.1658mhz)
    Graphics Test 2- 43.48fps 1657-1666mhz (avg.1660mhz)
     
    Last edited: Mar 16, 2019
    Jackalito and OnnA like this.
  20. Thiago Diniz

    Thiago Diniz Member

    Messages:
    17
    Likes Received:
    11
    GPU:
    RX VEGA 64
    ok, so I did some more brief tests and I came to the conclusion that:

    Driver 19.3.2 - Wattman Settings (for exemple):
    P4: 1202 MHz - 1006 mV
    P5: 1517 MHz - 1056 mV
    P6: 1642 MHz - 1112 mV
    P7: 1727 MHz - 1168 mV
    Mem: 1100 Mhz - 1006 mV
    PL: 24%

    With the settings above on a Cold Boot (or if I simple restart the Windows) I always have a driver Crash/Reset seconds after starting FireStrike Stress test for the first time (HWiNFO reports a max of 175x MHz on Gpu Core)

    So after the gpu driver crash, I re-open Radeon Settings, Load SAME PROFILE ABOVE, and I'm able to stress FireStrike how many times I want, play games, etc.. without a single crash.

    If I just restart Windows, open some game/firestrike stress test for exemple, seconds after start using GPU I got a Driver Crash/Restart... if I just load profile again then I'm able to do whatever I want.

    This makes me wonder how many times I though my overclock/undervolt wasn't as unstable as it appears to be, because I did some tests then "ok, everything sounds good, I'll continue tomorrow", then the next day I started from last night point and got a crash at first run and "oh, come on, yestarday I did a lot of test and this settings was stable, and now at the first run I got a crash?"

    It seems to be related to PowerLimit, If I use the SAME config BUT with PL 0, I got no crash at all.. if I save settings with PL 24% (didn't test any other yet), I have the situation above.

    TL;DR:
    1) Start Windows (with settings applied on Wattman)
    3) FireStike Stress Test
    4) GPU Driver Crash/Reset
    5) Re-Apply SAME Settings on Wattman
    6) I'm good to go!
     
    Last edited: Mar 20, 2019 at 12:46 AM
    Mr. Sunshine and apple020997 like this.

Share This Page