Does the new AMD driver work with R9 Fury?
ya it's work with fury but in fury x not good 
Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 665. (Read 6590565 times)
August 17, 2017, 04:13:10 AM
August 17, 2017, 04:05:10 AM
I have 6 RX470 cards.
Update to the beta drive, then:
+ 9.7 claymore runs stable hashrate, but could not control temp and fan.
+ 9.8 claymore runs at very low hashrate, seem like could not control anything.
Update to the beta drive, then:
+ 9.7 claymore runs stable hashrate, but could not control temp and fan.
+ 9.8 claymore runs at very low hashrate, seem like could not control anything.
August 17, 2017, 03:58:11 AM
Does the new AMD driver work with R9 Fury?
August 17, 2017, 03:57:06 AM
I have the EXACT SAME problems...
Afterburner 4.4.0 Beta 12
AMD Beta Blockchain driver
RX480 cards
Windows 10 Pro (latest update).
Using driver 16.9.2 works without any problem.
Volt -70
Power +20
Core 1040
Memory 1885
Getting around 25.5 MH.s
Try with Afterburner 4.4.0 Beta 16 Afterburner 4.4.0 Beta 12
AMD Beta Blockchain driver
RX480 cards
Windows 10 Pro (latest update).
Using driver 16.9.2 works without any problem.
Volt -70
Power +20
Core 1040
Memory 1885
Getting around 25.5 MH.s
August 17, 2017, 03:56:19 AM
Upgraded to the latest beta driver with mining fix while coming from 17.5.2. Like others, I'm having some issues with voltages returning to default. Running Windows 10, mix 470/480/580.
I've read various posts relating to voltages not staying set, and I figured I'd add my own experiences in hopes of finding a workaround/solution.
What I see happening is that AMD drivers are not correctly storing voltage settings. The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.
Once the voltages are reset, all tools (wattman, overdriventool) still display the voltages as the user defined settings. To get the voltages back down, I must either increase, or decrease mV slightly, then return back to preferred setting.
A possible solution could be to have claymore dual miner check every minute or so, and if needed automatically re-apply cvddc and mvddc with a +/- 1 mV. My past experience using cvddc is that it sets only once when the miner is first launched and never tries to re-apply if settings have changed.
I've read various posts relating to voltages not staying set, and I figured I'd add my own experiences in hopes of finding a workaround/solution.
What I see happening is that AMD drivers are not correctly storing voltage settings. The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.
Once the voltages are reset, all tools (wattman, overdriventool) still display the voltages as the user defined settings. To get the voltages back down, I must either increase, or decrease mV slightly, then return back to preferred setting.
A possible solution could be to have claymore dual miner check every minute or so, and if needed automatically re-apply cvddc and mvddc with a +/- 1 mV. My past experience using cvddc is that it sets only once when the miner is first launched and never tries to re-apply if settings have changed.
Yes same bug here. As i wrote ~4 posts earlier. The clocks suddenly become unstable (and apparently also the voltages, as the WATT consumption from the wall spikes when this bug occurs). I get this bug only with newer driver than 17.5.2.
Quote
The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.
This all is absolutely true. I first encountered the bug when I went to fullscreen video playback in ZoomPlayer. Oddly this only happens with "EVR" as renderer, when i switch to MADVR as renderer, the bug does not appear.
Thanks to your hint, I can at least leave the computer run when I am gone, after I disabled the screen "power saving mode" in Windows to NEVER. So the clocks/vcore stay stable and I dont have to reapply settings in Wattman to fix the bug.
However, this is not the place to discuss the bug, IMO. I guess it is another DXVA hardware acceleration bug. We had many of these bugs in the past on the POLARIS architecture. Its AMDs fault and hopefully they will fix it in a driver update.
What i want to know is how to use just the driver files in the Claymore folder. If that is even possible or if Claymore could implement such a feature. This would be great. thx
August 17, 2017, 03:55:31 AM
Mixed RX480 / 470 6 Card rig (all cards modded) / Clay v9.8 / Win 10
- Wiped the old drivers, installed the new AMD dag fix drivers
- Patched the drivers
- Installed AB beta
Mining again and hashrate almost back to what it was before.
But....
Afterburner is pretty much useless now other than as a fan controller. No control over anything else whatsoever, gpu / mem / voltage - nothing...
Trixx looks like it's working but does either fuck all or drops the hashrate (on settings that have been perfect for nearly a year now).
Wattool doesn't work anymore either - showing no readings for anything.
Claymore crashes on DAG creation as soon as you try to use any -cclock settings in the batch file.
Wattman is the only thing that seems to work, allowing everything to be set as it should be with the desired results, but this new driver is so fucking unstable that the rig crashes every hour and every time it does wattman resets itself.
Props to AMD for trying to sort the problem for us, but this is just a fucking shambles.
The latest thing I'm trying is using AB as fan control and setting the mclock in Clay, so far it's working but will have to wait to see how stable it is.
**EDIT** Claymore crashed after 5 minutes - GPU's hung.
- Wiped the old drivers, installed the new AMD dag fix drivers
- Patched the drivers
- Installed AB beta
Mining again and hashrate almost back to what it was before.
But....
Afterburner is pretty much useless now other than as a fan controller. No control over anything else whatsoever, gpu / mem / voltage - nothing...
Trixx looks like it's working but does either fuck all or drops the hashrate (on settings that have been perfect for nearly a year now).
Wattool doesn't work anymore either - showing no readings for anything.
Claymore crashes on DAG creation as soon as you try to use any -cclock settings in the batch file.
Wattman is the only thing that seems to work, allowing everything to be set as it should be with the desired results, but this new driver is so fucking unstable that the rig crashes every hour and every time it does wattman resets itself.
Props to AMD for trying to sort the problem for us, but this is just a fucking shambles.
The latest thing I'm trying is using AB as fan control and setting the mclock in Clay, so far it's working but will have to wait to see how stable it is.
**EDIT** Claymore crashed after 5 minutes - GPU's hung.
I have the EXACT SAME problems...
Afterburner 4.4.0 Beta 12
AMD Beta Blockchain driver
RX480 cards
Windows 10 Pro (latest update).
Using driver 16.9.2 works without any problem.
Volt -70
Power +20
Core 1040
Memory 1885
Getting around 25.5 MH.s
August 17, 2017, 03:42:42 AM
I also have hardcoded volts and custom stages in bios besides regular mem straps patch.
Did you undervolt using BIOS mod on Windows? Please show how. AB beta 16 can not undervolt my 580s with new AMD blockchain driver.Same hier....7x 580 and don't works with AB 16 and the new blockchain driver about undervolt...so each card need more than 140W
But here we are writing A LOT OF PEOPLE only the same problems.....but no one answer what we can do....
To much ....to read everyday the same
August 17, 2017, 03:29:43 AM
I am not very comfortable with the idea of messing with the voltages in GPU BIOS.
So much that I would rather wait for a new miner version that can twist those voltages
So much that I would rather wait for a new miner version that can twist those voltages
August 17, 2017, 03:19:00 AM
I've checked Win10 + RX480, it seems it works, I see voltage changes in WattMan if I restart it. ADL does not report any errors.
Just to be clear:
Claymore 9.8, running on Win10 + AMD Blockchain drivers can overclock and underclock all parameters for the RX480?
my 480 refs and various 470 are doing fine.
Why You're setting voltages through config-file beside Your claim that You have already set them in BIOS? You know that You are making confusion, is it with intention?
You can do both.
EG: configure some base line in BIOS and do fine tuning later via config file.
The result only matters, is not it? Whatever works for you...
I'm talking about confusion between readers of the post. Obviously voltage setting through Claymore miner is not working with beta mining drivers, Ursul0 is posting screenshot claiming that it works for him. Truth is that he had voltages set in GPU BIOS...
August 17, 2017, 03:12:29 AM
I've checked Win10 + RX480, it seems it works, I see voltage changes in WattMan if I restart it. ADL does not report any errors.
Just to be clear:
Claymore 9.8, running on Win10 + AMD Blockchain drivers can overclock and underclock all parameters for the RX480?
my 480 refs and various 470 are doing fine.
Why You're setting voltages through config-file beside Your claim that You have already set them in BIOS? You know that You are making confusion, is it with intention?
You can do both.
EG: configure some base line in BIOS and do fine tuning later via config file.
The result only matters, is not it? Whatever works for you...
August 17, 2017, 03:08:03 AM
I've checked Win10 + RX480, it seems it works, I see voltage changes in WattMan if I restart it. ADL does not report any errors.
Just to be clear:
Claymore 9.8, running on Win10 + AMD Blockchain drivers can overclock and underclock all parameters for the RX480?
my 480 refs and various 470 are doing fine.
Why You're setting voltages through config-file beside Your claim that You have already set them in BIOS? You know that You are making confusion, is it with intention?
August 17, 2017, 02:38:26 AM
-cvddc set target GPU core voltage, multiplied by 1000. For example, "-cvddc 1050" means 1.05V. You can also specify values for every card, for example "-cvddc 900,950,1000,970". Supports latest AMD 4xx cards only in Windows.
Note: for NVIDIA cards this option is not supported.
-mvddc set target GPU memory voltage, multiplied by 1000. For example, "-mvddc 1050" means 1.05V. You can also specify values for every card, for example "-mvddc 900,950,1000,970". Supports latest AMD 4xx cards only in Windows.
Note: for NVIDIA cards this option is not supported.
Hi Claymore, is there any chance to have both parameters working for AMD RX 5xx cards in the next miner release? Note: for NVIDIA cards this option is not supported.
-mvddc set target GPU memory voltage, multiplied by 1000. For example, "-mvddc 1050" means 1.05V. You can also specify values for every card, for example "-mvddc 900,950,1000,970". Supports latest AMD 4xx cards only in Windows.
Note: for NVIDIA cards this option is not supported.
August 17, 2017, 02:33:44 AM
Upgraded to the latest beta driver with mining fix while coming from 17.5.2. Like others, I'm having some issues with voltages returning to default. Running Windows 10, mix 470/480/580.
I've read various posts relating to voltages not staying set, and I figured I'd add my own experiences in hopes of finding a workaround/solution.
What I see happening is that AMD drivers are not correctly storing voltage settings. The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.
Once the voltages are reset, all tools (wattman, overdriventool) still display the voltages as the user defined settings. To get the voltages back down, I must either increase, or decrease mV slightly, then return back to preferred setting.
A possible solution could be to have claymore dual miner check every minute or so, and if needed automatically re-apply cvddc and mvddc with a +/- 1 mV. My past experience using cvddc is that it sets only once when the miner is first launched and never tries to re-apply if settings have changed.
I've read various posts relating to voltages not staying set, and I figured I'd add my own experiences in hopes of finding a workaround/solution.
What I see happening is that AMD drivers are not correctly storing voltage settings. The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.
Once the voltages are reset, all tools (wattman, overdriventool) still display the voltages as the user defined settings. To get the voltages back down, I must either increase, or decrease mV slightly, then return back to preferred setting.
A possible solution could be to have claymore dual miner check every minute or so, and if needed automatically re-apply cvddc and mvddc with a +/- 1 mV. My past experience using cvddc is that it sets only once when the miner is first launched and never tries to re-apply if settings have changed.
Something crucial is missing in your explanation...
How do you know that voltage resets when the same voltage is displayed?
you can see it in HWiNFO64 or on the wall.
August 17, 2017, 01:20:43 AM
Anyone use R9 290/290x/390/390x have tasted new driver from AMD ? Please show the hashrate with this new driver ?
August 17, 2017, 01:18:58 AM
Upgraded to the latest beta driver with mining fix while coming from 17.5.2. Like others, I'm having some issues with voltages returning to default. Running Windows 10, mix 470/480/580.
I've read various posts relating to voltages not staying set, and I figured I'd add my own experiences in hopes of finding a workaround/solution.
What I see happening is that AMD drivers are not correctly storing voltage settings. The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.
Once the voltages are reset, all tools (wattman, overdriventool) still display the voltages as the user defined settings. To get the voltages back down, I must either increase, or decrease mV slightly, then return back to preferred setting.
A possible solution could be to have claymore dual miner check every minute or so, and if needed automatically re-apply cvddc and mvddc with a +/- 1 mV. My past experience using cvddc is that it sets only once when the miner is first launched and never tries to re-apply if settings have changed.
I've read various posts relating to voltages not staying set, and I figured I'd add my own experiences in hopes of finding a workaround/solution.
What I see happening is that AMD drivers are not correctly storing voltage settings. The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.
Once the voltages are reset, all tools (wattman, overdriventool) still display the voltages as the user defined settings. To get the voltages back down, I must either increase, or decrease mV slightly, then return back to preferred setting.
A possible solution could be to have claymore dual miner check every minute or so, and if needed automatically re-apply cvddc and mvddc with a +/- 1 mV. My past experience using cvddc is that it sets only once when the miner is first launched and never tries to re-apply if settings have changed.
Something crucial is missing in your explanation...
How do you know that voltage resets when the same voltage is displayed?
August 16, 2017, 11:42:46 PM
updated to 17.7.2 and 9.8 and I cannot keep memory clock at 2045 where I usually keep it.. it keeps bouncing 2045 to 1000 and back to 2045 as a result my hash rate is saw tooth even on my pool page. evn in wattman, the slider is not able to be set to a static value.. seems greyed out.
I installed with DDU to clear old drivers, I also tried upgrading to the new beta drivers and no fix.
it was fine prior to upgrading to 17.7.2
Has anyone else come across this issue?
ASUS ROG Strix Radeon RX 580
https://i.imgur.com/OZ0Zs3C.png
I installed with DDU to clear old drivers, I also tried upgrading to the new beta drivers and no fix.
it was fine prior to upgrading to 17.7.2
Has anyone else come across this issue?
ASUS ROG Strix Radeon RX 580
https://i.imgur.com/OZ0Zs3C.png
-Not 17.7.2 but CRIMSON BETA
Had the same issue when using 17.7.2 drivers. Went back to 17.4.4 where it was running before with no issues mining ETH.
August 16, 2017, 11:26:18 PM
Hi Claymore,
I believe the voltage issues with 9.8 and the beta driver, are specific to the RX580 cards, from what I've read the RX480s are just fine with the beta driver.
I believe the voltage issues with 9.8 and the beta driver, are specific to the RX580 cards, from what I've read the RX480s are just fine with the beta driver.
Not true, 480s here, voltage control doesn't work at all on the new driver.
on Afterburner, latest beta, try to set the voltage control in settings to thirdparty
August 16, 2017, 11:25:05 PM
Ok so I need some help here:
Rig
Windows 7 64 bit
3x RX 560 1x RX 570
Rig was working fine then I decided to installed the Beta Drivers that fix the dag issue
I ran DDU then rebooted then ran the driver installation
Rebooted
My card Bois's are all modified
When I install PixelPatcher and reboot the windows boot logo comes up then black screen
If I undo the Pixel patcher everything is fine but I cannot mine as the cards are altered so I need the patcher but if I install the patcher I get a black screen
So a fresh install of Windows fixed the black screen with the beta drivers but I have another issue when i go to run 9.8 or even 9.7 it starts gets to the point where just before it creates the DAG file then it crashesRig
Windows 7 64 bit
3x RX 560 1x RX 570
Rig was working fine then I decided to installed the Beta Drivers that fix the dag issue
I ran DDU then rebooted then ran the driver installation
Rebooted
My card Bois's are all modified
When I install PixelPatcher and reboot the windows boot logo comes up then black screen
If I undo the Pixel patcher everything is fine but I cannot mine as the cards are altered so I need the patcher but if I install the patcher I get a black screen
I reverted back to older AMD drivers for now as the current frustration and inability to control the voltage for 3-4Mh is not worth it. Hopefully this will get more refined over the coming weeks
August 16, 2017, 11:07:39 PM
Hi Claymore,
I believe the voltage issues with 9.8 and the beta driver, are specific to the RX580 cards, from what I've read the RX480s are just fine with the beta driver.
I believe the voltage issues with 9.8 and the beta driver, are specific to the RX580 cards, from what I've read the RX480s are just fine with the beta driver.
Not true, 480s here, voltage control doesn't work at all on the new driver.
August 16, 2017, 10:53:32 PM
Mixed RX480 / 470 6 Card rig (all cards modded) / Clay v9.8 / Win 10
- Wiped the old drivers, installed the new AMD dag fix drivers
- Patched the drivers
- Installed AB beta
Mining again and hashrate almost back to what it was before.
But....
Afterburner is pretty much useless now other than as a fan controller. No control over anything else whatsoever, gpu / mem / voltage - nothing...
Trixx looks like it's working but does either fuck all or drops the hashrate (on settings that have been perfect for nearly a year now).
Wattool doesn't work anymore either - showing no readings for anything.
Claymore crashes on DAG creation as soon as you try to use any -cclock settings in the batch file.
Wattman is the only thing that seems to work, allowing everything to be set as it should be with the desired results, but this new driver is so fucking unstable that the rig crashes every hour and every time it does wattman resets itself.
Props to AMD for trying to sort the problem for us, but this is just a fucking shambles.
The latest thing I'm trying is using AB as fan control and setting the mclock in Clay, so far it's working but will have to wait to see how stable it is.
**EDIT** Claymore crashed after 5 minutes - GPU's hung.
- Wiped the old drivers, installed the new AMD dag fix drivers
- Patched the drivers
- Installed AB beta
Mining again and hashrate almost back to what it was before.
But....
Afterburner is pretty much useless now other than as a fan controller. No control over anything else whatsoever, gpu / mem / voltage - nothing...
Trixx looks like it's working but does either fuck all or drops the hashrate (on settings that have been perfect for nearly a year now).
Wattool doesn't work anymore either - showing no readings for anything.
Claymore crashes on DAG creation as soon as you try to use any -cclock settings in the batch file.
Wattman is the only thing that seems to work, allowing everything to be set as it should be with the desired results, but this new driver is so fucking unstable that the rig crashes every hour and every time it does wattman resets itself.
Props to AMD for trying to sort the problem for us, but this is just a fucking shambles.
The latest thing I'm trying is using AB as fan control and setting the mclock in Clay, so far it's working but will have to wait to see how stable it is.
**EDIT** Claymore crashed after 5 minutes - GPU's hung.
Jump to: