Quote from: MrJay on October 01, 2013, 08:49:23 PM

Quote from: swiftshoot on October 01, 2013, 03:35:23 PM

Quote from: mattle74 on October 01, 2013, 01:36:01 PM

Quote from: atp1916 on October 01, 2013, 11:38:41 AM

Um, do you have any scientific support of such a claim? Not tryin' to flame, but first time i've ever heard that theory.

If anything, the disruption on each start/stop cycle is like giving the cards a mini-break.

Either way, my cards are all in the low 70s C range, and every little disconnect / reconnect only drops their temps maybe 5-10C before the server kicks back up.

I doubt this getwork failure between each coin change will cause any damage to your graphics cards. But this is what I was complaining about when I said I see getwork failures on this pool. It happens between every coin change. I have tried middlecoin, multipool and CryptoSwitcher to jump between coins. None of them have getwork failures or any delay when switching coins.

Middlecoin.com has getwork failures.... when switching.

So does Multipool, all 3 of the multi crypto mining pools have this issue/problem/whatever it is. Usually my miners will trip over to a backup pool for a few seconds and then back to the main pool to continue on with the new round.

FYI, for the "breaks" from the multipool, I have it fall over onto a good paying coin... Made 0.00595612 BTC from it for about 10-20 minutes of outage/failovers. If you put the right coin as failover, you can hit a nice block or 3. I ended up getting 2 blocks in the same minute. Just make cgminer failover into SOLO Mining Mode when hashco.ws is not responding, NOT to another pool. I average about 4 blocks a day in failover mode.