Thanks for the update.
BTW, I like the fact that you mining engine resets a card if it detects any problems. A very good feature to have and improves my uptime. I use it as a gage so that if I'm pushing my cards too hard, just back it off a bit.
Can't wait to see what you have in store for the next update.
not always reset when an error occurs with the memory, then Miner restarts, and because of this the developer is often started.
|2018 - 04 - 11 17:00:49| GPU1: unspecified launch failure
|2018 - 04 - 11 17:00:49|Cuda error in func 'cuda_check_cpu_setTarget' at line 41 : unspecified launch failure.
GPU3: unspecified launch failure
Cuda error in func 'cuda_check_cpu_setTarget' at line 41 : unspecified launch failure.
|2018 - 04 - 11 17:00:49| GPU4: GeForce GTX 1070, 35.93 MH/s
|2018 - 04 - 11 17:00:49| GPU0: Gigabyte GTX 1070, 35.45 MH/s
|2018 - 04 - 11 17:00:49| GPU5: GeForce GTX 1070, 96.54 MH/s
|2018 - 04 - 11 17:00:49| GPU5: unspecified launch failure
Cuda error in func 'cuda_check_cpu_setTarget' at line 41 : unspecified launch failure.
|2018 - 04 - 11 17:00:49| GPU0: unspecified launch failure
|2018 - 04 - 11 17:00:49|Cuda error in func 'cuda_check_cpu_setTarget' at line 41 : unspecified launch failure.
GPU4: unspecified launch failure
Cuda error in func 'cuda_check_cpu_setTarget' at line 41 : unspecified launch failure.
what is it? At me 2x1070ti and 1x1070 give 45mh, and at you 1x1070 gives 35 mh, it is the big overclocking and from here mistakes