Forum Discussion
You might use the following Cleanup Utility to remove old driver components before reinstalling the driver set.
https://www.amd.com/en/support/kb/faq/gpu-601
Thanks.
@EA_Barrywhich driver set do you recommend?
the latest one or an older one?
also thank you for ur reply
- 4 years ago
Faced the same problem. When you start the game, the computer goes into protection. I had to turn off the power. I managed to get around this problem. In the tdp settings, you need to set -50% (I did not try to set a higher value) and start the game. After starting the menu, you can return the settings back. (the same problem appeared in "layers of fear". Perhaps the problem is in the drivers.
- 4 years ago
could you find a stable driver? If so, please advise which one. (Rx 590)
- 4 years ago
EDIT: disregard everything I've said below. Although I've solved the error message, the whole computer keeps crashing while under heavy GPU load (unrelated to Apex). I suggest everyone experiencing crashes to test a heavy GPU load (for example, using something like https://foldingathome.org/ or another game) to rule out a hardware failure. In my case, I highly suspect the PSU is acting strange: will replace soon and update.
___
I had the same problem: skipped roughly 1 year of updates due to traveling, went back home and updated Adrenalin to the latest version and since then I'd get random crashes.
Specs: Win10, AsRock B350 Pro4, Ryzen 5 1600, RX580 8GB nitro+
I tried uninstalling all the GPU drivers and reinstalling them: no luck.
I then uninstalled Adrenalin and didn't reinstall it. I just let Windows do its thing and auto-install the default GPU drivers (without Adrenalin).
Make sure Windows does this, otherwise you'll be stuck at 60FPS and with no drivers.Right click on your desktop, select "Display settings" > advanced display settings, then check that refresh rate is the highest your monitor allows. If it's not, then wait for Windows to install the drivers.
In "Devices Manager", this is how the appropriate drivers looks like:
Another thing I did is disable the CPU overclocking (I was at 3.3mhz, with a base clock of 3.2mhz), but I'm pretty sure that was not the problem.