Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux)

[aaronsace]

Anyone got problem with 280x doing 0 h/s in 5.0? Works just fine with 4.0.
I have updated drivers from 15.7.1 to latest crimson 16.11.3 - same thing.

This is a mixed with nvidia rig with 280x being the only AMD card present:

Code:

ZEC: Stratum - Connected (equihash.eu.nicehash.com:3357)
ZEC: Authorized
Pool sets new share target: 0x01e1e1e1 (diff: 136H)
ZEC: Share accepted!

GPU #0: Tahiti, 3072 MB available, 32 compute units
ZEC - Total Speed: 0.000 H/s, Total Shares: 0, Rejected: 0, Time: 00:00
ZEC: GPU0 0.000 H/s
Pool switches: ZEC - 0
Current ZEC pool share target: 0x01e1e1e1 (diff: 136H)
GPU0 t=47C fan=49%

Reward is at 5.14 now, will get up to 10.0 - expect twice the price drop.

Please read previous posts. Run two separate windows. Use -di and -mport.

Thats why I have written `This is a mixed with nvidia rig with 280x being the only AMD card present:`
There are no other AMD cards there, this is the only claymore ZEC miner running.
Anyway I have tried it to run with " -di 0 -mport 0", but still nothing

Update to the latest drivers from AMD and remove any overclock/mods.

[Wandika]

my fury has the biggest gain hittiing 180 H/s..maybe its the HBM memory, imagine when HBM2 is released with the rx 490, that gpu will probably outclass the rx 480 and HBM cards by a huge margin.

What is your Fury setting? What is the Catalyst version and the GPU frequency?

My R9 Nano with driver 16.9.1, 1000/500 can only reach about 155H/s. 15.2 is ever slower.

[qqqq]

I've got some strange behavior of the miner while tested v5.0.
Miner detected all my cards but used only first one.
Here is some piece of log.
17:30:47:046   283c   parse packet: 296
17:30:47:051   283c   new buf size: 0
17:30:47:056   283c   ZEC: 11/14/16-17:30:47 - New job from zec-eu1.nanopool.org:6666
17:30:47:061   283c   target: 0x00147ae1 (diff: 3200H)
17:30:47:066   283c   ZEC - Total Speed: 114.094 H/s, Total Shares: 4, Rejected: 0, Time: 00:01
17:30:47:071   283c   ZEC: GPU0 114.094 H/s, GPU1 0.000 H/s, GPU2 0.000 H/s, GPU3 0.000 H/s, GPU4 0.000 H/s
17:30:48:934   1378   ZEC: put share nonce 21d
17:30:48:939   1378   ZEC round found 1 shares
17:30:48:945   283c   ZEC: 11/14/16-17:30:48 - SHARE FOUND - (GPU 0)

Does anybody have same problem?
On v3.1 all works fine with the same setup.

Please read previous posts. Run two separate windows.

It's not working! I got same issue. When two miners working in the same time All GPU show Incorrect Data like this and half hashrate

GPU #1 returned incorrect data! 293f5d2
GPU #0 returned incorrect data! 123ada6

if i close one, the second back to normal mining.

First window put "-mport 0 -di 0"
Second window put "-mport 0 -di 1234"

Thanks man -mport 0 in each miner instance solve the issue. I guessed it was needed at least in 1 of 2 miner.

[adaseb]

Should bounce from here. Very low risk/High Reward trade.

Thank you, bro. I've lost 20% today

IT was a valid bull flag, however supply exceeded demand, and when support broke at the daily low everybody bailed. I lost money too but only like a few %.

Very hard to trade this coin since you can only go long and can't short.

[hawkfish007]

Anyone seeing random hash rate drop specially for RX 470s? After running overnight I found 2 out of 7 470 were hashing at 33 sols but the rest are at 110. This happened in 2 rigs both with 7 470s.

[Bojcha]

What do you rejoice? It is advantageous when your speed is higher than the other. And when the rate rises in all, you are in relation to other, standing pat are.

It just kills the coin.

Exactly - the only one actually making money is Claymore xD

If you check history, my miner is not x3 faster than others, I just see how fast others miners and release a bit faster version. This time I have to release faster version due to new miner. If people stop this speed racing I'll stop it too, but you know it won't work
Also do note my miner is not for NVidia, not for CPU and not for Linux, so if I release miner with x2 speed, network difficult is not going to raise x2 too.

Claymore, possible to add CPU affinity for miner in some next version? it Seems that on one core miner is more 'stable'.

[xeridea]

What do you rejoice? It is advantageous when your speed is higher than the other. And when the rate rises in all, you are in relation to other, standing pat are.

It just kills the coin.

Exactly - the only one actually making money is Claymore xD

If you check history, my miner is not x3 faster than others, I just see how fast others miners and release a bit faster version. This time I have to release faster version due to new miner. If people stop this speed racing I'll stop it too, but you know it won't work
Also do note my miner is not for NVidia, not for CPU and not for Linux, so if I release miner with x2 speed, network difficult is not going to raise x2 too.

Claymore, possible to add CPU affinity for miner in some next version? it Seems that on one core miner is more 'stable'.

https://blogs.msdn.microsoft.com/santhoshonline/2011/11/24/how-to-launch-a-process-with-cpu-affinity-set/
It would be cool to have in miner though, since /start opens another window. Many use /start in restart loops anyway (not really necessary with Claymore miners most the time....)

