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

[Akyboy]

s://www.virustotal.com/gui/file/88ec5032cb3b31a28cf2ac1649186478ef1d88d8749664ca3b8a1a5867fb6cdf?nocache=1

I have 3070 cards and DAG verification is failing with Afterburner OC settings that iv been using for months. (CC -502, MC +1200 PL 46)

Can  you try v1.44 beta please

Thanks for the beta version,..

this is what im getting now:
00:00:00 [2022-01-22 11:34:15.992]
00:00:00 [2022-01-22 11:34:15.992] Welcome to Team Black Miner 1.44
00:00:00 [2022-01-22 11:34:15.992]
00:00:00 [2022-01-22 11:34:15.992]
00:00:00 [2022-01-22 11:34:15.992] No devices are set
00:00:00 [2022-01-22 11:34:15.992] Shutting down threads
00:00:00 [2022-01-22 11:34:20.001] Exiting

Looks like GPU is not found at all now

Scratch above!
Installed latest drivers,... and it found GPUs, but there is another error now (Control thread exited - Stratum thread exited)

00:00:00 [2022-01-22 11:45:07.400]
00:00:00 [2022-01-22 11:45:07.400] Welcome to Team Black Miner 1.44
00:00:00 [2022-01-22 11:45:07.400]
00:00:00 [2022-01-22 11:45:07.400]
00:00:00 [2022-01-22 11:45:07.480] GPU0 NVIDIA GeForce RTX 3070 8GB added to miner as Cuda device
00:00:00 [2022-01-22 11:45:07.482] Trying eth-se.flexpool.io:4444 (ethash)
00:00:00 [2022-01-22 11:45:07.582] GPU0 Started Cuda work thread
00:00:00 [2022-01-22 11:45:07.838] Pool responded successfully to subscribe
00:00:00 [2022-01-22 11:45:07.964] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-22 11:45:08.092] Pool responded successfully to authorize
00:00:00 [2022-01-22 11:45:08.092] Difficulty is set to 0.931308
00:00:00 [2022-01-22 11:45:10.352] GPU0 Starting generating ethash dag (Epoch: 468)
00:00:00 [2022-01-22 11:45:10.466] GPU0 DAG generated in 2.34 seconds (4882428kb)
00:00:00 [2022-01-22 11:45:10.466] GPU0 Autoselect kernel activated
00:00:00 [2022-01-22 11:45:10.466] GPU0 XIntensity set to 284
00:00:00 [2022-01-22 11:45:10.466] Job 4a40bef5 (Validating Dag..)
00:00:00 [2022-01-22 11:45:15.062] GPU0 Dag verification failed. Exiting...
00:00:00 [2022-01-22 11:45:15.062] Shutting down threads
00:00:00 [2022-01-22 11:45:15.068] Control thread exited
00:00:00 [2022-01-22 11:45:15.068] Stratum thread exited
00:00:00 [2022-01-22 11:45:19.077] Exiting

[sp_]

00:00:00 [2022-01-22 11:45:15.062] GPU0 Dag verification failed. Exiting...
00:00:00 [2022-01-22 11:45:15.062] Shutting down threads
00:00:00 [2022-01-22 11:45:15.068] Control thread exited
00:00:00 [2022-01-22 11:45:15.068] Stratum thread exited
00:00:00 [2022-01-22 11:45:19.077] Exiting

Thanks for testing. I have uploaded another one. Can you test please.

https://github.com/sp-hash/TeamBlackMiner/releases/tag/v1.44

TeamBlackMiner_1_44_cuda_11_6_beta2.7z

[Akyboy]

00:00:00 [2022-01-22 11:45:15.062] GPU0 Dag verification failed. Exiting...
00:00:00 [2022-01-22 11:45:15.062] Shutting down threads
00:00:00 [2022-01-22 11:45:15.068] Control thread exited
00:00:00 [2022-01-22 11:45:15.068] Stratum thread exited
00:00:00 [2022-01-22 11:45:19.077] Exiting

Thanks for testing. I have uploaded another one. Can you test please.

https://github.com/sp-hash/TeamBlackMiner/releases/tag/v1.44

TeamBlackMiner_1_44_cuda_11_6_beta2.7z

Code:

[sup]00:00:00 [2022-01-22 12:27:27.118]
00:00:00 [2022-01-22 12:27:27.118]
00:00:00 [2022-01-22 12:27:27.118] Welcome to Team Black Miner 1.44
00:00:00 [2022-01-22 12:27:27.118]
00:00:00 [2022-01-22 12:27:27.118]
00:00:00 [2022-01-22 12:27:27.201] GPU0 NVIDIA GeForce RTX 3070 8GB added to miner as Cuda device
00:00:00 [2022-01-22 12:27:27.204] Trying eth-se.flexpool.io:4444 (ethash)
00:00:00 [2022-01-22 12:27:27.313] GPU0 DAG intensity set to 1
00:00:00 [2022-01-22 12:27:27.313] GPU0 Started Cuda work thread
00:00:00 [2022-01-22 12:27:27.497] Pool responded successfully to subscribe
00:00:00 [2022-01-22 12:27:27.625] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-22 12:27:27.736] Pool responded successfully to authorize
00:00:00 [2022-01-22 12:27:27.736] Difficulty is set to 0.931308
00:00:00 [2022-01-22 12:27:29.928] GPU0 Starting generating ethash dag (Epoch: 468)
00:00:00 [2022-01-22 12:27:30.039] GPU0 DAG intensity set to 1
00:00:00 [2022-01-22 12:27:34.525] GPU0 DAG generated in 6.77 seconds (4882428kb)
00:00:00 [2022-01-22 12:27:34.525] GPU0 Autoselect kernel activated
00:00:00 [2022-01-22 12:27:34.525] GPU0 XIntensity set to 284
00:00:00 [2022-01-22 12:27:34.525] Job f7560589 (Validating Dag..)
00:00:00 [2022-01-22 12:27:34.637] GPU0 Dag verification failed.
00:00:00 [2022-01-22 12:27:34.752] GPU0 Dag verification failed.
00:00:00 [2022-01-22 12:27:34.865] GPU0 Dag buffer verified ok!
00:00:00 [2022-01-22 12:27:41.696] Job 16128bdd (Autotuning..)
00:00:00 [2022-01-22 12:27:42.142] GPU0 Kernel Speed 98 100 99 99 99 98 99 99 99 99 99 99 99 99 98 98
00:00:00 [2022-01-22 12:27:42.142] GPU0 using gpu kernel 1
00:00:00 [2022-01-22 12:27:53.496] Job 92cf3ccb[/sup]

And looks like I got a slightly higher hash rate... with the same clock I am getting 1+Mh/s more.

But also, there is new error:

00:00:02 [2022-01-22 12:29:34.645] mining.submit: Pool reponded with error
00:00:02 [2022-01-22 12:29:34.645] Error(-2): Invalid PoW Solution

[sp_]

I uploaded another one

TeamBlackMiner_1_44_cuda_11_6_beta3.7z

please try again.

[Akyboy]

I uploaded another one

TeamBlackMiner_1_44_cuda_11_6_beta3.7z

please try again.

Still same:

Code:

00:00:00 [2022-01-22 13:12:21.151]
00:00:00 [2022-01-22 13:12:21.151] Welcome to Team Black Miner 1.44
00:00:00 [2022-01-22 13:12:21.151]
00:00:00 [2022-01-22 13:12:21.151]
00:00:00 [2022-01-22 13:12:21.248] GPU0 NVIDIA GeForce RTX 3070 8GB added to miner as Cuda device
00:00:00 [2022-01-22 13:12:21.251] Trying eth-se.flexpool.io:4444 (ethash)
00:00:00 [2022-01-22 13:12:21.401] GPU0 DAG intensity set to 1
00:00:00 [2022-01-22 13:12:21.401] GPU0 Started Cuda work thread
00:00:00 [2022-01-22 13:12:21.577] Pool responded successfully to subscribe
00:00:00 [2022-01-22 13:12:21.704] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-22 13:12:21.832] Pool responded successfully to authorize
00:00:00 [2022-01-22 13:12:21.832] Difficulty is set to 0.931308
00:00:00 [2022-01-22 13:12:24.291] GPU0 Starting generating ethash dag (Epoch: 468)
00:00:00 [2022-01-22 13:12:24.402] GPU0 DAG intensity set to 1
00:00:00 [2022-01-22 13:12:32.479] GPU0 DAG generated in 10.63 seconds (4882428kb)
00:00:00 [2022-01-22 13:12:32.479] GPU0 Autoselect kernel activated
00:00:00 [2022-01-22 13:12:32.479] GPU0 XIntensity set to 284
00:00:00 [2022-01-22 13:12:32.479] Job 96ad282c (Validating Dag..)
00:00:00 [2022-01-22 13:12:32.554] GPU0 Dag verification failed.
00:00:00 [2022-01-22 13:12:32.554] Shutting down threads
00:00:00 [2022-01-22 13:12:32.560] Control thread exited
00:00:00 [2022-01-22 13:12:32.560] Stratum thread exited
00:00:00 [2022-01-22 13:12:36.569] Exiting

[sp_]

Still same:

please try again

TeamBlackMiner_1_44_cuda_11_6_beta4.7z Dag creation is 3x slower in this release.

[Akyboy]

Still same:

please try again

TeamBlackMiner_1_44_cuda_11_6_beta4.7z

Same log as the previous one.

[sp_]

Same log as the previous one.

And you are using --dagintensity 1 ? How much do you have to reduce the clock to make it work?

I use --lock-cclock [1200,1200] on the 3070 Moblile. you need to run as admin

[Akyboy]

Same log as the previous one.

And you are using --dagintensity 1 ? How much do you have to reduce the clock to make it work?

I use --lock-cclock [1200,1200] on the 3070 Moblile. you need to run as admin

yes --dagintensity 1 is there
if/when i run as admin miner doesnt even start:

Code:

C:\Windows\system32>timeout 10

Waiting for  8 seconds, press a key to continue ...

C:\Windows\system32>goto :loop

C:\Windows\system32>TBMiner --algo ethash --hostname eth-se.flexpool.io --port 4444 --wallet XXXXXXXXXXXXXXXXXXXXX --worker-name XXXXXXXXXXXXXX --lock-cclock [1200,1200] --dagintensity 1
'TBMiner' is not recognized as an internal or external command,
operable program or batch file.

I wasnt adjusting afterburner for clock, but if i reset to default values it will work fine

[Akyboy]

It works on 1100 , once i bump it up to 1150+ it start failing.

I still cannot run it as admin for some reason..

[sp_]

It works on 1100 , once i bump it up to 1150+ it start failing.

I still cannot run it as admin for some reason..

Rightclick on the TBMiner.exe file in the folder, select properties / compabillity / run as admin

new upload

TeamBlackMiner_1_44_cuda_11_6_beta5.7z

add --lock-cclock [1200,1200] in the bat file

[Akyboy]

It works on 1100 , once i bump it up to 1150+ it start failing.

I still cannot run it as admin for some reason..

Rightclick on the TBMiner.exe file in the folder, select properties / compabillity / run as admin

new upload

TeamBlackMiner_1_44_cuda_11_6_beta5.7z

add --lock-cclock [1200,1200] in the bat file

Did that, now CMD opens in 2 windows, perhaps that is ok.
Now this error comes back:

00:00:00 [2022-01-22 14:07:49.714] GPU0 DAG intensity set to 1
00:00:00 [2022-01-22 14:07:49.714] GPU0 Started Cuda work thread
00:00:00 [2022-01-22 14:07:49.784] GPU0 GPU clocks set to "(gpuClkMin 1200, gpuClkMax 1200)" for GPU 00000000:08:00.0
00:00:00 [2022-01-22 14:07:49.889] Pool responded successfully to subscribe
00:00:00 [2022-01-22 14:07:50.029] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-22 14:07:50.140] Pool responded successfully to authorize
00:00:00 [2022-01-22 14:07:50.156] Difficulty is set to 0.931308
00:00:00 [2022-01-22 14:07:52.335] GPU0 Starting generating ethash dag (Epoch: 468)
00:00:00 [2022-01-22 14:07:52.465] GPU0 DAG intensity set to 1
00:00:00 [2022-01-22 14:07:52.466] GPU0 DAG generated in 2.29 seconds (4882428kb)
00:00:00 [2022-01-22 14:07:52.466] GPU0 Autoselect kernel activated
00:00:00 [2022-01-22 14:07:52.466] GPU0 XIntensity set to 284
00:00:00 [2022-01-22 14:07:52.466] Job cbb9ce20 (Validating Dag..)
00:00:00 [2022-01-22 14:07:52.524] GPU0 Dag verification failed.
00:00:00 [2022-01-22 14:07:52.524] Shutting down threads
00:00:00 [2022-01-22 14:07:52.538] Control thread exited
00:00:00 [2022-01-22 14:07:52.538] Stratum thread exited

[Akyboy]

I am leaving the house now and can continue testing tomorrow.
Thanks for support!

[sp_]

I am leaving the house now and can continue testing tomorrow.
Thanks for support!

TeamBlackMiner_1_44_cuda_11_6_beta6.7z

The dag is taking 10 seconds on the 3070 Mobile in 1-44 beta 6 with --dagintensity 1. I am able to run stable on higher memclocks

[wasarianta]

not bad...

https://ibb.co/RTzqKwy

[ekgd39]

I am leaving the house now and can continue testing tomorrow.
Thanks for support!

TeamBlackMiner_1_44_cuda_11_6_beta6.7z

The dag is taking 10 seconds on the 3070 Mobile in 1-44 beta 6 with --dagintensity 1. I am able to run stable on higher memclocks

https://i.ibb.co/KGmn76x/1-44.png

My observations for almost a day of mining on a 12x3080 no LHR rig.
1. If you are using Hive OS, use cuda 11.4, 11.5 gives a slight drop in hashrate.
2. I tried all the cores of the miner, the core does not automatically set correctly in Hive OS (1.42 core 1, 1.43 core 3). You must manually set the sign from 6 to 8 if you use 1.42 and 12-15 if use 1.43 20xx 30xx series of cards.
3. It makes no sense to set the core clock above 1440, it does not give any performance, it only increases the temperature of the cards and power consumption. This only works on older cards like 1070, 1080, 1080 Ti with gdd5 memory. On cards with GDDR 6-6X memory, the core does not participate in ETH mining and there is NO point in increasing it!
I tested the range from 1200 to 1600, anything above 1440 gives a drop in hashrate.
4. Option --xintensity , you need to select individually, for example, it works better for me on 8100 than on 4096.

Bugs that I found, on a rig with 13 video cards 3090x2 3080x7 3070 x4 NO LHR, I could not achieve stable operation, constant dag generation errors and a lot of invalid shares. Also, a 12x3070 NO lhr rig gives errors during dag generation, option --dagintensity 1 is always on.

Wishes, you should conduct detailed tests under HIVE OS, mining on Windows is extremely inconvenient and not popular. Big miners don't use Windows. Improve stability and fix core map definition.

I will continue to test it on different rigs to find bugs and errors in the hive, as well as to find the optimal settings.

https://i.ibb.co/7QxhBbb/2022-01-23-151607.png

[wasarianta]

a lot of invalid shares.

i use --tweak / -u [6] and work better to reduce than w/o --tweak / -u

• . Maybe you would try.

[ekgd39]

a lot of invalid shares.

i use --tweak / -u [6] and work better to reduce than w/o --tweak / -u

• . Maybe you would try.

What is your up time ? With tweak ?

[KillrBee]

I am leaving the house now and can continue testing tomorrow.
Thanks for support!

TeamBlackMiner_1_44_cuda_11_6_beta6.7z

The dag is taking 10 seconds on the 3070 Mobile in 1-44 beta 6 with --dagintensity 1. I am able to run stable on higher memclocks

My observations for almost a day of mining on a 12x3080 no LHR rig.
1. If you are using Hive OS, use cuda 11.4, 11.5 gives a slight drop in hashrate.
2. I tried all the cores of the miner, the core does not automatically set correctly in Hive OS (1.42 core 1, 1.43 core 3). You must manually set the sign from 6 to 8 if you use 1.42 and 12-15 if use 1.43 20xx 30xx series of cards.
3. It makes no sense to set the core clock above 1440, it does not give any performance, it only increases the temperature of the cards and power consumption. This only works on older cards like 1070, 1080, 1080 Ti with gdd5 memory. On cards with GDDR 6-6X memory, the core does not participate in ETH mining and there is NO point in increasing it!
I tested the range from 1200 to 1600, anything above 1440 gives a drop in hashrate.
4. Option --xintensity , you need to select individually, for example, it works better for me on 8100 than on 4096.

Bugs that I found, on a rig with 13 video cards 3090x2 3080x7 3070 x4 NO LHR, I could not achieve stable operation, constant dag generation errors and a lot of invalid shares. Also, a 12x3070 NO lhr rig gives errors during dag generation, option --dagintensity 1 is always on.

