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

[RooiWillie]

No, because pool doesn't notify miner that the share is stale, you can only see it on pool dashboard

Bummer, but OK. I'll spit the cards up into two - AMD / NVidia and see what the pool reports.

[1714152328]

1714152328

[1714152328]

1714152328

[1714152328]

1714152328

[1714152328]

1714152328

[frikazoid]

Hi

-oldkernels - solved problems =)

[Sjalero]

11.4/11.5 is a highly welcome update, better hashrate stability and much less stales.

Thanks a lot Claymore, keep it going!

[Koinmen]

Hey guys,

I still have a number of stale shares on ethermine.org whilst using v11.5. To give you an idea, I regularly get over 10% stale shares. I mine with 2 x GTX 1050ti, 1 x rx470 and 1 x rx480.

So onto the question, Claymore, is it possible to log what gpu is submitting the stale share?

No, because pool doesn't notify miner that the share is stale, you can only see it on pool dashboard

I think that all shares over 95ms  go to stale shares.  I my case  6  gtx1060 with 11.4  run about 3% stale, but who increment the stale more is the bad quality power wires check the 6 or 8 pin plug male-female, when I make by myself the wires the stales were reduced.

[big al]

I think the problem is ethermine servers.

[DiHunter]

Hey guys,

I still have a number of stale shares on ethermine.org whilst using v11.5. To give you an idea, I regularly get over 10% stale shares. I mine with 2 x GTX 1050ti, 1 x rx470 and 1 x rx480.

So onto the question, Claymore, is it possible to log what gpu is submitting the stale share?

No, because pool doesn't notify miner that the share is stale, you can only see it on pool dashboard

Really?! So how does this option works, if miner does not know about stale shares:

-estale   send Ethereum stale shares to pool, it can increase effective hashrate a bit. Default value is "1", set "-estale 0" if you don't want to send stale shares.

[ddjjxxiiaa]

Hello guys,
I am a noob miner since 2 months. From 10.6 to 11.4, i have got a same problem.

I have 6 RX588 rig, 30M hashrate for each card.

Sometimes after restarting the Claymore, or after reboot the machine and then start the Claymore, the Hashrate will down to 26 or 27, it may be return to 30 by itself after one or two hour, maybe not.

If i disable the GPU by clicking the number for 5 sec, and then enable it, the hashrate will be return to 30.

Does anyone has the same problem or the solution?

Thanks ~~~~~~~~~~~

Nobody else has the same problem?

[Claymore]

Hey guys,

I still have a number of stale shares on ethermine.org whilst using v11.5. To give you an idea, I regularly get over 10% stale shares. I mine with 2 x GTX 1050ti, 1 x rx470 and 1 x rx480.

So onto the question, Claymore, is it possible to log what gpu is submitting the stale share?

No, because pool doesn't notify miner that the share is stale, you can only see it on pool dashboard

Really?! So how does this option works, if miner does not know about stale shares:

-estale   send Ethereum stale shares to pool, it can increase effective hashrate a bit. Default value is "1", set "-estale 0" if you don't want to send stale shares.

Pool sees different rate of stale shares than miner, it's always higher, so I don't see any reason to show stale shares rate of the miner, it's quite low. However, due to some delays on pool and also network delays, pool always will get more stale shares than miner knows.
The only way to get the pool stale shares rate is to get appropriate response from pool, but pool does not notify miner that the share is stale. To understand it deeply you should learn how pool mining works in details.

[Sjalero]

Hey guys,

I still have a number of stale shares on ethermine.org whilst using v11.5. To give you an idea, I regularly get over 10% stale shares. I mine with 2 x GTX 1050ti, 1 x rx470 and 1 x rx480.

So onto the question, Claymore, is it possible to log what gpu is submitting the stale share?

No, because pool doesn't notify miner that the share is stale, you can only see it on pool dashboard

Really?! So how does this option works, if miner does not know about stale shares:

-estale   send Ethereum stale shares to pool, it can increase effective hashrate a bit. Default value is "1", set "-estale 0" if you don't want to send stale shares.

As I understand a stale share is a share which was sent to the pool by another miner before yours sent it. So your miner sent a share which already was accepted by the pool. When you know this you understand why only the pool knows which share is stale is and which isn't.

[Poweriser]

Hello guys,
I am a noob miner since 2 months. From 10.6 to 11.4, i have got a same problem.

I have 6 RX588 rig, 30M hashrate for each card.

Sometimes after restarting the Claymore, or after reboot the machine and then start the Claymore, the Hashrate will down to 26 or 27, it may be return to 30 by itself after one or two hour, maybe not.

If i disable the GPU by clicking the number for 5 sec, and then enable it, the hashrate will be return to 30.

Does anyone has the same problem or the solution?

Thanks ~~~~~~~~~~~

Nobody else has the same problem?

Similarly

[HHunter]

I have 4 rigs that have MSI RX 570 Armor cards and 4 with other brand cards, when i upgrade claymore to 11.4 from 11 at least 3 of the cards on each of the MSI card rigs fail.

1 x MSI rig is using 6 x RX570 4GB = Cards stop mining 11.4 on linux, 1500 straps bios
3 x MSI rigs are 18 x RX570 8GB = Cards stop mining with 11.4 on linux, standard bios

4 x Rigs with mix of RX570 Nitro+, Gigabyte RX570, RX570 Pulse on 11.4 on linux = mining fine with not a single card stopping.

Very odd that its just the MSI Armor cards, only one else seeing this?

Is everyone getting the same hashrate increase with 11.5 using the oldkernals?

Thanks
 

[nitrobg]

Hello guys,
I am a noob miner since 2 months. From 10.6 to 11.4, i have got a same problem.

