-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Featurerequest: Restart Miner on 0 MH/s #199
Comments
They are some scripts around to deal with that. |
Have got the same issue occurring from time to time on a small 2x1060 rig. |
another watchdog: |
If we get an API on that program, monitoring the hashrate and restarting the miner will be easy. |
Ethminer_Watchdog does not work on us2.ethermine.org:14444 ? |
if its a stratum you need to correct -F to -S in mining.cmd 2nd solution: use stratum proxy (that is the way i personally run my miner) |
Error: |
config string according to ethermine would be; anyway easiest way is to use stratum proxy,. ( https://github.com/Atrides/eth-proxy/releases ) |
Changing only (Your_Ethereum_Address.RigName) |
@Git1Hub2 29Mh/s on a 1060 3G?! What type of card, memory and overclock?! |
Is it right? 1 GTX 1060 3G MSI MEMORY SANSUNG --cuda-parallel-hash 4 --cuda-streams 10 --cuda-grid-size 8192 --cuda-block-size 256 -v 9 |
Oh yep that's a good result! |
your mining url is false |
Why is the MH / s so high? I already tried a lot and I can not change ... I'm a beginner in this rsrs sorry |
its because of your memory speed, it is maxed out. |
@Git1Hub2 |
I downloaded the cuda_8.0.61_win10 from 1.3gb |
I encountered the same issue while playing around with different clock-speeds, power and maximum wattage and wrote a little script to restart on low watts (low MHz sounds even better ...):
|
I believe now the issue have been solved #757 (added --exit parameter to exit whenever an error occurred). |
Its not solved, but a workaround exists now. |
@smurfy what is the workaround? |
Hey Devteam,
first of all: Thank you for your great work. Ethminer ist running verry fast an stable on Nvidia-Cards now. We're running a 6x GTX 1070 rig @arround 190mh/s! Way better than Claymore!
But theres one feature wich would be verry nice. Sometimes (didn't find a reason yet) the Miner has "CUDA unspecific launch fail" and puts out 0 MH/s, for hours if you dont stop and restart it.
It would be verry nice if you could start Monitoring this issue and just restart the Miner if something like this happens...
KR
The text was updated successfully, but these errors were encountered: