Topic: EWBF's CUDA Zcash miner - page 30. (Read 2164326 times)

bets miner for equihash ever! Thanks dev. Using it for over 4 months. restarting the system (ubuntu) twice a day by default and all runs smoothly.

In first post, the new verson is still named 0.3.4b, and not 0.3.4c or 0.3.5...

 My LINUX rigs usually go for months (if the POWER stays up long enough) without reboots - I'd say years but I haven't had a year straight with no power outages here (had *2* outages last summer due to brushfires burning power lines).
 Win 7 machines (the few I have left) are lucky to manage A month without problems.

Thanks for the info.  I will just let it run!

btw.. I shouldn't say all are at "1070's are about 472 Sols average each."  sorry about that,...  gpu's are 469,449,451,466,465, 442,.. but they vary a bit.
Asus and EVGA cards.

Sometime my rigs self reboot after 14-16 days of running maybe due to window update. For me, I reboot them after each 1.5 month for cleaning.
By the way, your hashrate is pretty impressive. My MSI 1070 seahawk could reach only 448sol/s at 140W power limit, core: +50, mem: +40.     

Just curious how long some of you run your miners before rebooting, etc.
I finally have mine pretty stable as it is a new rig, and it's been running 24hrs now and still going.  6 1070's at 2771 Sol/s average now.  Sometimes it goes over 2800 Sols/s

All 1070's are about 472 Sols average each.

i switch the gpu's with an other computer
it was always crashing  did not mater  underclock overclcok stock or whatever

maybe old am2 motherboard are not compatible ?
switched with an am3+ with rx560  now both ring are running normal
getting  410 with little oc  they doing 390 at stock  i did not try high oc yet
but first i have to update windows again on that one it s running an older win10  (so cannot do eth)
gonna need to do a fresh install the ssd is to small for an upgrade
i tried to clone a bigger ssd to a smaller  but it make trouble (even there is all the data in the begin of the disk) the reported ssd size is wrong even after scandisk)
and when you use it it make strange thinks, like i change computer ip but after reboot the old one is back just act like my profil is read only)

Got deleted because of virus flags and instability..

New version: http://cryptomining-blog.com/

It might also be worthwhile to check you CPU load. Your PSU is powerful enough?
Did you install afterburner and made any custom settings? It looks a little bit as if the cards don’t have enough power.

It's very low hashrate for GTX1070. What is your OC settings? Do you use 0.3.4b version of EWBF? It also could be because of Windows build version. I had similar problem with Win10 without Aniverssary update. After reinstalling to 1703build hashrate became normal (470Sol/s at 150W consumption)

Hi i setup on centos but miner is not connecting to a pool and exited with error 1 when i use the command:
./miner --server --user

. --pass x --port --cuda_devices 0

Of course i replace everything in the bracket with the appropriate values.

Do you have any idea what is going on?
I used same address as the one i used in windows. and compared the URL and port address exactly same.
On both centos (linux) and windows, using ewbf and it works in windows.

linux machine on which it is failing:
asus z270 with core i3
centos7.2
nvidia driver installed successfully.

THanks.,

Is there still ongoing development on this miner or dev abandoned the project?

i build my first  1070 ring yesturday

but it get a lot of trouble now

Temp: GPU0: 65C GPU1: 60C GPU2: 54C GPU3: 57C
GPU0: 391 Sol/s GPU1: 333 Sol/s GPU2: 336 Sol/s GPU3: 385 Sol/s
Total speed: 1445 Sol/s
INFO 00:59:53: GPU3 Accepted share 1845ms [A:4, R:0]
INFO 00:59:58: GPU3 Accepted share 703ms [A:5, R:0]
INFO 01:00:01: GPU3 Accepted share 984ms [A:6, R:0]
INFO 01:00:04: GPU0 Accepted share 1532ms [A:5, R:0]
INFO 01:00:07: GPU0 Accepted share 297ms [A:6, R:0]
Temp: GPU0: 69C GPU1: 58C GPU2: 52C GPU3: 58C
GPU0: 343 Sol/s GPU1: 292 Sol/s GPU2: 278 Sol/s GPU3: 325 Sol/s
Total speed: 1238 Sol/s
CUDA: Device: 1 Thread exited with code: 6
CUDA: Device: 3 Thread exited with code: 6
CUDA: Device: 2 Thread exited with code: 6
CUDA: Device: 0 Thread exited with code: 6
INFO: Detected new work: 1c70
Temp: GPU0: 57C GPU1: 55C GPU2: 47C GPU3: 48C
GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s
Total speed: 0 Sol/s
ERROR: Looks like GPU0 are stopped. Restart attempt.
INFO: GPU0 are restarted.
ERROR: Looks like GPU1 are stopped. Restart attempt.
INFO: GPU1 are restarted.
ERROR: Looks like GPU2 are stopped. Restart attempt.
INFO: GPU2 are restarted.
ERROR: Looks like GPU3 are stopped. Restart attempt.
INFO: GPU3 are restarted.
CUDA: Device: 0 User selected solver: 0
CUDA: Device: 1 User selected solver: 0
CUDA: Device: 3 User selected solver: 0
CUDA: Device: 2 User selected solver: 0
CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 2 Thread exited with code: 46

computer was an older version of win10 and had some bugs
so i did a fresh install with last win10

but got a lot of trouble
computer always crashing a lot

it already started with installing the driver, i had to try 4 times


yesturday i was mining lyra because it was more stable the zec miner

but now even that don't work

*** ccminer 2.2 for nVidia GPUs by tpruvot@github ***
    Built with VC++ 19 and nVidia CUDA SDK 9.0 32-bits

  Originally based on Christian Buchner and Christian H. project
  Include some algos from alexis78, djm34, sp, tsiv and klausT.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

