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

Try on 2miners.com with --lhr-unlock[1] --log. 70% tdp on the card below 1500 coreclock . mem 10200 or more (linux 2550). Reboot the rig and let it start clean without any programs in the backround. In a mixed card environment add --xintensity 3000 for the other nvidia cards.

10GB 3080 LHR

On linux you need to add swap. 4GB * 12 = 48gb should be enough

https://minerstat.com/help/how-to-increase-virtual-memory-on-linux

You're right, ETC works. But on ETH Gminer works on that rig without problems. What can I do to make TBM work?

You probobly have too little memory in the rig. add 4gb virtual memory per card. Does ethereum classic mining work?

Can't start TBM 1.61 on 12x cards rig under RaveOs.

https://i.postimg.cc/XNfZNV2D/Untitled-2.jpg

But with fewer cards, the program starts on same rig.

https://i.postimg.cc/T1FNHrZC/Untitled-4.jpg

Which cards? 3060ti LHR3 unlocks with -85

--lhr-unlock [-85]

Any LHR updates for the latest releases?

I still cannot get my LHR hashrates to stabilize even after trying all the recommended values you provided in previous posts.

v1.61 is looking good. One testrig has been running for 48 hours on the hiveon.com pool with more than 10000 accepted and no rejected shares.

The testrigs ran for 20 hours on v1.60 without rejects, but  then I got a internet problem with a timeout, and the 0.5% rejected shares bug was back after reconnecting. (hiveon)
Found the problem, and will release a fix in 1.61 soon.
----------------------------
Team Black Miner v1.61

1. Fix rejected shares after pool disconnection and reconnection on some pools.

TeamBlackMiner_1_61_cuda_11_5.7z
https://www.virustotal.com/gui/file/2905fbc2d0c17551de6b0a7713ac6b94b580965b3a6d2e5e9a19a4948ec707cb?nocache=1

TeamBlackMiner_1_61_cuda_11_4.7z
https://www.virustotal.com/gui/file/cf09be27ce8ec4690e25383cc7c49a971e56fbe3cad5869e5a577e64b7ca2b31?nocache=1

TeamBlackMiner_1_61_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/c22832b00b39a4d9db2e7d58b6ac967c09fa2dc2db5887120971695588f49e3d?nocache=1

TeamBlackMiner_1_61_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/d2b6c2c1e0fe26b1c175621baf944eac345cdff81213e0de2601fff9aa11c660?nocache=1

--------------------
linux binaries re-uploaded, with a minor console output fix

2 rigs in 2miners xintensity 4096, 1 flex xintensity 512 , 1 flex xintensity default
I will try v1.60 next weakend

try v1.60.
Which pool, and which intensity?

but the problem its in 4 rigs, all GPU0 with diferent set in core and mem, its not the core

Try to increase the coreclock to above 1500. 1580?. Higher core gives a slightly higher voltage and stable hashrates on the rtx 3090.

-------------


Team Black Miner v1.60

1. Fixed rare crash in stats/gpu thread.
2. Removed illegal shares on GPU0 for the hiveon pool and other ethproxy pools.
3. Added support for mining on Asia/America servers on btc.com

https://github.com/sp-hash/TeamBlackMiner/releases

TeamBlackMiner_1_60_cuda_11_5.7z
https://www.virustotal.com/gui/file/ed9d9b2f5041b6d346a10bb9be248cd1d8ff0aaf88733d657da5615ee4bfc92d?nocache=1

TeamBlackMiner_1_60_cuda_11_4.7z
https://www.virustotal.com/gui/file/61691ed4179abf8a22b549b3b4a1d868eb7e9232d293eeddd021c4123c83cfdc?nocache=1

TeamBlackMiner_1_60_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/f6f3bcb03ca19c627ca50b97bd1952e267c21ff130e86d14a57eb9aa64bb0b45?nocache=1

