NBMiner v42.2, 100% LHR unlock for ETH mining !

[kristikun]

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

[1713456454]

1713456454

[1713456454]

1713456454

[1713456454]

1713456454

[1713456454]

1713456454

[nebutech]

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.

[davith75]

Mmm pool side show 10kh/s less then what miner shows  and when it does show near what miner shows it slowly drops. On BTM

I don't know where you're located, but for the BTM since all the pools are in China, you can expect to lose 10% of the Hasrate from the timeout & disconnection you have.

For instance in Europe I have 34kh/s reported in the miner, 30kh/s effective on F2pool.
Basically it mines good when China is sleeping, and I get horrible drop when it's their afternoon / evening.

[nebutech]

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.

[kristikun]

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

[Cryptarded]

@nebutech How does one use this feature?

"Add new option to tune CPU usage when mining Grin."

[Cryptarded]

Nevermind I see it

[nebutech]

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.

[nebutech]

New version with Grin29 improvement and Turing cards support!
 

[nebutech]

new version v21.2 with bug fixed.

[softerthansteel]

new version v21.2 with bug fixed.

Hash rate drops regulary on 2018 ti /undervolted/ on equal intervals - 10 seconds 2.03 g/s, 10 seconds 1.74 g/s wich is strange. No such drops with bminer or gminer.

[nebutech]

new version v21.2 with bug fixed.

Hash rate drops regulary on 2018 ti /undervolted/ on equal intervals - 10 seconds 2.03 g/s, 10 seconds 1.74 g/s wich is strange. No such drops with bminer or gminer.

Have you tried with stock settings?

[softerthansteel]

new version v21.2 with bug fixed.

Hash rate drops regulary on 2018 ti /undervolted/ on equal intervals - 10 seconds 2.03 g/s, 10 seconds 1.74 g/s wich is strange. No such drops with bminer or gminer.

Have you tried with stock settings?

Just tested it. It seems to hold little bit stable 2.10 - 2.14 g/s, but drops to 1.8 in longer intervals compared to undervolted card. Maybe it's power related or maybe it's normal, I dont know. I just expected to see relatively stable hash. But yeah, looks better not undervolted.

https://imgur.com/oCeKoVU

[cirlama]

new version v21.2 with bug fixed.

Hash rate drops regulary on 2018 ti /undervolted/ on equal intervals - 10 seconds 2.03 g/s, 10 seconds 1.74 g/s wich is strange. No such drops with bminer or gminer.

Have you tried with stock settings?

Just tested it. It seems to hold little bit stable 2.10 - 2.14 g/s, but drops to 1.8 in longer intervals compared to undervolted card. Maybe it's power related or maybe it's normal, I dont know. I just expected to see relatively stable hash. But yeah, looks better not undervolted.

https://imgur.com/oCeKoVU

it drops for me either on v21.2, grin 31, win 10 latest drivers, single gpu pc with core i7 (so it's not cpu related), 1080 ti max power @70% (base = 1.35 g/s, drops to 1.14 and rarelly to 0.95 g/s)
it didn't on v21.0 (was stable at 1.34 g/s)

edit: it's stable on v21.2 at 1.48 g/s @100% power load, but I don't want that...

[biospb]

versions 21.1 & 21.2 are slower than 21.0 on 1070ti C31 on linux (driver 418): only 9.2-9.3 vs 10.8 per rig. 15% slowdown!

[nebutech]

New version with bug fix.

1. Fix bug: Occasionlly lower local hashrate than previously version.
2. Do not run GPU if mining pool not connected when mining Grin & AE.

[cirlama]

New version with bug fix.

1. Fix bug: Occasionlly lower local hashrate than previously version.
2. Do not run GPU if mining pool not connected when mining Grin & AE.

ok thanks, seems to be fix for me (grin31, win10, 1080ti)
you should have changed the version number, it could be confusing...

[Veter288]

BTM 1660,1660ti ?

[nebutech]

BTM 1660,1660ti ?

Do not have these cards.

Though the miner should work on those cards as NVIDIA claims their compute capability is 7.5, which is the same as RTX 20's.

[davith75]

BTM 1660,1660ti ?

Don't think you'll be profitable.
The whole point of this miner is the use of Tensor Cores on BTM, which you don't have at all on a 1660/1660ti.
So basically you'll be the same as a 1070 at most.