You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a 4 rigs that are 13 1060 6gb gpu rigs on ethOS, intensity is 21, core +70 mem -502 power 100watts, Randomly, after 30min to 4 or 5hrs after switching to the dev pool I get stratum connection timeout errors, then it starts reporting block height and difficulty after a few lines over a few minutes then says 'pool switching timeout error' then switches back to my mining pool then just hangs up by continuing to report out block heights and difficulty with a random stratum difficulty line from time to time but never starts hashing again. I have tried multiple settings on core, mem and intensity and the same results. I am unable to get this running stable. I have a 1080ti rig with 2 cards at the moment but same form factor can house 13 gpus and has 2 PSU's, no problems at all. Please, if you have any thoughts on this let me know! Thank you in advance for your time.
The text was updated successfully, but these errors were encountered:
I have a 4 rigs that are 13 1060 6gb gpu rigs on ethOS, intensity is 21, core +70 mem -502 power 100watts, Randomly, after 30min to 4 or 5hrs after switching to the dev pool I get stratum connection timeout errors, then it starts reporting block height and difficulty after a few lines over a few minutes then says 'pool switching timeout error' then switches back to my mining pool then just hangs up by continuing to report out block heights and difficulty with a random stratum difficulty line from time to time but never starts hashing again. I have tried multiple settings on core, mem and intensity and the same results. I am unable to get this running stable. I have a 1080ti rig with 2 cards at the moment but same form factor can house 13 gpus and has 2 PSU's, no problems at all. Please, if you have any thoughts on this let me know! Thank you in advance for your time.
The text was updated successfully, but these errors were encountered: