Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[TechPark]

Please provide the link to beta driver

There was a link 2 pages before:
https://bitcointalk.org/index.php?topic=2068446.msg20663225#msg20663225

This is what I thought. Its not a beta AMD driver. This is an modification performed by an individual. One of the links is not opening. The second has a virus alerts. Be aware! Have not you had any issues with that driver? Are you still using it?

One should think twice before installing untrusted software on his money making machine.
Sometimes we see people surprised when their miner mines for elsebody

yea, right.
An individual who managed to solve  AMD driver problem for specific cards, compiled whole driver pack and even make it install without fuss on Win10?
And did that for 2 days after first leakage that such driver exists ?!

i missed your point... Did you try it yourself? Does it work for you flawlessly? Congratulations then. I did not see an increase of the hashing power, so this is the fact I trust.

[1714967472]

1714967472

[1714967472]

1714967472

[restless]

Are you using custom bios (eg timings for lower domains copied to 1875 and 2000)?
If yes, you need atikmdag patch
If not, you can't get max speed

[BennyT]

Hey guys looking for some input here. I'm getting wildly inconsistent hash rates on my 5 x 1060 rig. Three more cards arriving tomorrow but want to sort this out.

On 9.8 Screenshot my ETH hash rate is is 102.xx but every once in a while it drops down to 50 or 60 mh/s and as you can see a few of the cards will drop to 1 mh/s but some of the other ones drop to 14 or 15. One of my GPU fans is also reporting 0% but the card is cool and the fans are still spinning.

On 9.7 performance is not too bad... But it's around 100 mh/s and the performance only dips down to 94 - 97 mh/s occasionally. I haven't seen the cards drop down to 1 mh/s however I will still see the GPU fan drop to 0.

Currently on 384.90 since it gave the best results at the top end but I've tried 368 and 372 with no difference in the problems, only that the top end hash rate is insignificantly lower.

No clue what's going on here! Any help would be appreciated.

[agtprvctr]

Finally I can test and confirm that AMD has fixed the issue with slowdown at high DAG epochs for Vega/Polaris/Fiji cards. They are going to release new drivers in a few days.

Have you heard any new updates from AMD since? Wondering if they're having last minute issues with the release. I'd like to avoid using an unofficial user-modded driver.

Separately, I just assembled an AMD rig with 6x RX480, and I'm new to AMD, would folks mind educating me as to the following:

1) Is BIOS modding still the way to go for under-volting and optimizing memory timings? Or can a lot of that be achieved with the latest Wattman?
2a) If BIOS mods are still the way to go, I read that as of a certain Catalyst version it won't work with modified BIOS, so does that mean when the new Catalyst with DAG fix releases, it won't work with the BIOS mods? How will we be able to use the new driver with DAG fix AND run with modded BIOS?
2b) If Wattman can largely achieve power reduction and improved

Apologies in advance if this issue has been widely discussed, I didn't see directly relevant results with the preliminary Google searches I've done thus far.

[androstan1234]

Finally I can test and confirm that AMD has fixed the issue with slowdown at high DAG epochs for Vega/Polaris/Fiji cards. They are going to release new drivers in a few days.

Have you heard any new updates from AMD since? Wondering if they're having last minute issues with the release. I'd like to avoid using an unofficial user-modded driver.

Separately, I just assembled an AMD rig with 6x RX480, and I'm new to AMD, would folks mind educating me as to the following:

1) Is BIOS modding still the way to go for under-volting and optimizing memory timings? Or can a lot of that be achieved with the latest Wattman?
2a) If BIOS mods are still the way to go, I read that as of a certain Catalyst version it won't work with modified BIOS, so does that mean when the new Catalyst with DAG fix releases, it won't work with the BIOS mods? How will we be able to use the new driver with DAG fix AND run with modded BIOS?
2b) If Wattman can largely achieve power reduction and improved

Apologies in advance if this issue has been widely discussed, I didn't see directly relevant results with the preliminary Google searches I've done thus far.

1)  For the love of all that is holy and good, do not use Wattman.  It's awful.

2a) It still works, you just have to re-patch/sign with atikmdag patcher.

2b) Don't use Wattman.

[Call_Me_Bambi]