[amirheavy666]

I have one R9 390x and one RX 480 but with claymore ver 5.0 just Rx480 work !!

i give this error : (port is busy, use different -mport value)

 
and with claymore 4.0 both of R 390x and R480x works !!!

what i must do

[Swimmer63]

Claymore -

I have a miner with one R9 290x and one RX480.  With v5.0 my RX480 is screaming fast, but now the 290 does not mine.  My PC alternates between recognizing the 290 and not mining it to recognizing it but with an error in the device manager.  Have tried both 15.12 and the current driver.  Does not seem to help.  Not sure if this is related to what you are referencing here or not.

[Cobra98]

I have one R9 390x and one RX 480 but with claymore ver 5.0 just Rx480 work !!

i give this error : (port is busy, use different -mport value)

 
and with claymore 4.0 both of R 390x and R480x works !!!

what i must do

Go back 1 page, u have to run 2 instances of v5.0 if u have mixed cards with rx400 series

[olcaytu2005]

Anyone seeing random hash rate drop specially for RX 470s? After running overnight I found 2 out of 7 470 were hashing at 33 sols but the rest are at 110. This happened in 2 rigs both with 7 470s.

Yup, had to go back to optiminer for now. Ran 2 hours with full speed, rest 8 hours was dropping dropping until it dropped like %25 (total hash speed), I had enough. Cards are getting overheated. And they are not even oc'ed.

[fredeq]

Anyone got problem with 280x doing 0 h/s in 5.0? Works just fine with 4.0.
I have updated drivers from 15.7.1 to latest crimson 16.11.3 - same thing.

This is a mixed with nvidia rig with 280x being the only AMD card present:

Code:

ZEC: Stratum - Connected (equihash.eu.nicehash.com:3357)
ZEC: Authorized
Pool sets new share target: 0x01e1e1e1 (diff: 136H)
ZEC: Share accepted!

GPU #0: Tahiti, 3072 MB available, 32 compute units
ZEC - Total Speed: 0.000 H/s, Total Shares: 0, Rejected: 0, Time: 00:00
ZEC: GPU0 0.000 H/s
Pool switches: ZEC - 0
Current ZEC pool share target: 0x01e1e1e1 (diff: 136H)
GPU0 t=47C fan=49%

Reward is at 5.14 now, will get up to 10.0 - expect twice the price drop.

Ok managed to fix it by copying `data.bin` and `data2.bin` from other working miner.
Either I downloaded an early broken version or somehow this fucked when unzipping.

[Vaculin]

I have one R9 390x and one RX 480 but with claymore ver 5.0 just Rx480 work !!

i give this error : (port is busy, use different -mport value)

 
and with claymore 4.0 both of R 390x and R480x works !!!

what i must do

You just use a different port. For example -mport  2345

[GH]

https://blogs.msdn.microsoft.com/santhoshonline/2011/11/24/how-to-launch-a-process-with-cpu-affinity-set/
It would be cool to have in miner though, since /start opens another window. Many use /start in restart loops anyway (not really necessary with Claymore miners most the time....)

Use

Code:

start /B

(HELP START)

[xeridea]

I have one R9 390x and one RX 480 but with claymore ver 5.0 just Rx480 work !!

i give this error : (port is busy, use different -mport value)

 
and with claymore 4.0 both of R 390x and R480x works !!!

what i must do

You just use a different port. For example -mport  2345

The error is saying the remote monitoring port (for the sweeeeet ethman) is already used.  On second instance, disable with -mport 0, or change port it uses (default is 3333), if using ethman, update port for 2nd instance.

It is explained by Claymore also.  https://bitcointalk.org/index.php?action=profile;u=306958;sa=showPosts

[xeridea]

To the dozens who keep spamming help for issue with mixed cards.  Read the forum... and Claymore's posts

A workaround for rigs with mixed cards (Polaris and old cards): start two miners with "-di" option, one for Polaris cards and second for other cards. Use "-mport 0" option to disable port for remote management and avoid red message in second miner.
I will fix it soon.

It can also happen with Fury and non Fury cards.

[adaseb]

If you are using the 1500 Straps with your 470 4GB, dont run higher than 1800Mhz, its not like ETH and it will FREEZE your system.

Go stock or use 1800Mhz instead. It will run fast at first and then slow down due to massive memory errors.

[king_pin]

A workaround for rigs with mixed cards (Polaris and old cards): start two miners with "-di" option, one for Polaris cards and second for other cards. Use "-mport 0" option to disable port for remote management and avoid red message in second miner.
I will fix it soon.

You should also fix the issue I mentioned a few weeks back.
-di does not work properly:
when I write -di 1,2,3 instead of 3 devices I get 0,1,2,3 or 4 cards running!!!

[Tuner77]

V5 rocks. 2x480 8gb, 4x 470 4gb, just upgraded miner and getting nice rates at the pool. Will report 24/hr rate tomorrow.

[olcaytu2005]

If you are using the 1500 Straps with your 470 4GB, dont run higher than 1800Mhz, its not like ETH and it will FREEZE your system.

Go stock or use 1800Mhz instead. It will run fast at first and then slow down due to massive memory errors.

Im using 1500 straps and 1750 mem. Still getting huge memory errors or invalid shares on log. Same settings, optiminer runs perfect with slightly lower but more accurate hash and sharerate.