EWBF's CUDA Zcash miner

[mirny]

I switched to this miner and got 350sols with a Gigab G1 1070.. (no OC, sadly 100% tdp, i cant lower that without trashing speeds)

BUT... i left the miner overnight and i found it crashed two hours later... I lost the whole night of mining. My fault for testing it unattended.

No probably not your fault, try running more instances (2-3), you will get speed increase and if one instance crashes than you still have the other.

It does not help, because whole machine is crashing, not just miner.
So, improved stability in next release, would be much appreciated.

[1714198022]

1714198022

[1714198022]

1714198022

[1714198022]

1714198022

[1714198022]

1714198022

[lokko]

EWBF 0.0.8


2 x GTX 1080 OC
GPU0: 450 Sol/s GPU1: 451 Sol/s
Total speed: 901 Sol/s


Thanks a lot !

[du44]

Can confirm, what 0.0.8b more stable than 0.0.7b and little more hashrate.
Thanks.

[m1n1ngP4d4w4n]

Nice work for 0.0.8b, improved stability and a tad bit more hashrate.

Would love to see some more options like logging, remote json admin port and stuff

Keep up the good work !

[xPwnK]

970 gets a bit less hashrate with 0.0.8 than 0.0.7. Does anyone else have this problem with maxwell cards?
260 sol/s with 0.0.7 and 250 sol/s with 0.0.8

[lyolyalya]

Nice work for 0.0.8b, improved stability and a tad bit more hashrate.

Would love to see some more options like logging, remote json admin port and stuff

Keep up the good work !

joining=)best miner!keep on tuning=)

[t2yax]

any plans for zcoin ??

[CoffeeCat]

What you would folks say are the best clocks for 1070 and a 1080? I want to get the most hashing power while saving on electricity. (Electric costs are high for me.)

[m1n1ngP4d4w4n]

What you would folks say are the best clocks for 1070 and a 1080? I want to get the most hashing power while saving on electricity. (Electric costs are high for me.)

If your electricity costs are high, best keep @50% tdp, that's what i do, any other combo just isn't enough profitability.

for OC settings, you would probably have to do your own testing, because each card is different depending on design, makers, making and so on.

My own settings atm and im still working on them, is +135 core / +575 mem @50% tdp +20% vCore (6x EVGA FTW 1070 micron chip memory) yielding about 375sols/s each for 92w each in nvidia-smi, whole rig consuming 695w (cpu, mobo, fans, and psu efficiency in play). I also run with 3 ewbf process, 2x cards per process for maximum efficiency (i have to test with lower amount of process since ewbf made changes in 0.0.7b, to see if it's as efficient running only one or 2 process, would save a few watts, will see that this week-end)

Those are just general settings, you would have to make your own testings to find the sweetest spot

[Kompik]

What you would folks say are the best clocks for 1070 and a 1080? I want to get the most hashing power while saving on electricity. (Electric costs are high for me.)

If your electricity costs are high, best keep @50% tdp, that's what i do, any other combo just isn't enough profitability.

for OC settings, you would probably have to do your own testing, because each card is different depending on design, makers, making and so on.

My own settings atm and im still working on them, is +135 core / +575 mem @50% tdp +20% vCore (6x EVGA FTW 1070 micron chip memory) yielding about 375sols/s each for 92w each in nvidia-smi, whole rig consuming 695w (cpu, mobo, fans, and psu efficiency in play). I also run with 3 ewbf process, 2x cards per process for maximum efficiency (i have to test with lower amount of process since ewbf made changes in 0.0.7b, to see if it's as efficient running only one or 2 process, would save a few watts, will see that this week-end)

Those are just general settings, you would have to make your own testings to find the sweetest spot

How do you up the vCore on the EVGA? I have EVGA SC and when i up the core in MSI afterburner it has absolutelly no effect. To keep the 375 sols i therefore need to have at least 65% TDP with the same overclock as you do. It consumes roughly 110 - 115W for 375 sols.
Also saying you run two processes for one card means 12 EWBF miners running per 6x rig?

[m1n1ngP4d4w4n]

What you would folks say are the best clocks for 1070 and a 1080? I want to get the most hashing power while saving on electricity. (Electric costs are high for me.)

If your electricity costs are high, best keep @50% tdp, that's what i do, any other combo just isn't enough profitability.

for OC settings, you would probably have to do your own testing, because each card is different depending on design, makers, making and so on.

My own settings atm and im still working on them, is +135 core / +575 mem @50% tdp +20% vCore (6x EVGA FTW 1070 micron chip memory) yielding about 375sols/s each for 92w each in nvidia-smi, whole rig consuming 695w (cpu, mobo, fans, and psu efficiency in play). I also run with 3 ewbf process, 2x cards per process for maximum efficiency (i have to test with lower amount of process since ewbf made changes in 0.0.7b, to see if it's as efficient running only one or 2 process, would save a few watts, will see that this week-end)

Those are just general settings, you would have to make your own testings to find the sweetest spot

How do you up the vCore on the EVGA? I have EVGA SC and when i up the core in MSI afterburner it has absolutelly no effect. To keep the 375 sols i therefore need to have at least 65% TDP with the same overclock as you do. It consumes roughly 110 - 115W for 375 sols.

In the afterburner option you need to go in general tab, and in the compatibility properties section, check unlock voltage control "extended MSI", and unlock voltage monitoring. You should be able to OC Vcore after afterburner restarting.
For the process, i run 3 instance of EWBF each targeting 2 cards (i have basically 3 bat file with the --cuda-devices switch)
as for the sols/s, this is an average, i get sometimes 380, sometimes 365/370, but yeah on average i hit about 745/750 per EWBF process (each with 2 cards) using 376.19 nvidia drivers just for info too

[Kompik]

In the afterburner option you need to go in general tab, and in the compatibility properties section, check unlock voltage control "extended MSI", and unlock voltage monitoring. You should be able to OC Vcore after afterburner restarting.
For the process, i run 3 instance of EWBF each targeting 2 cards (i have basically 3 bat file with the --cuda-devices switch)

Yes I have that but it does seem to do anything!

[m1n1ngP4d4w4n]

In the afterburner option you need to go in general tab, and in the compatibility properties section, check unlock voltage control "extended MSI", and unlock voltage monitoring. You should be able to OC Vcore after afterburner restarting.
For the process, i run 3 instance of EWBF each targeting 2 cards (i have basically 3 bat file with the --cuda-devices switch)

Yes I have that but it does seem to do anything!

Did you upgraded your GPU bios ? maybe not at the latest version, i "seem" to remember it was locked @ first on my FTW ones, maybe voltage are still locked on SC version i have no idea, sorry mate

[Kompik]

In the afterburner option you need to go in general tab, and in the compatibility properties section, check unlock voltage control "extended MSI", and unlock voltage monitoring. You should be able to OC Vcore after afterburner restarting.
For the process, i run 3 instance of EWBF each targeting 2 cards (i have basically 3 bat file with the --cuda-devices switch)

Yes I have that but it does seem to do anything!

Did you upgraded your GPU bios ? maybe not at the latest version, i "seem" to remember it was locked @ first on my FTW ones, maybe voltage are still locked on SC version i have no idea, sorry mate

Yes I did, but i will try to see if there are some new ones! You are right that it is probably locked. Thanks!

[_javi_]

Some workers are stopped attempting to restart....
and again and again...

No OC...

376.09 drivers..

is this ok for this miner..=
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

??

[anorganix]

I see a lot of people using 376.09 drivers.
Is there a specific reason not to use latest drivers? I'm mining just fine with 376.33.

[xPwnK]

I see a lot of people using 376.09 drivers.
Is there a specific reason not to use latest drivers? I'm mining just fine with 376.33.

No, but there isn't reason to update your drivers either.
376.33 drivers don't increase your hashrate.

[bensam1231]

Updating my bios's was a huge PITA all for about 8% more hashrate. When you have mixed manufacturers on one PC a lot of the update utilities don't respect models and will flash their bios over other manufacturers cards. That was a lot of fun digging up bios's to flash them back after that. Other manufacturers wont flash multiple cards (Asus update). It was a grab bag.

Best method is using nvflash and updating one of the cards with the manufacturers package, saving the updated bios with Nvflash, and then flashing all the cards at once by unplugging other models from the system.

In other news apparently you can't get that last couple % out of cards by running multiple instances anymore. EWBF still only uses 97-98% of my GPUs where as Nicehash uses 99-100%.


Worth noting, when running on Maxwell (970s) hashrate is 10% slower then Nicehash's miner. That's a pretty big difference. If you're running multiple Maxwell rigs it's better to stick with EQM.

Also .8 is still quite unstable. Multiple machines were completely stable with EQM, I have to reduce the memory clock a extra 100mhz to be stable in .8.

[m1n1ngP4d4w4n]

I see a lot of people using 376.09 drivers.
Is there a specific reason not to use latest drivers? I'm mining just fine with 376.33.

No, but there isn't reason to update your drivers either.
376.33 drivers don't increase your hashrate.

Well with the newest pascal cards, you can always hope something will improve, but usually it'll do nothing if your previous version isn't that far from current. I recommend doing testing, and for easyness to change between version use restore point in windows, very useful

Updating my bios's was a huge PITA all for about 8% more hashrate. When you have mixed manufacturers on one PC a lot of the update utilities don't respect models and will flash their bios over other manufacturers cards. That was a lot of fun digging up bios's to flash them back after that. Other manufacturers wont flash multiple cards (Asus update). It was a grab bag.

Best method is using nvflash and updating one of the cards with the manufacturers package, saving the updated bios with Nvflash, and then flashing all the cards at once by unplugging other models from the system.

In other news apparently you can't get that last couple % out of cards by running multiple instances anymore. EWBF still only uses 97-98% of my GPUs where as Nicehash uses 99-100%.


Worth noting, when running on Maxwell (970s) hashrate is 10% slower then Nicehash's miner. That's a pretty big difference. If you're running multiple Maxwell rigs it's better to stick with EQM.

Also .8 is still quite unstable. Multiple machines were completely stable with EQM, I have to reduce the memory clock a extra 100mhz to be stable in .8.

Latest version 0.0.8b with 3 process has an average GPU usage of 99% for me. (1 bat file per 2 cards on 6 cards rigs).

Stability wise, running with no rejected shares for the last 4 hours @ average 374sols/s per card. I use the same OC i was using with EQM, so far so good

Agree with you, bios updating for heterogeneous rigs is horrible...

Code:

Wed Dec 28 20:42:21 2016       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 376.19                 Driver Version: 376.19                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name            TCC/WDDM | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1070   WDDM  | 0000:01:00.0     Off |                  N/A |
| 27%   61C    P2    85W /  92W |    636MiB /  8192MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1070   WDDM  | 0000:02:00.0     Off |                  N/A |
| 24%   60C    P2    92W /  92W |    558MiB /  8192MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 1070   WDDM  | 0000:03:00.0     Off |                  N/A |
| 26%   60C    P2    92W /  92W |    558MiB /  8192MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 1070   WDDM  | 0000:04:00.0     Off |                  N/A |
| 27%   61C    P2    92W /  92W |    558MiB /  8192MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
|   4  GeForce GTX 1070   WDDM  | 0000:05:00.0     Off |                  N/A |
| 25%   60C    P2    94W /  92W |    558MiB /  8192MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
|   5  GeForce GTX 1070   WDDM  | 0000:06:00.0     Off |                  N/A |
| 26%   61C    P2    92W /  92W |    558MiB /  8192MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1000  C+G   C:\Windows\System32\dwm.exe                  N/A      |
|    0      3156  C+G   C:\Windows\explorer.exe                      N/A      |
|    0      4124  C+G   ...ost_cw5n1h2txyewy\ShellExperienceHost.exe N/A      |
|    0      4340  C+G   ...indows.Cortana_cw5n1h2txyewy\SearchUI.exe N/A      |
|    0      5828    C   C:\MINING\EWBF_ZEC\miner.exe                 N/A      |
|    1      5596    C   C:\MINING\EWBF_ZEC\miner.exe                 N/A      |
|    2      5828    C   C:\MINING\EWBF_ZEC\miner.exe                 N/A      |
|    3      5776    C   C:\MINING\EWBF_ZEC\miner.exe                 N/A      |
|    4      5776    C   C:\MINING\EWBF_ZEC\miner.exe                 N/A      |
|    5      5596    C   C:\MINING\EWBF_ZEC\miner.exe                 N/A      |
+-----------------------------------------------------------------------------+

Would love to see threading support from EWBF, as well as loggin and monitoring features for sure

[petrmaje]

Hi,
I have a issue with yours miner, Linux version.
Latest working version is 0.05b.

+---------------------------------+
| EWBF's Zcash CUDA miner. 0.0.5b |
+---------------------------------+
INFO: Target: 007fffffffffffff...
INFO: Detected new work: 1482962614_64854
INFO: Detected new work: 1482962614_64854
CUDA: Device: 0 GeForce GTX 1060 6GB, 6072 MB
INFO 23:04:01: GPU0 Accepted share 297ms [A:1, R:0]
INFO 23:04:07: GPU0 Accepted share 298ms [A:2, R:0]

Newer versions crased with this:
+---------------------------------+
| EWBF's Zcash CUDA miner. 0.0.8b |
+---------------------------------+
INFO: Target: 007fffffffffffff...
INFO: Detected new work: 1482962393_64849
INFO: Detected new work: 1482962393_64849
ERROR: Cannot run workers.

Does your miner require OPENCL files? I have installed driver without OPENCL files, because I had problems with second videocard installed in my PC. Other miners (claymore, genoil) works well. Where is the problem?
Thanks
Petr