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

[PB_SilentMiner]

Before the Byzantium update, my average hashrate was withing 3-4MH of my reported rate. But as of late its nearer 25-28MH difference.
Any ideas?

What is your ping time to pool and how many stale shares do you get at the pool?

Ping time from rig1
Pinging eu1.ethermine.org [46.105.121.53] with 32 bytes of data:
Reply from 46.105.121.53: bytes=32 time=30ms TTL=52
Reply from 46.105.121.53: bytes=32 time=22ms TTL=52
Reply from 46.105.121.53: bytes=32 time=22ms TTL=52
Reply from 46.105.121.53: bytes=32 time=21ms TTL=52

Ping statistics for 46.105.121.53:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 30ms, Average = 23ms

ping time from rig2
Pinging eu1.ethermine.org [46.105.121.53] with 32 bytes of data:
Reply from 46.105.121.53: bytes=32 time=21ms TTL=52
Reply from 46.105.121.53: bytes=32 time=21ms TTL=52
Reply from 46.105.121.53: bytes=32 time=20ms TTL=52
Reply from 46.105.121.53: bytes=32 time=21ms TTL=52

Ping statistics for 46.105.121.53:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 21ms, Average = 20ms


Number of stale shares has risen from practically nothing 0-2/3 every 10 mins up to 15-20 every 10 mins

[wOvAN]

Before the Byzantium update, my average hashrate was withing 3-4MH of my reported rate. But as of late its nearer 25-28MH difference.

Any ideas?

Switch from Ethmine to Drawfpool. Share difficulty on E. 4000MH on D. 2000MH. so there should be less stales, or other pool with lower diff per share

press S to see current diff

[Snowykingdom]

Goodbye clayclay fee  

https://bitcointalk.org/index.php?topic=1792180.msg23444415#msg23444415

No need to pay clayclay after so many versions...

Yes, he has great miner but clayclay is fed well already and should lower the fee instead of getting more greedy.

[aameeshah]

Woot! Nice Dev fee update in latest. thx Claymore.
Can u plz look into pathetic Windows 10 crashes! It made me switch 2 win7. None of ur other miners crash but ETH is very unstable on Win10.

[kkourmousis]

Goodbye clayclay fee  

https://bitcointalk.org/index.php?topic=1792180.msg23444415#msg23444415

No need to pay clayclay after so many versions...

Yes, he has great miner but clayclay is fed well already and should lower the fee instead of getting more greedy.

So your argument is that @Claymore earned more than you think he should have (through his work, not by luck or cheat) ?

First of all, mentioning the method this guy uses to cheat is pretty much an invitation @Claymore to lock it up.

Secondly, do you see a single outcome on this that can result in better mining for us all? Claymore getting pissed and stopping support of his miner would be much more catastrophic than your 1% fee

[FlowLive]

Goodbye clayclay fee  

https://bitcointalk.org/index.php?topic=1792180.msg23444415#msg23444415

No need to pay clayclay after so many versions...

Yes, he has great miner but clayclay is fed well already and should lower the fee instead of getting more greedy.

So your argument is that @Claymore earned more than you think he should have (through his work, not by luck or cheat) ?

First of all, mentioning the method this guy uses to cheat is pretty much an invitation @Claymore to lock it up.

Secondly, do you see a single outcome on this that can result in better mining for us all? Claymore getting pissed and stopping support of his miner would be much more catastrophic than your 1% fee

AMEN!
Keep'em comin' Claymore!
 

[Snowykingdom]

So your argument is that @Claymore earned more than you think he should have (through his work, not by luck or cheat) ?

First of all, mentioning the method this guy uses to cheat is pretty much an invitation @Claymore to lock it up.

Secondly, do you see a single outcome on this that can result in better mining for us all? Claymore getting pissed and stopping support of his miner would be much more catastrophic than your 1% fee

Stop for being fuckin hypocrite in this crypto world, even your friends will kill you for each penny you have  

BTFW, you are not the only person who never used a proprietary software without breaking it aren't you?

BS.

[UMICHStatistican]