[2017-12-03 01:15:45] Starting on stratum+tcp://europe.lyra2z-hub.miningpoolhub.com:20581
[2017-12-03 01:15:45] NVAPI GPU monitoring enabled.
[2017-12-03 01:15:45] 4 miner threads started, using 'lyra2z' algorithm.
[2017-12-03 01:15:54] Stratum difficulty set to 10 (0.03906)
[2017-12-03 01:15:54] GPU #3: Intensity set to 16, 65536 cuda threads
[2017-12-03 01:15:54] GPU #2: Intensity set to 16, 65536 cuda threads
[2017-12-03 01:15:54] GPU #0: Intensity set to 16, 65536 cuda threads
[2017-12-03 01:15:54] GPU #1: Intensity set to 16, 65536 cuda threads
[2017-12-03 01:16:01] GPU #1: GeForce GTX 1070, 70.78 kH/s
[2017-12-03 01:16:02] GPU #0: MSI GTX 1070, 66.01 kH/s
[2017-12-03 01:16:02] GPU #2: GeForce GTX 1070, 65.61 kH/s
[2017-12-03 01:16:02] GPU #3: GeForce GTX 1070, 61.78 kH/s
[2017-12-03 01:16:35] Stratum difficulty set to 5 (0.01953)
[2017-12-03 01:17:04] GPU #2: GeForce GTX 1070, 1553.32 kH/s
[2017-12-03 01:17:05] GPU #1: GeForce GTX 1070, 1473.96 kH/s
[2017-12-03 01:17:06] GPU #0: MSI GTX 1070, 1451.93 kH/s
[2017-12-03 01:17:06] GPU #3: GeForce GTX 1070, 1529.05 kH/s
[2017-12-03 01:17:26] GPU #3: GeForce GTX 1070, 1467.27 kH/s
[2017-12-03 01:17:26] accepted: 1/1 (diff 0.113), 4228.53 kH/s yes!
[2017-12-03 01:17:32] GPU #3: GeForce GTX 1070, 1464.36 kH/s
[2017-12-03 01:17:48] GPU #2: GeForce GTX 1070, 2140.79 kH/s
[2017-12-03 01:17:48] GPU #1: GeForce GTX 1070, 2056.73 kH/s
[2017-12-03 01:17:48] GPU #3: GeForce GTX 1070, 5280.93 kH/s
[2017-12-03 01:17:48] GPU #0: MSI GTX 1070, 2047.18 kH/s
[2017-12-03 01:17:49] GPU #1: the launch timed out and was terminated
[2017-12-03 01:17:49] GPU #3: the launch timed out and was terminated
[2017-12-03 01:17:49] GPU #2: the launch timed out and was terminated
[2017-12-03 01:17:49] GPU #0: the launch timed out and was terminated
[2017-12-03 01:17:49] GPU #3: the launch timed out and was terminated
[2017-12-03 01:17:49] GPU #1: the launch timed out and was terminated
[2017-12-03 01:17:49] GPU #2: the launch timed out and was terminated


maybe some compatibility isue with the old am2  motherboard  i switch the gpus with an other computer, looks like it s working now

Thanks for the recommendations guys, I spent most of today playing with the settings and taking notes and I finally managed to bring my efficiency to 4 sol/w however my hash is down to 360 h/s

I tested 10 different TDP settings from 100% all the way down to 50% and noticed that the GPU is the most profitable at 60% TDP, that's with stock settings for the rest, then I started playing with core and memory and strangely I came up to the fact that memory boost is slightly lowering my hash rate and core boost is boosting my hashrate

Below are my optimal settings as far as efficiency is concerned

Hash: 360 Sol/s
TDP: 60% (90 Watts)
No Memory OC
Core OC: 1914mhz (+205)
Temperature: 65 degrees
Fan speed: 25% (Auto)
Efficiency: 4 sol/w

 Undervolt, NOT overvolt, for better efficiency - or leave the voltage untouched and let the card TDP management deal with it.
 for 112 watts on a 1070 though, that's not a horrible hashrate.

These are ment to be monsters when clocked right along with the EVGA cards.

Try these settings and see how it goes...

Core: (+140)
Memory: (-202 or -303)
Voltage: Stock setting and then play from there
TDP: Stock setting and then play from there

You guys think we will get a new version anytime soon? Better optimization? This miner is still the best but i would be happy if i could mine faster 

Hello everyone,

Newbie miner here, So I finished assembling my first mining rig and I'm currently testing and fine tuning it using one Zotac 1070 GPU before installing the other 5

I'm not sure but my results appear to be not so great, I got a maximum of 435 sol/s with 100 tdp but I'm achieving better efficiency at 75% TDP by getting around 3.50 sol/w

What's confusing me is that memory and core OC doesn't seem to have any impact on performance, i tried all sorts of combination and I'm only able to get a good control of Sol/s by adjusting the TDP only

I'm using Windows 10 with the latest nVidia driver, my current settings are:

Core: 1594 (+148)
Memory: 4360 (+557)
Voltage: +20%
TDP: 75% (112 watts)
Temperature : 65 degrees
Fan speed : 30% (Auto)
Hash: 395 Sol/s


I also noticed that whatever I do I can never push the temperature more than 70 degrees and I the fan never blew more than 50%, is there something I'm missing here ?

Is an efficiency of 3.50 sol/w acceptable or is there room to improve it?

Thanks guys

its probably a pool issue, post your config and well see what we can do to help.

what pools are you using? post also your CPU systems and hardware specs