My rig was running well with 6 gpus.  I moved it to a new location.  Now one gpu (rx 570 rog strip 4gb) doesn't work at all.  Gpu-z doesn't show any info for it.  Worried It's just a dead card now, but not sure what could have caused it.  Maybe just rma.
For another gpu (rx 570 msi twin frozr 4 gb), everything looks fine in gpuz, but if it's plugged in when the miner starts, I get a windows error popup saying the .exe has stopped working, before dag creation.  Seems like the card is good and this problem should be fixable.
The other four (xfx rx 480 8gb, rog strix rx 580 8 gb, msi armor rx 580 4 gb, and powercolor red dragon 4 gb) are smooth and stable as long as the twin frozr isn't plugged in.
Any ideas?

I've had a few occasions where Claymore start then a box pops up and says something like "EthDcrMiner64.exe has stopped working" (usually after I've messed around with something).
I tried the usual delete video drivers with DDU and reinstall drivers, but that didn't work.
The only soloution I found that worked was to do a complete clean re-install of Windows.

[androstan1234]

My rig was running well with 6 gpus.  I moved it to a new location.  Now one gpu (rx 570 rog strip 4gb) doesn't work at all.  Gpu-z doesn't show any info for it.  Worried It's just a dead card now, but not sure what could have caused it.  Maybe just rma.
For another gpu (rx 570 msi twin frozr 4 gb), everything looks fine in gpuz, but if it's plugged in when the miner starts, I get a windows error popup saying the .exe has stopped working, before dag creation.  Seems like the card is good and this problem should be fixable.
The other four (xfx rx 480 8gb, rog strix rx 580 8 gb, msi armor rx 580 4 gb, and powercolor red dragon 4 gb) are smooth and stable as long as the twin frozr isn't plugged in.
Any ideas?

I've had a few occasions where Claymore start then a box pops up and says something like "EthDcrMiner64.exe has stopped working" (usually after I've messed around with something).
I tried the usual delete video drivers with DDU and reinstall drivers, but that didn't work.
The only soloution I found that worked was to do a complete clean re-install of Windows.

Thanks.  Yeah I tried DDU + reinstall drivers already.  Clean reinstall of windows would really be a pain in the neck, but it does seem to be a windows problem.

If I knew my shit better there's probably some registry tweak or something that would fix it.

[Trimegistus]

Finally I can test and confirm that AMD has fixed the issue with slowdown at high DAG epochs for Vega/Polaris/Fiji cards. They are going to release new drivers in a few days.

Have you heard any new updates from AMD since? Wondering if they're having last minute issues with the release. I'd like to avoid using an unofficial user-modded driver.

Separately, I just assembled an AMD rig with 6x RX480, and I'm new to AMD, would folks mind educating me as to the following:

1) Is BIOS modding still the way to go for under-volting and optimizing memory timings? Or can a lot of that be achieved with the latest Wattman?
2a) If BIOS mods are still the way to go, I read that as of a certain Catalyst version it won't work with modified BIOS, so does that mean when the new Catalyst with DAG fix releases, it won't work with the BIOS mods? How will we be able to use the new driver with DAG fix AND run with modded BIOS?
2b) If Wattman can largely achieve power reduction and improved

Apologies in advance if this issue has been widely discussed, I didn't see directly relevant results with the preliminary Google searches I've done thus far.

1) Yes, BIOS modding is the way to go! But make sure you know what you are doing, ok?

2) With recent drivers, you'll need to patch them otherwise they won't work with the modded BIOS. Check it out: https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher

3) With current drivers, WattTool is the best choice to undervolt/underclock your rigs. Get it here: http://www.overclock.net/t/1609782/watttool-a-simple-tool-that-combines-overclocking-with-vrm-monitoring-tweaking-for-rx-400-series

4) WattMan sucks...  

[agtprvctr]

Finally I can test and confirm that AMD has fixed the issue with slowdown at high DAG epochs for Vega/Polaris/Fiji cards. They are going to release new drivers in a few days.

Have you heard any new updates from AMD since? Wondering if they're having last minute issues with the release. I'd like to avoid using an unofficial user-modded driver.

Separately, I just assembled an AMD rig with 6x RX480, and I'm new to AMD, would folks mind educating me as to the following:

1) Is BIOS modding still the way to go for under-volting and optimizing memory timings? Or can a lot of that be achieved with the latest Wattman?
2a) If BIOS mods are still the way to go, I read that as of a certain Catalyst version it won't work with modified BIOS, so does that mean when the new Catalyst with DAG fix releases, it won't work with the BIOS mods? How will we be able to use the new driver with DAG fix AND run with modded BIOS?
2b) If Wattman can largely achieve power reduction and improved

Apologies in advance if this issue has been widely discussed, I didn't see directly relevant results with the preliminary Google searches I've done thus far.

1) Yes, BIOS modding is the way to go! But make sure you know what you are doing, ok?

