Quote from: zeii on January 22, 2018, 10:23:54 AM

this is my log. use v2.4 but still there. and temp.of gpu1 is N/A

Thank you for the log. We will try to reproduce the problem and fix it for the next release (later this week).

Quote from: jendabenda on January 22, 2018, 12:50:11 PM

It seems your fix didnt work out. I had big crash last night (5/24). Its happening pretty much always at night local time (+1 GMT). Maybe some DAG generation issue? This was probably biggest I had. On 2.2b it was just like 1-3 machines thru night and sometimes they recovered. This time it was also with windows error phoneixminer stopped working.( maybe not all of them).

Version 2.4

Is there any way to use maybe another software or somethink to execute bat or sth to close and start again mining? I think ill need to go back to claymore....

Thank you for the logs - they are really helpful. The good news is that this is a different problem - not the reconnect issue as before (which seems to be fixed as no one reports it anymore) but a DAG generation instability/crash because during DAG generation GPUs draw more significantly power than in normal operation. There are a few ways to fix this and you have probably used them with the Claymore's miner, so we aren't going to invent the wheel and will implement the following options in the next release that is expected in a few days:
-lidag command-line option to decrease the speed of DAG generation in order to lower the power needed
-gser command-line option to avoid DAG generation on all GPUs simultaneously, which may strain the PSU(s)
-eres command-line option to allocated more memory than needed for the current DAG epoch in order to avoid allocating memory on each DAG switch

As DAGs are always generated on starting the miner and this didn't happen then, most probably the -eres option (which will be enabled by default) and probably -lidag as well should solve the DAG switch instabilities.