⛏Team Black Miner (ETHB3 ETHW ETC VTC KAWPOW FIROPOW EVRPROGPOW MEOWPOW +dual)

[somaton]

256 is fine here with 1 3060 v1 on test-rig, with locked core, v 1.11:

  1241m [2021-10-05 15:52:24.075] miningpoolhub.com (ethash)    PING: 112ms    DIFFICULTY: 3.00     EPOCH: 445
  1241m [2021-10-05 15:52:24.075]
  1241m [2021-10-05 15:52:24.075] ID   BOARD   HASHRATE/W   HASHRATE   AVERAGE      SHARES
  1241m [2021-10-05 15:52:24.075] GPU0   3060   467.59 kH/W   50.50 MH/s   50.50 MH/s   283/0/0 (100.00)

My second test-rig is under 1.09 int 64, does not work good with newer versions:

  1004m [2021-10-05 15:56:21.147] ID   BOARD   TYPE   HASHRATE/W   HASHRATE   AVERAGE      SHARES
  1004m [2021-10-05 15:56:21.147] GPU0   3070   Cuda   503.62 kH/W   63.96 MH/s   63.95 MH/s   298/0/0 (100.00)
  1004m [2021-10-05 15:56:21.147] GPU1   3060Ti   Cuda   467.57 kH/W   63.12 MH/s   63.20 MH/s   293/0/0 (100.00)
  1004m [2021-10-05 15:56:21.147] GPU2   3060   Cuda   469.95 kH/W   50.28 MH/s   50.27 MH/s   223/0/0 (100.00)
  1004m [2021-10-05 15:56:21.147]          1441.14 kH/W   177.37 MH/s   177.42 MH/s   814/0/0 (100.00)


Can you give any example how to use -c --configfile?

[sp_]

  1004m [2021-10-05 15:56:21.147] GPU2   3060   Cuda   469.95 kH/W   50.28 MH/s   50.27 MH/s   223/0/0 (100.00)

The miner will try to estimate the stale shares, but you should always check on the pool as well if they any detect stales. Or change to a pool which doesn't care about stales.

accepted/rejected/stale
223/0/0 (100% accepted)

Can you give any example how to use -c --configfile?

https://github.com/sp-hash/TeamBlackMiner#example-configuration-file


[moderator's note: consecutive posts merged]

[dle378]

My second test-rig is under 1.09 int 64, does not work good with newer versions:

  1004m [2021-10-05 15:56:21.147] ID   BOARD   TYPE   HASHRATE/W   HASHRATE   AVERAGE      SHARES
  1004m [2021-10-05 15:56:21.147] GPU1   3060Ti   Cuda   467.57 kH/W   63.12 MH/s   63.20 MH/s   293/0/0 (100.00)
  1004m [2021-10-05 15:56:21.147]          1441.14 kH/W   177.37 MH/s   177.42 MH/s   814/0/0 (100.00)

What OC settings are you using for the 3060 TI?

Depends on the pool. If the pool pay for stale shares the default 256 is fine. Flexpool, ethermine( ? ), nicehash and a couple of other doesn't pay for stale shares, so the miner need a lower --xintensity. Usually when a pool display the stale share amount, they eigther pay nothing or a reduced amount for stale shares. Sometimes the stale payout percentage is documented in the FAQ section of the pool.

On flexpool if you see this:



It meens that do don't get payed for around 5% of the shares that you submit (stales), and you have to lower the intensity of the miner.
Miningpoolhub.com, 2miners.com, nanopool.org, woolypool.com and many others pay the full amount for stale shares.

The ethereum blockchain is paying for stale work. They are called uncle blocks, and this is different from other chains like Bitcoin, Doge, Dash etc.

A mining pool can be configured to submit uncle blocks and not credit you for the work. Stealing 5% of your profit.

Got it.

I was always under the impression that it was best to ensure your miner submits a higher percentage of Accepted Shares vs Stale Shares?

Is that not the case anymore?

[moderator's note: consecutive posts merged]

[sp_]

I was always under the impression that it was best to ensure your miner submits a higher percentage of Accepted Shares vs Stale Shares?
Is that not the case anymore?

Depends on the pool, but less than 5% stales doesn't seem to affect the profit on ethereum/ethereum classic mining.
For bitcoin and other coins stales are bad.
Increasing the xintensity will increase the hashrate, increase the amount of stale shares and also the power.

[sukidesu]

Stack : Ubuntu 18.04, TBM 1.11

I need to launch the miner BEFORE overclocking the cards through nvidia-settings. If I overclock before, I get the DAG error :

Code:

     0m [2021-10-05 16:18:57.653] GPU3 Dag verification failed. Exiting...
     0m [2021-10-05 16:18:57.653] Shutting down threads
     0m [2021-10-05 16:18:57.653] Stratum thread exited
     0m [2021-10-05 16:18:57.662] GPU6 thread exited
     0m [2021-10-05 16:18:57.677] GPU5 thread exited
     0m [2021-10-05 16:18:57.692] Control thread exited
     0m [2021-10-05 16:18:57.696] GPU4 thread exited
     0m [2021-10-05 16:18:57.962] GPU0 Dag verification failed. Exiting...
     0m [2021-10-05 16:18:57.962] Shutting down threads
     0m [2021-10-05 16:18:57.964] GPU1 Dag verification failed. Exiting...
     0m [2021-10-05 16:18:57.964] Shutting down threads
     0m [2021-10-05 16:18:57.966] GPU2 Dag verification failed. Exiting...

Also, under Share (256/0/0), what do mean the 3 values ? Stales is before rejected ?

[sp_]

Also, under Share (256/0/0), what do mean the 3 values ? Stales is before rejected ?

accepted/rejected / (stale estimate)
226/0/0 (100% accepted)

The mining pools doesn't report the staleshare count, so the estimate might be different from the pool stalerate.

[sukidesu]

Also, under Share (256/0/0), what do mean the 3 values ? Stales is before rejected ?

accepted/rejected / (stale estimate)
226/0/0 (100% accepted)

The mining pools doesn't report the staleshare count, so the estimate might be different from the pool stalerate.

This is what I get on flexpool + TBM 1.11 with xintensity 224 :

Code:

    20m [2021-10-05 16:39:52.301] ID    BOARD   HASHRATE/W      HASHRATE        AVERAGE         SHARES
    20m [2021-10-05 16:39:52.301] GPU0  3070    468.03 kH/W     65.06 MH/s      85.86 MH/s      16/0/1 (100.00%)
    20m [2021-10-05 16:39:52.301] GPU1  3070    468.45 kH/W     65.11 MH/s      89.32 MH/s      14/0/3 (100.00%)
    20m [2021-10-05 16:39:52.301] GPU2  3070    468.39 kH/W     65.11 MH/s      94.17 MH/s      17/0/1 (100.00%)
    20m [2021-10-05 16:39:52.301] GPU3  3070    436.96 kH/W     65.11 MH/s      101.43 MH/s     18/0/0 (100.00%)
    20m [2021-10-05 16:39:52.301] GPU4  3080    462.39 kH/W     105.42 MH/s     113.54 MH/s     32/0/1 (100.00%)
    20m [2021-10-05 16:39:52.301] GPU5  3090    437.95 kH/W     130.51 MH/s     117.62 MH/s     27/0/1 (100.00%)
    20m [2021-10-05 16:39:52.301] GPU6  3080    457.87 kH/W     104.85 MH/s     104.77 MH/s     27/0/1 (100.00%)
    20m [2021-10-05 16:39:52.301]               3200.03 kH/W    601.17 MH/s     706.71 MH/s     151/0/8 (100.00%)

Still seems to generate a lot of stales (same o/c as t-rex which was 0.2% stales). Should I play with the o/c or the xintensity ?

[sp_]

Still seems to generate a lot of stales (same o/c as t-rex which was 0.2% stales). Should I play with the o/c or the xintensity ?

You need to check the stale rate poolside on the web page. The miner indicate 5.2980132% stale which is too high. But with vardiff the stalerate can decrease over time.
Mine on a higher difficulty will reduce stales. Mining with a lower xintensity will decrease stales.

[dle378]

Depends on the pool, but less than 5% stales doesn't seem to affect the profit on ethereum/ethereum classic mining.
For bitcoin and other coins stales are bad.
Increasing the xintensity will increase the hashrate, increase the amount of stale shares and also the power.

How do you determine the amount of power that is sufficient for the xintensity value? If I change the xintensity to 256, should I increase my PL to 75%, or is that overkill?

[sp_]

How do you determine the amount of power that is sufficient for the xintensity value? If I change the xintensity to 256, should I increase my PL to 75%, or is that overkill?

You need to test it yourself. Tune the rig. Different cards need different tuning.

With the right pool and more power --xintensity 512 can give a few more MHASH. If the Dag creation is unstable, you can lower the coreclock and memclock, increase intensity and power and still get a better hashrate. Mine on pools with high difficulty.

found one more bug in 1.11:
what happened to 3060 TI?

Fixed in v1.12 . The cards on the picture are rtx 3060 ti , non LHR. Not RTX 3060

[moderator's note: consecutive posts merged]

[sp_]

I need to launch the miner BEFORE overclocking the cards through nvidia-settings. If I overclock before, I get the DAG error :

Sometimes it helps to lower the core and memclock, add a little power and mine with a high --xintensity

fresh install done but no luck here.

Any luck with v1.11?

[moderator's note: consecutive posts merged]

[Alexstabilini]

fresh install done but no luck here.

Any luck with v1.11?

no..same result as the old version!

[sp_]

no..same result as the old version!

Try to rename the files

nvapi64.dll to nvapi64.dll_ and
OpenCL.dll ro OpenCL.dll_

In the folder

[Alexstabilini]

no..same result as the old version!

Try to rename the files

nvapi64.dll to nvapi64.dll_ and
OpenCL.dll ro OpenCL.dll_

In the folder

with 2 dll renamed

p104

C:\Users\Administrator\Desktop\a\TeamBlackMiner_1_11_cuda_11_4>Set ETH_WALLET=0x8a1E0bE188865f239bC9866d08ae62d6Fa2b181D

C:\Users\Administrator\Desktop\a\TeamBlackMiner_1_11_cuda_11_4>TBMiner --algo ethash -U [1] --no-ansi --xintensity 1 --hostname eth.pool.zet-tech.eu --port 8005 --wallet 0x8a1E0bE188865f239bC9866d08ae62d6Fa2b181D --worker_name DESKTOP-820EGVB
     0m [2021-10-05 20:49:45.589] OpenCL driver version: 471.96
     0m [2021-10-05 20:49:45.589] Cuda driver version: 11.4
     0m [2021-10-05 20:49:45.589] Cuda runtime API version: 11.4
     0m [2021-10-05 20:49:45.589]
     0m [2021-10-05 20:49:45.589]
     0m [2021-10-05 20:49:45.589]
     0m [2021-10-05 20:49:45.589] Welcome to Team Black Miner 1.11
     0m [2021-10-05 20:49:45.589]
     0m [2021-10-05 20:49:45.589]
     0m [2021-10-05 20:49:45.729] GPU0  0GB added to miner as Cuda device
     0m [2021-10-05 20:49:45.807] Trying eth.pool.zet-tech.eu:8005 (ethash)
     0m [2021-10-05 20:49:45.854] Pool responded successfully to subscribe
     0m [2021-10-05 20:49:45.917] GPU0 Started Cuda work thread
     0m [2021-10-05 20:49:49.402] GPU0 Starting generating ethash dag (Epoch: 445)
     0m [2021-10-05 20:49:49.402] GPU0 DAG generated in 3.49 seconds (4694011kb)
     0m [2021-10-05 20:49:49.402] GPU0 XIntensity set to 1

     0m [2021-10-05 20:49:49.417] Shutting down threads
     0m [2021-10-05 20:49:49.433] Stratum thread exited
     0m [2021-10-05 20:49:49.433] Control thread exited
     0m [2021-10-05 20:49:53.433] Exiting

and 1060


C:\Users\Administrator\Desktop\a\TeamBlackMiner_1_11_cuda_11_4>Set ETH_WALLET=0x8a1E0bE188865f239bC9866d08ae62d6Fa2b181D

C:\Users\Administrator\Desktop\a\TeamBlackMiner_1_11_cuda_11_4>TBMiner --algo ethash -U [9] --no-ansi --xintensity 1 --hostname eth.pool.zet-tech.eu --port 8005 --wallet 0x8a1E0bE188865f239bC9866d08ae62d6Fa2b181D --worker_name DESKTOP-820EGVB
     0m [2021-10-05 20:52:05.593] OpenCL driver version: 471.96
     0m [2021-10-05 20:52:05.593] Cuda driver version: 11.4
     0m [2021-10-05 20:52:05.593] Cuda runtime API version: 11.4
     0m [2021-10-05 20:52:05.593]
     0m [2021-10-05 20:52:05.593]
     0m [2021-10-05 20:52:05.593]
     0m [2021-10-05 20:52:05.593] Welcome to Team Black Miner 1.11
     0m [2021-10-05 20:52:05.593]
     0m [2021-10-05 20:52:05.593]
     0m [2021-10-05 20:52:05.749] GPU0  0GB added to miner as Cuda device
     0m [2021-10-05 20:52:05.812] Trying eth.pool.zet-tech.eu:8005 (ethash)
     0m [2021-10-05 20:52:05.874] Pool responded successfully to subscribe
     0m [2021-10-05 20:52:05.968] GPU0 Started Cuda work thread
     0m [2021-10-05 20:52:09.265] GPU0 Starting generating ethash dag (Epoch: 445)
     0m [2021-10-05 20:52:09.453] GPU0 DAG generated in 3.48 seconds (4694011kb)
     0m [2021-10-05 20:52:09.453] GPU0 XIntensity set to 1
     0m [2021-10-05 20:52:12.484] C:\gc\TBMiner\source\sp_cuda\cudaminer.cpp:cuda_search():394: A cuda runtime error occured: the launch timed out and was terminated
     0m [2021-10-05 20:52:12.484] Shutting down threads
     0m [2021-10-05 20:52:12.500] Stratum thread exited
     0m [2021-10-05 20:52:12.500] Control thread exited
     0m [2021-10-05 20:52:16.500] Exiting

[sp_]

can you change the folder from

C:\Users\Administrator\Desktop\a\

to a local folder somewhere. The program/your user need write access to the folder.

f.ex c:\tbminer\

[dle378]

How do you determine the amount of power that is sufficient for the xintensity value? If I change the xintensity to 256, should I increase my PL to 75%, or is that overkill?

You need to test it yourself. Tune the rig. Different cards need different tuning.

With the right pool and more power --xintensity 512 can give a few more MHASH. If the Dag creation is unstable, you can lower the coreclock and memclock, increase intensity and power and still get a better hashrate.

Just acquired my 6th 3060 TI NON-LHR and modified the --xintensity value to 256.

https://imgur.com/a/EzKtBev

Let's see how this runs for the next 24 hours.

Great work by the way!!!!! 

[sukidesu]

Results with Flexpool (poolside). Rig of 3070s, 3080s and 3090s :

- T-Rex = 813 mh/s
- TBM + XInt 256 + low diff = 752 mh/s
- TBM + XInt 256 + hi diff = 843 mh/s
- TBM + XInt 128 + low diff = 786 mh/s

Testing now with XInt 128 + hi diff. But it definitely looks like the hi diff helps on better results, even though it doesn't seem to change the % of stales that much (poolside). Also, XInt 256 is definitely too many stales.

Definitely believe this miner can achieve nice results, but it really requires to play around.

[sp_]

Some days ago I got a PM on reddit from a farmowner who earned more money now With the Team Black Miner than he did before the London hard fork. But you need to tune, and perhaps change the pool. Each pool has different optimal settings. The xintensity has changed. --xintensity -1 on nvidia is now increasing and decreasing the amount of work sent to the GPU to try to reduce stale shares. This results in an unstable hashrate and clockrate locally in the miner, but added around 10MHASH poolside (175MHASH rig) on pools that don't accept stales.

[Alexstabilini]

Hi! i have changed dir but nothing happened..
i'm now in crazypool..this is the full log..

with gminer and trex its okay..any idea?


C:\a\TeamBlackMiner_1_11_cuda_11_4>Set ETH_WALLET=0x8a1E0bE188865f239bC9866d08ae62d6Fa2b181D

C:\a\TeamBlackMiner_1_11_cuda_11_4>TBMiner --algo ethash --hostname eu.crazypool.org --port 3333 --wallet 0x8a1E0bE188865f239bC9866d08ae62d6Fa2b181D --worker_name DESKTOP-820EGVB
     0m [2021-10-06 10:58:56.516] OpenCL driver version: 471.96
     0m [2021-10-06 10:58:56.516] Cuda driver version: 11.4
     0m [2021-10-06 10:58:56.516] Cuda runtime API version: 11.4
     0m [2021-10-06 10:58:56.516] 
     0m [2021-10-06 10:58:56.516]                                 
     0m [2021-10-06 10:58:56.516] 
     0m [2021-10-06 10:58:56.516] Welcome to Team Black Miner 1.11
     0m [2021-10-06 10:58:56.516]                                 
     0m [2021-10-06 10:58:56.516] 
     0m [2021-10-06 10:58:56.657] GPU0 NVIDIA P104-100 8GB added to miner as Cuda device
     0m [2021-10-06 10:58:56.813] GPU1 NVIDIA P104-100 8GB added to miner as Cuda device
     0m [2021-10-06 10:58:56.954] GPU2 NVIDIA P104-100 8GB added to miner as Cuda device
     0m [2021-10-06 10:58:57.094] GPU3 NVIDIA P104-100 8GB added to miner as Cuda device
     0m [2021-10-06 10:58:57.329] GPU4 NVIDIA P104-100 8GB added to miner as Cuda device
     0m [2021-10-06 10:58:57.469] GPU5 NVIDIA P104-100 8GB added to miner as Cuda device
     0m [2021-10-06 10:58:57.610] GPU6 NVIDIA P104-100 8GB added to miner as Cuda device
     0m [2021-10-06 10:58:57.735] GPU7 NVIDIA P104-100 8GB added to miner as Cuda device
     0m [2021-10-06 10:58:57.876] GPU8 NVIDIA P104-100 8GB added to miner as Cuda device
     0m [2021-10-06 10:58:58.048] GPU9 NVIDIA GeForce GTX 1060 6GB 6GB added to miner as Cuda device
     0m [2021-10-06 10:58:58.235] GPU10 NVIDIA GeForce GTX 1060 6GB 6GB added to miner as Cuda device
     0m [2021-10-06 10:58:58.266] Trying eu.crazypool.org:3333 (ethash)
     0m [2021-10-06 10:58:58.298] Extranonce is set to 4317740380834496512
     0m [2021-10-06 10:58:58.298] Pool responded successfully to subscribe
     0m [2021-10-06 10:58:58.329] Pool responded successfully to extranonce subscribe
     0m [2021-10-06 10:58:58.345] Extranonce is set to 18373727705532203008
     0m [2021-10-06 10:58:58.345] Extranonce is set to 4317740380834496512
     0m [2021-10-06 10:58:58.360] Pool responded successfully to authorize
     0m [2021-10-06 10:58:58.376] Difficulty is set to 1.999969
     0m [2021-10-06 10:58:58.438] GPU0 Started Cuda work thread
     0m [2021-10-06 10:58:58.642] GPU1 Started Cuda work thread
     0m [2021-10-06 10:58:58.829] GPU2 Started Cuda work thread
     0m [2021-10-06 10:58:59.016] GPU3 Started Cuda work thread
     0m [2021-10-06 10:58:59.298] GPU4 Started Cuda work thread
     0m [2021-10-06 10:58:59.501] GPU5 Started Cuda work thread
     0m [2021-10-06 10:58:59.704] GPU6 Started Cuda work thread
     0m [2021-10-06 10:58:59.907] GPU7 Started Cuda work thread
     0m [2021-10-06 10:59:00.110] GPU8 Started Cuda work thread
     0m [2021-10-06 10:59:00.392] GPU9 Started Cuda work thread
     0m [2021-10-06 10:59:00.563] GPU10 Started Cuda work thread
     0m [2021-10-06 10:59:02.704] GPU1 Starting generating ethash dag (Epoch: 445)
     0m [2021-10-06 10:59:02.704] GPU1 DAG generated in 4.07 seconds (4694011kb)
     0m [2021-10-06 10:59:02.704] GPU1 XIntensity set to 256

     0m [2021-10-06 10:59:02.720] Shutting down threads
     0m [2021-10-06 10:59:02.736] Stratum thread exited
     0m [2021-10-06 10:59:02.736] GPU3 thread exited
     0m [2021-10-06 10:59:02.736] Control thread exited
     0m [2021-10-06 10:59:02.736] GPU5 thread exited
     0m [2021-10-06 10:59:02.736] GPU10 thread exited
     0m [2021-10-06 10:59:02.736] GPU7 thread exited
     0m [2021-10-06 10:59:02.736] GPU8 thread exited
     0m [2021-10-06 10:59:02.736] GPU2 thread exited
     0m [2021-10-06 10:59:02.736] GPU6 thread exited
     0m [2021-10-06 10:59:02.736] GPU9 thread exited
     0m [2021-10-06 10:59:02.736] GPU4 thread exited
     0m [2021-10-06 10:59:02.954] GPU0 Starting generating ethash dag (Epoch: 445)
     0m [2021-10-06 10:59:06.736] Exiting

C:\a\TeamBlackMiner_1_11_cuda_11_4>timeout 10

In attesa da  7 secondi. Premere un tasto per continuare...

[sp_]

try

TBMiner --algo ethash --hostname eu.crazypool.org --port 3333 --wallet 0x8a1E0bE188865f239bC9866d08ae62d6Fa2b181D --worker_name DESKTOP-820EGVB --xintensity 1

I am out of ideas. You seem to get the same problem we see on windows 8.1 / older cuda toolkits. This optimized miner is using new features of the latest cuda toolkits, so 11.2 or higher is required. Perhaps you can try to install cuda 11.4 ?

reinstall windows 10?