Claymore, you are a star! I would still gladly cough up 1%! 

With that said, in the ETH miner, there is an option -MINRIGSPEED - whats the chance of getting it in the XMR miner?

Hi Guys,

Can I specify the logfile name and maximum size (i.e. 75MB)?

Sadly, no joy for me. With an OC that was working before, I get BSODs after about 12 minutes of mining. The same setup runs fine with Phoenix miner.

Setting -tt 4 as per the quote above, only shows the GPU Temp and fan speed line every 120 seconds. Is the same possible for the GPU hashrate stats lines?

Awesome, thank you! Will try as soon as I am back home again. As Murphy will have it, I am out of town for a while. Will keep you posted if I find any other solutions too!

Hey guys, have any of you had an issue with V11.5, where when connection was lost to the pool, the miner resumed when the connection was restored, but at a lower hashrate?

At ~1:45am this morning, my miner lost connection, and when the connection was restored, the AMD cards mined at less than 50% of their usual hash rate. Strangely though, the NVidia cards on the rig resumed at their normal hashrate.

AMD Cards: Powercolor RX470, MSI Armor RX480
NVidia Cards: 2 x GTX 1050Ti

The log file:

01:43:23:567   15b0   ETH - Total Speed: 86.369 Mh/s, Total Shares: 913, Rejected: 1, Time: 12:03
01:43:23:567   15b0   ETH: GPU0 28.862 Mh/s, GPU1 29.061 Mh/s, GPU2 14.241 Mh/s, GPU3 14.206 Mh/s
01:43:24:223   15b0   buf: {"id":6,"jsonrpc":"2.0","result":true}
01:43:27:285   15b0   ETH: checking pool connection...
01:43:27:285   15b0   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
01:43:27:348   1370   checked ETH share on CPU, spent 5ms
01:43:27:348   1370   sent: {"worker":"Frankenstein","id":12,"method":"eth_submitWork","params": #RooiWillie - Line shortened for readability
01:43:27:348   1370   ETH: put share nonce 95e143d80337a242
01:43:27:363   15b0   ETH: 03/24/18-01:43:27 - SHARE FOUND - (GPU 2)
01:43:27:504   15b0   buf: {"id":3,"jsonrpc":"2.0","result": #RooiWillie - Line shortened for readability
01:43:27:692   15b0   buf: {"id":12,"jsonrpc":"2.0","result":true}
01:43:27:692   15b0   ETH: Share accepted (343 ms)!
01:43:37:301   15b0   ETH: checking pool connection...
01:43:37:301   15b0   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
01:43:37:520   15b0   buf: {"id":3,"jsonrpc":"2.0","result": #RooiWillie - Line shortened for readability
01:43:43:363   15b0   sent: {"id":6,"worker":"Frankenstein","jsonrpc":"2.0","method":"eth_submitHashrate","params": #RooiWillie - Line shortened for readability
01:43:43:582   15b0   buf: {"id":6,"jsonrpc":"2.0","result":true}

#RooiWillie - Removed a few log entries to make it more readable...

01:45:29:770   15b0   ETH: checking pool connection...
01:45:29:770   15b0   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
01:45:29:989   15b0   buf: {"id":3,"jsonrpc":"2.0","result": #RooiWillie - Line shortened for readability
01:45:36:645   15b0   buf: {"id":0,"jsonrpc":"2.0","result": #RooiWillie - Line shortened for readability
01:45:36:645   15b0   remove first packet 248
01:45:36:645   15b0   ETH: 03/24/18-01:45:36 - New job from eu1.ethermine.org:5555
01:45:36:645   15b0   target: 0x0000000112e0be82 (diff: 4000MH), epoch 176(2.37GB)
01:45:36:676   15b0   ETH - Total Speed: 56.436 Mh/s, Total Shares: 914, Rejected: 1, Time: 12:05
01:45:36:676   15b0   ETH: GPU0 12.901 Mh/s, GPU1 15.053 Mh/s, GPU2 14.250 Mh/s, GPU3 14.232 Mh/s

Sadly there is not much to be done here. You have 3 options:
1. Keep up with this method until it does not work anymore
2. Mine something else
3. Set up your rig with Linux. Source: https://www.youtube.com/watch?v=QPaee47TCZc

I have to be honest, the only reson I added in the -ethi argument was to avoid the miner having to detect what value to use, especially with the rig restarting once in a while because of the 0 fan speed picked up by Polly.

For me, faster startup means faster $$$. 

You did not mention GPU, but I am using -ethi 10 on Red Devil RX470 4GB and -ethi 14 on MSI Armor RX480 4GB

I can confirm that the miner is behaving well with my cards with the following OCs:

NVidia GTX 1050ti: +600 memory, -100 gpu clock and 75% power (samsung memory)
AMD RX470 4GB: 1500 mem straps, 96 TDP, 1125 gpu clock, 2000MHz memory
AMD RX480 4GB: 1500 mem straps, 104 TDP, 1125 gpu clock, 2000MHz memory

I have not had a crash yet. But in once instance, after mining the DEV Fee, I had a serious drop in hash rate across all GPUs (RX470, RX480, 2 x GTX 1050ti).

And it only happened once thus far.

I have also noticed the fan speed is reported as 0 once in a while, then Polly restarts the rig, although it was quite unneccesary. When I used multi pool miner some time ago, the API also reported zero fan speeds at random intervals.

Finally, stale shares are ranging from 4% to 15%. But overall hash rate increase seems to outweigh this by about 0.0001 ETH per day.

OK, so as promised, I split the rig up into NVidia and AMD seperately to see what happens. Only NVidia submitted stale shares. I even went and ran the pairs as 1 x RX 470 and 2 x GTX 1050ti, each with a hashrate of ~28MH/s.

Here is the strange one, in this setup (2 x Claymore instances, NVidia + AMD), the rig submitted less stale shares as when compared to a single Claymore instance with the cards mixed.. But it was not really stable. NVidia kept on restarting.

I am back to the mixed setup where I have a 6 - 9% stale share rate for the past 12 Hours.

Some rig info for the 28 / 28 test:
1 x RX 470, 1500 mem straps, memory OC to 2000MHz.
2 x GTX 1050Ti, +650MHz memory OC, - 100MHz CPU UC, 75% Power
Latest Windows 10 Pro, Claymore excluded from Defender
Core2Duo E8400, 4GB Ram, 16GB Virtual memory
~17% CPU Usage, 46% memory usage whilst login with TeamViewer
Polly keeping an eye on things

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

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?