2) With recent drivers, you'll need to patch to them otherwise they won't work with the modded BIOS. Check it out: https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher

3) With current drivers, WattTool is the best choice to undervolt/underclock your rigs. Get it here: http://www.overclock.net/t/1609782/watttool-a-simple-tool-that-combines-overclocking-with-vrm-monitoring-tweaking-for-rx-400-series

4) WattMan sucks... 

Thank you guys so much!

[trecore4]

Very clever to release this type of mining. Recently I have been working with nicehash and minergate where they can start the smart mining which is nothing but dual mining for alternative coins. However I have experienced too much power consumption when this happens.

I want to ask whether it is the case with this software too or not. I'm sure it's all about the hardware though.

[Ursul0]

yea, right.
An individual who managed to solve  AMD driver problem for specific cards, compiled whole driver pack and even make it install without fuss on Win10?
And did that for 2 days after first leakage that such driver exists ?!

"talented coder" like lamers would say. Or just an individual with proper tools and well informed of the current AMD customer needs.

EDIT: does the trick for 470 & 480 refs on asrock ann, Win10. need AB for undervolt (only the straps mod). performance is back, but volts are too high for my taste.
On mixed 470 nitos+refs on z270(UEFI Win10) having various issues. now flashing volts there... we'll see...

[Marvell1]

I dont know if its bug with the drivers or the 9.8 version of claymore but on about half my machines

the hash rate goes from 28ms or so to 8 and stays there till i have to reboot the rigs

[boysie]

speed report

9.8/latest AMD driver (dag fix)

480/8G = 29MH/900MH dcr
470/4G = 28.8MH/635MH dcr = issue with stable hash, keeps dropping to 14MH
570/4g = 30MH/660MH dcr = issue with stable hash, keeps dropping to 14MH
Vega FE 16G = 37.5MH/1.3GH dcr = issue with heat, any thing over 60c throttles down to 32.5MH/900MH dcr

Cards used: REF 480 + Red Devil 8G 480 + Nitro+OC 470 and 570 4GB + Vega FE 16GB Air.

Boysie

[davescream]

Claymore, why -cvddc and -mvddc are not work below 1000 mv ?  If I set "-cvddc 960 -mvddc 960" for example, gpuz and AB show 1000+ mv.

Im using new AMD beta driver and dual miner 9.8
---
Found the answer:

@Claymore
The miner doesn't apply -cvddc less than 900mv  on my RX570
-cvddc 880 applies the same voltage as -cvddc 900
Is it by design?  I could still knock some watts down if it allowed me to.

If you cannot set lower voltage it means that AMD ADL library cannot do it.

[AltcoinScamfinder]

It keeps crashing for my 2 x Vega cards. How can I single mine ETH only with these cards? (what flags? options etc.)

[AltcoinScamfinder]

speed report

9.8/latest AMD driver (dag fix)

480/8G = 29MH/900MH dcr
470/4G = 28.8MH/635MH dcr = issue with stable hash, keeps dropping to 14MH
570/4g = 30MH/660MH dcr = issue with stable hash, keeps dropping to 14MH
Vega FE 16G = 37.5MH/1.3GH dcr = issue with heat, any thing over 60c throttles down to 32.5MH/900MH dcr

Cards used: REF 480 + Red Devil 8G 480 + Nitro+OC 470 and 570 4GB + Vega FE 16GB Air.

Boysie

What does your config file look like?

[ayiphelmy]

It keeps crashing for my 2 x Vega cards. How can I single mine ETH only with these cards? (what flags? options etc.)

-mode 1 add this

[AltcoinScamfinder]

It keeps crashing for my 2 x Vega cards. How can I single mine ETH only with these cards? (what flags? options etc.)

-mode 1 add this

In config or or the start.bat? and before  or after the address/wallet info?

[ayiphelmy]

It keeps crashing for my 2 x Vega cards. How can I single mine ETH only with these cards? (what flags? options etc.)

-mode 1 add this

In config or or the start.bat? and before  or after the address/wallet info?

Ethdcrminer64 -epool your pool -ewal your wallet  -epsw x -eworker your worker -mode 1 this is an example

[AltcoinScamfinder]

It keeps crashing for my 2 x Vega cards. How can I single mine ETH only with these cards? (what flags? options etc.)

-mode 1 add this

In config or or the start.bat? and before  or after the address/wallet info?

Ethdcrminer64 -epool your pool -ewal your wallet  -epsw x -eworker your worker -mode 1 this is an example

Sweet thx, I'll give it a try.