Author

Topic: Claymore Eth Dual Miner issues on AMD & NVIDIA (Read 1093 times)

member
Activity: 80
Merit: 10
Hi all.

Searched High and Low, no solution found to this, extremely frustrating result.

I run 3 rigs all with AMD GPUs (RX470 Modified). I also run a work PC that has a 1080ti. Upon trying Claymore miner out on all rigs including the Nvidia powered PC, I get a strange issue. A multitude of New Jobs, but no shares. Eventually it will submit a share or two on the 3 main mining rigs because they are running at 150-180Mhash. But a share or two is not good enough. The pools just keep throwing jobs at me and I am not submitting anything.

Same goes for the Nvidia rig which is running at 33Mhash. New jobs, no shares. All I get is the following;

ETH: 04/18/17-13:22:56 - New job from asia.expanse.miningpoolhub.com:20565
ETH - Total Speed: 33.515 Mh/s, Total Shares: 2, Rejected: 0, Time: 00:13
ETH: GPU0 33.515 Mh/s
ETH: 04/18/17-13:23:51 - New job from asia.expanse.miningpoolhub.com:20565
ETH - Total Speed: 33.021 Mh/s, Total Shares: 2, Rejected: 0, Time: 00:14
ETH: GPU0 33.021 Mh/s
ETH: 04/18/17-13:24:30 - New job from asia.expanse.miningpoolhub.com:20565
ETH - Total Speed: 32.709 Mh/s, Total Shares: 2, Rejected: 0, Time: 00:14
ETH: GPU0 32.709 Mh/s
ETH: 04/18/17-13:25:25 - New job from asia.expanse.miningpoolhub.com:20565
ETH - Total Speed: 33.400 Mh/s, Total Shares: 2, Rejected: 0, Time: 00:15
ETH: GPU0 33.400 Mh/s

I had to go back to SGminer which, for ETH, or any ethash algo, sucks, because it crashes out so easily and I get less hash. But it works, so that's the main thing. I would much rather use Claymore for this. I will post my batch file command;

EthDcrMiner64.exe -epool asia.expanse.miningpoolhub.com:20565 -ewal *** -epsw *** -di 0 -r 1 -wd 0 -nofee 1 -allpools 1 -esm 3

This happens on all pools for all rigs. Nanopool does the same.

Why is this happening and how can it be corrected.

for nvidia get rid of -di 0 if you only have one card also -r 1 dont need it and change -esm to 0 i would also recommend trying it without the -nofee option as well also for nvidia if your not dual mining use ccminer
and for amd i use asm 0 see i mostly dual mine eth on nanopool  and decred on suprnova
newbie
Activity: 32
Merit: 0
Same problem here , i am curios about the answer of your question !! Smiley UP !!!!
newbie
Activity: 45
Merit: 0
Hi all.

Searched High and Low, no solution found to this, extremely frustrating result.

I run 3 rigs all with AMD GPUs (RX470 Modified). I also run a work PC that has a 1080ti. Upon trying Claymore miner out on all rigs including the Nvidia powered PC, I get a strange issue. A multitude of New Jobs, but no shares. Eventually it will submit a share or two on the 3 main mining rigs because they are running at 150-180Mhash. But a share or two is not good enough. The pools just keep throwing jobs at me and I am not submitting anything.

Same goes for the Nvidia rig which is running at 33Mhash. New jobs, no shares. All I get is the following;

ETH: 04/18/17-13:22:56 - New job from asia.expanse.miningpoolhub.com:20565
ETH - Total Speed: 33.515 Mh/s, Total Shares: 2, Rejected: 0, Time: 00:13
ETH: GPU0 33.515 Mh/s
ETH: 04/18/17-13:23:51 - New job from asia.expanse.miningpoolhub.com:20565
ETH - Total Speed: 33.021 Mh/s, Total Shares: 2, Rejected: 0, Time: 00:14
ETH: GPU0 33.021 Mh/s
ETH: 04/18/17-13:24:30 - New job from asia.expanse.miningpoolhub.com:20565
ETH - Total Speed: 32.709 Mh/s, Total Shares: 2, Rejected: 0, Time: 00:14
ETH: GPU0 32.709 Mh/s
ETH: 04/18/17-13:25:25 - New job from asia.expanse.miningpoolhub.com:20565
ETH - Total Speed: 33.400 Mh/s, Total Shares: 2, Rejected: 0, Time: 00:15
ETH: GPU0 33.400 Mh/s

I had to go back to SGminer which, for ETH, or any ethash algo, sucks, because it crashes out so easily and I get less hash. But it works, so that's the main thing. I would much rather use Claymore for this. I will post my batch file command;

EthDcrMiner64.exe -epool asia.expanse.miningpoolhub.com:20565 -ewal *** -epsw *** -di 0 -r 1 -wd 0 -nofee 1 -allpools 1 -esm 3

This happens on all pools for all rigs. Nanopool does the same.

Why is this happening and how can it be corrected.
Jump to: