EWBF's CUDA Zcash miner

[mez]

Does anybody has 6x 1080 rig and could share information about hashrate, power consumption from wall?  I plan to build some rig, and consider if 1070 or 1080 will be best choice at the moment.

i have 2 riggs with 4 x 1080TI each.
but the hashrate and power consumption is based on many factors.
you will approximately get 700 sol @ 250 watt per gpu. how much that is from wall depends on psu, ambient temp and more

[Heguli97]

Does anybody has 6x 1080 rig and could share information about hashrate, power consumption from wall?  I plan to build some rig, and consider if 1070 or 1080 will be best choice at the moment.

i have 2 riggs with 4 x 1080TI each.
but the hashrate and power consumption is based on many factors.
you will approximately get 700 sol @ 250 watt per gpu. how much that is from wall depends on psu, ambient temp and more

You could get 50-70 sol more each with 260 watts for the 1080ti.

[EWBF_]

Version 0.3.4b released.
Many new features on the way.
Web page screenshot: https://s4.postimg.org/opjzemkwt/Screenshot_20170611_220048.png

[notsure85]

Thank you very much for your time and work you put into this miner.
I am having trouble with eexit parameter, it doesnt quit on connection loss to pool.
Makes using the miner in multi-algo script difficult.
Maybe you could look into it.

[EWBF_]

Thank you very much for your time and work you put into this miner.
I am having trouble with eexit parameter, it doesnt quit on connection loss to pool.
Makes using the miner in multi-algo script difficult.
Maybe you could look into it.

what eexit value do you use?
You need to use the value 3 or 2. In case of connection failure, the miner will perform 3 attempts to reconnect and only after that will exit.

[notsure85]

this is how i start

--server europe.equihash-hub.miningpoolhub.com --port 12023 --eexit 2 --user XXX --pass XXX --tempunits C --templimit 75 --api 0.0.0.0:42000

when pool switches I see

"ERROR: Lost connection with the Server."
"INFO: Attempt to restore connection."
"ERROR: Stratum authorization error"

and then it just stays at 0 Sols without quitting. (waited 10m +)
Would be great if there was an option to quit immediately on connection loss.

Thank you for your support.

[patrike]

Version 0.3.4b released.
Many new features on the way.

Many thanks for this release and the new API with start time and current pool. This makes it possible for me to include more monitoring information in Awesome Miner.

[lokko]

First times thanks for your work, the miner 0.3.4 starts with 1922sol and then goes down to 1850sol temperatures have not increased, a bug?


Has done itself, apparently a temperature problem

[LuisMafixD]

Version 0.3.4b.

EWBF's Zcash cuda miner.
Expected speeds 500 sols/s gtx 1080, 444 sols/s gtx1070. 300 gtx1060 6G. Stock settings.
Writen for pascal gpus but works on cards with at least 1Gb memory, and Compute Capability 2 and higher.
Miner contain dev fee 2%.
Sorry for my bad english  

Version 0.3.4b
A slightly improved speed of about 2%
Added option --intensity, sets maximum intensity.
Added support for configuration files.
Added option --config, sets the name of the config file.
Added support for failover servers, through config files.
Added new values to the api method getstat.
Added http api you can use http://127.0.0.1:42000/getstat address to get statistics.
Added simple web page with statistics, simply open the api address in the web browser. (Experemental)
Fixed couple of bugs.

Version 0.3.3b
Added option --pec power efficiency calculator.
Added option --fee developer fee control.
Use miner --help command for more information.

FAQ:
Q: How to select a GPU that will be used by a miner
A: Use option --cuda_devices 0 1 2 digits is id of the devices which will be used.

Q: How intensity works?
A: The miner uses adaptive intensity and tries to use the maximum intensity value, with the help of the --intensity option you can set a limit on the maximum intensity, this will slightly reduce gpu usage and performance. Allowed values 1 - 64. You can set different values for each cards --intensity 64 64 64 64

Q: How to use config?
A: You can run the miner like all previous versions with command line arguments, in this case the config file will be ignored. If you sets the --config argument, the specified config file will be used, all other command line arguments will be ignored. If you run a miner without command line arguments, the miner will try to use the default config file miner.cfg.

Q: How to use failover servers
A: This feature works only with config files, see config examples, supplied with the miner.

Windows x64
https://mega.nz/#F!usQh2bTa!3qp_PaiO-dw3F0mpvLXynA
https://drive.google.com/open?id=0B9EPp8NdigFianNlcUh0YWFhOVE

Linux x64
https://mega.nz/#F!aop0BLaR!qQUGG6C2ZhE2zAC0XAlMSw
https://drive.google.com/open?id=0B9EPp8NdigFibDl2MmdXaTFjWDQ

Cuda Zcash miner of EWBF V 0.34b Does not improve Hast rate (+ 2%) Miner contains dev fee 2%.

[Heguli97]

Cuda Zcash miner of EWBF V 0.34b Does not improve Hast rate (+ 2%) Miner contains dev fee 2%.

Well it did for me. 

[LuisMafixD]

Cuda Zcash miner of EWBF V 0.34b Does not improve Hast rate (+ 2%) Miner contains dev fee 2%.

Well it did for me. 

Pff ...
I guess I should thank 

1% fee Flypool
2% EWBF
+ Diff

Does not have Hash rate improvements..

[YIz]

I'm getting 270Sol/s with a G1 970, is it a normal hashrate? any ways to improve it?
By the way, when I try to startup the miner and there's no internet connection it just closes, any way to prevent this and make the miner stay running until there's internet? thanks.

[GOLDbarISmine]

I'm getting 270Sol/s with a G1 970, is it a normal hashrate? any ways to improve it?
By the way, when I try to startup the miner and there's no internet connection it just closes, any way to prevent this and make the miner stay running until there's internet? thanks.

thats about the average, getting 300sols/s will need a lot of power.

[Elder III]

What does this error mean? I get it with both of the latest versions of the miner, tested on suprnova with ZCL and nicehash with ZEC.

Temp: GPU1: 39C
GPU1: 0 Sol/s
Total speed: 0 Sol/s
ERROR: Looks like GPU1 are stopped. Restart attempt.
INFO: GPU1 are restarted.
CUDA: Device: 1 User selected solver: 0
CUDA: Device: 1 Thread exited with code: 46

[dannygroove]

Can someone post me an nvidia-smi from a 1080TI?

[The_Threat]

What does this error mean? I get it with both of the latest versions of the miner, tested on suprnova with ZCL and nicehash with ZEC.

Temp: GPU1: 39C
GPU1: 0 Sol/s
Total speed: 0 Sol/s
ERROR: Looks like GPU1 are stopped. Restart attempt.
INFO: GPU1 are restarted.
CUDA: Device: 1 User selected solver: 0
CUDA: Device: 1 Thread exited with code: 46

Probably an unstable overclock, what is your core and mem clock and what GPU failed? 1070?

[QuadraQ]

I've been using your excellent mining software for over a month on my 5 750ti rig. But I recently upgraded two of the 750 Ti cards to GTX 1060 cards, so now I have three 750 Ti's and two 1060's (with another on the way). I do have a very modest overclock setup for all the cards with MSI's Afterburner (I was overclocking the 750 Ti cards before I got the 1060 cards).

So your miner was rock solid with the 5 750 Ti's (overclocked) but now I'm having trouble with the 1060's included in the mix. What's weird is that everything goes great for a long while and then suddenly I get this for all five cards:

Thread exited with code: 73

It tries to restart but fails and then I get stuck in a loop with this error:

Thread exited with code: 46

and it tries to restart fails then code 46 again, over and over.

Really frustrating to spend $500 on hardware and then be stymied because of a stability problem. Any idea what's going on?

Hi, may be many reasons why this happens, error 73 break down the cuda context, and all gpu stops with the same error, (this error unrecoverable and helps only miner restart), so the cause of the problem can be one gpu, and you need to find which one, and then check this gpu separately. And first, what you need to do is make sure that you have enough PSU power. Make all the tests on stock gpu settings.

Well I took out the 1060's and put them in a different rig, and put back the 750 Ti's they had replaced. Upgraded to version 0.3.4b. Set to the same modest overclock settings I've been using for years in this rig. I have a 1000 watt power supply and under full load this rig uses about 350 watts (I have a meter) so power isn't an issue. It went for a while and then stopped with "Thread exited with code: 4" for all five of the GPUs and then it's the same as before as it tries to restart and fails with "Thread exited with code: 46" over and over. I'm using the latest CUDA version 8.0.61. What does error code 4 mean?

[bangarang]

I got this error;

thread exit code 77

what does it mean?

i have reinstalled the drivers, and reset the overclock settings to default.

[nUm81]

Version 0.3.4b released.
Many new features on the way.
Web page screenshot: https://s4.postimg.org/opjzemkwt/Screenshot_20170611_220048.png

Thank you for the update EWBF, excellent miner and love the new web API.

For a future release when you get around to it, could you look at allowing multiple instances (miners) to all pool there API data back to one master or one master to collect the data from the other instances so that they can all be displayed on the one web API?

[cinderz45]

EWBF your miner is excellent. Mining Zencash with it is very profitable. Thank you!!!  

I run a 1080 Ti (cuda_devices 0) and a 1080 (cuda_devices 1). My 1080 does not seem to respond to your intensity settings properly.

i=64 64 is 1080 ~530 Sol/s

i=64 12 is 1080 still ~530 Sol/s

In both cases my card will cash while running other programs or trying to navigate windows desktop.

intensity might be not functioning properly.

For now, setting --solver=0 3 is my best solution.

Only issue is that it changes Sol/s to 360-380, but it is nice and stable.