Quote from: blueknight32 on March 22, 2021, 11:52:49 AM

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

https://ibb.co/TWwggdG

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.