Pages:
Author

Topic: EWBF's Cuda Equihash Miner 0.6 - page 22. (Read 85805 times)

full member
Activity: 198
Merit: 160
July 26, 2018, 08:34:33 AM
=== ONLY RELATED TO AION ==
Hi guys,
 
I've noticed that your miner submits lots of low difficulty shares on the AION pool. I have opened an issue here: https://github.com/nanopool/ewbf-miner/issues/88

Can you please check? Also, let me know in case you need any additional assistance.

Last, but not least, thank you for your work.

Regards


Yes, I know about this, it will be fixed in the next release.
newbie
Activity: 1
Merit: 0
July 26, 2018, 03:43:43 AM
=== ONLY RELATED TO AION ==
Hi guys,
 
I've noticed that your miner submits lots of low difficulty shares on the AION pool. I have opened an issue here: https://github.com/nanopool/ewbf-miner/issues/88

Can you please check? Also, let me know in case you need any additional assistance.

Last, but not least, thank you for your work.

Regards
full member
Activity: 1022
Merit: 221
We are not retail.
July 26, 2018, 12:15:03 AM
Pretty stable close to 24 hour mark. all nivida

60 / 150 / 580-740

One crash in 12 hour span, still not able to run a bat file specifically.
newbie
Activity: 13
Merit: 0
July 25, 2018, 02:32:44 PM
please work your maigc for a fully functional amd miner....
newbie
Activity: 19
Merit: 0
July 25, 2018, 01:40:11 PM
My miner sometimes crashes with this error and does not recover:

I have to exit/close the miner and restart it. This seems to happen randomly.

Could you add an argument/switch that closes the miner when this error occurs, so my script would restart it?

Code:
...
25.07.2018 18:39:22 Total speed: 442 Sol/s
25.07.2018 18:39:23 INFO: GPU5 Accepted share 47ms [A:1042, R:1]
25.07.2018 18:39:34 INFO: GPU9 Accepted share 47ms [A:969, R:1]
25.07.2018 18:39:40 INFO: GPU9 Accepted share 63ms [A:970, R:1]
25.07.2018 18:39:50 INFO: GPU5 Accepted share 63ms [A:1043, R:1]
25.07.2018 18:39:50 INFO: GPU7 Accepted share 63ms [A:1004, R:0]
25.07.2018 18:39:53 Temp: GPU0 57C GPU1 56C GPU2 60C GPU3 62C GPU4 62C GPU5 59C GPU6 60C GPU7 59C GPU8 64C GPU9 61C GPU10 59C GPU11 64C GPU12 65C
25.07.2018 18:39:53 GPU0: 34 Sol/s GPU1: 35 Sol/s GPU2: 34 Sol/s GPU3: 32 Sol/s GPU4: 34 Sol/s GPU5: 35 Sol/s GPU6: 34 Sol/s GPU7: 36 Sol/s GPU8: 31 Sol/s GPU9: 34 Sol/s GPU10: 35 Sol/s GPU11: 33 Sol/s GPU12: 35 Sol/s
25.07.2018 18:39:53 Total speed: 442 Sol/s
25.07.2018 18:39:56 INFO: GPU4 Accepted share 62ms [A:960, R:0]
25.07.2018 18:40:00 INFO: GPU5 Accepted share 62ms [A:1044, R:1]
25.07.2018 18:40:23 CUDA: Device: 2 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 6 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 12 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 5 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 1 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 4 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 9 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 10 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 3 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 0 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 7 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 8 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 11 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 Temp: GPU0 56C GPU1 55C GPU2 58C GPU3 62C GPU4 62C GPU5 59C GPU6 58C GPU7 58C GPU8 63C GPU9 60C GPU10 59C GPU11 64C GPU12 63C
25.07.2018 18:40:23 GPU0: 36 Sol/s GPU1: 34 Sol/s GPU2: 32 Sol/s GPU3: 36 Sol/s GPU4: 33 Sol/s GPU5: 35 Sol/s GPU6: 35 Sol/s GPU7: 35 Sol/s GPU8: 35 Sol/s GPU9: 35 Sol/s GPU10: 34 Sol/s GPU11: 36 Sol/s GPU12: 35 Sol/s
25.07.2018 18:40:23 Total speed: 451 Sol/s
25.07.2018 18:40:23 WARNING: Looks like GPU0 are stopped. Restarting...
25.07.2018 18:40:23 INFO: GPU0 are restarted.
25.07.2018 18:40:23 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:23 WARNING: Looks like GPU1 are stopped. Restarting...
25.07.2018 18:40:23 INFO: GPU1 are restarted.
25.07.2018 18:40:24 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU2 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU2 are restarted.
25.07.2018 18:40:24 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU3 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU3 are restarted.
25.07.2018 18:40:24 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU4 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU4 are restarted.
25.07.2018 18:40:24 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU5 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU5 are restarted.
25.07.2018 18:40:24 CUDA: Device: 5 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU6 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU6 are restarted.
25.07.2018 18:40:25 CUDA: Device: 6 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU7 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU7 are restarted.
25.07.2018 18:40:25 CUDA: Device: 7 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU8 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU8 are restarted.
25.07.2018 18:40:25 CUDA: Device: 8 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU9 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU9 are restarted.
25.07.2018 18:40:25 CUDA: Device: 9 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU10 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU10 are restarted.
25.07.2018 18:40:25 CUDA: Device: 10 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU11 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU11 are restarted.
25.07.2018 18:40:26 CUDA: Device: 11 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:26 WARNING: Looks like GPU12 are stopped. Restarting...
25.07.2018 18:40:26 INFO: GPU12 are restarted.
25.07.2018 18:40:26 CUDA: Device: 12 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:27 WARNING: Looks like GPU0 are stopped. Restarting...
25.07.2018 18:40:27 INFO: GPU0 are restarted.
25.07.2018 18:40:27 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:27 WARNING: Looks like GPU1 are stopped. Restarting...
25.07.2018 18:40:27 INFO: GPU1 are restarted.
25.07.2018 18:40:27 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:27 WARNING: Looks like GPU2 are stopped. Restarting...
25.07.2018 18:40:27 INFO: GPU2 are restarted.
...

More info
13x EVGA 1070
Pool: https://btg.2miners.com
Command line options: miner.exe --algo 144_5 --pers BgoldPoW --server btg.2miners.com --port 4040 --user
.rig1 --pass x
Power limit: 75%
Mem OC: 0
Core OC: 0
Virtual mem: 170GB

Miner: v0.4


This rig has worked almost flawlessly with DSTM's equihash miner. The only occassional hiccups have been due to previous OC settings.
newbie
Activity: 84
Merit: 0
July 25, 2018, 01:10:27 PM
I just tried the EWBF miner and I really like it - works stable and I am getting good hasrates: My standard 1070 gets around 19.4 KSol/s with 96.5 algo on the pool side and it is throttled down to 90% power which keeps it cool...
hero member
Activity: 1092
Merit: 552
Retired IRCX God
July 25, 2018, 12:46:40 PM
Hahah...maybe it can be changed to just ewbf or ewbf cuda Smiley
Or maybe you could not try to use a screwdriver as a hammer, chisel, saw, and vise all in one....
newbie
Activity: 28
Merit: 0
July 25, 2018, 10:13:19 AM
Hahah...maybe it can be changed to just ewbf or ewbf cuda Smiley
full member
Activity: 1022
Merit: 221
We are not retail.
July 25, 2018, 10:06:48 AM
Use batfile : miner  --algo 144_5 --server btg.suprnova.cc --port 8866 --user username.rigname --pass x --pers BgoldPoW

I have a few 1070ti of my own, my settings are 65 power / +125 core / + 550 mem ...

Getting around 38 Sols, on low power and low temps...

Yea right now I'm seeing the about the same in OC's about 37-42 sol per card.

60 pwr / +150 core /+580-740 mem (one card is finicky) on all 1070 ti's

55 sol on one 1080 ti : 60 pwr / +150 core / 760 mem

I did the bat file prior, didn't work.

Running .4 and using Zhash for the new BTG Fork and am getting a ton of rejected shares.  I've tried with and without afterburner running so the OC isn't causing this

GPU0: 603 Sol/s GPU1: 385 Sol/s GPU2: 705 Sol/s
Total speed: 1693 Sol/s
INFO 07:51:15: GPU0 Rejected share 203ms [A:0, R:38]
INFO 07:51:16: GPU0 Rejected share 250ms [A:0, R:39]
INFO 07:51:18: GPU1 Rejected share 187ms [A:0, R:17]
INFO 07:51:24: GPU2 Rejected share 206ms [A:0, R:39]
INFO 07:51:26: GPU2 Rejected share 187ms [A:0, R:40]
INFO 07:51:26: GPU1 Rejected share 189ms [A:0, R:18]
INFO 07:51:29: GPU1 Rejected share 203ms [A:0, R:19]
INFO 07:51:31: GPU1 Rejected share 191ms [A:0, R:20]
INFO 07:51:34: GPU2 DevFee Accepted share
INFO 07:51:36: GPU2 DevFee Accepted share

I have this issue and why changed the miner.cfg file for some reason it wouldnt select the the correct algo from the bat file

I have this problem all time:

04.07.2018 13:45:52 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:52 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:53 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:53 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:53 CUDA: Device: 5 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:53 WARNING: Looks like GPU0 are stopped. Restarting...
04.07.2018 13:45:53 INFO: GPU0 are restarted.
04.07.2018 13:45:53 WARNING: Looks like GPU1 are stopped. Restarting...
04.07.2018 13:45:53 INFO: GPU1 are restarted.
04.07.2018 13:45:54 WARNING: Looks like GPU2 are stopped. Restarting...
04.07.2018 13:45:54 INFO: GPU2 are restarted.
04.07.2018 13:45:54 WARNING: Looks like GPU3 are stopped. Restarting...
04.07.2018 13:45:54 INFO: GPU3 are restarted.
04.07.2018 13:45:54 WARNING: Looks like GPU4 are stopped. Restarting...
04.07.2018 13:45:54 INFO: GPU4 are restarted.
04.07.2018 13:45:54 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:54 WARNING: Looks like GPU5 are stopped. Restarting...
04.07.2018 13:45:54 INFO: GPU5 are restarted.


I have 6x 1070 ti, the OC is ok i think, 65 TDP, 180 core, 550 memory, windows 10.
Thanks for helps.

Not enough info:  
pool?
size of virtual memory?
v0.2 or v.03 miner?
bat file settings?

suprnova.cc
20000 virtual
v0.3
miner  --algo 144_5 --pers BgoldPoW --server btg.suprnova.cc --port 8866 --user user.user --pass x --pec --log 2
pause

I have tried to remove all the OC and it works stable for more than 15 hours, so I guess it was too much OC, but I do not think I had much OC.

