Unfortunately, without Visual Studio connected to the app when this occurs it will be hard to track.

Each minute, after updating prices, I check that the process has not gone into a "HasExited" state.   If it has, then I restart the miner.  When your miner crashed, did it exit out or was it sitting at some sort of error display?  If the miner window went away completely then it should have restarted on the next minute.

Any info on the state things were in will be helpful.

One workaround I can think of adding is a max time to mine.  Set a time of one or two hours after which the miner will be killed and restarted, same as if there was an algo switch.  If the miner is hung then this should get it back in a running state.  When I get the time based event code in I'll make that one more feature to include.

I really wish NiceHash would implement a worker ID (appended on the address) so you could see what each miner is doing from the NiceHash website.  I've had a similar problem (before using NHC) on my second machine which I don't look at very often.  Unfortunately, its hash rate is low enough to be lost in the noise of the main machine.

Question.  Are all of your machines on the same network?  I'm thinking about trying to create a monitor app that could get redirected output from all mining rigs on one network.  Will probably use multicast for simplicity, which means it would not cross a router.  Just curious if there is any demand for something like this.

PS: Dang flicker!  I really need to get the minimum time hooks in. I'm bouncing between X11 and X13 again tonight.  Spent one whole minute on X13 before switching back.