Wishes, you should conduct detailed tests under HIVE OS, mining on Windows is extremely inconvenient and not popular. Big miners don't use Windows. Improve stability and fix core map definition.

I will continue to test it on different rigs to find bugs and errors in the hive, as well as to find the optimal settings.

I've extensively tested TBM with an RTX3090 and can conclusively say that setting the core clock above 1440 does make a difference, especially in a windows environment.  setting core clock is the only way we have to set the voltage of the cards in Linux, and 1650 for the GPU sets the voltage to 0.78 which is the sweet spot for the 3090 with a high xintensity value.

I've tested 1500, 1550 and 1600 and the only way I've been able to obtain 135+ MH/s at-pool hashrate is by being at 1650 -- I will provide one caveat on those numbers, is that the testing was done on versions 1.24 to 1.28, afterwards I stopped because I was happy with the performance, and the later versions focused on LHR, which for some reason had a negative effect on the non-LHR cards until this last release. Version 1.27 was where I was able to achieve the highest rates on my 3090, and version 1.41 is where the AMD cards started to achieve 66+ MH/s under windows and 65+ under HiveOS.

-Xintensity of 8100 seems like it's much too high, since it will reduce the number of jobs being requested and lower the time your GPU is in compute mode, there's a significant drop off in at-pool performance when you get over a certain number, despite what the client says.  The client may very well be hashing at a greater speed, but for whatever reason, the number of shares generated will suffer at higher intensities, which may be due to how work threads are abandoned when new jobs come in as per the stratum protocol.  So those long running jobs are being held when they should have been released for a new, potentially lower difficulty job -- or that's my best guess. 

[ekgd39]

I am leaving the house now and can continue testing tomorrow.
Thanks for support!

TeamBlackMiner_1_44_cuda_11_6_beta6.7z

The dag is taking 10 seconds on the 3070 Mobile in 1-44 beta 6 with --dagintensity 1. I am able to run stable on higher memclocks

https://i.ibb.co/KGmn76x/1-44.png

My observations for almost a day of mining on a 12x3080 no LHR rig.
1. If you are using Hive OS, use cuda 11.4, 11.5 gives a slight drop in hashrate.
2. I tried all the cores of the miner, the core does not automatically set correctly in Hive OS (1.42 core 1, 1.43 core 3). You must manually set the sign from 6 to 8 if you use 1.42 and 12-15 if use 1.43 20xx 30xx series of cards.
3. It makes no sense to set the core clock above 1440, it does not give any performance, it only increases the temperature of the cards and power consumption. This only works on older cards like 1070, 1080, 1080 Ti with gdd5 memory. On cards with GDDR 6-6X memory, the core does not participate in ETH mining and there is NO point in increasing it!
I tested the range from 1200 to 1600, anything above 1440 gives a drop in hashrate.
4. Option --xintensity , you need to select individually, for example, it works better for me on 8100 than on 4096.

Bugs that I found, on a rig with 13 video cards 3090x2 3080x7 3070 x4 NO LHR, I could not achieve stable operation, constant dag generation errors and a lot of invalid shares. Also, a 12x3070 NO lhr rig gives errors during dag generation, option --dagintensity 1 is always on.

Wishes, you should conduct detailed tests under HIVE OS, mining on Windows is extremely inconvenient and not popular. Big miners don't use Windows. Improve stability and fix core map definition.

I will continue to test it on different rigs to find bugs and errors in the hive, as well as to find the optimal settings.

https://i.ibb.co/7QxhBbb/2022-01-23-151607.png

I've extensively tested TBM with an RTX3090 and can conclusively say that setting the core clock above 1440 does make a difference, especially in a windows environment.  setting core clock is the only way we have to set the voltage of the cards in Linux, and 1650 for the GPU sets the voltage to 0.78 which is the sweet spot for the 3090 with a high xintensity value.

I've tested 1500, 1550 and 1600 and the only way I've been able to obtain 135+ MH/s at-pool hashrate is by being at 1650 -- I will provide one caveat on those numbers, is that the testing was done on versions 1.24 to 1.28, afterwards I stopped because I was happy with the performance, and the later versions focused on LHR, which for some reason had a negative effect on the non-LHR cards until this last release. Version 1.27 was where I was able to achieve the highest rates on my 3090, and version 1.41 is where the AMD cards started to achieve 66+ MH/s under windows and 65+ under HiveOS.

OK,  I think you use it now ? Can you show your up time in hive os ?