- Aug 25, 2001
- 56,571
- 10,206
- 126
Can someone point out some suggestions?
I was running 16.11.4, on an RX 460 4GB Nitro card, that had it's shaders unlocked via BIOS mode.
I tried to install 16.12.1, and it said it installed. I clicked "restart later", and then restarted manually.
Waterfox gave an app exception error when shutting down, and then upon restart, was stuck in low-res screen.
Windows will only let me go up to 1360x768, no higher. I'm on a 4K display.
Attempting to open Radeon settings, brings up a message, that no AMD video card / drivers are detected.
I've attempted to install 16.12.2 as well, but that seemed to only want to re-install the driver that was already on there that failed.
I'm running Win10 64-bit 1607, with an i5-6400 overclocked a bit.
I never had issues with re-starting with my original drivers on there, after doing the shader unlock.
Could AMD have had a "poison pill" in their drivers, that detected and disabled shader-unlocked cards? Would AMD actively try to destroy hardware like that?
I was running 16.11.4, on an RX 460 4GB Nitro card, that had it's shaders unlocked via BIOS mode.
I tried to install 16.12.1, and it said it installed. I clicked "restart later", and then restarted manually.
Waterfox gave an app exception error when shutting down, and then upon restart, was stuck in low-res screen.
Windows will only let me go up to 1360x768, no higher. I'm on a 4K display.
Attempting to open Radeon settings, brings up a message, that no AMD video card / drivers are detected.
I've attempted to install 16.12.2 as well, but that seemed to only want to re-install the driver that was already on there that failed.
I'm running Win10 64-bit 1607, with an i5-6400 overclocked a bit.
I never had issues with re-starting with my original drivers on there, after doing the shader unlock.
Could AMD have had a "poison pill" in their drivers, that detected and disabled shader-unlocked cards? Would AMD actively try to destroy hardware like that?