T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner

[Wotan Wipeout]

4 x 3070 Zotac, 1 x 3060ti

Sometimes more luck on shares, sometimes less.

18:38:41 New Job: fba48650 Difficulty: 8.72G
18:38:48 New Job: 8c155a21 Difficulty: 8.72G
+------+----+-----+-----------+--------+----+-----+-----+-------------+
| GPU Temp Fan Speed Shares Core Mem Power Efficiency |
+------+----+-----+-----------+--------+----+-----+-----+-------------+
| GPU0 45 C 0 % 60.45 MH/s 495/0/0 1455 7880 112 W 539.71 KH/W |
| GPU1 42 C 0 % 60.50 MH/s 505/0/0 1395 7900 112 W 540.21 KH/W |
| GPU2 42 C 0 % 60.50 MH/s 466/0/0 1335 7900 113 W 535.37 KH/W |
| GPU3 40 C 0 % 60.50 MH/s 483/0/0 1215 7900 112 W 540.14 KH/W |
| GPU4 61 C 50 % 59.05 MH/s 442/0/0 1410 7700 120 W 492.05 KH/W |
| 300.99 MH/s 2391/0/0 569 W 528.98 KH/W |
+------+----+-----+-----------+--------+----+-----+-----+-------------+
18:38:53 Uptime: 0d 19:29:39 Shares/Minute: 2.04 Electricity: 11.090kWh

[1714150180]

1714150180

[1714150180]

1714150180

[1714150180]

1714150180

[willi9974]

GPU #0: ASUS RTX 3070
Coreclock: -502 --> 930 MHz (is on max minus value)
Memclock: +1500 --> 8300 MHz (is on max plus value)
Powerlimit: 54%
Found 166 Shares in 6,5 hours

20210328 16:40:57 GPU #0: ASUS RTX 3070 - 60.59 MH/s, [T:62C, P:128W, F:70%, E:473kH/W], 166/166 R:0%


GPU #1:  RTX 3070
Coreclock: -502 --> 630 MHz (is on max minus value)
Memclock: +1500 --> 8300 MHz (is on max plus value)
Powerlimit: 55%
Found 108 Shares in 6,5 hours

20210328 16:40:57 GPU #1: RTX 3070      - 60.77 MH/s, [T:52C, P:120W, F:32%, E:511kH/W], 108/117 R:7.69%



What do you mean i could do better...?

Are they same makes of vram?  different vram has different ideal settings. 

Here you can see the two cards, all have Samsung memory or can i see on other place / tool more details...

[aavvaallooss]

Here you can see the two cards, all have Samsung memory or can i see on other place / tool more details...
https://i.ibb.co/kmJ0kgC/image.png
[/quote]

Maybe because different BIOS version?

[miner29]

They are definitely not the exact same...see one report Asus RTX 3070 and next reports RTX 3070.....

[dedizonesv2]

I don´t understand the last added command line "--validate-shares          Validate shares before sending to a pool. Also enables share diff info".
What is for? It´s good or bad for avoid stale or invalid shares?

Me to i don't understant this parametre

how to add in json config ?

"validate-shares":

OR

"validate-shares": 1

thank you for helping me for the others it was easy but I don't know what this parameter is for but also how it is activated in hiveOS the configuration file is in json!

[willi9974]

came invalid shares more from a to low "Power Limit" or more from a to high "memory frequence"?

[FAIL] 989/1016 - Provided PoW solution is invalid!, 55ms ... GPU #1

[aavvaallooss]

came invalid shares more from a to low "Power Limit" or more from a to high "memory frequence"?

[FAIL] 989/1016 - Provided PoW solution is invalid!, 55ms ... GPU #1

In my case always because too much memory overclocking

[dedizonesv2]

Okay So I'm seriously pissed about this issue. I have my usual T-rex miner config setup (Same one I have been using since before my network change) but wen the screen shuts off it seems the miner connection fails which is ridiculous. The only thing changed was I went from the crappy cox all in one gateway modem/router to a Ubiquiti Dream machine pro. My computer is connected via hardwire cat6 and get 7ms pings, 850 mb/s down and no network problems other wise BUT it seems like maybe the dream machine is blocking something at the network level? I have added the entire trex folder to the windows 10 exclusion list and have actually just fully disabled the win10 antivirus for now. The computer is not set to sleep only the screen is. All low power settings are disabled for things such as the the Ethernet NIC and video card. Once the screen shuts off after 10 minutes about 3 minutes later the miner stops connecting with the errors listed in the image attached to link. I am using t-rex-0.19.11-win-cuda11.1 for my MSI RTX 3090 with current

code : t-rex.exe -a ethash -o stratum+tcp://us2.ethermine.org:4444 -u 0xmineraddress -p x -w rig0 pause

Yes, check pcie / monitor powersafe in windows

Disable shutoff computer and juste poweroff screen with button on/off or connected electrical outlet.

For me i have open topic: https://bitcointalk.org/index.php?topic=5327048.0

When I look at "screen -r miner" I sometimes randomly get a #GPU which displays 1875 Ms ... GPU # 0 | 5.04 G
Then everything becomes correct again, could someone tell me what is really this latency time?

Is this the time it took him to request a JOB, calculate it and then send it to the pool? who could be involved in the GPU? CPU? a network disturbance ?

And for this I don´t understand the last added command line "--validate-shares   

how to add in json config ?

"validate-shares":

OR

"validate-shares": 1

It would be good if the software creator came more often and answered questions, we participate in the dev fee but also more explanatory documentation would be welcome because currently it is the community that provides the support.

[JayDDee]

The miner doesn't request jobs, the stratum server sends them.

Latency is the network delay between sending a share and receiving the acknowledgement.

Validate shares means the CPU will verify the GPU hash is correct by performing a CPU hash on the same data
before submitting it as a share.

High latency has nothing to do with the miner or validate shares. It's a networking issue.

[hb81]

What does this mean?

--send-stales Don't drop stale shares

Also curious of this.

--validate-shares Validate shares before sending to a pool. Also enables share diff info

What is the actual point of those?
Could that Validate shares cause more stales?
I usually have 1-2% of stales. Now there is not any stales about 9 hours. I think its my internet connection.
Can't have wires so have to play with 4G mobile network. 5G spreading all around. (Don't worry.. here in Finland we have quite good mobile connections)
4G modem and CAT6 to rig.
Ping to pool is avg 31ms. So not bad. Just tested.
Sometimes OK share tells quite long times. Now that i look miner there is one share with 317ms. Right after that there is one with 54ms.

[hb81]

Hmm.. now that i looked in the pool and there was now stale share. Right about same time what miner reported OK share with longer time.
Any ideas or is this just situation that ia cant do nothing? 

[JayDDee]

What does this mean?

--send-stales Don't drop stale shares

Also curious of this.

--validate-shares Validate shares before sending to a pool. Also enables share diff info

They aren't related. Validate shares tests the validity with the CPU before submitting it. Stale shares
are valid, just too late to be accepted.

Higher latency means higher probability of stale shares being submitted. The miner can detect if a job
has gone stale while it was hashing a valid share. Since the miner spent the effort to find a valid share
it can choose whether to submit it anyway and risk it being rejected, or discard it.

[dedizonesv2]

The miner doesn't request jobs, the stratum server sends them.

Latency is the network delay between sending a share and receiving the acknowledgement.

Validate shares means the CPU will verify the GPU hash is correct by performing a CPU hash on the same data
before submitting it as a share.

High latency has nothing to do with the miner or validate shares. It's a networking issue.

Tks Bro  

I have a network problem? therefore on a RIG but not the other two, sometimes it is the others but this one. that's why I ask

No more worries since this morning, I just rebooted the TREX miners 3/4 times

[leojoyms]

Anyone have stale shares increased in eth with this latest version??

[NikiKa]

Hi everybody ,
what mean "!" in DAG generating string ?

20210330 00:28:48 GPU #1: DAG generated [crc: bdc4b7d7(!), time: 5825 ms], memory left: 4.95 GB
20210330 00:28:48 GPU #2: DAG generated [crc: 36ddfb5a(!), time: 5833 ms], memory left: 4.95 GB
20210330 00:28:48 GPU #3: DAG generated [crc: a56cf2cd, time: 5823 ms], memory left: 4.95 GB
20210330 00:28:48 GPU #5: DAG generated [crc: 5483d6c7(!), time: 5836 ms], memory left: 4.95 GB

[highlander1992]

any fix for memory leak rtx 2060 gddr6? I applied "--no-nvml" command and nvlm patch  and still getting memory leak.

[dedizonesv2]

Anyone have stale shares increased in eth with this latest version??

Yes: news version stale bad share, a rollback to "t-rex-ver. 0.19.12-cuda111" no stale

We are still waiting for me to dev, participate in the topics a little ... and explain to us !!!

any fix for memory leak rtx 2060 gddr6? I applied "--no-nvml" command and nvlm patch  and still getting memory leak.

there are also problems see here https://github.com/trexminer/T-Rex/issues

Post issue

[chemz]

They aren't related. Validate shares tests the validity with the CPU before submitting it. Stale shares
are valid, just too late to be accepted.

Hi! Does that mean that if we're not using this argument in the .bat file we're going to have potentially less valid shares? How does it differ from the Rejected statistics? If I get an Invalid share in the miner, but not a Rejected one, am I not having 1 valid share less either way?

Thanks!

[CoolTomik]

Is there way how to get OC info about mining GPU cards like core Voltage/Mem frq/core frq over json api?

[highlander1992]

Anyone have stale shares increased in eth with this latest version??

Yes: news version stale bad share, a rollback to "t-rex-ver. 0.19.12-cuda111" no stale

We are still waiting for me to dev, participate in the topics a little ... and explain to us !!!

any fix for memory leak rtx 2060 gddr6? I applied "--no-nvml" command and nvlm patch  and still getting memory leak.

there are also problems see here https://github.com/trexminer/T-Rex/issues

Post issue

I manage to solve this out.It was some kind of virus @ mscorsvw.exe hidden in net run time network with windows files.Some bastard tried to rob me