Quote from: remix4life on November 16, 2017, 02:55:40 PM

Quote from: m1n1ngP4d4w4n on November 16, 2017, 01:22:00 PM

You can probably get something similar with setting up a batch script that after it exit the miner because of disconnect (use the --noreconnect miner switch) it restart the miner on a different pool. Have to be sure the miner exit on pool error. But should work

Hey that's a good idea, but I don't think I can do that in my rig,

I've got a strange experience using zm after running 15 hours give or take, I received an e-mail from flypool, said that my miner was offline. Then I checked my rig, Internet connection ok, zm still running and mining but not sending any shares to the pool (only reporting my hashrate, temp, etc) therefore the pool sent an e-mail.

I tried to close the miner and restart it again, everything going back to normal. Now I have to set my batch file to auto restart zm every 12 hours, been running good for about a week. I tried to make a loop like you suggested but it didn't work, the miner didn't auto restarted like it used to be, it just opened new cmd window with the new backup pool address but not mining because the gpus somewhat still minning in the first cmd. Huh

Sound like a driver crash, odd that the miner doesn't crash either, you could try to kill all binaries, and do a nvidia drivers reset, then restart the miner, may work, your solution work too

are you using latest version with the --noconnect ?

Me i noticed another odd thing, if you use the miner multiple times throught the day, the hashrate lower gradually like 1% each time it's started, if you reboot the rig it's back up to the normal hashrate, i never noticed this with EWBF, it's kinda odd.