EWBF's Cuda Equihash Miner 0.6

[fistsofgod]

Sometimes miner crashes and tries to restart:

"
14:06:42 CUDA: Device: 6 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:43 WARNING: Looks like GPU7 are stopped. Restarting...
14:06:43 INFO: GPU7 are restarted.
14:06:43 CUDA: Device: 7 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU0 are stopped. Restarting...
14:06:44 INFO: GPU0 are restarted.
14:06:44 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU1 are stopped. Restarting...
14:06:44 INFO: GPU1 are restarted.
14:06:44 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU2 are stopped. Restarting...
14:06:44 INFO: GPU2 are restarted.
14:06:44 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU3 are stopped. Restarting...
14:06:44 INFO: GPU3 are restarted.
14:06:44 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:45 WARNING: Looks like GPU4 are stopped. Restarting...
14:06:45 INFO: GPU4 are restarted.
14:06:45 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
"


I kill task  manually and start the task again, then everything works fine

It would be very good if he himself began anew independently

windows 10, 8 cards : 6/1070 +2/1080ti
drivers nvidia 01.06.2018  ver. 24.21.13.9811

I had this same problem and I decreased my OC until this stoppped happening. noticed my SOL/s stayed about the same also as i decreased.

this is my run.bat, it will restart on errors and such:

:restart
@echo  off
TIMEOUT 3
miner.exe --algo 144_5 --pers BgoldPoW --server us-east.equihash-hub.miningpoolhub.com --port 20595 --user xxxx --pass x --pec --fee x --log 2 --eexit 1
ping 127.0.0.1 > nul
goto :restart

[rosalco]

hello, guys. yeah, i have 2 1060 gpus on windows 10. in verison 0.3 it works fine, but 0.4, 0.5 im take crushing error who caused reboot my farm with cool message - thread exited with message the launch timed out and was terminated.
WAIDW?

[Zheko87]

How many sol/s per one 1066 on zhash algo gives 0.5 version?

[baraday]

fukanoshi call his miner as a fastest one, anyone checked already ewbf VS fukanoshi?

funakoshi vs ewbf:

tried on a 1080 ti, same OC settings, same pool, same coin (btcz)

funakoshi 59-61 sol/s
ewbf 69-71 sol/s

[sky999]

this old readmy (previous version for zec) is fully work with this new ewbf miner? https://github.com/nemosminer/EWBF-Zec-Miner/blob/master/Help.txt

[alexivan_58]

I had this same problem and I decreased my OC until this stoppped happening. noticed my SOL/s stayed about the same also as i decreased.

Yes, it's because of the OC, but the idea in message, the miner himself could restart, and not do it manually.
If the restart can be done by closing / execute the program, then this can be implemented inside the program itself.

[MineOrDie]

Any possible improvements for 96_5, or this is the limit?

[Regulater]

I am having issues with the API loading. It states the API failed every so often.

[konqueror]

I am having issues with the API loading. It states the API failed every so often.

You need to wait a little bit more when restarting miner. I suppose the API listen process needs more time to close connections.

[Salem87]

dear i know maybe its stupid question but whats the alg for Zcash and whats the miner command line will be . thanks and sorry again

[Dr_Victor]

dear i know maybe its stupid question but whats the alg for Zcash and whats the miner command line will be . thanks and sorry again

Zcash uses Equihash-algo. Try ZecMiner64 or EWBF miner:
miner --server us-east.equihash-hub.miningpoolhub.com --user username.workername --pass x --port 20570

[Salem87]

dear i know maybe its stupid question but whats the alg for Zcash and whats the miner command line will be . thanks and sorry again

Zcash uses Equihash-algo. Try ZecMiner64 or EWBF miner:
miner --server us-east.equihash-hub.miningpoolhub.com --user username.workername --pass x --port 20570

thanks for your help but may i know what algo shall i use in EWBF i mean like 210_9 or something , because the new one i must put the alg number on it right
thanks again for your help

[darkneorus]

dear i know maybe its stupid question but whats the alg for Zcash and whats the miner command line will be . thanks and sorry again

Zcash uses Equihash-algo. Try ZecMiner64 or EWBF miner:
miner --server us-east.equihash-hub.miningpoolhub.com --user username.workername --pass x --port 20570

thanks for your help but may i know what algo shall i use in EWBF i mean like 210_9 or something , because the new one i must put the alg number on it right
thanks again for your help

*  Solver for equihash 200,9 has been deleted.

[Salem87]

dear i know maybe its stupid question but whats the alg for Zcash and whats the miner command line will be . thanks and sorry again

Zcash uses Equihash-algo. Try ZecMiner64 or EWBF miner:
miner --server us-east.equihash-hub.miningpoolhub.com --user username.workername --pass x --port 20570

thanks for your help but may i know what algo shall i use in EWBF i mean like 210_9 or something , because the new one i must put the alg number on it right
thanks again for your help

*  Solver for equihash 200,9 has been deleted.

  ok what to do. will wait so. but  i like EWBF

[SchroedingerC]

fukanoshi call his miner as a fastest one, anyone checked already ewbf VS fukanoshi?

Funakoshi is slower than EWBF 0.3 on my RIGs.

[Dr_Victor]

dear i know maybe its stupid question but whats the alg for Zcash and whats the miner command line will be . thanks and sorry again

Zcash uses Equihash-algo. Try ZecMiner64 or EWBF miner:
miner --server us-east.equihash-hub.miningpoolhub.com --user username.workername --pass x --port 20570

thanks for your help but may i know what algo shall i use in EWBF i mean like 210_9 or something , because the new one i must put the alg number on it right
thanks again for your help

*  Solver for equihash 200,9 has been deleted.

  ok what to do. will wait so. but  i like EWBF

Use EWBF and enjoy
https://bitcointalk.org/index.php?topic=1707546.0

[EWBF_]

this old readmy (previous version for zec) is fully work with this new ewbf miner? https://github.com/nemosminer/EWBF-Zec-Miner/blob/master/Help.txt

Yes, except --solver option.

Any possible improvements for 96_5, or this is the limit?

It is difficult, but possible.

dear i know maybe its stupid question but whats the alg for Zcash and whats the miner command line will be . thanks and sorry again

This miner does not support equihash 200,9. I also think a couple of months, and it will be unprofitable for the GPU because of the asic's.

Sometimes miner crashes and tries to restart:

"
14:06:42 CUDA: Device: 6 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:43 WARNING: Looks like GPU7 are stopped. Restarting...
14:06:43 INFO: GPU7 are restarted.
14:06:43 CUDA: Device: 7 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU0 are stopped. Restarting...
14:06:44 INFO: GPU0 are restarted.
14:06:44 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU1 are stopped. Restarting...
14:06:44 INFO: GPU1 are restarted.
14:06:44 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU2 are stopped. Restarting...
14:06:44 INFO: GPU2 are restarted.
14:06:44 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU3 are stopped. Restarting...
14:06:44 INFO: GPU3 are restarted.
14:06:44 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:45 WARNING: Looks like GPU4 are stopped. Restarting...
14:06:45 INFO: GPU4 are restarted.
14:06:45 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
"


I kill task  manually and start the task again, then everything works fine

It would be very good if he himself began anew independently

windows 10, 8 cards : 6/1070 +2/1080ti
drivers nvidia 01.06.2018  ver. 24.21.13.9811

This is actually a common problem, you need to make sure that your overclocking is stable, note that different algorithms load gpu in different ways. Thus, stable overclocking on one algorithm does not guarantee stability for others.

Loving the higher hashrate

BUT STILL HAVING PROBLEMS WITH 12 CARD RIGS, it runs fine for about 5 minutes then crashes, GPU dump errors, help please, using SMOS

With fewer GPUs, no problems?

[TarzanCrazy]

Hi,
My first post here.
Is it possible to mine from magnificentpool with EWBF miner, directly to my wallet adress. I created a Jaxx wallet which is on my PC?
What would be the .bat command.
If it is not possible what kind of wallet do I need and what would the .bat command look like.
Best regards

[umine]

hello, guys. yeah, i have 2 1060 gpus on windows 10. in verison 0.3 it works fine, but 0.4, 0.5 im take crushing error who caused reboot my farm with cool message - thread exited with message the launch timed out and was terminated.
WAIDW?

I had practically the same problem with EWBF v0.5. On v0.4 everything works fine without reboot/restart for weeks. But with v 0.5 my miner crashed every hour. I ran each GPU in separate miner process and found which one GPU that crashed miner software. After that I just little reduce overclocking of that GPU and my rigs works well. I think the problem appears due to v0.5 uses more GPU (and power also) resources than older versions. If you think about stability just remember the first Equihash genoil miner  

[Scrubzer0]

this old readmy (previous version for zec) is fully work with this new ewbf miner? https://github.com/nemosminer/EWBF-Zec-Miner/blob/master/Help.txt

Yes, except --solver option.

Any possible improvements for 96_5, or this is the limit?

It is difficult, but possible.

dear i know maybe its stupid question but whats the alg for Zcash and whats the miner command line will be . thanks and sorry again

This miner does not support equihash 200,9. I also think a couple of months, and it will be unprofitable for the GPU because of the asic's.

Sometimes miner crashes and tries to restart:

"
14:06:42 CUDA: Device: 6 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:43 WARNING: Looks like GPU7 are stopped. Restarting...
14:06:43 INFO: GPU7 are restarted.
14:06:43 CUDA: Device: 7 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU0 are stopped. Restarting...
14:06:44 INFO: GPU0 are restarted.
14:06:44 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU1 are stopped. Restarting...
14:06:44 INFO: GPU1 are restarted.
14:06:44 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU2 are stopped. Restarting...
14:06:44 INFO: GPU2 are restarted.
14:06:44 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU3 are stopped. Restarting...
14:06:44 INFO: GPU3 are restarted.
14:06:44 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:45 WARNING: Looks like GPU4 are stopped. Restarting...
14:06:45 INFO: GPU4 are restarted.
14:06:45 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
"


I kill task  manually and start the task again, then everything works fine

It would be very good if he himself began anew independently

windows 10, 8 cards : 6/1070 +2/1080ti
drivers nvidia 01.06.2018  ver. 24.21.13.9811

This is actually a common problem, you need to make sure that your overclocking is stable, note that different algorithms load gpu in different ways. Thus, stable overclocking on one algorithm does not guarantee stability for others.

Loving the higher hashrate

BUT STILL HAVING PROBLEMS WITH 12 CARD RIGS, it runs fine for about 5 minutes then crashes, GPU dump errors, help please, using SMOS

With fewer GPUs, no problems?

No problems with fewer GPU's

I have 5 rigs that are 6-9 cards each and one 12 card rig, my 12 card has never fully worked on this new EWBF, I tried v0.2 and 3 and had gpu 10 and 11 crash over and over, v0.5 will sometimes only boot gpu 0 - 9 and run perfectly fine for days, but as soon as I reboot and get all 11-12 cards running it crashes within 10-15 minutes, I lowered OC to 50 core 200 mem and still crashes they are 1070ti, all my other 1070ti work 100% with 200 core 600 memory

I just rebooted again and it only booted gpu 0 - 9 so only 10 cards are working but its stable so I will leave it on for now....