EWBF's Cuda Equihash Miner 0.6

[micro_m]

have a problem with last 0.5v miner. When I start, miner.exe usage is 142mb memory. But after 24h this process use all available memory, 3.9gb for me. Restart is helps. Someone have this ussue? How you solve it? Maybe EWBFs have option for restart, like -r in Claymoors eth miner?

[hell_slayer]

anyone know how to downgrade B250 mining expert bios? ez flash 3 wont let me flash an older bios version

I think you can downgrade your bios by using afuefix64 EFI shell . I won't give you any links here , but you can use google search how to flash bios using afuefix64 . I used it for downgrade 2 times and it worked fine for me.
1) Put afuefix shell on your flash drive together with desired bios version . 2) boot from your flash drive and skip further EFI loading 3)type : fs6: (this can be different for you , to know your number you need to look what number will have Removable HardDisk in the list) 4)type : cd EFI 5) type : cd BOOT 6)type : ls
Now you'l see a directory where afuefix64 shell and desired bios should be allocated . 7) type : Afuefix64 "name of your bios" /B /P /N /K /X /CLRCFG , wait until flashing is finished and enjoy your new "old" bios 

[EWBF_]

Hello EWBF, i have problem with one rig from 20 on your program.

He started and after 20-30 sec go to restart. I reinstall drivers, make clean install, tried without overcloking and always same issue. Any idea how to fix my problem?  (Super stable + overclock on usual equihash on ZCL for example, or previous algo BTG) windows version.
I mine ANON coin here anon.2miners.com  144.5 algo

Rig with 8xGPU:

4 x 1080
1x 1070
3x 1060 3Gb

EDIT:

I turned off one by one gpu from devices, problem with one of my 1080 GPU....other 3 same (gigabyte 1080, same vendor, all same) works without problem. This gpu which cause problem, super stable at usual Equihash algo...don't know ho to solve problem, i tried to downgrade frequency from here -200 for mem and - 100 for GPU, still restart after 10 second of work.

Hello, I can recommend you to check the cables: riser and power, and also run a memtest for this gpu.

EWBF,

I just noticed you have Group and World write permissions set on your miner file in Linux. (I.E. 777)

Is this what you want or need?

Most executables ship set with Group and World write permissions off (I.E 755).

Let me know either way please.

OverDrive5

Hello, no, these permissions are not mandatory, you can set any permissions that are convenient for you.

have a problem with last 0.5v miner. When I start, miner.exe usage is 142mb memory. But after 24h this process use all available memory, 3.9gb for me. Restart is helps. Someone have this ussue? How you solve it? Maybe EWBFs have option for restart, like -r in Claymoors eth miner?

Hello, thanks for the message, this is definitely a problem, I will investigate it ASAP. Do you use windows?

[micro_m]

Hello, thanks for the message, this is definitely a problem, I will investigate it ASAP. Do you use windows?

Hi, yes I'm using win10. Below you can see task manager screenshot after miner restart.
http://i.piccy.info/i9/6d4b0e0b3e91d0b715d720f1699724c1/1537859828/58801/1251037/1.jpg

[fistsofgod]

all my gpus are working properly now. I was changing risers to troubleshoot the issue but windows decided to update at the same time. im not sure if the risers did it or the windows update, im leaning towards windows update. regardless, all issues have resolved themselves

[krnlx]

Not working with turing GPU RTX 2080, Linux, driver 410.57

Code:

+-------------------------------------------------+
|         EWBF's Eqihash CUDA miner. v0.5         |
+-------------------------------------------------+
14:09:51 INFO: Configured pools: 1
14:09:51 INFO: Selected pool: zero.suprnova.cc:6568
14:09:51 INFO: Algorithm: 192_7 "ZERO_PoW"
14:09:51 INFO: Devices: All.
14:09:51 INFO: Temperature limit: 100
14:09:51 INFO: Api: Disabled
---------------------------------------------------
14:09:52 INFO: Target: 0078787878787878...
14:09:52 INFO: Detected new work: 2abb
14:09:52 CUDA: Device: 0 GeForce RTX 2080, 7951 MB i:64
14:09:52 CUDA: Device: 1 GeForce RTX 2080, 7952 MB i:64
14:09:52 CUDA: Device: 2 GeForce RTX 2080, 7952 MB i:64
14:09:52 CUDA: Device: 3 GeForce RTX 2080, 7952 MB i:64
14:10:22 Temp: GPU0: 23C GPU1: 21C GPU2: 21C GPU3: 18C
14:10:22 GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s
14:10:22 Total speed: 0 Sol/s

Code:

Tue Sep 25 14:10:55 2018       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.57                 Driver Version: 410.57                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce RTX 2080    On   | 00000000:01:00.0  On |                  N/A |
|100%   23C    P2    47W / 255W |   2625MiB /  7951MiB |     17%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce RTX 2080    On   | 00000000:02:00.0 Off |                  N/A |
|100%   21C    P2    57W / 255W |   2618MiB /  7952MiB |     19%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce RTX 2080    On   | 00000000:03:00.0 Off |                  N/A |
|100%   21C    P2    42W / 255W |   2618MiB /  7952MiB |     17%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce RTX 2080    On   | 00000000:04:00.0 Off |                  N/A |
|100%   18C    P2    44W / 255W |   2618MiB /  7952MiB |     14%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1716      G   /usr/lib/xorg/Xorg                            12MiB |
|    0      9699      C   ./miner                                     2601MiB |
|    1      1716      G   /usr/lib/xorg/Xorg                             5MiB |
|    1      9699      C   ./miner                                     2601MiB |
|    2      1716      G   /usr/lib/xorg/Xorg                             5MiB |
|    2      9699      C   ./miner                                     2601MiB |
|    3      1716      G   /usr/lib/xorg/Xorg                             5MiB |
|    3      9699      C   ./miner                                     2601MiB |
+-----------------------------------------------------------------------------+

[revenant2017]

Not working with turing GPU RTX 2080, Linux, driver 410.57

Code:

+-------------------------------------------------+
|         EWBF's Eqihash CUDA miner. v0.5         |
+-------------------------------------------------+
14:09:51 INFO: Configured pools: 1
14:09:51 INFO: Selected pool: zero.suprnova.cc:6568
14:09:51 INFO: Algorithm: 192_7 "ZERO_PoW"
14:09:51 INFO: Devices: All.
14:09:51 INFO: Temperature limit: 100
14:09:51 INFO: Api: Disabled
---------------------------------------------------
14:09:52 INFO: Target: 0078787878787878...
14:09:52 INFO: Detected new work: 2abb
14:09:52 CUDA: Device: 0 GeForce RTX 2080, 7951 MB i:64
14:09:52 CUDA: Device: 1 GeForce RTX 2080, 7952 MB i:64
14:09:52 CUDA: Device: 2 GeForce RTX 2080, 7952 MB i:64
14:09:52 CUDA: Device: 3 GeForce RTX 2080, 7952 MB i:64
14:10:22 Temp: GPU0: 23C GPU1: 21C GPU2: 21C GPU3: 18C
14:10:22 GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s
14:10:22 Total speed: 0 Sol/s

Code:

Tue Sep 25 14:10:55 2018       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.57                 Driver Version: 410.57                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce RTX 2080    On   | 00000000:01:00.0  On |                  N/A |
|100%   23C    P2    47W / 255W |   2625MiB /  7951MiB |     17%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce RTX 2080    On   | 00000000:02:00.0 Off |                  N/A |
|100%   21C    P2    57W / 255W |   2618MiB /  7952MiB |     19%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce RTX 2080    On   | 00000000:03:00.0 Off |                  N/A |
|100%   21C    P2    42W / 255W |   2618MiB /  7952MiB |     17%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce RTX 2080    On   | 00000000:04:00.0 Off |                  N/A |
|100%   18C    P2    44W / 255W |   2618MiB /  7952MiB |     14%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1716      G   /usr/lib/xorg/Xorg                            12MiB |
|    0      9699      C   ./miner                                     2601MiB |
|    1      1716      G   /usr/lib/xorg/Xorg                             5MiB |
|    1      9699      C   ./miner                                     2601MiB |
|    2      1716      G   /usr/lib/xorg/Xorg                             5MiB |
|    2      9699      C   ./miner                                     2601MiB |
|    3      1716      G   /usr/lib/xorg/Xorg                             5MiB |
|    3      9699      C   ./miner                                     2601MiB |
+-----------------------------------------------------------------------------+

Can you try to mine at zergpool using the same algo? Someone has posted this on benchmarking the RTX 2080's.

[fistsofgod]

EWBF_, in next ver could you add an avg speed readout for avg sol/s, averaging the sol/s over the runtime of the miner since last start, and also avg efficiency in sol/w (averaging all cards together) over the runtime since last start?

[donlaiq]

Is EWBF's Cuda Equihash Miner 0.5 open source?

[revenant2017]

Is EWBF's Cuda Equihash Miner 0.5 open source?