Guys, I'm experiencing a problem on all my rigs with Remote Manager.  If I log onto any of my rigs remotely and startup Claymore's batch file, I can see all the fan speeds, temps, etc. in Claymore's remote manager.  It's great.   However, if I set claymore to autostart mining by placing a batch script within a scheduled task to run the batch script on startup, Claymore executes and starts mining, and I can see all the statistics in Claymore's remote manager, except fan speeds and temps are not displayed.  It seems only when Claymore is executed in an unattended mode does this happen.  Is there anyway to get the fan and temp stats to display in the remote manager with an autostart of Claymore?

Thanks.

[Vann]

You need a monitor or dummy plug in the primary GPU for the AMD driver to read the fan speed and temps.

[rodney2250]

Hey guys,

Could someone clarify the meaning of the different shares metrics in claymores' output?

Rejected shares - is this the same as stale shares?
Incorrect shares - invalid shares?
Total shares - is this the sum of valid+incorrect+rejected shares?

Thank you

[MentalNomad]

Goodbye clayclay fee  


No need to pay clayclay after so many versions...

Yes, he has great miner but clayclay is fed well already and should lower the fee instead of getting more greedy.

There's a much easier way to avoid the Claymore miner dev fees.

Use a different miner.

Stop for being fuckin hypocrite in this crypto world, even your friends will kill you for each penny you have  

Go learn what friends are; you apparently haven't had any.

[MentalNomad]

Hey guys,

Could someone clarify the meaning of the different shares metrics in claymores' output?

Rejected shares - is this the same as stale shares?
Incorrect shares - invalid shares?
Total shares - is this the sum of valid+incorrect+rejected shares?

Thank you

Total Shares: the sum count of all shares found by your GPUs since the last time you started Claymore.

Rejected share: share that you computed and sent to your mining pool, but which the mining pool rejected as not being correct. This might point to memory on your GPU being corrupted, perhaps because of overheating or because of an OC that is too high. If the memory is not faulty, a restart can clear it up, if it doesn't get driven too hard again.

Stale share: a share that you found and sent to the pool and was confirmed as correct, but which arrived too late; you sent a share when the pool had already moved on to a new block. This may point to a slow network connection, or perhaps your system is overtaxed and is unable to move your GPUs to the new work quickly enough when new work comes in. Everyone will have some small portion of stale shares, unless their miners are pretty much directly connected to the pool's servers and can get new work notices with almost no delay (which is pretty much impossible, unless you're running the pool servers and install the miners next to them.) If your pool provides multiple addresses, ping them and see which is "closest" to you (has the shortest time delay) and make sure you work with that address.

[TerranGas]

Hello, Guys. I'm asking for help as I got stuck with a problem. I read through the topic and tried many things. but didn't work out.

I have two farms mining ETH+DCR for 6 and 4 cards. The problem with a second farm.

I have 4 RX570 cards, motherboard ASrock z97. WIN 10 It used to give me 100 mh/s stable. However, then miner started to crash with the message:
"NO AMD OPENCL or NVIDIA CUDA GPUs found, exit".

ok... uninstall drivers, update cards with Crimson ReLive beta Blockchain Driver, patch drivers, restart and launch miner again.

The problem arises exactly in 120 minutes again... not 119 or 121, it is exactly two hours before it crashes again. The monitor blinks a couple of time. speed goes to 0, and the end.

I tried to repatch cards via bios (atiflash), played with graphic cards, nothing works. The only thing I noticed that if I launch 3 cards from 4... they work fine for a relatively long time without crashes. Notable, that I tried each of the card, and they seem to be normal.

However, when i start all 4... it works only 120 minute and "NO AMD OPENCL...".

Please, let me know if there are any ideas, I can provide you with more info, whatever you ask.

[rodney2250]

Total Shares: the sum count of all shares found by your GPUs since the last time you started Claymore.

Rejected share: share that you computed and sent to your mining pool, but which the mining pool rejected as not being correct. This might point to memory on your GPU being corrupted, perhaps because of overheating or because of an OC that is too high. If the memory is not faulty, a restart can clear it up, if it doesn't get driven too hard again.

