I’ve been mining ETH and ETC on 2 RX570 8G rigs (12 GPUs each) using HiveOS on several mining pools and got really good stability in the last few months. I switched to mining to Nicehash (Ethash) a few days ago and got really surprised because I get a lot of rejected/invalid shares. If I switch back to mining on a “standard” pool I don’t have any issue so I was wondering if I’m doing anything wrong? That’s really annoying as Nicehash was giving me really good profitability compared to other pools… I tried using several mining softwares (Claymore, Phoenixminer and others…) and different Nicehash servers but I still get the same issue only with Nicehash. Any idea about what’s causing this problem?
Rejected shares will always be on a Nicehash, usually somewhere around 1-2%. Their nature lies in the Nicehash protocol. You can’t do anything here.
Thus, you should lay somewhere 2% in losses when mining on a Nicehash.
I am around 4 to 5% in losses using Nicehash. But my 2 rigs sometimes also drop to 0 hashrate randomly only when mining to Nicehash and it happens 1 to 2 times an hour… So I think there is a real problem here and I tried everything but I can’t figure out what’s wrong with Nicehash.
4-5% - check what server are using. Use nearest for you.
Random hashrate drop - for this point need examine miner log to be clear what happened
This is what I captured in the miner log when it happened again a few minutes ago:
GPU9: DAG 72%
GPU11: DAG 66%
GPU2: DAG 66%
GPU3: DAG 66%
GPU1: DAG 66%
Eth speed: 0.000 MH/s, shares: 1526/30/0, time: 6:55
GPUs: 1: 0.000 MH/s (121) 2: 0.000 MH/s (133) 3: 0.000 MH/s (116) 4: 0.000 MH/s (144) 5: 0.000 MH/s (131) 6: 0.000 MH/s (116) 7: 0.000 MH/s (118) 8: 0.000 MH/s (133) 9: 0.000 MH/s (173) 10: 0.000 MH/s (130) 11: 0.000 MH/s (121) 12: 0.000 MH/s (120)
GPU7: DAG 72%
GPU10: DAG 96%
GPU12: DAG 96%
GPU4: DAG 81%
GPU8: DAG 96%
GPU9: DAG 96%
GPU6: DAG 84%
GPU11: DAG 84%
GPU10: DAG generated in 7.1 s (539.8 MB/s)
GPU12: DAG generated in 7.1 s (539.2 MB/s)
GPU8: DAG generated in 7.1 s (539.5 MB/s)
GPU9: DAG generated in 7.1 s (539.4 MB/s)
GPU5: DAG 72%
GPU2: DAG 72%
GPU3: DAG 72%
GPU7: DAG 91%
GPU1: DAG 72%
GPU6: DAG generated in 8.0 s (477.4 MB/s)
GPU11: DAG generated in 8.0 s (477.3 MB/s)
GPU4: DAG generated in 8.3 s (457.8 MB/s)
GPU7: DAG generated in 8.8 s (435.1 MB/s)
GPU5: DAG 96%
GPU2: DAG 94%
GPU3: DAG 94%
GPU1: DAG 94%
GPU5: DAG generated in 9.9 s (386.2 MB/s)
GPU2: DAG generated in 10.8 s (352.6 MB/s)
GPU3: DAG generated in 10.8 s (352.5 MB/s)
GPU1: DAG generated in 10.7 s (357.4 MB/s)
Eth speed: 270.814 MH/s, shares: 1526/30/0, time: 6:55
GPUs: 1: 0.000 MH/s (121) 2: 0.000 MH/s (133) 3: 0.000 MH/s (116) 4: 31.134 MH/s (144) 5: 31.348 MH/s (131) 6: 28.114 MH/s (116) 7: 26.728 MH/s (118) 8: 31.341 MH/s (133) 9: 31.359 MH/s (173) 10: 31.367 MH/s (130) 11: 28.090 MH/s (121) 12: 31.332 MH/s (120)
Eth: New job #1928773b from daggerhashimoto.eu.nicehash.com:3353; diff: 6872MH
Eth: New job #bc7a4a31 from daggerhashimoto.eu.nicehash.com:3353; diff: 6872MH
Eth speed: 361.353 MH/s, shares: 1526/30/0, time: 6:55
GPUs: 1: 28.132 MH/s (121) 2: 31.122 MH/s (133) 3: 31.152 MH/s (116) 4: 31.123 MH/s (144) 5: 31.369 MH/s (131) 6: 28.116 MH/s (116) 7: 26.730 MH/s (118) 8: 31.366 MH/s (133) 9: 31.365 MH/s (173) 10: 31.382 MH/s (130) 11: 28.124 MH/s (121) 12: 31.373 MH/s (120)
GPU1: 56C 60% 78W, GPU2: 55C 60% 76W, GPU3: 55C 60% 78W, GPU4: 55C 60% 75W, GPU5: 57C 60% 91W, GPU6: 57C 60% 77W, GPU7: 56C 60% 75W, GPU8: 55C 60% 86W, GPU9: 57C 60% 91W, GPU10: 55C 60% 90W, GPU11: 58C 60% 76W, GPU12: 57C 60% 86W
GPUs power: 980.5 W
Eth: New job #2e056d0b from daggerhashimoto.eu.nicehash.com:3353; diff: 6872MH
Eth: New job #186dd906 from daggerhashimoto.eu.nicehash.com:3353; diff: 6872MH
On Nicehash you lease your computing power on a certain algorithm. At any time, you can switch to mining another coin on this algorithm and at that moment the hash will drop to zero, the miner will download the DAG file for this coin. For example, switching between Ethereum and Ethereum Classic most often occurs (which coin is mined can actually be seen in the phoenix in the dashboard or indirectly by the epoch number of the DAG file from the miner’s log)