Download AMD Radeon Software Crimson 16.8.3 drivers

raken

2016-09-01 18:16

Battlefield 1 wrong driver I had the wrong driver update your driver message after upgrading to this driver and new Windows insider update. The problem is in Battlefield 1 forums and you have to change the number of your driver or you won't be able to connect. After changing the number I was able to connect again. Here's the forum posting with the fix. https://forums.battlefield.com/en-us/discussion/20023/please-update-amd-radeon-driver-help

#5329403

primetime^

2016-09-01 19:09

I think it was the xbox app after all......UVD 850mhz never triggered today so far! Kinda of a handy app but i can live without it lol https://lh3.googleusercontent.com/agnvr9SBHo-klbjhHsvGGQ4nnXnWvuRDtCpSkF-hOVMI_1n3hyfkjo14ZVaRJsoBgJEYotYZQDrXA8y0KVq11lIDfetU6VcMNMH_gMWYcI8EXEmgcgVU6c1M84iIviHiKgQR1SK-D0WhR0xWImHHPC-u0aksxr7fatKrZPk4ztVoasdLIKV6xJaDX_lwLxaLUKYPEAIlYcitIcBmYkRBO-1jS9zZFQYCuTqaJkEyTcXNa5h1dZFKMvLT7S5Kr2P7Qyeo8dpDlCCZQjqU4hyz4yx2xUukCxgB-Ibg_qW6fFLvMN-bsgkR2cn9gN54-tOw33kMHtDV1hXeAWNz5_zSNtB6034kwQiKax0tiMp9iQC6yM6IKTB8CAosIZ7_Pcgdv6CwaoFgFPA7zI1i_U65gQ-JCFvvxrvUTHjq_NqqLm1RFE7ZJsuXUyC83sRu77rDvFVo9dF4baQMiTlR7r_U8L5H4pW_-YWro3Y-sfycuct8XNTa_HIBHGwmjfd-Zkzq-aBp_zLQKyyHU5RgGj1fAlQ89zHprnvGf_nFoUbqoh4RuOX_lp7egSiEyhS0bQY2KZjDyIOJ_qE9KQQFMWUjyLmqGMjKfVQyPB4TTXuUC7BIUMcN=w1384-h804-no Several rounds of BF1 dx12 and UVD never kicked in!

#5329412

realmadrid

2016-09-01 19:33

wtf is not fix even flash bios :bang: the bug is come again :bang::wanker: https://s13.postimg.io/gr40pql6f/Sans_titre.png

#5329413

realmadrid

2016-09-01 19:36

I think it was the xbox app after all......UVD 850mhz never triggered today so far! Kinda of a handy app but i can live without it lol https://lh3.googleusercontent.com/agnvr9SBHo-klbjhHsvGGQ4nnXnWvuRDtCpSkF-hOVMI_1n3hyfkjo14ZVaRJsoBgJEYotYZQDrXA8y0KVq11lIDfetU6VcMNMH_gMWYcI8EXEmgcgVU6c1M84iIviHiKgQR1SK-D0WhR0xWImHHPC-u0aksxr7fatKrZPk4ztVoasdLIKV6xJaDX_lwLxaLUKYPEAIlYcitIcBmYkRBO-1jS9zZFQYCuTqaJkEyTcXNa5h1dZFKMvLT7S5Kr2P7Qyeo8dpDlCCZQjqU4hyz4yx2xUukCxgB-Ibg_qW6fFLvMN-bsgkR2cn9gN54-tOw33kMHtDV1hXeAWNz5_zSNtB6034kwQiKax0tiMp9iQC6yM6IKTB8CAosIZ7_Pcgdv6CwaoFgFPA7zI1i_U65gQ-JCFvvxrvUTHjq_NqqLm1RFE7ZJsuXUyC83sRu77rDvFVo9dF4baQMiTlR7r_U8L5H4pW_-YWro3Y-sfycuct8XNTa_HIBHGwmjfd-Zkzq-aBp_zLQKyyHU5RgGj1fAlQ89zHprnvGf_nFoUbqoh4RuOX_lp7egSiEyhS0bQY2KZjDyIOJ_qE9KQQFMWUjyLmqGMjKfVQyPB4TTXuUC7BIUMcN=w1384-h804-no Several rounds of BF1 dx12 and UVD never kicked in!

what is xbox app ???

#5329415

primetime^

2016-09-01 19:46

what is xbox app ???

Well its a built in windows app from the store. Press Windows/G and it should open up the game bar overlay in your game. I was just using it for taking screen shots and on occasion taking video as well (in dx12 games since were still waiting for msi afterburner dx12 support)

#5329416

herpaderpa

2016-09-01 19:48

I think it was the xbox app after all......UVD 850mhz never triggered today so far! Kinda of a handy app but i can live without it lol

that makes sense as it uses the VCE(not sure)

what is xbox app ???

http://support.xbox.com/en-us/xbox-on-windows/social/record-game-clips-game-dvr-windows-10

#5329420

realmadrid

2016-09-01 19:51

i have disable dvr win10 i don't like it but probleme i here is not dvr https://s13.postimg.io/gr40pql6f/Sans_titre.png

#5329429

Romulus_ut3

2016-09-01 20:10

This clock bug must be a Windows Anniversary Update issue, because before upgrading to it, I didn't have this. Now I do. Using the latest WHQL. Edit: Come to think of it, it was present in the 16.8.2 which is why I reverted back to 16.7.3 WHQL in the first place. :infinity:

#5329430

PrMinisterGR

2016-09-01 20:11

Most likely it's that but please report it so that something is done about it.

#5329432

realmadrid

2016-09-01 20:12

This clock bug must be a Windows Anniversary Update issue, because before upgrading to it, I didn't have this. Now I do. Using the latest WHQL.

+1 i think is Anniversary Update me to

#5329437

primetime^

2016-09-01 20:26

+1 i think is Anniversary Update me to

Well i certainly didnt have any clock issues prior to the update. Hopefully my issues will stay fixed since removing the xbox app lol:)

#5329441

AlleyViper

2016-09-01 20:36

Report sent again to AMD regarding the idle clock problem in W10 AU. I've never faced weird floating 3D clocks under gaming because my card isn't a late GHZ model, so it has only one 3D clock (1000/1400) and remains there. Still, it'll ignore any 3D OC via software in oficial mode if idle clocks are stuck at 501/1400 and it transitions to 3D.

#5329446

The Mac

2016-09-01 20:43

+1 i think is Anniversary Update me to

there were a number of changes to the windows presentation manager and UWP with the Anniversary Update, so its certainly probable.

#5329447

PieEyedPiper

2016-09-01 20: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.

This sounds rather on point.

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.

Tahiti has a large vdroop built into its specification. That probably comes into play when you make changes. vcore of 1200 on tahiti will never be above anything even close to 1.2v when under load. To AlleyViper: Thanks for going more in depth.

#5329448

AlleyViper

2016-09-01 20:53

OT: Also, some apps only read the highest VID that is set for lowest ASIC, instead of the actual one under use. As an example, this 7970 at stock voltage is a 1.050V part (82% ASIC Q) and hwmonitor will read 1.170V VID, while AB reads the correct 1.050V VID, and GPU-Z reads the resulting 1.014V after droop. Edit: IIRC, when editing with VBE7 the VDDC you input will be set for all ASIC parts so your card will always use it in 3D, instead of showing only the highest VDDC for the lowest ASIC (that your card may never use) as when you open an original bios. As an example, for the above card, VB7 will show 1.170V on an untouched bios (that will cover all 4 ASICs with different values such as 1.025V, 1.050V, 1.125V and finally 1.175V for the original 7970) even if it'll apply only 1.050V on this 82% ASIC Q.

#5329453

PrMinisterGR

2016-09-01 21:09

This sounds rather on point. Tahiti has a large vdroop built into its specification. That probably comes into play when you make changes. vcore of 1200 on tahiti will never be above anything even close to 1.2v when under load. To AlleyViper: Thanks for going more in depth.

My voltage is set at 1.268V on the VBios, and all apps (hwinfo, GPU-Z, Afterburner), report 1.268V when under stress. The voltage varies, of course, but it does reach that when needed.

#5329476

cyclone3d

2016-09-01 22:33

For those of you with the 79x0/280x clock bug in Win10 - I saw mentioned on another forum that it was the XBOX Live app that was causing it. As soon as it is uninstalled, it supposedly stops having issues.

#5329478

Bleib

2016-09-01 22:50

This driver might have stopped the black or gray screen of "death" I've been experiencing, but these never occurred in games but instead in windows.

#5329482

Undying

2016-09-01 23:04

For those of you with the 79x0/280x clock bug in Win10 - I saw mentioned on another forum that it was the XBOX Live app that was causing it. As soon as it is uninstalled, it supposedly stops having issues.

But what if i need XBOX Live app? That's not a solution. I didnt see the problem myself yet but for the ones who did, report please to AMD.

#5329487

PrMinisterGR

2016-09-01 23:16

For those of you with the 79x0/280x clock bug in Win10 - I saw mentioned on another forum that it was the XBOX Live app that was causing it. As soon as it is uninstalled, it supposedly stops having issues.

Is the Xbox Live app causing it, or is it the DVR? The DVR is turned off. You can't uninstall the Xbox app in Windows 10. Also I'm playing Forza Apex and I want the app :P