Quote from: darius510 on February 25, 2018, 03:26:49 AM

Another feature suggestion - give me some simplified way to figure out wtf happened to cause a miner to crash.

I've been having a hell of a time getting some of my miners stable recently. I have them autoswitching very frequently, and each rig seems to crash at least once a day. Its very difficult to nail down precisely what it was doing that caused it to crash. What would be super useful is if within a notification there was some way to identify the last thing it was mining before a crash. For example instead of it just saying "mining process not running, initiating restart" it would be awesome if it said "mining process not running (ccminer 4.4.2, lyra2re, ahashpool, intensity 22), initiating restart" or something like that. Then I'll be able to see at a glance in the notifications if there is some sort of pattern - for instance lyra2re is crashing, or dstm is crashing, or only miners at a certain intensity are crashing etc.) I know that technically this is all in the logs but that requires me to RDP to each box, dig through this enormous log file full of tons of unnecessary detail.

Very good point. I've received similar requests in the past to make this information more visible, but simply making it part of the notification message is a good idea. I will implement this in the next update so you can try it.