TeamBlackMiner_1_60_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/759b5d0f1e9aae34b936f76156ce3af3b28e5ab1e649cc7ccbdc4fc86bcf7d10?nocache=1

---------
The rejected shares on the hiveon.com pool seems to finally been fixed in this version. Does anyone get rejects there in 1.60?

hi, i have this question, in 4 rigs of rtx 3090 have this, drop in hash always GPU 0, screen of two, this if from comicion of miner?
https://i.imgur.com/m92VQgU.jpg

https://i.imgur.com/RGuy4UX.jpg

Try with ---dagintensity 1

I fail to reproduce this on my testrigs. Tried --xintensity 4096 to force the timeout, and the first timeout will appear but no crash after the gpu reset.It's probobly only reproducable on the 2miners.com pool. In debug I see that 2miners don't like to have the fee mining thread open, so it keeps restarting. Perhaps a workaround would be to mine the devfee on another pool.

I increased memclock of GPUs to use feature of copying dag from non corrupted to corrupted version and my miner are restarting now with errors:

00:00:24 [2022-03-14 22:01:26.318] source/sp_cuda/cudaminer.cpp:cuda_search():958: A cuda runtime error occured: unspecified launch failure
00:00:24 [2022-03-14 22:01:26.318] Shutting down threads
00:00:24 [2022-03-14 22:01:26.318] Stratum thread exited
00:00:24 [2022-03-14 22:01:26.324] Control thread exited
00:00:24 [2022-03-14 22:01:26.376] source/sp_cuda/cudaminer.cpp:cuda_search():958: A cuda runtime error occured: unspecified launch failure
00:00:24 [2022-03-14 22:01:26.376] Shutting down threads
00:00:24 [2022-03-14 22:01:26.379] source/sp_cuda/cudaminer.cpp:cuda_search():958: A cuda runtime error occured: unspecified launch failure
00:00:24 [2022-03-14 22:01:26.379] Shutting down threads
00:00:24 [2022-03-14 22:01:26.402] source/sp_cuda/cudaminer.cpp:cuda_search():958: A cuda runtime error occured: unspecified launch failure
00:00:24 [2022-03-14 22:01:26.402] Shutting down threads
00:00:24 [2022-03-14 22:01:26.403] source/sp_cuda/cudaminer.cpp:cuda_search():958: A cuda runtime error occured: unspecified launch failure
00:00:24 [2022-03-14 22:01:26.403] Shutting down threads
00:00:24 [2022-03-14 22:01:26.418] source/sp_cuda/cudaminer.cpp:cuda_search():958: A cuda runtime error occured: unspecified launch failure
00:00:24 [2022-03-14 22:01:26.418] Shutting down threads
00:00:25 [2022-03-14 22:01:29.303] Api thread exited
00:00:25 [2022-03-14 22:01:30.318] Exiting

and I cant troubleshoot what GPU is failing. We need more clear miner feedback to tune overclock.

Here's another example:

