I also have been getting this same error a lot with the past two driver sets, though I have a R9 Fury from Asus. There's absolutely no pattern to the crashes - it's happened when I've been standing around in XIV, when I've been crafting, and when I've been in dungeons; it would make sense if it happened under heavy stress like a raid or a dungeon, but not when I'm literally just standing in my apartment, which is a low key instanced zone.
I am on the current drivers, I went back to the last set of drivers, and the set before that. Nada mas difference. I'm seriously considering giving up on AMD and going for the new Star Wars nVidia cards, not just for my SW love, but in hopes of being able to play the game without crashes - which is sad because I've had an AMD card of some sort for like the past ten years after nVidia's performances slumped a bunch due to bad drivers. Guess now the wheel has turned and it's AMD's time to lack at driver architecture design.
I think what it is is the relive drivers interaction with windows 10.
Obviously, it needs to be fixed so and its been so long, so I'm going to
jump ship at the end of this year, but in the meanwhile, I found that the
drivers actually break my start menu. At first, I kept deleting the
drivers and reinstalling them to fix the start menu, but after a few
crashes, if you reboot, your start menu won't work, but I think it actually
stops the crashes. I've been using 17.8.2.
Sucks that I can't use my start menu, but better than crashing mid game
over and over.
If you manage to break the start menu there should be two instances of
Radeon Settings in your lil arrow menu on the bottom right. I've learned
the two instances is what breaks the start menu.
Sad its come to this right?