Most of the time it's GPU 0,1,2 that fail (probably because the load is distributed sequentially across all the GPU's, so the miner crash even before loading up all the gpu's), but it's across a whole 10 rigs of 6x1070, also to note they work perfectly on EWBF, hence why i was thinking ZM may push them harder than they can handle, but if nothing can be done "intensity" wise i guess i have to abandon the idea to use your miner on those specific rigs, and only keep the EVGA's one using it... It's also weird that even with no overclock the miner crash as fast than with OC.

I have tried dstm v0.5.4 and v0.5.5 for several weeks on my two rigs with Acrefawn autostart premium script (which BTW is great, saved me many sols). On one rig (6 x 1070 Asus Dual) I got on average 2800 sols. Comparing to EWBF it is almost 100 sols more. On second rig with mixed configuration (Palit 1060 , Strix 1070, Strix 1080Ti, Palit 1070) 1850 sols - no difference comparing to EWBF. My experience confirms that dstm is the best on gtx 1070. Initially I was very pleased with additional sols but frequent crashes forced me to revert to EWBF. I got crashes even without OC. Crashes are no problem with Acrefawn script but they reduce the sols performance advantage. I like dstm and it is promising but wait for further stability improvements and better sols performance.

EWBF is still better I have to say. The short term gains were never worth it compared to the stability.

Are you using 0.5.5?

For people having crashes:

Stability is of highest priority ofc, I'll try to reproduce this. I'm not sure if this is the result of unstable hardware - it's very helpful if you are able to provide some more detailed information.

Pls make sure you're on stock settings, no overclocking/undervolting etc.
Also pls report your OS, driver version, zm version, and the error message you're getting.
If there is a bug in zm I'll fix it pretty fast as soon as I'm able to reproduce it.

To be honest, I noticed after few days now that I dont think zm is the reason. Its more caused by the Windows update that messes up mining. My most stable rig is also bananas now. Im wondering hows it going for Linux users? Im thinking of switching to Linux if Windows is keeping to act up like this.

Here you go, using this command: --dev

Its switched off, this security update was forced on. There are multiple reports about it, read around willya.

Every cmd window will freeze if you click into the terminal, this is not dstm's miner fault, it's because you "paused" the process.
You can check here how to turn this off (just uncheck the "Quick Edit Mode"): https://superuser.com/questions/555160/windows-command-prompt-freezing-on-focus

I'm getting great results with this miner. Many thanks for your work, dstm.
No crashing here.

v0.5.3 was closing itself(?) occasionally, I assume it was losing connection to the pool and running out of reconnect attempts.
I'm testing 0.5.5 now to see if the problem still exists without the reconnect attempt limit.
Should really use the log I suppose.

GTX 1070
420sol/s @ 4.0 sols/w
Afterburner 800mV, +188mhz core, -50 mem

GTX 1080
515sol/s @ 4.2 sols/w
Afterburner 800mV, +125mhz core, -50 mem