I have 6 RX588 rig, 30M hashrate for each card.

Sometimes after restarting the Claymore, or after reboot the machine and then start the Claymore, the Hashrate will down to 26 or 27, it may be return to 30 by itself after one or two hour, maybe not.

If i disable the GPU by clicking the number for 5 sec, and then enable it, the hashrate will be return to 30.

Does anyone has the same problem or the solution?

Thanks ~~~~~~~~~~~

Nobody else has the same problem?

Similarly

Your cards might be throttling. Check GPU-Z and see if the core clock drops down than the one you've set. If they do - lower the voltage, preferably below 900, and try again. If they still throttle - increase the power limit by a notch.

[zibastian]

Hello guys,
I am a noob miner since 2 months. From 10.6 to 11.4, i have got a same problem.

I have 6 RX588 rig, 30M hashrate for each card.

Sometimes after restarting the Claymore, or after reboot the machine and then start the Claymore, the Hashrate will down to 26 or 27, it may be return to 30 by itself after one or two hour, maybe not.

If i disable the GPU by clicking the number for 5 sec, and then enable it, the hashrate will be return to 30.

Does anyone has the same problem or the solution?

Thanks ~~~~~~~~~~~

Nobody else has the same problem?

This is an issue with the driver, preventing the correct voltage to be applied after a GPU crash. You can also just restart the miner and you should get your hashrate back. This is not linked to Claymore, you should have the same behaviour with any miner

Zib

[DiHunter]

Hey guys,

I still have a number of stale shares on ethermine.org whilst using v11.5. To give you an idea, I regularly get over 10% stale shares. I mine with 2 x GTX 1050ti, 1 x rx470 and 1 x rx480.

So onto the question, Claymore, is it possible to log what gpu is submitting the stale share?

No, because pool doesn't notify miner that the share is stale, you can only see it on pool dashboard

Really?! So how does this option works, if miner does not know about stale shares:

-estale   send Ethereum stale shares to pool, it can increase effective hashrate a bit. Default value is "1", set "-estale 0" if you don't want to send stale shares.

Pool sees different rate of stale shares than miner, it's always higher, so I don't see any reason to show stale shares rate of the miner, it's quite low. However, due to some delays on pool and also network delays, pool always will get more stale shares than miner knows.
The only way to get the pool stale shares rate is to get appropriate response from pool, but pool does not notify miner that the share is stale. To understand it deeply you should learn how pool mining works in details.

Ok, thank you for explain.
Claymore,
Don't you want to add a new option into your miner: to set epools.txt (dpools.txt) files as options in command line or in config.txt file. That will let user to launch just different bat-files when switching to another coin without making each time changes in epools(dpools)-files for new alternative pools.

[ISUther]

Hello,
I just downloaded
Claymore Dual Ethereum++Decred Siacoin miner from:
https://mega.nz/#F!O4YA2JgD!n2b4iSHQDruEsYUvTQP5_w

If i open file named as "start" with note pad i have line like this over there:
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal Redhex.my -dpsw x

I do understand that i can replace eu1.ethermine.org:4444 with my pool address and dot rig name and e-mail.
like i had in older version:
Here is what i had in older version:
EthDcrMiner64.exe -epool eth-eu1.nanopool.org:9999 -ewal 0x43Ae5c0c80938a6596C29B4B7Bd699547791909F.Tannkaevab2/cocliosttro.tan@gmail.com -epsw x -mode 1 -ftime 10

But i do not understand what is that:
 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal Redhex.my -dpsw x

It looks like some one else pool and name?
SHould i replace those?
Is that mining to some one else?

[Claymore]

As I understand a stale share is a share which was sent to the pool by another miner before yours sent it. So your miner sent a share which already was accepted by the pool. When you know this you understand why only the pool knows which share is stale is and which isn't.

When two miners send same share it's called a duplicate share.
Stale share is a share that is sent too late, when pool is already working on new block.

Don't you want to add a new option into your miner: to set epools.txt (dpools.txt) files as options in command line or in config.txt file. That will let user to launch just different bat-files when switching to another coin without making each time changes in epools(dpools)-files for new alternative pools.

Ok, I will add it in next update.

[Sjalero]

As I understand a stale share is a share which was sent to the pool by another miner before yours sent it. So your miner sent a share which already was accepted by the pool. When you know this you understand why only the pool knows which share is stale is and which isn't.

When two miners send same share it's called a duplicate share.
Stale share is a share that is sent too late, when pool is already working on new block.

Don't you want to add a new option into your miner: to set epools.txt (dpools.txt) files as options in command line or in config.txt file. That will let user to launch just different bat-files when switching to another coin without making each time changes in epools(dpools)-files for new alternative pools.

Ok, I will add it in next update.

I love learning every day, thanks for clarification!

[DiHunter]

But i do not understand what is that:
 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal Redhex.my -dpsw x

It looks like some one else pool and name?
SHould i replace those?
Is that mining to some one else?

It's for dual mining - second coin options example. Delete it, if don't need, or set your own. Just read "Readme.txt" in miner folder!

Don't you want to add a new option into your miner: to set epools.txt (dpools.txt) files as options in command line or in config.txt file. That will let user to launch just different bat-files when switching to another coin without making each time changes in epools(dpools)-files for new alternative pools.

Ok, I will add it in next update.

Great! Thanks once more.

[0xb1]

Yep.. indeed version 11.5 seems to be a step forward.
Shares are found on a more regular basis, staleshares down to 0-2%.

Thumbs up.

[Haik]

I tried to reinstall geforce drivers but still no result. When i open this miner it only show this "The code execution can not proceed because OpenCL.dll was not found". How to fix this error?