Stale share: a share that you found and sent to the pool and was confirmed as correct, but which arrived too late; you sent a share when the pool had already moved on to a new block. This may point to a slow network connection, or perhaps your system is overtaxed and is unable to move your GPUs to the new work quickly enough when new work comes in. Everyone will have some small portion of stale shares, unless their miners are pretty much directly connected to the pool's servers and can get new work notices with almost no delay (which is pretty much impossible, unless you're running the pool servers and install the miners next to them.) If your pool provides multiple addresses, ping them and see which is "closest" to you (has the shortest time delay) and make sure you work with that address.

Thanks. What about incorrect share (as reported by claymore's miner)?

[MentalNomad]

Hello, Guys. I'm asking for help as I got stuck with a problem. I read through the topic and tried many things. but didn't work out.

I have two farms mining ETH+DCR for 6 and 4 cards. The problem with a second farm.

I have 4 RX570 cards, motherboard ASrock z97. It used to give me 100 mh/s stable. However, then miner started to crash with the message:
"NO AMD OPENCL or NVIDIA CUDA GPUs found, exit".

ok... uninstall drivers, update cards with Crimson ReLive beta Blockchain Driver, patch drivers, restart and launch miner again.

The problem arises exactly in 120 minutes again... not 119 or 121, it is exactly two hours before it crashes again. The monitor blinks a couple of time. speed goes to 0, and the end.

I tried to repatch cards via bios (atiflash), played with graphic cards, nothing works. The only thing I noticed that if I launch 3 cards from 4... they work fine for a relatively long time without crashes. Notable, that I tried each of the card, and they seem to be normal.

However, when i start all 4... it works only 120 minute and "NO AMD OPENCL...".

Please, let me know if there are any ideas, I can provide you with more info, whatever you ask.

I don't have a solution, but if it's really exactly 120 minutes, one workaround is to set the rig to auto-reboot after 119 minutes.

I've used that as a workaround on rigs running Win 10 Ent trial, which is good for 90 days... after 90 days, it expires, and will shut down after 60 minutes. So I set the machine up to reboot in 59 minutes. With a rig on SSD, it actually mines 98% as much as usual despite doing the reboots, so it's a good workaround until you have time to fix it properly.

[MentalNomad]

Thanks. What about incorrect share (as reported by claymore's miner)?

I don't see incorrect shares reported in Claymore's on-screen metrics.

Claymore reports Total and Rejected. For example:

Code:

ETH - Total Speed: 253.379 Mh/s, Total Shares: 2809, Rejected: 0, Time: 12:05

It will also display responses it gets from the pool, such as "Share accepted"; the pool would report Incorrect or Stale shares.

I'm pretty sure that an Incorrect Share report from a pool is counted by Claymore as Rejected.

If you're looking at an incorrect share note in the Claymore logfile, I'd call that a lot file, not a metric. But it means the same thing - it's not a valid share; it's an incorrect result. For example:

Code:

19:12:40:853	fcff9700	GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!

I think that's fairly self-explanatory. If not, please ask specifically about what's confusing you.

[rodney2250]

Ok. I think rejected and incorrect shares are different. Look at the example below (Claymore 9.:

Code:

GPU #0: Ellesmere, 4096 MB available, 36 compute units
GPU #1: Ellesmere, 4096 MB available, 36 compute units
GPU #2: Ellesmere, 4096 MB available, 36 compute units
GPU #3: Ellesmere, 4096 MB available, 32 compute units
GPU #4: Ellesmere, 8192 MB available, 32 compute units
GPU #5: Ellesmere, 8192 MB available, 32 compute units
ETH - Total Speed: 162.347 Mh/s, Total Shares: 13023(2222+2204+2132+2168+2187+2227), Rejected: 0, Time: 100:05
ETH: GPU0 27.513 Mh/s, GPU1 27.380 Mh/s, GPU2 26.206 Mh/s, GPU3 27.200 Mh/s, GPU4 27.025 Mh/s, GPU5 27.024 Mh/s
Incorrect ETH shares: GPU0 25, GPU1 76, GPU2 10
 1 minute average ETH total speed: 162.193 Mh/s
Pool switches: ETH - 0, DCR - 0
Current ETH share target: 0x00000000ffb34c02 (diff: 4300MH), epoch 34(1.27GB)
GPU0 t=73C fan=60%, GPU1 t=73C fan=50%, GPU2 t=72C fan=40%, GPU3 t=74C fan=49%, GPU4 t=69C fan=37%, GPU5 t=69C fan=38%

zero (0) rejected shares, but multiple incorrect shares: GPU0 25, GPU1 76, GPU2 10

Any ideas?

[davescream]

Ok. I think rejected and incorrect shares are different. Look at the example below (Claymore 9.:

zero (0) rejected shares, but multiple incorrect shares: GPU0 25, GPU1 76, GPU2 10

Any ideas?

I think incorrect shares is faulty shares which were detected locally.
Rejected shares are incorrect shares which were send to pool, but pool rejected it.

[kkourmousis]

zero (0) rejected shares, but multiple incorrect shares: GPU0 25, GPU1 76, GPU2 10

Any ideas?

Download HWinfo and check your gpus for memory errors. As long as you have errors you should drop clocks or increase voltage. When errors get to 0 ypu are not incorrect hashes free, I am not sure why, must be that tight memory straps of modded BIOS. In my case I stil have ~1% Incorrecr hashes (compared to accepted hashes)

[MentalNomad]

I think incorrect shares is faulty shares which were detected locally.
Rejected shares are incorrect shares which were send to pool, but pool rejected it.

I think that's right.

Ok. I think rejected and incorrect shares are different. Look at the example below (Claymore 9.:

Code:

GPU #0: Ellesmere, 4096 MB available, 36 compute units
GPU #1: Ellesmere, 4096 MB available, 36 compute units
GPU #2: Ellesmere, 4096 MB available, 36 compute units
GPU #3: Ellesmere, 4096 MB available, 32 compute units
GPU #4: Ellesmere, 8192 MB available, 32 compute units
GPU #5: Ellesmere, 8192 MB available, 32 compute units
ETH - Total Speed: 162.347 Mh/s, Total Shares: 13023(2222+2204+2132+2168+2187+2227), Rejected: 0, Time: 100:05
ETH: GPU0 27.513 Mh/s, GPU1 27.380 Mh/s, GPU2 26.206 Mh/s, GPU3 27.200 Mh/s, GPU4 27.025 Mh/s, GPU5 27.024 Mh/s
Incorrect ETH shares: GPU0 25, GPU1 76, GPU2 10
 1 minute average ETH total speed: 162.193 Mh/s
Pool switches: ETH - 0, DCR - 0
Current ETH share target: 0x00000000ffb34c02 (diff: 4300MH), epoch 34(1.27GB)
GPU0 t=73C fan=60%, GPU1 t=73C fan=50%, GPU2 t=72C fan=40%, GPU3 t=74C fan=49%, GPU4 t=69C fan=37%, GPU5 t=69C fan=38%

zero (0) rejected shares, but multiple incorrect shares: GPU0 25, GPU1 76, GPU2 10

Any ideas?

I can see one incorrect share or two in some of my 24-hour logs, but not most of them. Maybe I've just never seen one, on-screen.

I do notice that you have six cards... and of the four cards over 70C, three are throwing incorrect shares. The two that are below 70C are clean.

I can tell you that I crank my fans way higher at those temps than you do; when the GPU core is that hot, the memory may be even hotter, and many cards can't handle it. I have cards that crap out entirely when they break 70C. Some cards can obviously go way hotter; varies between brands and models, and within a model, can vary by individual card and/or where it is in the rig (because of airflow.)

Also, side note: the power draw for fans goes up more than linearly as you go above 50%; the back pressure makes the fan noisy and less power-efficient. Backing off the OC may even be more cost-effective than pinning the fan at 100%.