Topic: EWBF's Cuda Equihash Miner 0.6 - page 20. (Read 85776 times)
I found running separate batch files helps with up time, but crashing still occurs regardless of clocks. I did find of my four card set GPU 1 & 2 crashed "more regularly". (4x 1070ti's)
Anyone else getting random crashes...My miners will run fine for a day or two then I will get "all cuda devices are busy " error and the miner keep rolling with that error ... I even have a card that will not start with this error, I tried no over clock and even under volting but does not seem to help.
Seem to be more prevalent with my 1070 and 1080ti rigs.
Seem to be more prevalent with my 1070 and 1080ti rigs.
It's random. There's nothing you can do currently.
Anyone else getting random crashes...My miners will run fine for a day or two then I will get "all cuda devices are busy " error and the miner keep rolling with that error ... I even have a card that will not start with this error, I tried no over clock and even under volting but does not seem to help.
Seem to be more prevalent with my 1070 and 1080ti rigs.
Seem to be more prevalent with my 1070 and 1080ti rigs.
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?
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?
Guess I've been busy to look into the confirm times. Looking at my exchange deposits they took over 6 hours.
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.
Guess I've been busy to look into the confirm times. Looking at my exchange deposits they took over 6 hours.
Hope everyone dropped their BTG bags earlier.
You mean before 51%-attack?Was there an attack? I was just talking about the price drop. My Nivida card love some EWBF miner though, hope the kinks are worked out soon. On to something else though.
Hope everyone dropped their BTG bags earlier.
You mean before 51%-attack?Hope everyone dropped their BTG bags earlier.
You mean before 51%-attack?
Hope everyone dropped their BTG bags earlier.
0.4 TY!!!
980ti - 32 sol/s
pw 70% +145 cc +428 mc
980 - 25 32 sol/s pw 70 % +131 cc +294 mc
970 - 18 - 24 sols pw 70% +98 cc +302 mc
980ti - 32 sol/s
pw 70% +145 cc +428 mc980 - 25 32 sol/s
pw 70 % +131 cc +294 mc970 - 18 - 24 sols
pw 70% +98 cc +302 mcGive me Readme.txt please!
what do you want a readme for? you could have asked a question instead
I am sure someone in this thread is able to help you - so what do you need help with?try to mine btc in mining pool hub and alwys get rejected shares .... what i am doing wrong ?
thx
thx
how does your bat file look like?
great performance for 1063 on 144_5!
try to mine btc in mining pool hub and alwys get rejected shares .... what i am doing wrong ?
thx
+-------------------------------------------------+
| EWBF's Eqihash CUDA miner. v0.4 |
+-------------------------------------------------+
19:13:13 INFO: Configured pools: 1
19:13:13 INFO: Selected pool: europe.equihash-hub.miningpoolhub.com:20595
19:13:13 INFO: Algorithm: 144_5
19:13:13 INFO: Devices: All.
19:13:13 INFO: Temperature limit: 80
19:13:13 INFO: Api: Disabled
---------------------------------------------------
19:13:14 INFO: Target: 000da740da740da7...
19:13:14 INFO: Detected new work: a317
19:13:15 CUDA: Device: 0 GeForce GTX 1080 Ti, 11171 MB i:64
19:13:15 CUDA: Device: 1 GeForce GTX 1080 Ti, 11172 MB i:64
19:13:15 CUDA: Device: 2 GeForce GTX 1080 Ti, 11172 MB i:64
19:13:44 Temp: GPU0: 71C GPU1: 71C GPU2: 70C
19:13:44 GPU0: 50 Sol/s GPU1: 51 Sol/s GPU2: 55 Sol/s
19:13:44 Total speed: 156 Sol/s
19:13:59 INFO: GPU0 Rejected share 403ms [A:0, R:1]
19:14:04 INFO: Detected new work: a318
19:14:14 Temp: GPU0: 73C GPU1: 73C GPU2: 73C
19:14:14 GPU0: 51 Sol/s GPU1: 53 Sol/s GPU2: 53 Sol/s
19:14:14 Total speed: 157 Sol/s
thx
+-------------------------------------------------+
| EWBF's Eqihash CUDA miner. v0.4 |
+-------------------------------------------------+
19:13:13 INFO: Configured pools: 1
19:13:13 INFO: Selected pool: europe.equihash-hub.miningpoolhub.com:20595
19:13:13 INFO: Algorithm: 144_5
19:13:13 INFO: Devices: All.
19:13:13 INFO: Temperature limit: 80
19:13:13 INFO: Api: Disabled
---------------------------------------------------
19:13:14 INFO: Target: 000da740da740da7...
19:13:14 INFO: Detected new work: a317
19:13:15 CUDA: Device: 0 GeForce GTX 1080 Ti, 11171 MB i:64
19:13:15 CUDA: Device: 1 GeForce GTX 1080 Ti, 11172 MB i:64
19:13:15 CUDA: Device: 2 GeForce GTX 1080 Ti, 11172 MB i:64
19:13:44 Temp: GPU0: 71C GPU1: 71C GPU2: 70C
19:13:44 GPU0: 50 Sol/s GPU1: 51 Sol/s GPU2: 55 Sol/s
19:13:44 Total speed: 156 Sol/s
19:13:59 INFO: GPU0 Rejected share 403ms [A:0, R:1]
19:14:04 INFO: Detected new work: a318
19:14:14 Temp: GPU0: 73C GPU1: 73C GPU2: 73C
19:14:14 GPU0: 51 Sol/s GPU1: 53 Sol/s GPU2: 53 Sol/s
19:14:14 Total speed: 157 Sol/s
I have two cards this miner refuses to work on, very strange.. It will start with some hashrate of around 30 and then next update it will drop to half and then it will be 0. I've tried running only 4 cards and still, the same cards lock up and won't restart. I'll try previous versions to see if this is something new to this version. It keeps repeating the same error messages, card #2 locked up, restarting.. card #4 locked up, restarting.. But it can never restart them for them to work.
Update: even previous versions have this issue. It's the same 2 cards, these 2 cards work fine on other algos but when I try equi 192 7 these 2 cards lock up using ewbf. I have 8x 1080ti, even if I try running one instance of 4 cards (0,1,2,3) , card# 2 will lock up after a couple of minutes. If I try to run an instance of cards 4,5,6,7 then card #4 will lock up. If I try to run an instance with all 8 cards, then cards 2,4 will lock up. It's like those 2 cards do not like this miner.
Update: even previous versions have this issue. It's the same 2 cards, these 2 cards work fine on other algos but when I try equi 192 7 these 2 cards lock up using ewbf. I have 8x 1080ti, even if I try running one instance of 4 cards (0,1,2,3) , card# 2 will lock up after a couple of minutes. If I try to run an instance of cards 4,5,6,7 then card #4 will lock up. If I try to run an instance with all 8 cards, then cards 2,4 will lock up. It's like those 2 cards do not like this miner.
Has anyone tried using the Eth pill with no overclock on 192 7 to see if that works since this is a memory intensive algo? Also, is there a limitation of only 6 cards on this miner in windows?
Guys how to add failover server in hiveos ewbf 0.3?
Isn't that in the "miner" file not application?
Update:
7% utilization of the CPU with four runs on, nothing else. Currently I see pool side flux of 300 sols to 170 sols (includes 1080 ti at 55 sols steady). I think I'm on the hair of a couple cards still, three drops today. was hoping to run a full frame tonight but will wait. Things look steady now. All core clocks are +150 still but highest mem clock is down to 720.
36-42 sols per 1070 ti
55 sols frim 1080 ti
216 sol average. See how next hours go.
Guys how to add failover server in hiveos ewbf 0.3?
Jump to: