EWBF's CUDA Zcash miner

[sublimus]

You have just a few rejects (far less than 0,5%), thats normal

it means that so there is no solution ?

It means someone else submitted the solution before you.

[Muspelheim]

You have just a few rejects (far less than 0,5%), thats normal

it means that so there is no solution ?

It means someone else submitted the solution before you.

oh, i see. thank you for your informative comments

[trekala]

hello everyone, first time poster here.

I have 1x ASUS GTX 1070 Dual and 2x EVGA GTX 1070 SC.
when using v0.3.3b miner i get ~430 sol/s per card
when using v0.3.4b miner i get ~370 sol/s
anyone has any clue what's going on?

running on Win10 x64 and have no extra options in my .bat file

thanks

[jenifive]

4x Palit 1070 Super Jetstream with 70 limit, 90 core, 350 memory

Nvidia driver 382.05

Version is 0.3.4b

Why my miner stopping every time?

I dont have such issues on Claymore or ccminer.

[vecher]

4x Palit 1070 Super Jetstream with 70 limit, 90 core, 350 memory

Nvidia driver 382.05

Version is 0.3.4b

Why my miner stopping every time?

I dont have such issues on Claymore or ccminer.

https://i.imgur.com/SJkDEyP.png

Have the exact same issues on 1080s

[Aureliusy]

From earlier post (not by me, but works for me as well)
Setting the (-r 240) "restart by user" switch to every 4 hours solved my problem.

[Atae]

How to auto restart EWBF when Temperatures below 40c.

[Locorobzilla]

Hi all

Using 6 * GTX1070 GPUs on Win 10 x64 Pro with the latest NVidia Drivers and Miner 0.3.4b
But I get the following error and then crashes

INFO: Detected new work: e104
INFO 23:26:03: GPU0 Accepted share 344ms [A:7, R:0]
CUDA: Device: 0 Thread exited with code: 30
CUDA: Device: 2 Thread exited with code: 30
CUDA: Device: 5 Thread exited with code: 30
CUDA: Device: 1 Thread exited with code: 30
CUDA: Device: 3 Thread exited with code: 30
CUDA: Device: 4 Thread exited with code: 30
ERROR: Looks like GPU0 are stopped. Restart attempt.
INFO: GPU0 are restarted.
CUDA: Device: 0 User selected solver: 0
ERROR: Looks like GPU2 are stopped. Restart attempt.
INFO: GPU2 are restarted.
ERROR: Looks like GPU3 are stopped. Restart attempt.
INFO: GPU3 are restarted.
ERROR: Looks like GPU4 are stopped. Restart attempt.
INFO: GPU4 are restarted.
ERROR: Looks like GPU5 are stopped. Restart attempt.
INFO: GPU5 are restarted.
CUDA: Device: 0 Thread exited with code: 46
ERROR: Looks like GPU1 are stopped. Restart attempt.
INFO: GPU1 are restarted.
CUDA: Device: 3 User selected solver: 0
CUDA: Device: 5 User selected solver: 0
CUDA: Device: 4 User selected solver: 0
CUDA: Device: 2 User selected solver: 0
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 1 User selected solver: 0
CUDA: Device: 5 Thread exited with code: 46
CUDA: Device: 4 Thread exited with code: 46
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 1 Thread exited with code: 46
Temp: GPU0: 0C GPU1: 0C GPU2: 0C GPU3: 0C GPU4: 0C GPU5: 0C
GPU0: 420 Sol/s GPU1: 421 Sol/s GPU2: 379 Sol/s GPU3: 428 Sol/s GPU4: 386 Sol/s GPU5: 422 Sol/s
Total speed: 2456 Sol/s
INFO: Detected new work: e105
Temp: GPU0: 0C GPU1: 0C GPU2: 0C GPU3: 0C GPU4: 0C GPU5: 0C
GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s GPU4: 0 Sol/s GPU5: 0 Sol/s
Total speed: 0 Sol/s
Temp: GPU0: 0C GPU1: 0C GPU2: 0C GPU3: 0C GPU4: 0C GPU5: 0C
GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s GPU4: 0 Sol/s GPU5: 0 Sol/s
Total speed: 0 Sol/s



But after a restart one of the GPUs is not detected and the temp sensor is not working (see below)

