Sure I will try to help. Not sure why you are not able to get help from those you should be able to get from, the ones that made your card, not AMD. AMD makes the graphics chip that goes on the card that the manufacturer uses they are the first line of support. If they don't follow a reference design that can alter things even more, and most cards don't. So don't be fed up with AMD, your cards maker is the one that is supposed to give you support, did you ask them? Have you already asked AMD? Did you open a support ticket? There is a report link in Radeon Settings or on the contact us page of the website. These forums are users just like you and we are just helping each other as best we can. Just asking because the last chance seems harsh if this is the first you have reached out. I do get however how frustrating it is to spend good money for something to not live up to expectations. Unfortunately a common reality in our world today.
Now on to your issue. Make sure Windows is fully up to date, all updates even optional, especially the .Net ones. Your specs look good so I would download the latest driver. Install it using the custom not express option and choose clean install. Upon successful install and restart we are going to change a setting. Go to Radeon Settings, Gaming, Global Settings, Global Wattman, look down until you come to the "Power Limit Slider" slide it all the way to the right to it's maximum. This will raise the power ceiling a bit but is still in normal operational range and is not over-powering. Make sure your Windows Settings are set for "High Performance" too not on balanced which is default. If this does not fix things I would look to other usual suspects like turning off Overlays from the game launching software you use such as steam or origin. Good luck and report back if this doesn't help we can go from there.
Oh I have the Skyrim game, have not played it in a couple years but will fire it up tonight and see if it runs okay for me. My system is a RX 580 and i7 7700k so similar enough that if its a driver bug it shouldn't work for me either. Will write back what I find.
