DeepCool LS720 (LCS) review
Fractal Design Pop Air RGB Black TG review
Palit GeForce GTX 1630 4GB Dual review
FSP Dagger Pro (850W PSU) review
Razer Leviathan V2 gaming soundbar review
Guru3D NVMe Thermal Test - the heatsink vs. performance
EnGenius ECW220S 2x2 Cloud Access Point review
Alphacool Eisbaer Aurora HPE 360 LCS cooler review
Noctua NH-D12L CPU Cooler Review
Silicon Power XPOWER XS70 1TB NVMe SSD Review
Download AMD Radeon Software Crimson 16.8.3 drivers
You can now download the new AMD Radeon Software Crimson Edition drivers release 16.8.3 driver released for Deus Ex: Mankind Divided and the new Battlefield 1 Beta.
Download Nvidia GeForce 372.70 WHQL driver - 08/30/2016 06:07 PM
Download the Nvidia GeForce GameReady 372.70 WHQL driver as released by NVIDIA. This driver provides the optimal experience for World of Warcraft: Legion, Battlefield 1: Open Beta, Deus Ex: Mankind Di...
Download Nvidia GeForce 372.54 WHQL drivers - 08/16/2016 08:54 AM
Download the Nvidia GeForce GameReady 372.54 WHQL driver as released by NVIDIA. nVIDIA GeForce Game Ready WHQL display driver version 372.54. This driver provides optimal experience for No Man&r...
Download AMD Radeon Software Crimson 16.8.2 driver - 08/13/2016 08:55 AM
You can now download the new AMD Radeon Software Crimson Edition drivers release 16.8.2 driver released for No Man's Sky, also some bugs related to "Overwatch," have been tackled like i...
Download AMD Radeon Software Crimson 16.8.1 driver - 08/09/2016 09:28 AM
You can now download the new AMD Radeon Software Crimson Edition drivers release 16.8.1 driver which adds improved power distribution for the Radeon RX 460 / 470 and 480 as well as performance improv...
Download AMD Radeon Software Crimson 16.7.3 WHQL driver - 07/29/2016 09:13 AM
AMD released a new driver build today, interestingly enough it contains just one optimization, and that is Rise of the Tomb Raider performance increase up to 10% versus Radeon Software Crimson Editio...
cod6da
Member
Posts: 37
Joined: 2014-11-26
Member
Posts: 37
Joined: 2014-11-26
#5329335 Posted on: 09/01/2016 04:08 PM
need new driver for de md
need new driver for de md
The Mac
Senior Member
Posts: 4404
Joined: 2011-08-24
Senior Member
Posts: 4404
Joined: 2011-08-24
#5329341 Posted on: 09/01/2016 04:25 PM
?
New AMD CrossFire profile added for DirectX® 11:
Deus Ex™: Mankind Divided
Battlefield™ 1 Beta
need new driver for de md
?
New AMD CrossFire profile added for DirectX® 11:
Deus Ex™: Mankind Divided
Battlefield™ 1 Beta
primetime^
Senior Member
Posts: 909
Joined: 2013-10-24
Senior Member
Posts: 909
Joined: 2013-10-24
#5329357 Posted on: 09/01/2016 04:56 PM
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) :
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.
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) :
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.
PrMinisterGR
Senior Member
Posts: 8004
Joined: 2014-09-27
Senior Member
Posts: 8004
Joined: 2014-09-27
#5329363 Posted on: 09/01/2016 05:07 PM
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
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
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 14900
Joined: 2014-10-25
New Driver working OK so far