+-------------------------------------------------+
|         EWBF's Zcash CUDA miner. 0.3.4b         |
+-------------------------------------------------+
INFO: Current pool: mining.miningspeed.com:3092
INFO: Selected pools: 1
INFO: Solver: Auto.
INFO: Devices: All.
INFO: Temperature limit: 90
INFO: Api: Listen on 127.0.0.1:42000
---------------------------------------------------
ERROR: Cannot initialize NVML. Temperature monitor will not work!
INFO: Target: 001aaaaaaaaaaaab...
INFO: Detected new work: e112
CUDA: Device: 0 GeForce GTX 1070, 8192 MB i:64
CUDA: Device: 1 GeForce GTX 1070, 8192 MB i:64
CUDA: Device: 2 GeForce GTX 1070, 8192 MB i:64
CUDA: Device: 3 GeForce GTX 1070, 8192 MB i:64
CUDA: Device: 4 GeForce GTX 1070, 8192 MB i:64
CUDA: Device: 0 Selected solver: 0
CUDA: Device: 1 Selected solver: 0
CUDA: Device: 2 Selected solver: 0
CUDA: Device: 4 Selected solver: 0
CUDA: Device: 3 Selected solver: 0

[moeinbiz]

I have 5 rigs each one 6 x MSI 1070 Gaming X but one of them give me Thread exited with code: 4 on Zec miner 0.3.4b after a few minutes of mining and won't restart GPUs while other 4 rigs almost have no problems.
Meanwhile I can see a lot of WHEA-Logger warning messages on windows 10 x64 event viewer (Event Id: 17) but no error.

A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Bus:Device:Function: 0x0:0x1B:0x5
Vendor ID:Device ID: 0x8086:0xA2EC
Class Code: 0x30400

Anyone can guide me for these WHEA warnings?
Also is there any reference for exit codes 4 and 30?



https://i.imgur.com/sebfWVL.png

https://i.imgur.com/tPIRLJf.png

[Socket54]

I have had the stopped, attempt restart problems when setting up my 1080Ti's.
My issue was unstable clocks. Once i was able to find a sweet spot they have ran smoothly.
Here are my settings:


I could of course do a much better overclock, but i prefer a bit lower temps and better proficiency ratio

[carlo_0000]

I would get the new Galax 1070. I know they are a cheaper brand but I have 2 Galax 1060 6GB and they are great at mining ZEC or ETH.

Pascal chipset cards (10xx) use much less power for the same hash-rate as other cards deliver.

Also, if you decide to re-sell it, you are much more likely to get more of your money back with a Galax 1070

still funny how some people recommend nvidia for mining

nothing better than rx470-570's     , it s not for nothing you can not find any on sale

less power argument is not correct ever  the 570's undervolt pretty good

[TheHypnoToad]

I would get the new Galax 1070. I know they are a cheaper brand but I have 2 Galax 1060 6GB and they are great at mining ZEC or ETH.

Pascal chipset cards (10xx) use much less power for the same hash-rate as other cards deliver.

Also, if you decide to re-sell it, you are much more likely to get more of your money back with a Galax 1070

still funny how some people recommend nvidia for mining

nothing better than rx470-570's     , it s not for nothing you can not find any on sale

less power argument is not correct ever  the 570's undervolt pretty good

Hello, how many Sol/s would I get from an undervolted 570? How much power would it use undervolted? Thanks

[sublimus]

I would get the new Galax 1070. I know they are a cheaper brand but I have 2 Galax 1060 6GB and they are great at mining ZEC or ETH.

Pascal chipset cards (10xx) use much less power for the same hash-rate as other cards deliver.

Also, if you decide to re-sell it, you are much more likely to get more of your money back with a Galax 1070

still funny how some people recommend nvidia for mining

nothing better than rx470-570's     , it s not for nothing you can not find any on sale

less power argument is not correct ever  the 570's undervolt pretty good

Hello, how many Sol/s would I get from an undervolted 570? How much power would it use undervolted? Thanks

470 & 570s series are good to mine ETH
Use Nvidia if you want to mine ZEC (equihash)

[mforce]

Does anyone know if it is possible to dual mine (zcash + some other altcoin) with Nvidia gpus (2x1080tis)?

[thesavoyard]

I would get the new Galax 1070. I know they are a cheaper brand but I have 2 Galax 1060 6GB and they are great at mining ZEC or ETH.

Pascal chipset cards (10xx) use much less power for the same hash-rate as other cards deliver.

Also, if you decide to re-sell it, you are much more likely to get more of your money back with a Galax 1070

still funny how some people recommend nvidia for mining

nothing better than rx470-570's     , it s not for nothing you can not find any on sale

less power argument is not correct ever  the 570's undervolt pretty good

Haha hahaha hahaha

Ignorant or trolling?

[carlo_0000]

I would get the new Galax 1070. I know they are a cheaper brand but I have 2 Galax 1060 6GB and they are great at mining ZEC or ETH.

Pascal chipset cards (10xx) use much less power for the same hash-rate as other cards deliver.

Also, if you decide to re-sell it, you are much more likely to get more of your money back with a Galax 1070

still funny how some people recommend nvidia for mining

nothing better than rx470-570's     , it s not for nothing you can not find any on sale

less power argument is not correct ever  the 570's undervolt pretty good

Hello, how many Sol/s would I get from an undervolted 570? How much power would it use undervolted? Thanks

check amd thread , not sure anymore , it s lot more profitable on eth  if my memory is correct  rx570 does some more than 280 on zec (up to 300 with OC)
power on eth is 100-112w   so for zec it s a bit less (or same but higher clock)

and so definetly cheaper and faster than an gtx1060 3G

i have a model with1 small fan, cannot oc higher because it hit 84° and clock down , it s only doing 250sol
i did not under volt yet

[il_minatore]

if 1050 can get 150 sol/s then 5 of them would be 750 sol/s

is it better 5x 1050 or 2x 1060 3G + 1x 1050 instead?

or 2x second hand 970 + 1x 1050...

or even a single 1080ti?

in dilemma right now...  

any opinion? anyone?

why not 2 x 1070?

can't afford that yet. best i can get is 2x 1060 + 1x 1050 from the money & power wise.
but yesterday i check 980ti can get around 480 sol/s which is on par with 1070. i can get 2nd hand 980ti in here around $400 so maybe that one is better?
new zotac 1060 6gb is $290 in here so x2 = $480 but that can get me maybe around 600 sol/s

haha... dizzy... need a beer... 

How did you get 480sol/s with a 980ti? THanks

[mettalmag]

