(04-10-2017 02:50 PM)johny66cz Wrote: [ -> ]Hi, I have a problem with new driver 17.4.1 and new atikmadg patcher. After overclocking the core in Crimson, frequency returns to default. I have RX 480 with modded bios.
That's not a patch issue. The patch does not deal with core overclocking.
(04-10-2017 07:14 AM)sugar Wrote: [ -> ]Sadly I have some issues with latest drivers. Win10 x64, 17.4.1 beta 1.3 CRU & latest 1.4.5 patcher. Basically on first boot everything works fine, I can patch the driver, add resolutions - it all works (assuming I just restart the driver itself), however as soon as I reboot - OS doesn't see GPU until I enable scaling and I have to keep it ON to be able to use GPU (change resolution in Windows, boot game whatnot). Unsure if its identical to the issue that was with previous drivers, but yeh. Let me know if I can help with bit more info.
I don't know what you mean. If the OS didn't see the GPU, you wouldn't be able to open Radeon Settings to enable GPU scaling. Are you seeing error messages? Describe what happens.
Nope, basically if I use CRU - after one reboot I can't change any of the settings in Windows - like resolution is locked. Whenever trying to launch a game in that state it says that 3D adapter is not found, however I can open Radeon Settings and enable GPU Scaling - which fixes the issue, until I disable it... I will try latest drives to see if it is still the issue. Thanks!
My resolution is locked too with the latest drivers and i can't play far cry 4(message:Could not find suitable display settings)
(04-14-2017 04:09 PM)Dorian Wrote: [ -> ]My resolution is locked too with the latest drivers and i can't play far cry 4(message:Could not find suitable display settings)
(04-14-2017 05:42 AM)sugar Wrote: [ -> ]Nope, basically if I use CRU - after one reboot I can't change any of the settings in Windows - like resolution is locked. Whenever trying to launch a game in that state it says that 3D adapter is not found, however I can open Radeon Settings and enable GPU Scaling - which fixes the issue, until I disable it... I will try latest drives to see if it is still the issue. Thanks!
This seems like an unrelated driver bug. What video card do you have? Is this happening with DVI or HDMI? What resolutions are you adding?
The issue with lock resolution is gone with the latest drivers (17.4.3).BTW my card is Sapphire RX 460 2GB.So everything is fine again.Lets play Dark Souls 3
I need some guidance on gpu serwer I am working on.
I have bsod issue when the 6th GPU is installed.
'Attempt to execute noexecute memory'
My cards - rx570. Modded bios. When I use bios signature patcher with 6th card onboard I have bsod. When I unplug the 6th card win10 boots but one card is not patched - error 43 (4 are patched). The same with 4 cards plugged. 3 working - one not. I have managed to boot win10 with 5 cards onboard two times, but after restart again one card gets error code 43.
Drivers 17.4.3. With older drivers and rx470 everything worked fine, but rx570 requires 17.4.3.
I've spent 2 days to resolve this issue and failed. Please help. I have tried every single step I've read on this forum. Nothing worked.
(04-21-2017 08:49 AM)levap Wrote: [ -> ]I need some guidance on gpu serwer I am working on.
I have bsod issue when the 6th GPU is installed.
'Attempt to execute noexecute memory'
My cards - rx570. Modded bios. When I use bios signature patcher with 6th card onboard I have bsod. When I unplug the 6th card win10 boots but one card is not patched - error 43 (4 are patched). The same with 4 cards plugged. 3 working - one not. I have managed to boot win10 with 5 cards onboard two times, but after restart again one card gets error code 43.
Drivers 17.4.3. With older drivers and rx470 everything worked fine, but rx570 requires 17.4.3.
I've spent 2 days to resolve this issue and failed. Please help. I have tried every single step I've read on this forum. Nothing worked.
What Mainboard are you using? I have the exact same problem with RX580s. My Mainboard is a Biostar TB250-BTC with 4GB RAM and G3930. I also flashed back the old Bios and the same problem exists even without modded Bios. Therefore, I think it is either the Mainboard, which is causing trouble or the driver. So my question to you again: Which Setup are you using? If you are using a different mainboard, it is most certainly the driver.
I use asRock H81 btc pro, intel g1840 and 8gb of memory
I think there is a bug in 17.4.3 ati driver.
Yeah I think so, too at this point. I think it is a good idea, if everybody, who has this issue contacts AMD to push them to release a fix for this.