Radeon Software Crimson ReLive Edition 17.4.2

Discussion in 'Videocards - AMD Radeon Drivers Section' started by SpecChum, Apr 12, 2017.

  1. Passus

    Passus Maha Guru

    Messages:
    1,105
    Likes Received:
    203
    GPU:
    GTX 1060 3GB
    RIP RadeonPro
     
  2. d0X

    d0X Member Guru

    Messages:
    182
    Likes Received:
    9
    GPU:
    MSI GTX1070 GamingX
    I guess RadeonPro finally shows it's age. :(

    EDIT: Passus beat me to it :p
     
  3. ldwar

    ldwar Member Guru

    Messages:
    100
    Likes Received:
    0
    GPU:
    Sapp HD390x crossfire
    Win 10 1703 but was also using before creator update , and it was the same
     
  4. Romulus_ut3

    Romulus_ut3 Master Guru

    Messages:
    670
    Likes Received:
    138
    GPU:
    AMD RX 570 4GB
    Let's request JapaMD for an update?
     

  5. TDurden

    TDurden Ancient Guru

    Messages:
    1,980
    Likes Received:
    3
    GPU:
    Sapphire R9 390 Nitro
    Same thing here..
    Did you find a fix?
     
  6. janos666

    janos666 Master Guru

    Messages:
    678
    Likes Received:
    50
    GPU:
    MSI GTX1070 SH EK X 8Gb
    Does this one still crash on boot (with "...protected memory region..." error) just like all the others above 17.1.2 with 6 Polaris cards (or possibly any number above 3)?
    I checked them all for myself so far but I got tired of having to attach a monitor+keyboard and reinstall 17.1.2 after a DDU run in safemode.
     
  7. Chastity

    Chastity Ancient Guru

    Messages:
    1,981
    Likes Received:
    498
    GPU:
    Nitro 390/GTX1070M
    Running Win 10 CU + 17.4.2. DA:I working fine here, in both DX11 and Mantle with fullscreen. I do have the issue with OC settings not applying, however.

    I did disable the Game Bar notification from showing up.
     
    Last edited: Apr 18, 2017
  8. N0bodyOfTheGoat

    N0bodyOfTheGoat Member Guru

    Messages:
    192
    Likes Received:
    0
    GPU:
    Sapphire Nitro R9 390 8GB
    Had this too, makes the mouse cursor jumpy too. Close the Flash containing window, butter smooth again.
     
  9. Gregorez

    Gregorez Member Guru

    Messages:
    145
    Likes Received:
    2
    GPU:
    CFX MSI R9 290 Gaming 4G
    Did this and still Old Blood and RAGE don't launch.

    Are you on Creators Update+17.4.2 ?
     
  10. urdus12

    urdus12 New Member

    Messages:
    7
    Likes Received:
    0
    GPU:
    msi r9 390 8gb
    driver 17.4.3 is broken for dx9 games........
     

  11. bryter

    bryter New Member

    Messages:
    7
    Likes Received:
    0
    GPU:
    Gigabyte 7950 Windforce
    We must really be two opposites because for me 17.4.3 and Windows 10 Creator Update is the first time I DON'T have UVD bug since 16.7.2. I switched back to my original bios, I don't need my custom anymore.
    For me it was all the time. If I played a game it went to UVD state 2 all the times, if I did something like browsing (anything really) it went to UVD state 1 all the times, and never back to idle 300/150. Now it always go to the correct high frequencies when gaming and always back to idle. Thank you Bill Gates. EDIT: Sorry I'm on 17.4.3
     
    Last edited: Apr 19, 2017
  12. godknowswhy

    godknowswhy Member Guru

    Messages:
    132
    Likes Received:
    1
    GPU:
    All sorts
    Can anyone narrow down on the UVD clock? Interesting bryter appears to be on Intel, whereas Seren appears to be on AMD... opposite results, same driver.
     
  13. bryter

    bryter New Member

    Messages:
    7
    Likes Received:
    0
    GPU:
    Gigabyte 7950 Windforce
    Sorry I made a mistake, I'm actually on 17.4.3 drivers, the WHQL that came out yesterday
     
  14. Chastity

    Chastity Ancient Guru

    Messages:
    1,981
    Likes Received:
    498
    GPU:
    Nitro 390/GTX1070M
    Not here. Blanket statements suggesting all DX9 games are broken should be avoided. Next time list titles that were tested so things can be confirmed by others.
     
  15. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    7,004
    Likes Received:
    137
    GPU:
    Sapphire 7970 Quadrobake
    It's disabled for me too. Are you sure that RadeonPro is actually working? You have OSD? Are you sure that the games are running in actual/real fullscreen?
     

  16. Chastity

    Chastity Ancient Guru

    Messages:
    1,981
    Likes Received:
    498
    GPU:
    Nitro 390/GTX1070M
    Yes running fullscreen DX11 on 1703 + 17.4.3

    Note the OSD + FPS counter

    [​IMG]

    Needless to say, but RP has no effect when running in Mantle. :)
     
    Last edited: Apr 19, 2017
  17. urdus12

    urdus12 New Member

    Messages:
    7
    Likes Received:
    0
    GPU:
    msi r9 390 8gb
    medieval total war 2 csgo mass effect 2 and 3 dont launch bf1 bf4 witcher 3 metro last light redux all of the games that work are dx11 games
    :bang:
     
    Last edited: Apr 19, 2017
  18. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    7,004
    Likes Received:
    137
    GPU:
    Sapphire 7970 Quadrobake
    Of course not :p
    I'm running it in DX11. I get the same issues with both DAI and The Witcher 3. You're 1000% certain that they are in true fullscreen? Have you done any tweaks to your system/RP setup? How did you disable the Game Bar? When you alt-tab out of the games, returning to them is normal? I haven't tried 17.4.3 yet.
     
  19. Chastity

    Chastity Ancient Guru

    Messages:
    1,981
    Likes Received:
    498
    GPU:
    Nitro 390/GTX1070M
    No unusual changes. I disabled the Game Bar popup by checking the box saying Do not show me again. Just got my 390 back on Monday, DDU NV driver for gtx285 sli, installed 390 and installed latest 17.4.3 whql. RadeonPro is unmodified, added game profile in order to enable OSD. So no mods.
     
  20. Shakabutt

    Shakabutt New Member

    Messages:
    8
    Likes Received:
    0
    GPU:
    Sapphire R9 280
    happy to report that i got no more gcn 1.0 uvd clock bugs since updating to this driver and Win 10 creator.

    Have no ideea what they did but i was struggling with this bug since 16.7.2 .

    3 days and no bugs so far.Clocks perform normaly
     

Share This Page