Download AMD Radeon Software Crimson 16.8.3 drivers

s0x

2016-08-31 23:13

Thanks, and thanks also to @Luke7 (http://forums.guru3d.com/showpost.php?p=5329031&postcount=80) 16.8.3 (16.300) vs 16.8.2 (16.300) vs 16.6.2 (16.200) Firestrike: http://www.3dmark.com/compare/fs/9997140/fs/9857309/fs/9803001 Still better scores for me on the 16.200 branch of drivers; same with the API overhead on DX11 being higher on this newer branch (for me at least).

#5329095

passenger

2016-09-01 00:52

Thanks men, will test them tomorrow.

#5329118

AlleyViper

2016-09-01 02:09

Idle clocks bug on 7970 :\

#5329146

THEAST

2016-09-01 06:10

A random blank or colored screen may be experienced intermittently on some Radeon RX 400 series products while gaming.

Was anybody actually experiencing this that they have fixed it now? I have seen at least 10 people in this board alone, including myself, who are experiencing the clock bug with 79XX/280 cards and this is not even acknowledged in this driver; yet I don't remember seeing anybody reporting the issue mentioned in the changelog...

#5329154

primetime^

2016-09-01 06:55

Was anybody actually experiencing this that they have fixed it now? I have seen at least 10 people in this board alone, including myself, who are experiencing the clock bug with 79XX/280 cards and this is not even acknowledged in this driver; yet I don't remember seeing anybody reporting the issue mentioned in the changelog...

the clock bug where it drops to UVD speed (850mhz) all of a sudden for NO ****ING REASON and fps drops to 40 because of it lol. Im so ****ing pissed....up till now the drivers have been great for this card...How they **** up cards this old?:bang: I thought UVD for for like playing videos and stuff...Why the GD driver clock down in the middle of a game? Im very much interested in if someone has found a work around or something to this issue....games dont play very good at 850mhz:bang: Near as i can tell clock blocker and radeon mod have no effect on correcting this bug either..really sucks! I cant speak for others but i have indeed reported it as a driver bug to AMD.

#5329225

Undying

2016-09-01 11:54

Idk, primetime i just played BF1 with a new driver, 1165mhz the whole game. I've never seen any drop in core clock. Idle clocks also 150/300 it isnt stuck in 500/1250. Can any other Tahiti owners report their experience? I didnt see any flickering in BF1 with this driver, compared to yesterday with 16.8.2. Game also seems smoother, no stuttering on my part. One more thing, primetime. When you are flashing your bios, UVD isnt supposed to be set at lower clock (old Pill Monster trick) It should look like this (my bios) : https://s17.postimg.org/o8f7w573j/Untitled.png https://s13.postimg.org/dx19doz07/Untitled.png

#5329231

Garwinski

2016-09-01 12:19

For some reason with Battlefield 1, with crossfire I have lower than 30 fps with this driver, while when using only 1GPU yesterday with 16.7 or something, I got mostly around 50 fps. Both my gpus have steady 3d clocks and gpu usage on both cards is around 60%, so it would seem that I should be having higher fps as more of my pc is being used, or at least not lower fps, but it is not the case. EDIT: From ultra to medium, I have around 25 fps, when I set the preset to Low, I get around 40fps. Strange that that is the only setting that impacts performance noticeably.That 40fps is still lower than the 50fps on preset High which I got yesterday though. Nothing is maxed out in terms of usage(CPU, RAM, GPU, SSD).

#5329267

realmadrid

2016-09-01 13:46

Idk, primetime i just played BF1 with a new driver, 1165mhz the whole game. I've never seen any drop in core clock. Idle clocks also 150/300 it isnt stuck in 500/1250. Can any other Tahiti owners report their experience? I didnt see any flickering in BF1 with this driver, compared to yesterday with 16.8.2. Game also seems smoother, no stuttering on my part. One more thing, primetime. When you are flashing your bios, UVD isnt supposed to be set at lower clock (old Pill Monster trick) It should look like this (my bios) : https://s17.postimg.org/o8f7w573j/Untitled.png https://s13.postimg.org/dx19doz07/Untitled.png

it work thank you no more damn bug clock :banana: https://s10.postimg.io/x9hg1qcc9/Sans_titre.png https://s15.postimg.io/gdbnvc1gr/Sans_titre2.png https://s3.postimg.io/u7qq9vaer/Sans_titre3.png

#5329280

edilsonj

2016-09-01 14:02

Thanks. Another round to DX12 crossfire or SLI support.

#5329327

go4brendon

2016-09-01 15:48

Been waiting for this yay ty

#5329334

OnnA

2016-09-01 16:05

New Driver working OK so far 🙂

#5329335

cod6da

2016-09-01 16:08

need new driver for de md

#5329341

The Mac

2016-09-01 16:25

need new driver for de md

? New AMD CrossFire profile added for DirectX® 11: Deus Ex™: Mankind Divided Battlefield™ 1 Beta

#5329357

primetime^

2016-09-01 16:56

Idk, primetime i just played BF1 with a new driver, 1165mhz the whole game. I've never seen any drop in core clock. Idle clocks also 150/300 it isnt stuck in 500/1250. Can any other Tahiti owners report their experience? I didnt see any flickering in BF1 with this driver, compared to yesterday with 16.8.2. Game also seems smoother, no stuttering on my part. One more thing, primetime. When you are flashing your bios, UVD isnt supposed to be set at lower clock (old Pill Monster trick) It should look like this (my bios) : https://s17.postimg.org/o8f7w573j/Untitled.png https://s13.postimg.org/dx19doz07/Untitled.png

Have you tried the dx12 path as well? usually i can tell the clocks are triggering UVD when the fps number turns red lol. I will try modifying the bios...but i already tried it once last night. It sort of worked except the gpu voltage was not jumping up like it normally would...and would ctd every time i would start the game. I flashed it back and it was working fine again until the UVD throttle hit me again. Heres the thing. I suspect its the xbox dvr app triggering the power saving. Seems like the clock bug always gets triggered when taking a screenshot or starting video dvr almost every time. The bad thing is i think the clock bug triggers a few times even when i didnt take a screenshot, but i could have accidentally hit windows/G unintentionally.

#5329363

PrMinisterGR

2016-09-01 17:07

Another issue is that the card won't drop clocks UNDER 501/1500 either. For me the card clocks correctly in game (my vbios is like Undying showed), but it will not clock down to 300/150. I have to restart the pc or reset the driver using RadeonMod, for it to behave correctly. I wonder if we all get the same bug, just with different manifestations due to different boards/bios revisions. I have also created a thread in the official AMD community forums about it. AMD doesn't seem to care about this forum any more, but if all of us post in their community they have to at least take a look. https://community.amd.com/message/2745858

#5329366

Yxskaft

2016-09-01 17:12

Has anyone tried Battlefield 1 with these drivers? Any difference in performance for both DX11 and DX12?

#5329375

primetime^

2016-09-01 17:39

one of the odd issues with modding my bios is it shows 1.2 volts for gpu voltage, but it actually runs around 1.275 even though VB7 shows 1200. What ended up happening after i tried playing with the changed UVD speed (i changed it to 1100mhz instead of 850), i could not even start a game..it would just sorta never fully start. When this was happening i looked at the gpu voltage and it was under 2 volts lol (which explains the issue lol) Its like what VBE7 sees as actual values is not what these xfx cards really actually uses lol. Anyways i shouldn't have to modd a perfectly working bios to begin with, when its been perfect up till they gimped my performance with the 16.8 (? i believe when it started) I did remove the xbox app to at least see if it was triggering UVD some how...now BF1 is offline again! (so i have to wait to test fully)

#5329376

primetime^

2016-09-01 17:42

Maybe AMD driver team was told to GIMP our drivers so we buy new RX480's lol. They stole a play for nvidias play book lol!:puke2:

#5329378

Maxima

2016-09-01 17:44

WTF These AMD drivers are just causing hard freezes for me, and I'm not using any Windows insider builds. I then have to go into safe mode to clean out the driver otherwise it won't boot. It's an enduro laptop w/ 8850m, if that matters.

#5329379

primetime^

2016-09-01 17:45

Another issue is that the card won't drop clocks UNDER 501/1500 either. For me the card clocks correctly in game (my vbios is like Undying showed), but it will not clock down to 300/150. I have to restart the pc or reset the driver using RadeonMod, for it to behave correctly. I wonder if we all get the same bug, just with different manifestations due to different boards/bios revisions. I have also created a thread in the official AMD community forums about it. AMD doesn't seem to care about this forum any more, but if all of us post in their community they have to at least take a look. https://community.amd.com/message/2745858

All this CANT be just a coincidence with all us having same series of cards, but different bios and actually cards. I have never actually had clock bug anywhere like this before (except 3dmark, which was there fault)