Provided PoW solution is invalid leading to const rejected shares

[adiel91]

Happy to get assistance

After ~12 hours of mining with 2 GPUs, I start getting invalid shares, but only on the 2nd GPU which is RTX 3070.

• Trex miner 0.25.2
• GPU 0 - RTX 3090 , GPU 1 - RTX 3070
• DAG build mode is set to 2 for both of the cards
• 3070 OC Settings - Set in JSON Config file: CPU Clock: -300 Mem Clock: 1350 Fan Setting: t:70[45-85]

When checking trex log, I see that right before shares started to be rejected - I got:

20220205 23:51:44 ethash epoch: 471, block: 14148504, diff: 4.29 G 20220205 23:51:53 ethash epoch: 471, block: 14148505, diff: 4.29 G 20220205 23:51:58 [FAIL] 2033/2034 - Provided PoW solution is invalid!, 68ms ... GPU #1

No DAG Regeneration occured. First error observed - Rejected got 0.15% right after. 2nd Error observed after ~7 minutes - Rejected bumped up to 0.3%

Only restarting miner entirely and i'm back to 0% Appreciate any help

Thanks

[adiel91]

@trexminer is it possible to add some flag for "auto-restart miner on rejected shares" or similar? by total percentage of rejected shares / or even on non-0 percentage, will auto-restart the miner (i.e. disable OC, restart, build DAG, apply OC) ?

It could be very useful. what do you think? :) Currently due to the issue above, i as forced to write small utility to monitor the t-rex log file, and when encountering this error or rejected shares percentage, it reboots the pc (Then miner is auto started again on boot)

Thank you