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

[merc84]

v 3.3

It's strange. After starting this version first time it says that the DAG file is corrupted on EVERY my RIG of 6. But the problem was with only one of them. The others were mining well instead. So, it looks like the DAG with the wrong CRC doesn't mean that you can't mine... Or... like something wrong with the DAG file integrity check in the miner.

But, thank you, Mr. Claymore )

Claymore already stated that the dag generated by v3.2 is not compatible with v3.3

[restless]

Which decred pool is best atm?

I tried suprnova and pool.mn, but on both pools I see 20-25% of hashrate reported by miner 3.3 :S

Trying zpool.ca with

-dpool stratum+tcp://mine.zpool.ca:5744 -dwal DecredWallet -dpsw c=DCR,decred

But I see no accepted shares on-site :/

[thesaltonsea]

Use Coinme - https://www2.coinmine.pl/dcr/index.php , less than 1% rejects with stratum

[Lastmoadman]

ver 3.3 is bad for machines with weak cpu/hdd
Many freezes when finished generating first dag, then starting next one and attempt to start mining.
Also I had several "crc dag fail" after normal miner restart.
I'm back to 3.2 - it is cool! But I miss failover option.
Can we disable crc check somehow? I had no problem with corrupted DAG's before with Claymore miner ...

I have the same problem. After generating the first DAG, the computer will crash. I may have to reduce the intensity or the clock frequency.

[citronick]

Which decred pool is best atm?

I tried suprnova and pool.mn, but on both pools I see 20-25% of hashrate reported by miner 3.3 :S

Trying zpool.ca with

-dpool stratum+tcp://mine.zpool.ca:5744 -dwal DecredWallet -dpsw c=DCR,decred

But I see no accepted shares on-site :/

i get about 1-2% rejects at zpool - still best stratum site that pays in BTC.

With BTC price high now, maybe worth it to collect in BTC.

So change your syntax to:

-dpool stratum+tcp://mine.zpool.ca:5744 -dwal <<BTC address>> -dpsw c=BTC,decred

[Claymore]

