Quote from: kristikun on March 11, 2019, 01:35:19 PM

Quote from: nebutech on March 11, 2019, 01:31:25 PM

Quote from: kristikun on March 11, 2019, 01:15:18 PM

Quote from: nebutech on March 11, 2019, 12:18:38 PM

Quote from: kristikun on March 11, 2019, 11:39:34 AM

Hello thanks for your hard work seems like this is only miner win10 compatible with gtx1080ti on cuckto31 my hash rate stable 1,5 im using nicehash pool but when checking speed 80% time it shows 0 hashrate , 20 % of time it shows actual speed 1,2-1,6 when checked after 24hours of mining the reported speed is only around 0,6 becouse 80% of time its not reporting any hashing activity but miner sends shares but probably not enough ? Please let me know if this is normal on cucktoo

When you say "checking speed", do you mean checking on nicehash website?

Nicehash gives a very high difficulty to miner due to large amount of miner rigs it connected. So the frequency of submitting found share to nicehash will be significantly lower than other pool (eg. sparkpool, f2pool).

And the hashrate calculated on nicehash based on how much share the miner submitted, could be very different from local hashrate, caused by the high difficulty.

I don't know how many 1080tis that you have, but if you got only 1 or 2 cards, then a relative big gap between nicehash reported hashrate and local hashrate could be normal, otherwise there's something wrong.

Thank you for answer im using only 1 gtx1080ti (zotac) and im checking hashrates on nh website / nh mobile apk , this relative big gap coused by high dif stratum which u mention would affect every other algo i connect to on nicehash to but this is just ur miner and cucktoo 31 algo on which i get this gap, When im mining x16r , beam , lyra2rev3 and other algos supported by nicehash i get hashrate fluctuaction but nothing like this and the result by pool = miner hashrate atleast most of the time but on cucktoo the local hashrate just doesnt get near pool reported hashrate , not in hashrates not in profit thats why im asking coz i cant double check on other miners since there isnt any around working on windows....

I carefully checked the communications between miner and nicehash.

There do exists a bug, when nicehash send a clean job, nbminer do not kill current job on GPU immediately.

This bug has much lower effect on other Grin pools (1% as most), since there are typically only 1 or 2 clean jobs every minute on other mining pools.

Things get different on Nicehash, the percentage of clean jobs is much higher, so this could be the reason that miner do not report any hashrate on nicehash for a certain amount of time.

I'll fix this issue in the next version, hopefully in next few days.

Thank you for your answer and keep the hard work GG

Fixed in v21.1.