The software still shows a miner panel, but it says something like can't get hashrate and "Accepted 0 of 0 results". No crashes being reported, the output just stops being updated. It usually happens on a algorithm switch. The software doesn't start another process.
I hadn't tried a different miner, but I switched them on both Neoscrypt and Lyra2v2.
As of right now, I'm going to try MPH for Equihash (is there any way to just select Equihash?), Blockmasters for specific coins/auto switch, and Blazepool for everything else. I'll run this for a week or so and see how it goes. I've got my price spike set at $5.50 for 1080, $4.50 for 1070s and $3.50 for 1060s. I have a good little list of some alt-coins that I HODL, so right now, I'm just interested in Bitcoin so I can save that for other alt-coins that I may become interested in. Wish me luck!
One of misunderstanding about the software that I am still trying to find an effective way of conveying is that neither Klaust nor Ethminer provide a way of parsing their screen output due to how they are programmed. They are still mining in the background, but the software displays a message in the mining panel that says hash rates are unavailable. You can verify this because in those cases the mining windows are minimized to the task bar versus being redirected to the Miners tab.
As for mining panels that show 0 of 0 results for several minutes, there could be some different causes. Sometimes the pool changes difficulty too frequently, preventing the miner from finding a block. The one thing I noticed about the Neoscrypt miner is that it can be slow to find a block even on a 1080 on some bigger pools such as Blaze. Other times there could be an issue with the miner process throwing an uncommon error the software doesn't recognize yet. When this type of situation occurs, I'd appreciate if you could copy the current miner output (either from the panel or a log file if you have them enabled) for that GPU so I can identify the specific situation and hopefully make some adjustments in the code to better handle it in the future.
In theory, you should be able to use the Algorithms tab on the pool to disable algorithms for a specific pool. Unfortunately, that filtering does not appear to be working correctly for MiningPoolHub in 1.9. I will include a fix for that in 1.9.1, which should be released in a couple of days.
Thanks again for your feedback and good luck with the new pool selection. Let me know if you have any other questions or concerns.