If I use the eth-proxy (stratum proxy) from dwarfpool (http://dwarfpool.com/static/eth-proxy-win.zip) running on localhost/local network, how do I make this program connect to it ? It already has the wallet address inside the .conf file of stratum. Or is that not supported and I must use the stratum address of dwarfpool directly ?

Another question: Are all the "shares" submitted on dwarfpool of equal value ? Or are they weighted according to the difficulty reported by the miner?

Also has anyone made some very precise calculations, considering current eth/decred prices and the performance of this merged miner, is it more profitable to mine them both with this program or just one of them?

AFAIK Dwarfpool eth-proxy is NOT supported.


2 Claymore, as I see there is -allpools option for every pool defined, what happens when my miner works on pool with
allpools 0, if dev fee won't work there?

Where do you see that -allpools option for every pool defined?
If devfee cannot work on a pool, you won't be able to use this pool, miner will show warning and remove this pool from the list until you add "-allpools 1" option.

[citronick]

ver 3.3 is bad for machines with weak cpu/hdd
Many freezes when finished generating first dag, then starting next one and attempt to start mining.
Also I had several "crc dag fail" after normal miner restart.
I'm back to 3.2 - it is cool! But I miss failover option.
Can we disable crc check somehow? I had no problem with corrupted DAG's before with Claymore miner ...

I have the same problem. After generating the first DAG, the computer will crash. I may have to reduce the intensity or the clock frequency.

similar scenario here... my CPU is Celeron 1840 with 8 GB RAM, and 20GB windows virtual memory.

It "freezes" for awhile, about 3-4 seconds.... then mine as per normal... I guess it got passed the DAG tasks completed with just enough juice to start mining.

I don't get this freezing in my AMD 8-core CPU, 16GB system.

[Claymore]

ver 3.3 is bad for machines with weak cpu/hdd
Many freezes when finished generating first dag, then starting next one and attempt to start mining.
Also I had several "crc dag fail" after normal miner restart.
I'm back to 3.2 - it is cool! But I miss failover option.
Can we disable crc check somehow? I had no problem with corrupted DAG's before with Claymore miner ...

I had problems with DAG on one of my test rigs after hard reboot. It sent wrong shares for a few hours before I noticed that something is wrong.
DAG file size was ok and it had correct signature at beginning, but it was corrupted. So I think checking CRC is necessary.
PM me some logs so I can check the details. I can postpone next DAG generation for a few minutes and/or reduce CPU load for it.
Anyway, v3.2 creates next DAG too, so you must see same freezes. The only difference is CRC check when DAG is loaded, but it must not take more than 2-4 seconds even on slow CPU.

[restless]

Where do you see that -allpools option for every pool defined?
If devfee cannot work on a pool, you won't be able to use this pool, miner will show warning and remove this pool from the list until you add "-allpools 1" option.

Its in the sample epools.txt

# POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F , PSW: x, WORKER: r270x, ESM: 1, ALLPOOLS: 1
# POOL: us1.ethermine.org:4444, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F, PSW: x, WORKER: , ESM: 1, ALLPOOLS: 0
# POOL: coinotron.com:3344, WALLET: YourUserName.YourWorkerName, PSW: YourWorkerPass, WORKER: , ESM: 2, ALLPOOLS: 1

[Claymore]

Where do you see that -allpools option for every pool defined?
If devfee cannot work on a pool, you won't be able to use this pool, miner will show warning and remove this pool from the list until you add "-allpools 1" option.

Its in the sample epools.txt

# POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F , PSW: x, WORKER: r270x, ESM: 1, ALLPOOLS: 1
# POOL: us1.ethermine.org:4444, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F, PSW: x, WORKER: , ESM: 1, ALLPOOLS: 0
# POOL: coinotron.com:3344, WALLET: YourUserName.YourWorkerName, PSW: YourWorkerPass, WORKER: , ESM: 2, ALLPOOLS: 1

Default epools.txt is a bit different:

# POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F, PSW: x, WORKER: , ESM: 0, ALLPOOLS: 0
# POOL: us1.ethermine.org:4444, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F, PSW: x, WORKER: , ESM: 1, ALLPOOLS: 0
# POOL: coinotron.com:3344, WALLET: YourUserName.YourWorkerName, PSW: YourWorkerPass, WORKER: , ESM: 2, ALLPOOLS: 1

So ALLPOOLS is 0 for most pools. It is required only for pools that use USERNAME.WORKER as login or as worker, miner will show warning and removes such pool from the list.

PS. I think everyone understands that "#" disables line as explained in readme. I did it because otherwise miner could switch to these pools and if you did not change credentials it will mine but not for you. At startup miner shows how many pools it accepted for ETH and DCR.

[restless]

Sorry, now I remember taht I added allpools 1 to dwarfpool in order to be sure that devfee is mined, can this be a problem?
Setting 1 when its not needed?

[Gagana]

The only one rig has this problem.

If I start it without "-allpools 1" option it can't connect to devfee pool and exits. If I start it with this option, then it starts, gets jobs but doesdidn't send the results back. I see in the log file:

Code:

12:29:25:775 a88 ETH: put share nonce c8fadd01420866c
12:29:25:775 a88 ETH round found 1 shares
12:29:25:785 10e4 ETH: 04/27/16-12:29:25 - SHARE FOUND - (GPU 2)
12:29:25:785 10e4 send: {"worker":"rig04","id":4,"method":"eth_submitWork","params":["0x0c8fadd01420866c","0x0373b2ccd691ee8dd82b0bf5cf6c6f7fa6b0cad8314253d69f4124659eec3a1e","0xb76e79e4824dca1525ea252fd29fc08a2819959a83331c571a2b16c2c0f6ee59"]}


12:29:25:835 10e4 got 15 bytes
12:29:25:835 10e4 buf: Internal Error

12:29:25:835 10e4 buf: InternalError

DCR is working perfect here. The problem is only with ETH.

My start command is

Code:

EthDcrMiner64.exe -wd 1 -r 0 -epool eth-ru.dwarfpool.com:8008 -ewal 0xXXXXXX -epsw rig04 -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal gagana.rig04 -eworker rig04 -dpsw x -allpools 1
 

What could it be?

[Claymore]

Sorry, now I remember taht I added allpools 1 to dwarfpool in order to be sure that devfee is mined, can this be a problem?
Setting 1 when its not needed?

-allpools is ignored for pools that support wallet addresses, like dwarfpool, ethpool, ethermine etc.

[Claymore]

The only one rig has this problem.

If I start it without "-allpools 1" option it can't connect to devfee pool and exits. If I start it with this option, then it starts, gets jobs but doesdidn't send the results back. I see in the log file:

Code:

12:29:25:775 a88 ETH: put share nonce c8fadd01420866c
12:29:25:775 a88 ETH round found 1 shares
12:29:25:785 10e4 ETH: 04/27/16-12:29:25 - SHARE FOUND - (GPU 2)
12:29:25:785 10e4 send: {"worker":"rig04","id":4,"method":"eth_submitWork","params":["0x0c8fadd01420866c","0x0373b2ccd691ee8dd82b0bf5cf6c6f7fa6b0cad8314253d69f4124659eec3a1e","0xb76e79e4824dca1525ea252fd29fc08a2819959a83331c571a2b16c2c0f6ee59"]}


12:29:25:835 10e4 got 15 bytes
12:29:25:835 10e4 buf: Internal Error

12:29:25:835 10e4 buf: InternalError

DCR is working perfect here. The problem is only with ETH.

My start command is

Code:

EthDcrMiner64.exe -wd 1 -r 0 -epool eth-ru.dwarfpool.com:8008 -ewal 0xXXXXXX -epsw rig04 -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal gagana.rig04 -eworker rig04 -dpsw x -allpools 1
 

What could it be?

1. -allpools is ignored for pools that support wallet addresses, like dwarfpool, ethpool, ethermine etc. So you can use -allpools 0 or 1 or remove it at all.
2. Just checked your command line (only set my wallet address) and it works, it finds ETH shares and pool accepts them.

[Rux]

claymore, i have 15.12 and my 2 x 280x on this new miner are mining aprox 11.6 mhs

what to do?

[Claymore]

claymore, i have 15.12 and my 2 x 280x on this new miner are mining aprox 11.6 mhs

what to do?

Did they mine faster on v3.2?

[Masked_Immortal]

is it possible to specify cards by name?
it seems different order between msi afterburner and miner

[Rux]

claymore, i have 15.12 and my 2 x 280x on this new miner are mining aprox 11.6 mhs

what to do?

Did they mine faster on v3.2?

it was 21-22 mhs per card on 3.2...

gimme 5 min to download 3.2 and start build dag with it... will get back with results asap

EDIT: same :/

270 8,9 mhs

2 x 280x 11mhs

i dont know what to do? :/

EDIT2:

in this rig i have 2 x 280x, and 2 x 270 ... on last miner no problems, 270 hashing 14 mhs and 280x hashing 21mhs

after i tried this new miner i got 11 mhs and 8 mhs

[thesaltonsea]

Even with lowered ethi , my rig is crashing and cant boot after that, its like that from the last 3-4 versions ... When we calculate the time that it is chrased and not mining for hours, the profit from the decred mining cant cover the so many hours downtime ... So the problem is not the ethi setting, maybe you changed something with the optimizations ?

[olajos]

why is lowered ethi to 8? my miners was perfectly working on 16. even i have a slightly bigger hashrate with 16