Topic: Team Black Miner (ETHW ETC Vertcoin Ravencoin Zilliqa +dual +tripple mining ) - page 99. (Read 34567 times)

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!!!!! 

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\

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

Try to rename the files

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

In the folder

no..same result as the old version!

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

---

Any luck with v1.11?

[moderator's note: consecutive posts merged]

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.

---

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

[moderator's note: consecutive posts merged]

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 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.

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


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 ?

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.

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 :


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

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.

What OC settings are you using for the 3060 TI?

---

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]

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)

---

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


[moderator's note: consecutive posts merged]

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?

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.

If default is 256 for nvidia, should I change xintensity?

We don't support tuning each card like this, but it can be added later. 50 and 1 is too low values for v1.11. On amd cards use without --xintensity. We are working on an improved kernel, but it will take some time



the other lines are not needed

---

Looking good.
The default --xintesity on nvidia is 256 in v1.11 but 224 produce less stale shares, so we might change the default in v1.12.

[moderator's note: consecutive posts merged]

GPU setup:

4x Nvidia 3060 TI FE
1x EVGA 3060 TI FTW3 ULTRA (NON-LHR)

GPU Overclock Settings:

Memory - +1050 (8,050 total)
Core - -200
Power Limit - 71%
Fan Speed - 70%

With the updated TBM v1.11 and new --xintensity recommended setting (--xintensity 224), I am getting 64+ MH per card (Total 322.14 MH) and with 0 stales/rejects so far (93+ mins running).

https://imgur.com/a/ekTsjnd

Is it safe to assume that it is working as intended?