Nope. It's not opensource. Mose Equihash mining software are not opensource. If you are finding other open source alternatives, sorry but what i know is they don't publish open source software.

[Andrey09]

If i use --fee 0 my performance will lower than if  i use default --fee 2?

EWBF ?

[EWBF_]

If i use --fee 0 my performance will lower than if  i use default --fee 2?

EWBF ?

No.

EWBF_, in next ver could you add an avg speed readout for avg sol/s, averaging the sol/s over the runtime of the miner since last start, and also avg efficiency in sol/w (averaging all cards together) over the runtime since last start?

Well, this is not a problem, only since version 0.7.

Not working with turing GPU RTX 2080, Linux, driver 410.57

Unfortunately, I'm still waiting for my RTX card. But thanks for the information.

hi,

start mine BTG

with
2x1070
1x1080

nooverclok

one of 1070 start but bet error,  stoped responde,

would like to know if posible to set intensity for each gpu, and how do that command line on bat. file.

using w10
tks,

if i start mine BTG with one card work without prolem.

Hi, if gpu does not respond, it means that the thread gets stuck in the cuda call, if this happens - you need to first check this gpu, its memory and all the cables connected to it. the --intensity parameter works similarly to --cuda_devices, for example: --cuda_devices 0 1 2 3 --intensity 64 64 1 64 sets the intensity 1 to gpu 2.

[dwarren]

Im running SMOS with this miner and was looking to upgrade my Nvidia to Cuda 9.2

I wanted to know if this miner is backward compatible?

Will it work with newer Nvidia drivers?

[abudfv2008]

Don't know has anyone reported. But there is a problem. Miner mines but nothing is shown on the pool. Rig just disappears. Caught it several times with different rigs. Zergpool on 144_5 algo.
Not sure whether it is pool or miner or pool/miner fault.

[revenant2017]

Don't know has anyone reported. But there is a problem. Miner mines but nothing is shown on the pool. Rig just disappears. Caught it several times with different rigs. Zergpool on 144_5 algo.
Not sure whether it is pool or miner or pool/miner fault.

Does this happen oftenly? Do any balances appear after you mined for 1 day? Have experienced this on different pool but they still show the right correct balance. Maybe it's on the pools side that has the problem.

[abudfv2008]

Don't know has anyone reported. But there is a problem. Miner mines but nothing is shown on the pool. Rig just disappears. Caught it several times with different rigs. Zergpool on 144_5 algo.
Not sure whether it is pool or miner or pool/miner fault.

Does this happen oftenly? Do any balances appear after you mined for 1 day? Have experienced this on different pool but they still show the right correct balance. Maybe it's on the pools side that has the problem.

Right now again - several hours passed since hashrate dropped and miner disappeared from pool. But miner was mining as before all that time.

[EWBF_]

Version 0.6 has been released.
In the next version additional improvements, Turing support, cuda 9.2 will replace 9.1 and probably will be added cuda 10 versions.

Im running SMOS with this miner and was looking to upgrade my Nvidia to Cuda 9.2

I wanted to know if this miner is backward compatible?

Will it work with newer Nvidia drivers?

Yes, it should work.

Don't know has anyone reported. But there is a problem. Miner mines but nothing is shown on the pool. Rig just disappears. Caught it several times with different rigs. Zergpool on 144_5 algo.
Not sure whether it is pool or miner or pool/miner fault.

The miner continues to work as long as the connection to the pool is alive, otherwise the devfee will be stopped, and the miner will try to restore connection with the pool. I'll connect my rig to Zergpool to see the situation.

[MineOrDie]

I see some minor performance decrease on 96_5 compared to 0.5

[Andrey09]

Version 0.6 has been released.
In the next version additional improvements, Turing support, cuda 9.2 will replace 9.1 and probably will be added cuda 10 versions.

Im running SMOS with this miner and was looking to upgrade my Nvidia to Cuda 9.2

I wanted to know if this miner is backward compatible?

Will it work with newer Nvidia drivers?

Yes, it should work.

Don't know has anyone reported. But there is a problem. Miner mines but nothing is shown on the pool. Rig just disappears. Caught it several times with different rigs. Zergpool on 144_5 algo.
Not sure whether it is pool or miner or pool/miner fault.

The miner continues to work as long as the connection to the pool is alive, otherwise the devfee will be stopped, and the miner will try to restore connection with the pool. I'll connect my rig to Zergpool to see the situation.

Any improvements in 0.6 according to 0.5 ?

[EWBF_]

I see some minor performance decrease on 96_5 compared to 0.5

what gpu?