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

Radeon Software Crimson Edition 16.10.3 Download & Discussion

Discussion in 'Videocards - AMD Radeon Drivers Section' started by SlackerITGuy, Oct 28, 2016.

  1. Romulus_ut3

    Romulus_ut3 Master Guru

    Messages:
    667
    Likes Received:
    137
    GPU:
    AMD RX 570 4GB
    Maybe you don't care, but the rest of us do.

    We clearly aren't overreacting. You flashed a custom BIOS that sets the UVD state 2 to your 24/7 OC clocks, but the rest of us who're using a stock BIOS can't apply OC clocks once the bug shows up.

    Since it doesn't bother you, kudos to you. But don't tell others not to complain because they have a right to. And that's the purpose of this forum to begin with.
     
  2. Undying

    Undying Ancient Guru

    Messages:
    11,559
    Likes Received:
    1,344
    GPU:
    Aorus RX580 XTR 8GB
    Thats right, Romulus. I did flash custom bios that sets UVD 2 state to my 3d clocks. Good to see you are paying attention. Maybe others should do it as well and avoid some issues.

    Thats why tools like Vbe7 is there for.
     
  3. Romulus_ut3

    Romulus_ut3 Master Guru

    Messages:
    667
    Likes Received:
    137
    GPU:
    AMD RX 570 4GB
    Not everyone is comfortable flashing their GPU BIOSes, and I don't think this is something the end users should have to deal with in the first place as it's the responsibility of the IHS drivers itself. Not everyone is comfortable having to use CRU's Restart64.exe 10 times a day just to reset the clocks when they get stuck. It's this train of thought is what made nvidia get away with scandals like the 3.5 GB of VRAM on the GTX 970 and the promised Asynchronous Shader support on the Maxwell series of cards which never came and now is disabled from within their drivers simply because users were "okay" with it.
     
  4. Turanis

    Turanis Maha Guru

    Messages:
    1,414
    Likes Received:
    151
    GPU:
    Gigabyte RX500
    That UVD bug looks like is more visible on old 79xx series than "new" 200 series.
    Maybe they change something in driver to make you upgrade,kidding. :D

    Anyway,Firefox or Chrome + hardware acceleration should not be used.Also uninstall useless Flash and java,because security reason.
     
    Last edited: Oct 30, 2016

  5. densou

    densou Member Guru

    Messages:
    114
    Likes Received:
    4
    GPU:
    GTX 1060 ITX 3GB
    not enough, mr.

    Chrome/Chromium doesn't like Radeon GPUs even on Linux :bang: what about trying if the bug is still there with A DIFFERENT (and overall better :nerd: ) browser and video player? e.g. Pale Moon (install Adblock Edge + Ghostery 5.x as main extensions ;) ) + Potplayer ?
     
  6. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    7,004
    Likes Received:
    136
    GPU:
    Sapphire 7970 Quadrobake
    Guys, the GPUs are old, but they are still supported and this should be fixed. Also flashing your bios won't solve the issue that makes the card never to use the proper 2D clock and always burn more power.

    My card is flashed, but I still want it fixed.
     
  7. gx-x

    gx-x Maha Guru

    Messages:
    1,266
    Likes Received:
    97
    GPU:
    MSI 1060 6G Armor
    once you run 3dmark and see that clocks are stuck and card is not boosting to it's proper clocks, you are more comfortable with that then adjusting card's bios? Hmmm.... interesting. Flashing the bios was the first thing I did when I got my 280x...Albeit, being AMD's fault, it doesn't mean I should wait on them to fix it, since it's been like...what... 3-4 years now?

    Keep being uncomfortable with bios flashing if you want, but that's the only way to fix the card(s).
     
  8. Seren

    Seren Master Guru

    Messages:
    291
    Likes Received:
    14
    GPU:
    Asus Strix RX570
    Still getting major DX9 issues in multiple games even after the 27/10 Windows patch and 16.10.3... Over-riding with old driver files doesn't work either :/
     
  9. Romulus_ut3

    Romulus_ut3 Master Guru

    Messages:
    667
    Likes Received:
    137
    GPU:
    AMD RX 570 4GB
    The Bios flash doesn't solve the clocks getting stuck at UVD State 01.
     
  10. Chastity

    Chastity Ancient Guru

    Messages:
    1,899
    Likes Received:
    459
    GPU:
    Nitro 390/GTX1070M
    Has anyone thought of trying a 3xx vBIOS on their 2xx card and see if the bug goes away?
     

  11. AlleyViper

    AlleyViper Master Guru

    Messages:
    446
    Likes Received:
    52
    GPU:
    MSI RX480 GX 8GB
    On older CPUs you simply cant play a 60fps YT video without awful skipping, not to mention that color space will be wrong and colors washed out. For a matter of comfort with the bug, it's more practical to leave it disable instead of restarting the driver most times before launching a game as I resort to, but it has shortcomings like that one.


    As others commented, it's different when you manually flashed UVD #2 clocks/voltage to match your desired OC, but the UVD #1 will still be too high for idle. Something similar can be done via AB in unofficial OC mode with PowerPlay concerning UVD #2 clocks (Edit: Not at all for a 280X, that's only for non boost cards where 3D and the highest UVD state are both #0 on the vbios). Btw, as UVD #2 is different (as a state) to a manually applied OC over the highest 3D clock, unless you also change base TDP on bios, +20% won't be applied but I guess you have covered that on VBE7.

    My post was a direct response to @passenger for a way to trigger the problem step by step with a common software combination, not a question about software alternatives as there can be many other conditions that trigger it. Thank you.

    At the time I've seen that on a 7970 (I rarely have 3dmark on my system) before a patch fixed it, it was exactly the same condition that happened when Chrome sets clock at UVD #1 in my step "1" example some posts back, due to video playing on 3DMark's GUI, only UVD #2 is used for 3D.
    Still, it was possible to bench with OC applied simply by setting MSI AB to unnoficial OC mode, no need for a bios flash.

    Also, let me be clear: Using AB in "unofficial overclocking mode with PowerPlay support" mode to set an OC will also allow the card to use manually defined 3D/OC clocks while the bug happens, as they seem to affect UVD #2, because my non-boost 7870/7970 will also use those OC clocks when playing video in a non-bug situation (unlike official mode). At least it seems to work currently with AB 4.3.0 and 16.10.3.
    But there's a chance that "+20%" will not be applied, I guess 7950 users will find it easier to test for throttling. The problem that remains are idle clocks, as with a bios flash.

    Edit: I've had a friend to test it on a 280X, but it doesn't seem to work, as UVD#2 isn't replaced by the AB OC (under or outside bug). So it might only work on older non-boost cards as the Asus 7870 DC2 V2 I'm testing in. On these non-boost cards, the highest UVD clock and 3D clock are both listed as #0 in VB7, unlike boost cards that use separate #0 and #6 ids.


    I guess only the R7 370 would be eligible over a R9 265, as probably older 7850 would have unsupported memory chips.
     
    Last edited: Oct 30, 2016
  12. Spartan

    Spartan Master Guru

    Messages:
    678
    Likes Received:
    2
    GPU:
    R9 290 PCS+
    No problem here on Hawaii.
     
  13. AlleyViper

    AlleyViper Master Guru

    Messages:
    446
    Likes Received:
    52
    GPU:
    MSI RX480 GX 8GB
    If it's in response to the UVD bug, it only affects Tahiti/Pitcairn on some systems. :)
     
  14. Rambo

    Rambo Master Guru

    Messages:
    266
    Likes Received:
    115
    GPU:
    RX 560 w8 4 Vega 56
    Omega has been released at 11.14, Crimsons - 11.15. Should we expected another big update at 11.16? AMD bought HiAlgo's technology a few months ago so They could do really good stuff.
     
  15. jmcc

    jmcc Member

    Messages:
    45
    Likes Received:
    0
    GPU:
    GTX 1050 Ti 4GB
    I have this issue with my R7 265, and until i read this i thought it was my VGA dying. So it is a driver problem? ok. Sometimes my video card stays at 450/1400 clock even when the computer is in idle. And when i enter a game it goes up to 900/1400 but does not reach card boost clock that is 925/1400. Also if i try using Afterburner to overclock it, vga clocks stays at 900/1400 no matter that I apply overclock using MSI afterburner. I have to turn off the computer (sometimes more than once, does not goes back to normal 300/150 clocks at the first time sometimes).

    I tried using windows power saving options to "balanced" instead of "maximum performance" but no result.
     

  16. AlleyViper

    AlleyViper Master Guru

    Messages:
    446
    Likes Received:
    52
    GPU:
    MSI RX480 GX 8GB
    Yes, that's exactly the problem. Your R7 265 is a CGN 1.0 Pitcairn such as the 7870 in my example. It'll ignore your OC because AB applies it to your boost clock id#, but on load it'll be stuck using the highest UVD clock instead (different id on vbios).

    Using 16.7.2 shouldn't give you that problem, unless there's something already loading the GPU (or using 2 displays on desktop use, resulting in higher idle clocks). If after a reboot you aren't getting back to 300/150, it might be due to Windows Fast Boot on (tbh, I find it strange).
    Other than that, you have the option to use CRU and run restart64.exe to reset the driver. Then you'll need to relaunch hwmonitor if monitoring with it, as it'll get stuck reporting the previous clock before the driver went down.
    Disabling HW acceleration on your browser or flash might help too.

    A more permanent fix is to edit your bios to set your permanent OC on both the boost clock and highest UVD clock so 900/1400 won't be used when stuck in UVD mode. You'll still be stuck at 450/1400 on idle, tough.

    Edit: @geko95gek for the post bellow: First time someone reports with a Thames GPU (same as 7970m), but as with Pitcairn and Tahiti, it's another CGN 1.0 card so it's seems to affect the whole family as Romulus_ut3 pointed. That really sucks on a mobile GPU for autonomy.
     
    Last edited: Oct 31, 2016
  17. geko95gek

    geko95gek Member

    Messages:
    24
    Likes Received:
    0
    GPU:
    Radeon HD 8970M 4GB
    Ok, weird thing. The UVD clock bug is back for me in 16.10.3. However, in 16.10.2 I dont have this bug.

    So, so weird?! Is AMD trying to test us, to see if people would notice lol
     
  18. Romulus_ut3

    Romulus_ut3 Master Guru

    Messages:
    667
    Likes Received:
    137
    GPU:
    AMD RX 570 4GB
    The UVD clock bug only affects GCN 1.0 it seems. I have it. I watch a couple of Youtube videos, close the browser, and it's there.
     
  19. z8373767

    z8373767 Member Guru

    Messages:
    174
    Likes Received:
    48
    GPU:
    Fury Nitro 1070/600
    Im lucker, because this bug is not annoying for me since 16.9.2. When im using Mozilla Firefox to surf on youtube and run the game, clocks is stuck on UVD, but if i close Firefox (game can still running), clocks back to normal.

    The Fastest way to instant fix clocks without restart PC is restart Video driver. You can force it in RadeonMod or restart.exe delivered with CRU.
     
    Last edited: Oct 31, 2016
  20. LocoDiceGR

    LocoDiceGR Ancient Guru

    Messages:
    1,904
    Likes Received:
    495
    GPU:
    Gigabyte R9 380 4G
    Thats i am waiting for :)
     

Share This Page