I also have this problem since July 2018
I have this problem with 0.3 & 0.4 version
- my cards didn't overclocked
- when I see that problem my cards work normally (I can adjust the fan)
- I close tool and run again,  it's normal
- someone said to increase "virtual memory" (but someone said It's still not work)

My info
suprnova.cc
67000 virtual
v0.4
miner  -U  --algo 144_5  --pers BgoldPoW  --server btg.suprnova.cc --user user.user --pass x --port 8866 --i=22 --api

How can I fix this problem ?

Try dropping your power %, I had this when I was using a psu that was 1200w for four cards.
member
Activity: 122
Merit: 10
July 25, 2018, 08:53:19 AM
WARNING: Looks like GPU0 are stopped. Restarting...


Is there a way to make the miner auto close and reopen when this happens? This error is very random and has nothing to do with overclocking.
hero member
Activity: 1092
Merit: 552
Retired IRCX God
July 25, 2018, 08:37:13 AM
Can the EWBF miner not include other algos? Such as neoscrypt, keccak, x16r, etc.
It could, but then it wouldn't be EWBF's Cuda Equihash MinerRoll Eyes
newbie
Activity: 28
Merit: 0
July 25, 2018, 08:27:57 AM
Can the EWBF miner not include other algos? Such as neoscrypt, keccak, x16r, etc.
newbie
Activity: 21
Merit: 0
July 25, 2018, 06:52:21 AM
Running .4 and using Zhash for the new BTG Fork and am getting a ton of rejected shares.  I've tried with and without afterburner running so the OC isn't causing this

Quote
GPU0: 603 Sol/s GPU1: 385 Sol/s GPU2: 705 Sol/s
Total speed: 1693 Sol/s
INFO 07:51:15: GPU0 Rejected share 203ms [A:0, R:38]
INFO 07:51:16: GPU0 Rejected share 250ms [A:0, R:39]
INFO 07:51:18: GPU1 Rejected share 187ms [A:0, R:17]
INFO 07:51:24: GPU2 Rejected share 206ms [A:0, R:39]
INFO 07:51:26: GPU2 Rejected share 187ms [A:0, R:40]
INFO 07:51:26: GPU1 Rejected share 189ms [A:0, R:18]
INFO 07:51:29: GPU1 Rejected share 203ms [A:0, R:19]
INFO 07:51:31: GPU1 Rejected share 191ms [A:0, R:20]
INFO 07:51:34: GPU2 DevFee Accepted share
INFO 07:51:36: GPU2 DevFee Accepted share
member
Activity: 176
Merit: 10
July 25, 2018, 04:43:43 AM
So far cuda 8 of the latest version (0.4) has been fine for my 1070 ti's. haven't fine tuned clocks yet but cards are stable so far with 100 pwr / +150 core /+500-600 Mem.

odd thing is I cant create a batch file to run off of in winX. I have to modify the miner.cfg file and run the miner.exe directly to connect to suprnova.cc at least. Nothing else has worked.

I'll update final clocks as they come, but sure others have beat me to some good numbers.

Use batfile : miner  --algo 144_5 --server btg.suprnova.cc --port 8866 --user username.rigname --pass x --pers BgoldPoW

I have a few 1070ti of my own, my settings are 65 power / +125 core / + 550 mem ...

Getting around 38 Sols, on low power and low temps...
newbie
Activity: 7
Merit: 0
July 25, 2018, 03:54:09 AM
can't understand what algo I need to put to mine ZEC. Also can't understand why sols per sec is so small.
full member
Activity: 1022
Merit: 221
We are not retail.
July 25, 2018, 12:20:48 AM
So far cuda 8 of the latest version (0.4) has been fine for my 1070 ti's. haven't fine tuned clocks yet but cards are stable so far with 100 pwr / +150 core /+500-600 Mem.

odd thing is I cant create a batch file to run off of in winX. I have to modify the miner.cfg file and run the miner.exe directly to connect to suprnova.cc at least. Nothing else has worked.

I'll update final clocks as they come, but sure others have beat me to some good numbers.
newbie
Activity: 1
Merit: 0
July 24, 2018, 08:44:11 PM
I have this problem all time:

04.07.2018 13:45:52 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:52 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:53 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:53 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:53 CUDA: Device: 5 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:53 WARNING: Looks like GPU0 are stopped. Restarting...
04.07.2018 13:45:53 INFO: GPU0 are restarted.
04.07.2018 13:45:53 WARNING: Looks like GPU1 are stopped. Restarting...
04.07.2018 13:45:53 INFO: GPU1 are restarted.
04.07.2018 13:45:54 WARNING: Looks like GPU2 are stopped. Restarting...
04.07.2018 13:45:54 INFO: GPU2 are restarted.
04.07.2018 13:45:54 WARNING: Looks like GPU3 are stopped. Restarting...
04.07.2018 13:45:54 INFO: GPU3 are restarted.
04.07.2018 13:45:54 WARNING: Looks like GPU4 are stopped. Restarting...
04.07.2018 13:45:54 INFO: GPU4 are restarted.
04.07.2018 13:45:54 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
04.07.2018 13:45:54 WARNING: Looks like GPU5 are stopped. Restarting...
04.07.2018 13:45:54 INFO: GPU5 are restarted.


I have 6x 1070 ti, the OC is ok i think, 65 TDP, 180 core, 550 memory, windows 10.
Thanks for helps.

Not enough info: 
pool?
size of virtual memory?
v0.2 or v.03 miner?
bat file settings?

suprnova.cc
20000 virtual
v0.3
miner  --algo 144_5 --pers BgoldPoW --server btg.suprnova.cc --port 8866 --user user.user --pass x --pec --log 2
pause

I have tried to remove all the OC and it works stable for more than 15 hours, so I guess it was too much OC, but I do not think I had much OC.

I also have this problem since July 2018
I have this problem with 0.3 & 0.4 version
- my cards didn't overclocked
- when I see that problem my cards work normally (I can adjust the fan)
- I close tool and run again,  it's normal
- someone said to increase "virtual memory" (but someone said It's still not work)

My info
suprnova.cc
67000 virtual
v0.4
miner  -U  --algo 144_5  --pers BgoldPoW  --server btg.suprnova.cc --user user.user --pass x --port 8866 --i=22 --api

How can I fix this problem ?
newbie
Activity: 11
Merit: 0
July 24, 2018, 01:34:06 PM
Cuda is related to Nvidia drivers that you have. Older display drivers use cuda 7.5, 8,.. etc and recent drivers use 9+ (most recent driver use cuda 9.2). You can run miner for cuda 8 although you have cuda 9 (but not vice versa). What is best for you, you'll have to test. Sometimes versions for older cuda work better and faster than versions for newer cuda.



Interesting, thank you.  I think I should at least try using the miner for newer cuda, it seems that it would be more appropriate, at least in theory.  Thanks a ton, any other feedback welcome of course.
newbie
Activity: 73
Merit: 0
July 24, 2018, 08:40:00 AM
Cuda is related to Nvidia drivers that you have. Older display drivers use cuda 7.5, 8,.. etc and recent drivers use 9+ (most recent driver use cuda 9.2). You can run miner for cuda 8 although you have cuda 9 (but not vice versa). What is best for you, you'll have to test. Sometimes versions for older cuda work better and faster than versions for newer cuda.

newbie
Activity: 11
Merit: 0
July 24, 2018, 08:31:24 AM
Sanity check needed here guys - I've been running 0.3 and now 0.4 with success but have always used the miner files labelled "...cuda8" - it occurs to me that maybe thats not the right, most efficient miner to use - I am running Win10 on all machines, latest patches, etc and using modern Nvidia GPU's like the 1080, 1070 with latest Nvidia driver. 

Can ewbf or someone clarify and maybe update the first post to include a pointer on which file to use under which Windows circumstance. 
Pages:
Jump to: