Quote from: Deathman20 on January 12, 2018, 04:13:58 AM

Quote from: d0n4ald on January 12, 2018, 03:00:37 AM

Quote from: JimboJambo_ZA on January 11, 2018, 10:54:11 AM

Quote from: Backy2221 on January 11, 2018, 09:54:23 AM

Quote from: turbulent0 on January 11, 2018, 12:43:17 AM

Quote from: JimboJambo_ZA on January 10, 2018, 08:16:34 AM

Quote from: rabbi-t on January 10, 2018, 02:48:15 AM

v.0.5.8 pool zen.suprnova.com
periodically i get such message in log
# connection closed by server r:0
# reconnecting
# connected to: zen.suprnova.cc:3618
# server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
# connection closed by server r:0
# reconnecting
# connected to: zen.suprnova.cc:3618
share counter drops to 0
gpus getting cold for some minutes, then the process starts again until next reconnect.
is this a bad thing? never got share zero-drop with 6x.

I have this exact same issue, every 3hrs my rigs get disconnected and reconnect for 5min before they start mining again. Internet is not the problem btw and the rigs dont have anti-virus or firewalls up.

the same issue, I get disconnected every 5 minutes with eu-ru01.miningrigrentals.com
but without disconnections to zec-eu1.nanopool.org
it is a pity, can't use with so many disconnections
Can it be an issue with low capacity of RAM? I have only 2gb Ram on my PC. Lan network.

I have the same problem on v0.5.8. Miner works for a day, and suddenly goes "zm.exe is not responding". At this point I must manually restart the Miner. This never happend to me on v0.5.7.

I've noticed that when too many recons happen then my mining client crashes. right now ive been mining 18hrs with only one reconnection and the rigs are running flawlessly. It's obviously an issue with maintaining a connection to the mining pool. Hopefully that gets sorted out soon enough. I've had this issue on 0.5.7 and 0.5.8 so rolling back to the previous version makes no difference. Right now I'll work on integrating this free open source watchdog script (https://bitcointalk.org/index.php?topic=2071108.0) that will reboot the mining client on crash and reboot my rigs on regular intervals just to manage the issue until the pool and client are working well together again.

im getting teh "zm.exe is not responding" error too, wonder if its my 1080ti settings of 150+ core too high?

I just switched to the dstm client and having zero issues with my 1080ti. Actually Its OCed more and clocked higher than I have ever been before!
Before using a different miner (EWBF) I managed around 700 H/sec with just a +100 on the core. No benefit to clocking the memory or anything else higher. Now I can run +200 Core / +500 Mem and even run at 90% TDP and get 752 H/sec! If I run at 100% TDP I get around 770 H/sec at these settings. I have yet to test it further but I'm sure I could tweak it even more. So I'd say with this at v0.5.8 you can mine at higher speeds and better output.

What card do you have? I get about the same hashrates, but my miner keeps crashing... :-(