So far so good, just switched some of my cards to ZEC and this was the miner I was advised to use and here I am.
I have several questions I would to get answers to and find solutions.
I'm running  8xGigabyte 1080s on one rig and they are working like a charm, no specific config, nothing, except OC, all cards running about 565-575 Sol/s - mems 120/600. Uptime 16 days.
Second one is with 8x EVGA FTW 1080s, first try was 125/680 which was working fine for more then 12 hours, then I got "Looks like GPU0 are stopped. Restart attempt." after what I lowered the mems on same as Gigabyte 120/600, but I constantly getting the same error.
So the question is next: (I will solve the OC problem with EVGA but if you have any suggestions I'd be glad to hear that) how can I configure the miner that if it stops hashing to restart itself?
With Claymore's miner I'm using script which force stops the terminal itself and launches it again, but in case of Claymore I have a triger to run the bat file to do this (in case anyone interested here's the script)

Code:

@echo off
call :sub >log-%DATE:~-4%-%DATE:~4,2%-%DATE:~7,2%_%time:~0,2%%time:~3,2%%time:~6,2%.txt
exit /b

:sub
echo. #############################################
echo. %time% Check if old miner process exists and kill it
taskkill /f /im EthDcrMiner64.exe
echo. %time% Starting new Miner process one...
start /d "E:\Claymore's Miner" start.bat
echo. %time% Done!
timeout 5 >nul
exit 0

So, is there any solution with EWBF miner to make it more autonomous?

The next and less important for now question is how can I combine different rigs in one monitoring also like in Claymore's monitoring? For ether 100+ rigs are monitored with one monitoring instance and emailing and sms monitoring gives me ability to quickly respond if something happens, how is this possible in EWBF case?

[moeinbiz]

So far so good, just switched some of my cards to ZEC and this was the miner I was advised to use and here I am.
I have several questions I would to get answers to and find solutions.
I'm running  8xGigabyte 1080s on one rig and they are working like a charm, no specific config, nothing, except OC, all cards running about 565-575 Sol/s - mems 120/600. Uptime 16 days.
Second one is with 8x EVGA FTW 1080s, first try was 125/680 which was working fine for more then 12 hours, then I got "Looks like GPU0 are stopped. Restart attempt." after what I lowered the mems on same as Gigabyte 120/600, but I constantly getting the same error.
So the question is next: (I will solve the OC problem with EVGA but if you have any suggestions I'd be glad to hear that) how can I configure the miner that if it stops hashing to restart itself?
With Claymore's miner I'm using script which force stops the terminal itself and launches it again, but in case of Claymore I have a triger to run the bat file to do this (in case anyone interested here's the script)

Code:

@echo off
call :sub >log-%DATE:~-4%-%DATE:~4,2%-%DATE:~7,2%_%time:~0,2%%time:~3,2%%time:~6,2%.txt
exit /b

:sub
echo. #############################################
echo. %time% Check if old miner process exists and kill it
taskkill /f /im EthDcrMiner64.exe
echo. %time% Starting new Miner process one...
start /d "E:\Claymore's Miner" start.bat
echo. %time% Done!
timeout 5 >nul
exit 0

So, is there any solution with EWBF miner to make it more autonomous?

The next and less important for now question is how can I combine different rigs in one monitoring also like in Claymore's monitoring? For ether 100+ rigs are monitored with one monitoring instance and emailing and sms monitoring gives me ability to quickly respond if something happens, how is this possible in EWBF case?

This might help you to restart EWBF miner in case of any error:

Code:

:restart
TIMEOUT 8
miner --server zec-eu1.nanopool.org --port 6666 --user [USER] --pass x --eexit 3 --log 2 --logfile ZCASH.%date:~6,4%%date:~3,2%%date:~0,2%.ewbf.log --pec
goto :restart

I personally use 127.0.0.1:42000 to monitor a rig on localhost and if you add firewall exception in windows plus port forwarding in router and a DDNS service, this could be accessible from everywhere, I also use an uptime monitor service to ping this address for each rig and send me notification for any down time.
Hope that help you.

[mettalmag]

So far so good, just switched some of my cards to ZEC and this was the miner I was advised to use and here I am.
I have several questions I would to get answers to and find solutions.
I'm running  8xGigabyte 1080s on one rig and they are working like a charm, no specific config, nothing, except OC, all cards running about 565-575 Sol/s - mems 120/600. Uptime 16 days.
Second one is with 8x EVGA FTW 1080s, first try was 125/680 which was working fine for more then 12 hours, then I got "Looks like GPU0 are stopped. Restart attempt." after what I lowered the mems on same as Gigabyte 120/600, but I constantly getting the same error.
So the question is next: (I will solve the OC problem with EVGA but if you have any suggestions I'd be glad to hear that) how can I configure the miner that if it stops hashing to restart itself?
With Claymore's miner I'm using script which force stops the terminal itself and launches it again, but in case of Claymore I have a triger to run the bat file to do this (in case anyone interested here's the script)

Code:

@echo off
call :sub >log-%DATE:~-4%-%DATE:~4,2%-%DATE:~7,2%_%time:~0,2%%time:~3,2%%time:~6,2%.txt
exit /b

:sub
echo. #############################################
echo. %time% Check if old miner process exists and kill it
taskkill /f /im EthDcrMiner64.exe
echo. %time% Starting new Miner process one...
start /d "E:\Claymore's Miner" start.bat
echo. %time% Done!
timeout 5 >nul
exit 0

So, is there any solution with EWBF miner to make it more autonomous?

The next and less important for now question is how can I combine different rigs in one monitoring also like in Claymore's monitoring? For ether 100+ rigs are monitored with one monitoring instance and emailing and sms monitoring gives me ability to quickly respond if something happens, how is this possible in EWBF case?

This might help you to restart EWBF miner in case of any error:

Code:

:restart
TIMEOUT 8
miner --server zec-eu1.nanopool.org --port 6666 --user [USER] --pass x --eexit 3 --log 2 --logfile ZCASH.%date:~6,4%%date:~3,2%%date:~0,2%.ewbf.log --pec
goto :restart

I personally use 127.0.0.1:42000 to monitor a rig on localhost and if you add firewall exception in windows plus port forwarding in router and a DDNS service, this could be accessible from everywhere, I also use an uptime monitor service to ping this address for each rig and send me notification for any down time.
Hope that help you.

Thanks for this tip, what dows this command actually do --eexit 3? All others I'm familiar with. And btw are there any live commands in live terminal like s or r in Claymore's miner?
I'm using remote monitoring and it's way nicer and comfortable than any others out there, but so far it has been good only for live preview