AMD Fury X Owners' Thread

Discussion in 'Videocards - AMD Radeon' started by Fox2232, Jun 25, 2015.

  1. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    7,889
    Likes Received:
    755
    GPU:
    Inno3D RTX 3090
    C'est moi. :D

    Try with GPU-Z, HWiNFO64, or MSI Afterburner, and see if any of them recognizes your card and the VRM it has. If one of them does, please play a bit and report max temps back.
    Thanks!
     
  2. Fox2232

    Fox2232 Ancient Guru

    Messages:
    11,809
    Likes Received:
    3,366
    GPU:
    6900XT+AW@240Hz
    Will be updating my #5 post here as much as time allows me.
     
  3. mR Yellow

    mR Yellow Ancient Guru

    Messages:
    1,935
    Likes Received:
    0
    GPU:
    Sapphire R9 Fury
    Thanks.
     
  4. Joschi

    Joschi Member

    Messages:
    16
    Likes Received:
    0
    GPU:
    Sapphire Fury X
    Hey, long time Lurker here, getting my Fury on Saturday, huge upgrade over the current 7870. i'm curious if the pump has been fixed already
     

  5. Fox2232

    Fox2232 Ancient Guru

    Messages:
    11,809
    Likes Received:
    3,366
    GPU:
    6900XT+AW@240Hz
    No noise from it here. But you can hear something else from card. If you run like 600fps, it ticks at 600Hz. In 3DMark API overhead test which increases number of draw calls, which reduces fps as result, you can hear it as it goes from low pitch to very low pitch, but I have case open at this moment.
    And you can't here it in games even at 120fps. :) My HD7970 did same in HL2 benchmark, as there it rendered over 1000fps (you have to unlock fps limit).
     
  6. MaxBlade

    MaxBlade Master Guru

    Messages:
    891
    Likes Received:
    11
    GPU:
    980Ti/970/390/+ more
  7. MSIMAX

    MSIMAX Active Member

    Messages:
    92
    Likes Received:
    41
    GPU:
    3x 290x cfx
    sub'd should be a interesting thread lol
     
  8. Fox2232

    Fox2232 Ancient Guru

    Messages:
    11,809
    Likes Received:
    3,366
    GPU:
    6900XT+AW@240Hz
    Sorry, please read my reply to him. It is nothing like test samples. When you record something with microphone you have no control over proper recording volume, nor frequencies such microphone boosts, dumpens.
    And then you have no control over reproduction volume.
    I had to take it to like 15% of volume to actually hear my PC which is on my desk with open side panel and is exactly 75cm away from my head.

    And please read OT.
     
    Last edited: Jun 26, 2015
  9. cowie

    cowie Ancient Guru

    Messages:
    13,273
    Likes Received:
    345
    GPU:
    GTX
    hey can one of you guys use afterburner (hit the "i")and get the guid or device id string?
    GF where you at?
     
  10. Fox2232

    Fox2232 Ancient Guru

    Messages:
    11,809
    Likes Received:
    3,366
    GPU:
    6900XT+AW@240Hz
    Not using Afterburner as all I need is in RP.
    [​IMG]
     

  11. Undying

    Undying Ancient Guru

    Messages:
    16,628
    Likes Received:
    5,542
    GPU:
    Aorus RX580 XTR 8GB
    Fox, hows that 2500k holding up with Fury? Maybe you'll need some Skylake upgrade when it hits... ;)
     
  12. Fox2232

    Fox2232 Ancient Guru

    Messages:
    11,809
    Likes Received:
    3,366
    GPU:
    6900XT+AW@240Hz
    Read post #5 for experience. Will update it day after day and as something new pops in.
    My graphical score in Firestrike was 15664 while Hilbert's with his uber CPU was 16081. So it is not holding me back. And I have W8.1 driver which I bugged to W10, so it is far from optimal.
    But his physics score is like 2.6 times higher.
    For now, I did not hit CPU wall anywhere I tested.

    Edit: Firestrike + drivers = LoL
    Firestrike-Link
    On left: Fury X release driver for W8.1 with Fury X code path (15.150.0.0). On Right W10 driver which does not have Fury X code path, so I used Tonga instead (15.200.1040.0.)
    And Yes, Graphical score went from 15664 to 16320 which is more than Hilbert's. (4.2% improvement).
     
    Last edited: Jun 26, 2015
  13. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    7,889
    Likes Received:
    755
    GPU:
    Inno3D RTX 3090
    And neither will you. Your CPU is 1GHz faster than any "non enthusiast" CPU Intel is selling currently.
     
  14. Paradoxx

    Paradoxx Member

    Messages:
    16
    Likes Received:
    2
    GPU:
    Asus Dual RX 580
    just a heads up, gpu-z was updated with fury x support
     
  15. lexer98

    lexer98 Master Guru

    Messages:
    667
    Likes Received:
    2
    GPU:
    GTX 1070 - WC
    Still using a Chill VRM controller this GPU ?
     

  16. gerardfraser

    gerardfraser Ancient Guru

    Messages:
    3,343
    Likes Received:
    763
    GPU:
    R9 290 Crossfire
    LOL I am here,they took my cash and not sent yet(next week they say now).Went to the local store none in the store yet either.
    I can buy a couple on newegg but that's next week also.I got lots of excuses.
     
  17. MaxBlade

    MaxBlade Master Guru

    Messages:
    891
    Likes Received:
    11
    GPU:
    980Ti/970/390/+ more
    Lol.. I just came across it.. and posted it. Thats all I know.. later.
     
  18. mR Yellow

    mR Yellow Ancient Guru

    Messages:
    1,935
    Likes Received:
    0
    GPU:
    Sapphire R9 Fury
    please keep us posted on the DX12 performance in 3dmark once supported drivers drop.
     
  19. fixel

    fixel Member

    Messages:
    24
    Likes Received:
    0
    GPU:
    Fury X
    This ain't nothing right? that's a fairly substantial improvement IMO.
     
  20. Fox2232

    Fox2232 Ancient Guru

    Messages:
    11,809
    Likes Received:
    3,366
    GPU:
    6900XT+AW@240Hz
    It is, but on other hand it is workload dependant.
    My favourite benchmark for drivers is AvP 2010. Your GPU will not be bottlenecked even by 2GHz CPU there, so it is all about driver optimizing what should GPU render and its rendering power.
    So while there is very real improvement in Firestrike, in AvP 2010 score went from 194,3 to 194,9 on maximum details. And that is in margin of error.
    But main point is that AMD's release driver with proper code path scores worse than not supported Windows 10 driver which does not have Fury X specific code.
    And that means AMD has room to improve their driver here.
     

Share This Page