Quote from: guzzzi on June 13, 2014, 05:26:57 AM

Quote from: KiloWatts on June 13, 2014, 05:17:59 AM

Quote from: guzzzi on June 13, 2014, 05:02:14 AM

Again ... about 6 Hours ago. N-Scrypt running well the last 15 Hours, then in the Night it switched to X13 and again back to N-Scrypt. 5 of my GPUs go off and 1 got the turn and was running well in the right speed Sad

Any solution for this? Missing 6 Hours every Day hurts.

Have you tested X13 on its own first to see if it's stable? (non-multiswitch port 3337)

I think it's wise with this multiswitching to be a little more conservative with how hard you push the GPUs, since you add the variable of switching. Keep your engine, clock, intensity, slightly lower than you would if you're mining only 1 algorithm. After you find settings that allow smooth switching, slowly tweak from there.

Yes working 100%. Switching between Scrypt/X11/X13 working perfect everythink runs stable. But NScrypt kills my GPU as soon there was a switch back to NScrypt.
Ok will try to set the Settings a little bit lower. But isnt it possible for SGMiner to start Algos slower? So reduce the Speed for the first minute to a minimum of speed, after that start to raise to the final configuration in full speed?

Yep I think we need a full 60 seconds at least for a memory flush to avoid those -4 Errors but I am not a chip designer.