Topic: EWBF's Cuda Equihash Miner 0.6 - page 19. (Read 85776 times)
any news for Maxwell? (GTX980)
It's great to see a v0.5 arrived . I noticed a hashrate improvements and seems like we can decrease mining intensity now . I want to thank you EWBF for your work and feedback on a community replies , as you are fixed all the major existing problems . :cheers:
Very nice boost to the hashrate based on the little bit of testing I have done so far. Nice indeed. 
I'm seeing 15-20% increases in 144,5 hash rates with my farm of 1060's. Moving on to the bigger metal now.
1070's - now getting average of 42 sol/s with v0.5 and an OC like this: 75% PL, +122 Core, +255 Mem
1080's - now getting average of 47-48 sol/s with v0.5 and OC like this: 70% PL, +97 Core, +401 Mem
For the 1080's, I'm seeing about a 16% gain over 0.4, with the same exact overclock and all, apples to apples, from the v0.4 days. WOW! Thank you sir!
UPDATE: 1080ti - just received this card, getting 70-71 sol/s with slight overclock 97/282 and 95% PL. FUN FUN FUN!
1070's - now getting average of 42 sol/s with v0.5 and an OC like this: 75% PL, +122 Core, +255 Mem
1080's - now getting average of 47-48 sol/s with v0.5 and OC like this: 70% PL, +97 Core, +401 Mem
For the 1080's, I'm seeing about a 16% gain over 0.4, with the same exact overclock and all, apples to apples, from the v0.4 days. WOW! Thank you sir!
UPDATE: 1080ti - just received this card, getting 70-71 sol/s with slight overclock 97/282 and 95% PL. FUN FUN FUN!
After a number of people here and in the other discords had mentioned that they were getting the cuda memory errors on their rigs after the .4 update, but getting less of them when they took their overclocks off, I've since followed the same route and seen better, but still frustrating results. I haven't added an OC profile to .5 yet, but it is running smoothly so far, and with much improved hash rates on the 1070ti's and 1080ti's. Currently running some variation of 65% TDP and 65-75% fan speeds with no core/mem adjustments. Would love to see what others are showing for stability on their OC settings on 0.5 with 1070ti+ cards.
WOW, now thats an update! best by a mile on my 1070ti and 1080ti
Just tried out v0.5 and its great so far. Awesome hashing improvement on my 1070 & 1080ti. Thanks and great work EWBF!
Good news everyone! v0.5 delivered.
Thanks for the work. Will hope to run here soon!
Good news everyone! v0.5 delivered.
Great release so far! Good results here. Good news everyone! v0.5 delivered.
Thank you very much! let's trying!
Good news everyone! v0.5 delivered.
WARNING: Looks like GPU0 are stopped. Restarting...
Is there a way to make the miner auto close and reopen when this happens? This error is very random and has nothing to do with overclocking.
Is there a way to make the miner auto close and reopen when this happens? This error is very random and has nothing to do with overclocking.
I just noticed that there is an "eexit" param, setting it to 1 seems to close the miner when errors occur. Still testing this, but it did close the miner for another error. So now you just need a bat script that restarts the miner as soon as it closes.
If using the cfg file: eexit 1
if using command line params: --eexit 1
Code:
@echo off
:restart
TIMEOUT 5
miner.exe --eexit 1
ping 127.0.0.1 > nul
goto :restart
:restart
TIMEOUT 5
miner.exe
ping 127.0.0.1 > nul
goto :restart
It would be nice if these parameters would be documented in the OP.
Hello everyone! I'm sorry that it's too late. I use previous EWBF zcash miner for zcash. What should i do to go to EWBF's Cuda Equihash Miner 0.4? Should i create a new wallet zcash? or create a new wallet BTG? or where i can read this info? sorry that it is too late for this old problem question. (sorry for my bad english)
Hello,
Don't apologize for being too late with your problem. It's never too late to learn!
You are absolutely right - some reading would be helpful, for example here www.google.com or here www.duckduckgo.com.
Then if you have technical problems with the miner please come back and we'll be happy to help (as much as we can)!
Hello everyone! I'm sorry that it's too late. I use previous EWBF zcash miner for zcash. What should i do to go to EWBF's Cuda Equihash Miner 0.4? Should i create a new wallet zcash? or create a new wallet BTG? or where i can read this info? sorry that it is too late for this old problem question. (sorry for my bad english)
https://forum.bitcoingold.org/t/double-spend-attacks-on-exchanges/1362
Are you seriously ? 51% attack? Yes, they can not keep the price because of the opportunity to quickly sell what the miners earned. Here the BTG "team" trying to increase the time spent on passing the circle under the guise of non-existent attacks ( found ==> waited conf.==> >>sold . The plug did not come out to profit at all. 1) Now we see the real network hash and it is so small that one person with 20 kk $ can buy video cards and arrange 51% of attacks
Otherwise, how can I explain the variables that are not amenable to logic and mathematics ....... I observ network hash for a week and I see this :
- Network Hashrate =2.83 Ms/s ,-diff = 97.505 K -diff = 117.505 K ---------is this how ??
- Network Hashrate =1.65 Ms/s ,-diff = 164.505 K and -diff = 250.505 K --is this how ??
- Network Hashrate =2.19 Ms/s ,-diff = 104.505 K ,-diff = 164.505 K ----is this how ??
Rent hash was an excellent cover all this time and did not give investors and miners to assess the realities of this coin, and they are such that one person can expose 51% the network BTG ,invested in it about 20kk $ its END?
Are you seriously ? 51% attack? Yes, they can not keep the price because of the opportunity to quickly sell what the miners earned. Here the BTG "team" trying to increase the time spent on passing the circle under the guise of non-existent attacks ( found ==> waited conf.==> >>sold . The plug did not come out to profit at all. 1) Now we see the real network hash and it is so small that one person with 20 kk $ can buy video cards and arrange 51% of attacks
Otherwise, how can I explain the variables that are not amenable to logic and mathematics ....... I observ network hash for a week and I see this :
- Network Hashrate =2.83 Ms/s ,-diff = 97.505 K -diff = 117.505 K ---------is this how ??
- Network Hashrate =1.65 Ms/s ,-diff = 164.505 K and -diff = 250.505 K --is this how ??
- Network Hashrate =2.19 Ms/s ,-diff = 104.505 K ,-diff = 164.505 K ----is this how ??
Rent hash was an excellent cover all this time and did not give investors and miners to assess the realities of this coin, and they are such that one person can expose 51% the network BTG ,invested in it about 20kk $ its END?
You may have a valid point here, but I'm struggling to understand it (mainly because of your English). I read your post three time, still don't understand half of your statements. Can you reformulate it in a coherent way?
Let's do the math. The net BTG hash is indeed quite low at the moment, let's say it's 2MH/s on average. That corresponds to ~ 50,000 GTX 1080 level GPUs. To perform 51% attack one needs ~ 50,000 GPUs with an average cost of ~ $500. One person can of course buy $25 mln worth of gpus, but one person cannot build a farm of that size. Where does the number of $20,000 come from (if that is what you mean by 20 kk $).
The hash power was obviously rented for the attacks (or was performed by one of larger existing farms).
https://forum.bitcoingold.org/t/double-spend-attacks-on-exchanges/1362
Are you seriously ? 51% attack? Yes, they can not keep the price because of the opportunity to quickly sell what the miners earned. Here the BTG "team" trying to increase the time spent on passing the circle under the guise of non-existent attacks ( found ==> waited conf.==> >>sold . The plug did not come out to profit at all. 1) Now we see the real network hash and it is so small that one person with 20 kk $ can buy video cards and arrange 51% of attacks
Otherwise, how can I explain the variables that are not amenable to logic and mathematics ....... I observ network hash for a week and I see this :
- Network Hashrate =2.83 Ms/s ,-diff = 97.505 K -diff = 117.505 K ---------is this how ??
- Network Hashrate =1.65 Ms/s ,-diff = 164.505 K and -diff = 250.505 K --is this how ??
- Network Hashrate =2.19 Ms/s ,-diff = 104.505 K ,-diff = 164.505 K ----is this how ??
Rent hash was an excellent cover all this time and did not give investors and miners to assess the realities of this coin, and they are such that one person can expose 51% the network BTG ,invested in it about 20kk $ its END?
Are you seriously ? 51% attack? Yes, they can not keep the price because of the opportunity to quickly sell what the miners earned. Here the BTG "team" trying to increase the time spent on passing the circle under the guise of non-existent attacks ( found ==> waited conf.==> >>sold . The plug did not come out to profit at all. 1) Now we see the real network hash and it is so small that one person with 20 kk $ can buy video cards and arrange 51% of attacks
Otherwise, how can I explain the variables that are not amenable to logic and mathematics ....... I observ network hash for a week and I see this :
- Network Hashrate =2.83 Ms/s ,-diff = 97.505 K -diff = 117.505 K ---------is this how ??
- Network Hashrate =1.65 Ms/s ,-diff = 164.505 K and -diff = 250.505 K --is this how ??
- Network Hashrate =2.19 Ms/s ,-diff = 104.505 K ,-diff = 164.505 K ----is this how ??
Rent hash was an excellent cover all this time and did not give investors and miners to assess the realities of this coin, and they are such that one person can expose 51% the network BTG ,invested in it about 20kk $ its END?
You may have a valid point here, but I'm struggling to understand it (mainly because of your English). I read your post three time, still don't understand half of your statements. Can you reformulate it in a coherent way?
Let's do the math. The net BTG hash is indeed quite low at the moment, let's say it's 2MH/s on average. That corresponds to ~ 50,000 GTX 1080 level GPUs. To perform 51% attack one needs ~ 50,000 GPUs with an average cost of ~ $500. One person can of course buy $25 mln worth of gpus, but one person cannot build a farm of that size. Where does the number of $20,000 come from (if that is what you mean by 20 kk $).
The hash power was obviously rented for the attacks (or was performed by one of larger existing farms).
Sure there is a way to block your posts on my end. But you are not getting the message here: it's not that I don't give shit whether you checked your transactions or not, NOONE gives shit. And therefore it would be more efficient to block your posts on YOUR end.
You can always open your own thread and post your ideas there. Or here is a better idea: try to go out and if you are lucky enough you can even find a girlfriend/boyfriend (depending on your gender and orientation).
I think you may have missed the point that the 51% attack increased exchange confirms 1000%. My post about the 6 hour confirm time was a direct reply to computer genie's link. I suppose my absentmindedness is annoying but these smaller coins have a reputation of attacks and heavy pumps and dumps to match. I do appreciate your consideration on my sexual preference though. I would recommend blocking my posts if they bother you.
Running .4 and using Zhash for the new BTG Fork and am getting a ton of rejected shares. I've tried with and without afterburner running so the OC isn't causing this
Quote
GPU0: 603 Sol/s GPU1: 385 Sol/s GPU2: 705 Sol/s
Total speed: 1693 Sol/s
INFO 07:51:15: GPU0 Rejected share 203ms [A:0, R:38]
INFO 07:51:16: GPU0 Rejected share 250ms [A:0, R:39]
INFO 07:51:18: GPU1 Rejected share 187ms [A:0, R:17]
INFO 07:51:24: GPU2 Rejected share 206ms [A:0, R:39]
INFO 07:51:26: GPU2 Rejected share 187ms [A:0, R:40]
INFO 07:51:26: GPU1 Rejected share 189ms [A:0, R:18]
INFO 07:51:29: GPU1 Rejected share 203ms [A:0, R:19]
INFO 07:51:31: GPU1 Rejected share 191ms [A:0, R:20]
INFO 07:51:34: GPU2 DevFee Accepted share
INFO 07:51:36: GPU2 DevFee Accepted share
Total speed: 1693 Sol/s
INFO 07:51:15: GPU0 Rejected share 203ms [A:0, R:38]
INFO 07:51:16: GPU0 Rejected share 250ms [A:0, R:39]
INFO 07:51:18: GPU1 Rejected share 187ms [A:0, R:17]
INFO 07:51:24: GPU2 Rejected share 206ms [A:0, R:39]
INFO 07:51:26: GPU2 Rejected share 187ms [A:0, R:40]
INFO 07:51:26: GPU1 Rejected share 189ms [A:0, R:18]
INFO 07:51:29: GPU1 Rejected share 203ms [A:0, R:19]
INFO 07:51:31: GPU1 Rejected share 191ms [A:0, R:20]
INFO 07:51:34: GPU2 DevFee Accepted share
INFO 07:51:36: GPU2 DevFee Accepted share
Zhash config will get you rejected shares for BTG.
BTG has its own config. I had this same problem with Awesome miner. Awesome miner list BTG under Zhash algo which gives rejected shares. To fix in Awesome miner, I had to create my own BTG coin and put it under the Equilhash BTG algo.
I was able to run the miner after editing the miner.cfg file and starting the miner application directly. For some reason now I'm able to run a batch file as intended. I'll try the the cuda 9 version tomorrow like meinerneiner after updates. These profits are hard to pass up right now.
Running .4 and using Zhash for the new BTG Fork and am getting a ton of rejected shares. I've tried with and without afterburner running so the OC isn't causing this
Quote
GPU0: 603 Sol/s GPU1: 385 Sol/s GPU2: 705 Sol/s
Total speed: 1693 Sol/s
INFO 07:51:15: GPU0 Rejected share 203ms [A:0, R:38]
INFO 07:51:16: GPU0 Rejected share 250ms [A:0, R:39]
INFO 07:51:18: GPU1 Rejected share 187ms [A:0, R:17]
INFO 07:51:24: GPU2 Rejected share 206ms [A:0, R:39]
INFO 07:51:26: GPU2 Rejected share 187ms [A:0, R:40]
INFO 07:51:26: GPU1 Rejected share 189ms [A:0, R:18]
INFO 07:51:29: GPU1 Rejected share 203ms [A:0, R:19]
INFO 07:51:31: GPU1 Rejected share 191ms [A:0, R:20]
INFO 07:51:34: GPU2 DevFee Accepted share
INFO 07:51:36: GPU2 DevFee Accepted share
Total speed: 1693 Sol/s
INFO 07:51:15: GPU0 Rejected share 203ms [A:0, R:38]
INFO 07:51:16: GPU0 Rejected share 250ms [A:0, R:39]
INFO 07:51:18: GPU1 Rejected share 187ms [A:0, R:17]
INFO 07:51:24: GPU2 Rejected share 206ms [A:0, R:39]
INFO 07:51:26: GPU2 Rejected share 187ms [A:0, R:40]
INFO 07:51:26: GPU1 Rejected share 189ms [A:0, R:18]
INFO 07:51:29: GPU1 Rejected share 203ms [A:0, R:19]
INFO 07:51:31: GPU1 Rejected share 191ms [A:0, R:20]
INFO 07:51:34: GPU2 DevFee Accepted share
INFO 07:51:36: GPU2 DevFee Accepted share
Zhash config will get you rejected shares for BTG.
BTG has its own config. I had this same problem with Awesome miner. Awesome miner list BTG under Zhash algo which gives rejected shares. To fix in Awesome miner, I had to create my own BTG coin and put it under the Equilhash BTG algo.
FWIW, I've transitioned now to using the cuda 9 based EWBF code rather than the one marked 'cuda8', and my cards have never been happier - I'm also now running the latest Nvidia drivers version 398.36, so not sure which resolved my crashes really - but between the 2 changes, I am running now 24 hours without a crash (knock on wood). YMMV and all that of course. My environment is a mix of about 80% 1060's, 10% 1070's, and 10% 1080's. With 1 lonely 980ti to keep the 'way back machine' gods happy. Love that card, and you couldn't pry it outta my hands!
But I digress. 0.4 is pretty sweet, all good on this end for now.
But I digress. 0.4 is pretty sweet, all good on this end for now.
Why are you even posting this? Do you think anyone gives fuck about your problems? Guess what? - no.
The last two pages are 50% your posts about ... h-m-m-m...nothing....
Stop spamming here.
Maybe the trail end here is not to topic, but I'm sure posting about my difficulties with the miner and my gpu clocks are fairly relevant. There been no intention of spam just conversation. Sorry to have been a bother. Isn't there a way to block my posts on your end?
Sure there is a way to block your posts on my end. But you are not getting the message here: it's not that I don't give shit whether you checked your transactions or not, NOONE gives shit. And therefore it would be more efficient to block your posts on YOUR end.
You can always open your own thread and post your ideas there. Or here is a better idea: try to go out and if you are lucky enough you can even find a girlfriend/boyfriend (depending on your gender and orientation).
Jump to: