thats not an AMD issue. that's not a GPU issue.
i've had that happen a dozen times across nvidia, intel, and amd cards on both windows, linux, and mac with both firefox and chrome.
your issue with the audio is common. on my old 970's this would happen where the audio on the gpu would become the default and I would have to switch back to my regular sound card. i use to have this issue with my onboard audio and dedicated pci-express sound card until i disabled it in my motherboards bios.
also resetting the bios before driver install? that's pointless to do. did you ever go back and reset all your motherboard settings back to what they were before you reset them back to defaults? you might of actually be causing issues with running it as default. default isn't always best and doesn't actually always work. the motherboard is designed to be manually set by the user (unless you know, its a premade dell). defaults are just there to boot up enough to go into bios or into the OS for something.
Wow, that looks like the starting of some old hand drawn Mario level. lol. Did your XFX card come with a driver disc/And did DDU maybe nuke yours? People tend to think it'll only pull off your AMD catalyst/crimson ones or nvidia equivalent. I know there's a XFX driver disc iso floating around on mega, not sure if it's for reference though. Our card (not a 480, an r7 series) got really wonky without putting on the sapphire drivers first after doing an uninstall. It seems frivolous with new ones, but sometimes there are some specific functions the partner card needs. I've seen some Sapphire Nitro+ fans not going without them or even not being detected.
Sorry if none of that even applies to you, wish I had some helpful insight for you.
My BIOS is the latest, the september release. I have several hard drives, including 1 with my old Win 7 to Win 10 upgrade, which are bootable, but I wanted to run my system on the 500 gig SSD, that was going to be my main. Yes, I know how BIOS works, on some occasions I had to look up some of the newest available settings. Tried it with factory defaults, optimized factory defaults, tweaked, just about everything and the kitchen sink. Everything is up to date. All my drivers are fresh downloads of newest versions from their respective sources and its a Brand Spanking new OS install right down to brand spanking new, re-downloaded media Creation Tool.
As far as installing and re-installing the Crimson drivers, I tried it in just about EVERY variety, 1st without any additional cleaning, then when I had problems with CCleaner, then with DDU, and yes, I know how to use CCleaner, double checked every single item and registry entry before cleaning. Then rinse / repeat the process through several versions of crimson up to the 16.9.1
I am currently on clean reinstall of Win 10 64 bit, build 1607 with latest updates and Crimson 16.8.3. I won't touch 16.9.1 due to what I already posted in my original post and again above. The only game that is up on my system is GW2, and I just noticed another anomaly, the following screenshots are as follows:
Played about 3 hours of WVW, heavy to very heavy battles ( 3 way map que), alt-tabbed to take the screen, the 2nd one is about 30 seconds after I logged out as system was returning back from heavy load, you can tell which is which easy enough by the CPU load. So you guys can see, yet another anomaly (bug?), thats in addition to that corruption type stripe I get as windows is booting up and in addition to other regular issues such as mouse cursor corruption, fans not operating properly at defaults, a single game crashing here and there, etc. All that other small stuff you can find in the other posts on these and other forums. I should note, this happens only with Crimson drivers and the RX 480, when I ran on my 7870, even as struggling as that was, and Catalyst 15.11 things were showing up correctly, none of the small bugs either, just everything was slow and of course I had to scale down the res and other settings as applicable which sucks.
I have made up my mind and I am definitely going to RMA this, if things go well I will get store credit and shell out another $150-200ish and just get a 1070, if not then I'll be stuck with another AMD which at this point I would prefer to be just entirely rid of due to amount of headaches, hassles, bugs, workarounds and most of all, time I have lost having to research all that stuff and try to fix it. I want my computer and gaming to be my hobby, not working on video card just trying to get it to function correctly.
I made this post in really last ditch hopes that some dev, or someone, might come up with some definitive and actual effective fix for these things, but I wasn't holding my breath for it. Hopefully some dev somewhere will see it and they will actually work on this kind of stuff so other people won't have to go through what I am experiencing.
To clarify, an RMA is to the manufacturer and will get you a replacement card. Returning it to the place of purchase would get you a refund or a replacement (depending on store policy). Hope you have a positive resolution.
thats not an amd driver issue. that's hwmonitor not reading the voltages correctly. i've had it done that to me before in the past even on nvidia cards. even hwinfo another popular monitor does this as well.
also nvidia is having its own fair share of issues so don't think the grass is greener on the other side:
>144hz flickering since pascal launch
>random fps drops since newest driver
>pascal high latency issue - ongoing - fixes in newer drivers sorta relieved some of it but not fully
let alone the typical complaints you see here on these very forms, even complaints like yours cropping up every month if you take the time and go through nvidia's own forums. such as the BSOD / unable to install drivers from holiday 2015 time frame. or even the drivers that fried a few display models in nvidia gpu equipped laptops.:
oh and the new geforce experience now requires a nvidia account to use some of its features such as shadowplay and also tracks everything you do now, even without a nvidia account. logs your game time, games installed, and such.
so really you will be replacing one issue with another.
If YOUR experiences are beyond YOUR control, what makes you think a 1070 would solve YOUR issues??
Because won't have to deal with crimson and all the crap it brings with it.
I can hang with small stuff, be patient for updates both from hardware manufacturers and microsoft, dips in FPS, little glitches here and there, those are to be expected with new tech and I can be patient. Tracking thing, either doesn't bother me or I can disable it or simply prevent the data from being sent in a huge and simple variety of ways.
144 MHz issues are not applicable to me, I am on this monitor PB277Q | Monitors | ASUS USA
However total system corruption resulting from driver install, +very possible permament hardware damage it caused, +the mouse cursor thing making things very difficult to use, or impossible in any situation where mouse cursor precision is required (for example graphics editing etc.) and which happens often, those are not things I can handle.
The hardware on this card was good up until the 16.9.1 drivers that did this. I like the removable fans, GPU, memory performance is good, temps are OK, the only thing I see that has some serious room for improvement is the heatsink design, double that since I have spent over a decade working with heatsinks, and heat and its dissipation in general. They could have made it much better at transfer without increasing the costs, in fact, would have probably reduced them, and make the board less noisy at same time when fans run at or close to max RPM and increase the noise levels as the air moves through it. But that is a small thing in comparison with this.
I'd rather have FPS dips and whatnot then what you see in my original post. FPS dips, screen flickers etc. are all annoyances that shouldn't be there, but they are not total and complete system breakers.
I'm really wondering if the recent GPU clock fixes included in the 16.9.1 have caused this, because my card is factory OCed, I have actually gotten it to run really well on the 16.7.2 with 2% underclock which brings it closer to reference clock in the past. Then, I updated the drivers cause fixes for the annoyances and this happened....
I would really like drivers, with fixes for bugs that won't kill my video card. It is unfortunate that it looks like I will be just receiving a replacement, I would really love to completely get away from the drivers that are known and confirmed to this sort of crap that you see here.
The solution isn't that complicated. Test the card in a different system (including a different monitor) and if it exhibits the same symptoms, RMA it. If you get a replacement card and it exhibits the same symptoms, it is very likely something else going on with your system.
You act as though Nvidia hasn't released WHQL drivers that have killed cards. They have. Use Google and you'll find examples quite quickly.
Drivers did not kill your card. Perhaps it was a bad card. Perhaps something in your PSU, or resetting the MB bios to default caused some voltage issue. You're are the only person to report such an issue. You reset your MB bios for a GPU driver install, so who knows what else you might have done.