AMD Radeon Catalyst 16.8.2 HOTFIX 16.30.2511.1001 (12/08/16) Download

Discussion in 'Videocards - AMD Radeon Drivers Section' started by CPC_RedDawn, Aug 12, 2016.

  1. AlleyViper

    AlleyViper Master Guru

    Messages:
    559
    Likes Received:
    114
    GPU:
    Strix 2070S|6700XT
    This has always happened to me from some years ago on a 7870, 3D OC isn't applied if Chrome/FF is running with hw accel. and has set clocks to a mid-state such as 501/1xxx. One way to go around that and have a 3D OC while Chrome was running in that mid clock state, was to use unofficial OC mode in AfterBurner. But since a few of the last drivers, only official (or the drivers Global Overdrive) seems to apply clocks, and unofficial mode became useless: after setting a clock and launching AB again, stock clocks are back.

    The recent "new bad thing" I reported it's the inability to revert to true idle clocks even after closing Chrome if mpc-hc has been launched while in that state, or after going to sleep at those mid-clocks.

    Before, it'd only be needed to close chrome to get back to 300/150 and then oficial mode 3D OCs would be applied. Now if one of the conditions above is met, it can't drop that wrong clock state for 2D.
     
    Last edited: Aug 24, 2016
  2. PieEyedPiper

    PieEyedPiper Master Guru

    Messages:
    628
    Likes Received:
    10
    GPU:
    RX 580
    My clocks went weird too with this driver. It's fixed now, wish I could say more. I just messed around with it, restarted, etc. for a few min and it stopped happening.
     
  3. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    8,125
    Likes Received:
    969
    GPU:
    Inno3D RTX 3090
    I have the same problem and reported it already. Please report it so that they will take a look at it. It's the same here. Something random will happen and the card will stay at 501/1500. It will boost correctly for 3D, but it won't ever go back to 300/150 again.
     
  4. cookieboyeli

    cookieboyeli Master Guru

    Messages:
    304
    Likes Received:
    47
    GPU:
    Gigabyte 1070 @2126
    Having this problem as well, clocks sticking to 1000/1500 on 280X instead of 1100/1500. Setting clocks to 1101 gets 1101 though, setting clocks to 1095 gets 1095, but setting clocks to 1100 gets 1000. (1100 is set in bios for both perf profiles)

    Also seeing it get stuck at around 500MHz on core in certain circumstances... :bang:
     

  5. Undying

    Undying Ancient Guru

    Messages:
    25,343
    Likes Received:
    12,754
    GPU:
    XFX RX6800XT 16GB
    What the hell are you guys talking about? I've got constant jumping (when needed) 1165/1500 - 500/1250 - 150/300 and its never stuck. This PC isnt turned down in 2 days.

    HWA in Chrome is On :

    [​IMG]

    Any way you can recreate the problem so i can test it?
     
  6. AlleyViper

    AlleyViper Master Guru

    Messages:
    559
    Likes Received:
    114
    GPU:
    Strix 2070S|6700XT
    Please check my post at the top of this page. The first step is to temporarily let Chrome stick clocks in the middle state 500/1500, you can do it by scrolling down for some time in facebook so it fills vram up until a certain point (scroll again until it sticks, if not for the first time). When this happens, Chrome should keep your card at those 500/1500 on idle. Up until now, it's regular behavior. (Closing Chrome should revert to 300/150)

    With those 500/1500 clocks forced in use by Chrome on the foreground or background, if you are using an official 3D OC mode such as AB default or Overdrive, they'll be ignored and your card will use the manufacturer's bios 3D default (at least on both my 7870 and 7970 which are models without boost). This has been regular behavior up til now too.

    Now, with Chrome idling your card at 500/1500 if you lanch MPC-HC and play something like a DXVA2 accelerated file, it'll for a moment use your bios default 3D clocks (instead of a custom 3D OC under oficial mode due to the above reason), and then, if the file isn't too demanding it should rest at 500/1500 back again while it plays. Now close MPC-HC, close Chrome, and the card won't be back to 300/150 with a plain desktop. This is the problem.

    Other way to trigger it by sleep is having Chrome open as in step one, in a state that is forcing those 500/1500 for itself. Now set the PC to sleep. After resuming, even if you close Chrome, you won't get 300/150, leaving the card stuck at 500/1500 on idle (and consequentially ignoring any 3D OC in oficial mode, only ramping to 3D bios clocks).

    PS: I've used 500/1500 as a general example for a 280X. In my pre-OC'd 7970 TOP hwmonitor would read 501/1400, 501/1375 for a vanilla 7970, etc. To be clear, I'm on W10 1607 x64, 16.8.2.
     
    Last edited: Aug 26, 2016
  7. Seren

    Seren Guest

    Messages:
    297
    Likes Received:
    16
    GPU:
    Asus Strix RX570
    Not sure if it helps but I'm using Firefox Dev x64 (hardware acceleration enabled on both browser and Flash but flash not enabled), not able to reproduce but I can with OpenGL games.
     
    Last edited: Aug 26, 2016
  8. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    8,125
    Likes Received:
    969
    GPU:
    Inno3D RTX 3090
    I don't even have Chrome, but it starts happening from a point on. I can't pinpoint the trigger exactly. It seems to be something between video acceleration and accelerated 2D somehow. I'm using Edge. Once it gets there, it will never go down until I restart.
     
  9. Pictus

    Pictus Master Guru

    Messages:
    234
    Likes Received:
    90
    GPU:
    RX 5600 XT
    Windows 10.0.14393 x64 + AMD R9 280x
    Crimson16.8.2 with No Man's Sky crashes sometimes during game
    explosion(space/ground), but with 16.7.3 this never happens.
     
  10. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    8,125
    Likes Received:
    969
    GPU:
    Inno3D RTX 3090
    It got stuck again for me. I still can't reproduce it reliably. What I have found though is that if I restart the driver using RadeonMod, the clock goes down to 300/150 as it should.
     

  11. Zemial

    Zemial Member Guru

    Messages:
    120
    Likes Received:
    0
    GPU:
    Sapphire Radeon 7970 @ CF
    Battlefiel 1 Beta ==> insane flickering when CF On. Good news is that my old 7970 can run the game ultra details on (except. fxaa medium), avg. 50-60fps.
     
  12. Dennisbest

    Dennisbest Member

    Messages:
    27
    Likes Received:
    0
    GPU:
    Sapphire Radeon 7950
    With crosffire you mean right?
     
  13. realmadrid

    realmadrid Guest

    Messages:
    176
    Likes Received:
    0
    GPU:
    GTX 1050 TI MSI OC
    same probleme when open mediaplayer or video youtube clock stuck on 500/1350 voltage 950 and temp 45° never down until I restart pc this problem driver or what ??
     
  14. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    8,125
    Likes Received:
    969
    GPU:
    Inno3D RTX 3090
    It looks like it is. We have to report it to AMD so that it gets fixed. If anyone hasn't, please use the report form and report it to them.
     
  15. ultraex2003

    ultraex2003 Master Guru

    Messages:
    271
    Likes Received:
    93
    GPU:
    Amd 2x290 Cfx

    bro !!!same problem heavy flickering here with 2x 290 :eyes:

    i try win 10 and win 7 64 exacly the same !
     

  16. realmadrid

    realmadrid Guest

    Messages:
    176
    Likes Received:
    0
    GPU:
    GTX 1050 TI MSI OC
    i send report done
     
  17. SuckaB

    SuckaB Member

    Messages:
    18
    Likes Received:
    0
    GPU:
    Sappire Atlantis Radeon 9800SE --> softmodded
    290 x2 here... Insane flickering but fixed by turning on direct x 12 and restarting game.
    Performance sucks though, barely 70fps on medium settings (1440) no AA
     
  18. primetime^

    primetime^ Master Guru

    Messages:
    909
    Likes Received:
    17
    GPU:
    Sapphire RX Vega 64
    I can confirm a power saving bug effecting 7970 280x owners where the dam card throttles to UVD speed (in my case 850mhz) so the power saving glitches have finally made there way down the line to us! All them other times it never effected us....But dam if it dont now!

    [​IMG]
     
  19. moaka

    moaka Guest

    Messages:
    291
    Likes Received:
    9
    GPU:
    RTX 2070 Super
    Instant crash after one game of BF1 with 16.8.2 back to 16.7.3 for stable perf ( ok now ) .
     
  20. Luke7

    Luke7 Guest

    Messages:
    69
    Likes Received:
    1
    GPU:
    4 GB

Share This Page