00:05:52 [2022-03-14 08:05:45.276] GPU1    gfx1030  575.87 kH/W   66.23 MH/s    66.22 MH/s    156/0/0      100.00%
00:05:52 [2022-03-14 08:05:50.586] GPU1 hashtime 20c
00:05:53 [2022-03-14 08:06:43.051] GPU1 hashtime 20c
00:05:53 [2022-03-14 08:07:12.860] GPU1: 1d
00:05:53 [2022-03-14 08:07:12.860] GPU1    gfx1030  575.85 kH/W   66.22 MH/s    66.22 MH/s    157/0/0      100.00%
00:05:54 [2022-03-14 08:07:35.516] GPU1 hashtime 20c
00:05:55 [2022-03-14 08:08:27.979] GPU1 hashtime 20c
00:05:55 [2022-03-14 08:08:47.132] GPU1    gfx1030  575.86 kH/W   66.22 MH/s    66.22 MH/s    157/0/0      100.00%
00:05:56 [2022-03-14 08:10:05.404] GPU1: 61
00:05:56 [2022-03-14 08:10:05.404] GPU1    gfx1030  2136.27 kH/W  66.22 MH/s    66.22 MH/s    157/0/0      100.00%
00:05:58 [2022-03-14 08:11:21.980] GPU1: ae
00:05:58 [2022-03-14 08:11:21.980] GPU1    gfx1030  2136.27 kH/W  66.22 MH/s    66.22 MH/s    157/0/0      100.00%
00:05:59 [2022-03-14 08:12:39.996] GPU1: fc
00:05:59 [2022-03-14 08:12:39.996] GPU1    gfx1030  2136.27 kH/W  66.22 MH/s    66.22 MH/s    157/0/0      100.00%
00:06:00 [2022-03-14 08:13:52.028] GPU1: 144
00:06:00 [2022-03-14 08:13:52.028] GPU1: has timed out, trying to restart..
00:06:00 [2022-03-14 08:13:52.028] GPU1    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      157/0/0      100.00%
00:06:01 [2022-03-14 08:15:10.236] GPU1: 192
00:06:01 [2022-03-14 08:15:10.236] GPU1    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      157/0/0      100.00%
00:06:03 [2022-03-14 08:16:26.844] GPU1: 1de
00:06:03 [2022-03-14 08:16:26.844] GPU1    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      157/0/0      100.00%
00:06:04 [2022-03-14 08:17:42.451] GPU1: 22a
00:06:04 [2022-03-14 08:17:42.451] GPU1    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      157/0/0      100.00%
00:06:05 [2022-03-14 08:19:01.088] GPU1: 279
00:06:05 [2022-03-14 08:19:01.091] GPU1    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      157/0/0      100.00%
00:06:07 [2022-03-14 08:20:19.228] GPU1: 2c7
00:06:07 [2022-03-14 08:20:19.228] GPU1    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      157/0/0      100.00%
00:06:08 [2022-03-14 08:21:33.532] GPU1: 311
00:06:08 [2022-03-14 08:21:33.532] GPU1    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      157/0/0      100.00%
00:06:09 [2022-03-14 08:22:47.305] GPU1: 35b
00:06:09 [2022-03-14 08:22:47.305] GPU1    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      157/0/0      100.00%
00:06:10 [2022-03-14 08:24:04.700] GPU1: 3a8
00:06:10 [2022-03-14 08:24:04.700] GPU1    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      157/0/0      100.00%
00:06:12 [2022-03-14 08:25:20.220] GPU1: 3f4
00:06:12 [2022-03-14 08:25:20.220] GPU1: GPU thread crashed exiting program.

The card failed at some point between 8:10 and 8:11 (you can tell by the increase in KH/W), three minutes later the card was officially pronounced dead and a restart was attempted, and 12 minutes after the restart was attempted, the card finally caused a restart of the miner.  I'm not sure what the debug output is supposed to identify, but the last hashtime value was posted at 8:07/8:08.  

The GPU1's stats just before the crash were stable and no values were out of anywhere near critical:

00:05:55 [2022-03-14 08:08:47.132] GPU1    gfx1030  OpenCL  0       693     27/0    80      1370    1069    115
00:05:55 [2022-03-14 08:08:47.132] GPU1    gfx1030  575.86 kH/W   66.22 MH/s    66.22 MH/s    157/0/0      100.00%

Then, just after:

00:05:56 [2022-03-14 08:10:05.404] GPU1    gfx1030  OpenCL  0       693     20/0    80      1370    1069    114  
00:05:56 [2022-03-14 08:10:05.404] GPU1    gfx1030  2136.27 kH/W  66.22 MH/s    66.22 MH/s    157/0/0      100.00%

Took almost 24 hours, but here's a crashed AMD GPU:

Initial Failure w/ stats:


Parsed GPU0 output from 1st failure to crash: