Topic: Windows 10 1709, AMD Drivers, and Afterburner - page 2. (Read 1087 times)
Has anyone tried one of the previous 4.4 beta versions? Do any of them work?
Im using the latest version with latest AMD Drivers.
12x RX 570 running fine, had the same issue with afterburner.
Sapphire STRIXX works fine, but i hate it.
I ended up undervolting and overclocking through the bios directly, and honestly it works better than afterburner
12x RX 570 running fine, had the same issue with afterburner.
Sapphire STRIXX works fine, but i hate it.
I ended up undervolting and overclocking through the bios directly, and honestly it works better than afterburner
Other general issues observed:
- Driver performance generally sucks, even with Patcher 1.4.6
- One system keeps reverting to a driver version from April 2017, even after a clean install of 17.11.1
The first thing I would do is switch to the blockchain driver, it was made for mining and helps a little. Never had a problem with afterburner.
It's the most recent version supported by the patcher and I know it works fine with 1709.
I read the blockchain version doesn't work with 1709, are you running it on 1709?
The Afterburner developers are claiming the problem with blank settings on Windows v1709 is a driver issue releated pixel patcher.
https://forums.guru3d.com/threads/afterburner-fails-to-display-clocks-on-patched-crimson-17-10-drivers.417926/
Maybe they will fix it but honestly it looks like they gimped Afterburner intentionally with multiple GPU builds because they are butt hurt about miners buying up GPU's
https://forums.guru3d.com/threads/13-gpus-and-or-latest-nvidia-driver-388-31-afterburner-crash-instantly.417993/
https://forums.guru3d.com/threads/13-gpus-and-or-latest-nvidia-driver-388-31-afterburner-crash-instantly.417993/#post-5493937
I reverted back to using the blockchain drivers on Windows 10 v1703 and Afterburner is working.
https://forums.guru3d.com/threads/afterburner-fails-to-display-clocks-on-patched-crimson-17-10-drivers.417926/
Maybe they will fix it but honestly it looks like they gimped Afterburner intentionally with multiple GPU builds because they are butt hurt about miners buying up GPU's
https://forums.guru3d.com/threads/13-gpus-and-or-latest-nvidia-driver-388-31-afterburner-crash-instantly.417993/
https://forums.guru3d.com/threads/13-gpus-and-or-latest-nvidia-driver-388-31-afterburner-crash-instantly.417993/#post-5493937
I reverted back to using the blockchain drivers on Windows 10 v1703 and Afterburner is working.
Interesting information, thanks for sharing this.
I'm getting by with Wattman right now.
After some success with a Single GPU Test Rig in updating to Windows 10 1709 with 17.11.1 Drivers and the latest version of Afterburner I decided to update 3 of my 7x GPU Rigs to this version.
Post the update, all 3 are having this common issue
I've tried the latest versions of DDU on affected systems and done clean installs of AMD Drivers.
Other general issues observed:
I have not yet run DDU in safe mode and obviously I know possible solutions are to revert to an earlier version of Windows 10 along with an older driver or just kick W10 entirely and move to SMOS.
I've seen several people out there indicate they are running this W10 build and these same drivers on rigs with success but I can't find anywhere a post where someone is experiencing these same issues.
I have not tried running 1709 with older more mining friendly drivers but I have found posts of people saying the drivers previously released will not work in 1709.
Anyone out there had similar experiences and found a solution that works in 1709?
Post the update, all 3 are having this common issue
- Afterburner 4.4.0 Final displays blank driver information for the card on all systems
I've tried the latest versions of DDU on affected systems and done clean installs of AMD Drivers.
Other general issues observed:
- Driver performance generally sucks, even with Patcher 1.4.6
- One system keeps reverting to a driver version from April 2017, even after a clean install of 17.11.1
I have not yet run DDU in safe mode and obviously I know possible solutions are to revert to an earlier version of Windows 10 along with an older driver or just kick W10 entirely and move to SMOS.
I've seen several people out there indicate they are running this W10 build and these same drivers on rigs with success but I can't find anywhere a post where someone is experiencing these same issues.
I have not tried running 1709 with older more mining friendly drivers but I have found posts of people saying the drivers previously released will not work in 1709.
Anyone out there had similar experiences and found a solution that works in 1709?
Use ATIKMDAG patcher if you use modded bios + set all cards individually to Compute instead of gaming mode.
Other general issues observed:
- Driver performance generally sucks, even with Patcher 1.4.6
- One system keeps reverting to a driver version from April 2017, even after a clean install of 17.11.1
Why are you running 17.11.1?
The first thing I would do is switch to the blockchain driver, it was made for mining and helps a little. Never had a problem with afterburner.
The Afterburner developers are claiming the problem with blank settings on Windows v1709 is a driver issue releated pixel patcher.
https://forums.guru3d.com/threads/afterburner-fails-to-display-clocks-on-patched-crimson-17-10-drivers.417926/
Maybe they will fix it but honestly it looks like they gimped Afterburner intentionally with multiple GPU builds because they are butt hurt about miners buying up GPU's
https://forums.guru3d.com/threads/13-gpus-and-or-latest-nvidia-driver-388-31-afterburner-crash-instantly.417993/
https://forums.guru3d.com/threads/13-gpus-and-or-latest-nvidia-driver-388-31-afterburner-crash-instantly.417993/#post-5493937
I reverted back to using the blockchain drivers on Windows 10 v1703 and Afterburner is working.
https://forums.guru3d.com/threads/afterburner-fails-to-display-clocks-on-patched-crimson-17-10-drivers.417926/
Maybe they will fix it but honestly it looks like they gimped Afterburner intentionally with multiple GPU builds because they are butt hurt about miners buying up GPU's
https://forums.guru3d.com/threads/13-gpus-and-or-latest-nvidia-driver-388-31-afterburner-crash-instantly.417993/
https://forums.guru3d.com/threads/13-gpus-and-or-latest-nvidia-driver-388-31-afterburner-crash-instantly.417993/#post-5493937
I reverted back to using the blockchain drivers on Windows 10 v1703 and Afterburner is working.
After some success with a Single GPU Test Rig in updating to Windows 10 1709 with 17.11.1 Drivers and the latest version of Afterburner I decided to update 3 of my 7x GPU Rigs to this version.
Post the update, all 3 are having this common issue
I've tried the latest versions of DDU on affected systems and done clean installs of AMD Drivers.
Other general issues observed:
I have not yet run DDU in safe mode and obviously I know possible solutions are to revert to an earlier version of Windows 10 along with an older driver or just kick W10 entirely and move to SMOS.
I've seen several people out there indicate they are running this W10 build and these same drivers on rigs with success but I can't find anywhere a post where someone is experiencing these same issues.
I have not tried running 1709 with older more mining friendly drivers but I have found posts of people saying the drivers previously released will not work in 1709.
Anyone out there had similar experiences and found a solution that works in 1709?
Post the update, all 3 are having this common issue
- Afterburner 4.4.0 Final displays blank driver information for the card on all systems
I've tried the latest versions of DDU on affected systems and done clean installs of AMD Drivers.
Other general issues observed:
- Driver performance generally sucks, even with Patcher 1.4.6
One system keeps reverting to a driver version from April 2017, even after a clean install of 17.11.1- Got this one resolved.
I have not yet run DDU in safe mode and obviously I know possible solutions are to revert to an earlier version of Windows 10 along with an older driver or just kick W10 entirely and move to SMOS.
I've seen several people out there indicate they are running this W10 build and these same drivers on rigs with success but I can't find anywhere a post where someone is experiencing these same issues.
I have not tried running 1709 with older more mining friendly drivers but I have found posts of people saying the drivers previously released will not work in 1709.
Anyone out there had similar experiences and found a solution that works in 1709?
Jump to: