mining rig 9x 1070ti and one 1070.
Keeps crashing half of the gpus thread exited with message:''out of memory''
works fine in old ewbf,tried to remove overclock settings same,tried to run 2 instances of ewbf same...
any help would be much appreciated...
Topic: EWBF's Cuda Equihash Miner 0.6 - page 38. (Read 85805 times)
Microsoft Defender detects Trojan:Win32/Bluteal.B!rfn in your v0.2 version, please comment. Thank you.
Defender is tagging actual M$ft dll files with that too; because, Winduhs!https://www.bleepingcomputer.com/news/security/windows-defender-detecting-legitimate-files-as-trojan-win32-blutealbrfn/
EWBF Cuda Equihash Miner v0.2
Greetings!
This is the initial release of a new miner for Equihash algorithm.
It is based on my last Zcash miner and almost completely repeats it.
Now closer to the topic:
* Parameter "solver" is disabled.
* Solver for equihash 200,9 has been deleted.
* Solvers for Equihash 192,7 and 144,5 has been added
* Added timestamps in the output to the screen and to the log file.
* Argument --algo is added, allow you to select Equihash variant allowed two values 144_5 and 192_7. This parameter is mandatory.
* Argument --pers is added, allow you to set personalization string (8 charachters) for equihash algorithm. This parameter is optional. Equihash by default uses the string "ZcashPoW", many other coins also use this string, but not all, some coins use their own string, and these are all differences, so for some coins, you need to set the --pers option to the required string, for example, Zero coin: https://bitcointalksearch.org/topic/annzerzero-your-transactions-are-your-business-3310714 uses the string "ZERO_PoW" and for mining this coin you need to pass arguments --algo 192_7 --pers ZERO_PoW ....
Fee is presented and by default 2%, argument --fee is presented too.
v0.2
* Reduced amount of rejected shares.
* Performance 144_5 is increased by ~ 5%.
* Added algorithm zhash it is similar to "--algo 144_5 --pers BitcoinZ." Now you can use "--algo zhash" string.
Expected performance:
144_5 uses ~2.2GB vram
1050ti ~12S/s
1060 ~20S/s
1070 ~30S/s
1080 ~35S/s
1080ti ~55S/s
192_7 uses ~2.9GB vram
1050ti ~7S/s
1060 ~12S/s
1070 ~18S/s
1080 ~20S/s
1080ti ~30S/s
Please note, that this is initial release, and it can be baggy or incompatible with many coins or pools.
Miner compiled with cuda 9.1 and cuda 8.0 for x64 linux and windows. Support devices with compute capability 5.0 and higher.
Windiws https://mega.nz/#F!fsAlmZQS!CwVgFfBDduQI-CbwVkUEpQ
Linux https://mega.nz/#F!3xYlSJDK!kG4kVLg1arbBuq1dd8u9aA
Linux https://drive.google.com/open?id=1jUhXYysli_x6MH_wQ9lY07c68Ze7WM8g
Windiws https://drive.google.com/open?id=1anfDRDVc_Fs_NceuZNuDK8HWZgcCdM3A
Greetings!
This is the initial release of a new miner for Equihash algorithm.
It is based on my last Zcash miner and almost completely repeats it.
Now closer to the topic:
* Parameter "solver" is disabled.
* Solver for equihash 200,9 has been deleted.
* Solvers for Equihash 192,7 and 144,5 has been added
* Added timestamps in the output to the screen and to the log file.
* Argument --algo is added, allow you to select Equihash variant allowed two values 144_5 and 192_7. This parameter is mandatory.
* Argument --pers is added, allow you to set personalization string (8 charachters) for equihash algorithm. This parameter is optional. Equihash by default uses the string "ZcashPoW", many other coins also use this string, but not all, some coins use their own string, and these are all differences, so for some coins, you need to set the --pers option to the required string, for example, Zero coin: https://bitcointalksearch.org/topic/annzerzero-your-transactions-are-your-business-3310714 uses the string "ZERO_PoW" and for mining this coin you need to pass arguments --algo 192_7 --pers ZERO_PoW ....
Fee is presented and by default 2%, argument --fee is presented too.
v0.2
* Reduced amount of rejected shares.
* Performance 144_5 is increased by ~ 5%.
* Added algorithm zhash it is similar to "--algo 144_5 --pers BitcoinZ." Now you can use "--algo zhash" string.
Expected performance:
144_5 uses ~2.2GB vram
1050ti ~12S/s
1060 ~20S/s
1070 ~30S/s
1080 ~35S/s
1080ti ~55S/s
192_7 uses ~2.9GB vram
1050ti ~7S/s
1060 ~12S/s
1070 ~18S/s
1080 ~20S/s
1080ti ~30S/s
Please note, that this is initial release, and it can be baggy or incompatible with many coins or pools.
Miner compiled with cuda 9.1 and cuda 8.0 for x64 linux and windows. Support devices with compute capability 5.0 and higher.
Windiws https://mega.nz/#F!fsAlmZQS!CwVgFfBDduQI-CbwVkUEpQ
Linux https://mega.nz/#F!3xYlSJDK!kG4kVLg1arbBuq1dd8u9aA
Linux https://drive.google.com/open?id=1jUhXYysli_x6MH_wQ9lY07c68Ze7WM8g
Windiws https://drive.google.com/open?id=1anfDRDVc_Fs_NceuZNuDK8HWZgcCdM3A
Microsoft Defender detects Trojan:Win32/Bluteal.B!rfn in your v0.2 version, please comment. Thank you.
questions.
1. BTG is is going to 144. when is that again.
2. When that happens. old miner will stop working and i must use new correct?
3. here is my script. what will i need to change?
miner.exe --server us-east.equihash-hub.miningpoolhub.com --user x --pass xx --port 20595
new script (help me with this, is this correct?)
miner.exe --algo 144_5 --server us-east.equihash-hub.miningpoolhub.com --user x --pass xx --port 20595
4. ( --pers )would help answer question above. is this needed for btg, if so, what do i change it to.
5. does --fee 0 work as intended??
ty!
1. BTG is is going to 144. when is that again.
2. When that happens. old miner will stop working and i must use new correct?
3. here is my script. what will i need to change?
miner.exe --server us-east.equihash-hub.miningpoolhub.com --user x --pass xx --port 20595
new script (help me with this, is this correct?)
miner.exe --algo 144_5 --server us-east.equihash-hub.miningpoolhub.com --user x --pass xx --port 20595
4. ( --pers )would help answer question above. is this needed for btg, if so, what do i change it to.
5. does --fee 0 work as intended??
ty!
See https://github.com/BTCGPU/BTCGPU/issues/331
1. Changes
Fork height: 536200 (May happen roughly July 1st, 2018. But the block height is the standard.)
Switch to Equihash-BTG
N,K: 144,5 #315
Personalization string: BgoldPoW #326
Solution size: 100 bytes
Typical memory usage for mining: ~2.5G per thread
Difficulty adjustment: #330
At the fork height, the difficulty will be reduced to 1/100th
Subsequent per-block Difficulty adjustments will be made via the LWMA difficulty adjustment algorithm.
Ok, thank you : I will take a look as soon as possible.
Any AMD miner?
Gents, who else has 12 card rigs on SMOS? I have 1070 and 1070ti rigs with 12x GPUs
last 10th, 11th and 12th card keep crushing (or rather, they do not even start mining), i have even removed overclock and tested with stock, still the same.
The rigs work fine with other miners, like EWBF 0.3.4b or Claymore for eth.
Since effectively out of 36 GPUs 7 - 8 are not working, i have switched back to ETH until this is sorted out.
last 10th, 11th and 12th card keep crushing (or rather, they do not even start mining), i have even removed overclock and tested with stock, still the same.
The rigs work fine with other miners, like EWBF 0.3.4b or Claymore for eth.
Since effectively out of 36 GPUs 7 - 8 are not working, i have switched back to ETH until this is sorted out.
Answer:
https://bitcointalksearch.org/topic/m.40306835
I'm waitnig for new version too.
Is there a significant difference with the unakoshi-miner?
What is it ? no point
even the best 1080 ti card has break even of one year currently
even the best 1080 ti card has break even of one year currently
There may not be much sense in buying new hardware now, but there's plenty of reason to keep mining with hardware that you have already bought and has paid for itself.
That is only if the electricity price is low.
...there's plenty of reason to keep mining with hardware that you have already bought and has paid for itself
AND
That is only if the electricity price is low.
no point
even the best 1080 ti card has break even of one year currently
even the best 1080 ti card has break even of one year currently
There may not be much sense in buying new hardware now, but there's plenty of reason to keep mining with hardware that you have already bought and has paid for itself.
That is only if the electricity price is low.
tested and compatible with all our Zhash pools @ Nibiru
LitecoinZ --> https://ltz.nibirupool.com/stats
BitcoinZ --> https://btcz.nibirupool.com/stats
Snowgem fork is coming as well --> https://xsg.nibirupool.com/stats
LitecoinZ --> https://ltz.nibirupool.com/stats
BitcoinZ --> https://btcz.nibirupool.com/stats
Snowgem fork is coming as well --> https://xsg.nibirupool.com/stats
Hello, started this miner with 6 1070 cards and its showing 8 sol hashrate per card. Does anyone know how to resolve this problem? WIN10, driver Nvidia driver 391.24 cuda 9.1, cards settings are in stock. I will be greatful for any help
Win10 x32 ? Troyans? Small pagefile?
no point
even the best 1080 ti card has break even of one year currently
even the best 1080 ti card has break even of one year currently
There may not be much sense in buying new hardware now, but there's plenty of reason to keep mining with hardware that you have already bought and has paid for itself.
no point
even the best 1080 ti card has break even of one year currently
even the best 1080 ti card has break even of one year currently
Hello, started this miner with 6 1070 cards and its showing 8 sol hashrate per card. Does anyone know how to resolve this problem? WIN10, driver Nvidia driver 391.24 cuda 9.1, cards settings are in stock. I will be greatful for any help
Nice to see ya back!
Played with v0.2 today with 1060x6 ssc. I only mine btg/zec/zcl for equihash so mined on the run,bat as is for ~200shares. Most nvidia OC cards already start above base so w/stock clocks it mined 12-13S/s @ 97-104w with less than 110ms latency. All accepted with only 2 rejects. Was on the 192_7 algo of course. Nvidia driver 391.24 cuda 9.1. Any cc overclock reduced efficiency as well as mem oc had 0 effect. As soon as I backed off the OC's it moved to ~14S/s. As usual EWBF will work well when the other equihash move to newer algos imho...
Played with v0.2 today with 1060x6 ssc. I only mine btg/zec/zcl for equihash so mined on the run,bat as is for ~200shares. Most nvidia OC cards already start above base so w/stock clocks it mined 12-13S/s @ 97-104w with less than 110ms latency. All accepted with only 2 rejects. Was on the 192_7 algo of course. Nvidia driver 391.24 cuda 9.1. Any cc overclock reduced efficiency as well as mem oc had 0 effect. As soon as I backed off the OC's it moved to ~14S/s. As usual EWBF will work well when the other equihash move to newer algos imho...
Is this miner for the equihash coins those already forked only? What are the algo codes such as 144_5, 200_9 and etc? Is there a place that I can check which coin has which algo code? Thanks.
Yes.You can use the pair BTCz coin and SuprNova pool (or an other pool, see my signature and the first post of the BTCz ANN thread).
https://crypt0.zone/calculator/s/9chfhxbv
+-------------------------------------------------+
| EWBF's Eqihash CUDA miner. v0.2 |
+-------------------------------------------------+
21:43:05 INFO: Used config file: miner.cfg
21:43:05 INFO: Current pool: zer-eu.forgetop.com:2052
21:43:05 INFO: Selected pools: 1
21:43:05 INFO: Algorithm: 192_7 "ZERO_PoW"
21:43:05 INFO: Devices: All.
21:43:05 INFO: Temperature limit: 82
21:43:05 INFO: Api: Listen on 127.0.0.1:42000
---------------------------------------------------
21:43:05 INFO: Target: 0320000000000000...
21:43:05 INFO: Detected new work: d22b
21:43:06 CUDA: Device: 0 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:06 CUDA: Device: 1 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:06 CUDA: Device: 2 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:06 CUDA: Device: 3 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:07 CUDA: Device: 4 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:07 CUDA: Device: 5 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:09 INFO: GPU2 Accepted share 111ms [A:1, R:0]
21:43:10 INFO: GPU4 Accepted share 111ms [A:1, R:0]
21:43:11 INFO: GPU0 Accepted share 111ms [A:1, R:0]
21:43:13 INFO: GPU0 Accepted share 111ms [A:2, R:0]
21:43:13 INFO: GPU0 Accepted share 223ms [A:3, R:0]
21:43:14 INFO: GPU3 Accepted share 111ms [A:1, R:0]
21:43:18 INFO: GPU2 Accepted share 111ms [A:2, R:0]
21:43:20 INFO: GPU3 Accepted share 112ms [A:2, R:0]
21:43:24 INFO: Detected new work: d22c
21:43:25 INFO: GPU4 Accepted share 112ms [A:2, R:0]
21:43:26 INFO: GPU3 Accepted share 112ms [A:3, R:0]
21:43:27 INFO: GPU4 Accepted share 111ms [A:3, R:0]
21:43:33 INFO: GPU1 Accepted share 112ms [A:1, R:0]
21:43:34 INFO: GPU3 Accepted share 112ms [A:4, R:0]
21:43:35 Temp: GPU0: 64C GPU1: 65C GPU2: 64C GPU3: 64C GPU4: 64C GPU5: 57C
21:43:35 GPU0: 10 Sol/s GPU1: 11 Sol/s GPU2: 9 Sol/s GPU3: 11 Sol/s GPU4: 10 Sol/s GPU5: 0 Sol/s
21:43:35 Total speed: 51 Sol/s
21:43:35 -----------+--------------+
| GPU | Power usage | Efficiency |
+-----+-------------+--------------+
| 0 | 64W | 0.16 Sol/W |
| 1 | 66W | 0.17 Sol/W |
| 2 | 73W | 0.12 Sol/W |
| 3 | 63W | 0.17 Sol/W |
| 4 | 70W | 0.14 Sol/W |
| 5 | 31W | 0.00 Sol/W |
+-----+-------------+--------------+
21:43:36 INFO: GPU4 Accepted share 112ms [A:4, R:0]
21:43:36 INFO: GPU4 Accepted share 112ms [A:5, R:0]
21:43:36 INFO: GPU3 Accepted share 112ms [A:5, R:0]
21:43:36 INFO: GPU0 Accepted share 171ms [A:4, R:0]
21:43:38 INFO: GPU2 Accepted share 112ms [A:3, R:0]
21:43:39 INFO: GPU3 Accepted share 111ms [A:6, R:0]
21:43:40 INFO: GPU4 Accepted share 111ms [A:6, R:0]
21:43:43 INFO: GPU3 Accepted share 112ms [A:7, R:0]
21:43:48 INFO: GPU4 Accepted share 112ms [A:7, R:0]
21:43:48 INFO: GPU0 Accepted share 111ms [A:5, R:0]
21:43:48 INFO: GPU5 Accepted share 182ms [A:1, R:0]
21:43:49 INFO: GPU3 Accepted share 111ms [A:8, R:0]
21:43:50 INFO: GPU4 Accepted share 111ms [A:8, R:0]
21:43:50 INFO: GPU4 Accepted share 112ms [A:9, R:0]
21:43:51 INFO: GPU3 Accepted share 111ms [A:9, R:0]
21:43:52 INFO: GPU4 Accepted share 112ms [A:10, R:0]
21:43:54 INFO: GPU4 Accepted share 112ms [A:11, R:0]
21:43:56 INFO: GPU4 Accepted share 111ms [A:12, R:0]
21:44:01 INFO: GPU5 Accepted share 111ms [A:2, R:0]
21:44:04 INFO: GPU3 Accepted share 111ms [A:10, R:0]
21:44:04 INFO: GPU5 Accepted share 112ms [A:3, R:0]
21:44:05 Temp: GPU0: 65C GPU1: 66C GPU2: 65C GPU3: 64C GPU4: 64C GPU5: 61C
21:44:05 GPU0: 10 Sol/s GPU1: 12 Sol/s GPU2: 10 Sol/s GPU3: 10 Sol/s GPU4: 11 Sol/s GPU5: 11 Sol/s
21:44:05 Total speed: 64 Sol/s
21:44:05 -----------+--------------+
| GPU | Power usage | Efficiency |
+-----+-------------+--------------+
| 0 | 65W | 0.15 Sol/W |
| 1 | 71W | 0.17 Sol/W |
| 2 | 69W | 0.14 Sol/W |
| 3 | 63W | 0.16 Sol/W |
| 4 | 74W | 0.15 Sol/W |
| 5 | 62W | 0.18 Sol/W |
+-----+-------------+--------------+
confirmed working with gtx 1060 3gb cards. this is with PL 75w +150 core and +1000 memory in Hive OS. Lucky, I thought my 1060 3gb cards were gonna not work with this!
on 144_5 I get 110-115 sol/s with the same settings.
Full disclosure. The rig I got this from is odd. I have some gigabyte g1 cards in it that have an 80w limit on how low I can set the power limit. The card can pull up to 200w for some reason. I have overclocked this thing to 2.1 ghz and have only seen a maximum of 120w so basically these cards are gigantic for nothing. And they are micron and cant OC for crap on memory. Mining eth with them going for + 500 to + 1000 on memory gets me an extra 0.25 mh/s. RIP
But this works great! and seems to run a little cooler
| EWBF's Eqihash CUDA miner. v0.2 |
+-------------------------------------------------+
21:43:05 INFO: Used config file: miner.cfg
21:43:05 INFO: Current pool: zer-eu.forgetop.com:2052
21:43:05 INFO: Selected pools: 1
21:43:05 INFO: Algorithm: 192_7 "ZERO_PoW"
21:43:05 INFO: Devices: All.
21:43:05 INFO: Temperature limit: 82
21:43:05 INFO: Api: Listen on 127.0.0.1:42000
---------------------------------------------------
21:43:05 INFO: Target: 0320000000000000...
21:43:05 INFO: Detected new work: d22b
21:43:06 CUDA: Device: 0 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:06 CUDA: Device: 1 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:06 CUDA: Device: 2 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:06 CUDA: Device: 3 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:07 CUDA: Device: 4 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:07 CUDA: Device: 5 GeForce GTX 1060 3GB, 3019 MB i:64
21:43:09 INFO: GPU2 Accepted share 111ms [A:1, R:0]
21:43:10 INFO: GPU4 Accepted share 111ms [A:1, R:0]
21:43:11 INFO: GPU0 Accepted share 111ms [A:1, R:0]
21:43:13 INFO: GPU0 Accepted share 111ms [A:2, R:0]
21:43:13 INFO: GPU0 Accepted share 223ms [A:3, R:0]
21:43:14 INFO: GPU3 Accepted share 111ms [A:1, R:0]
21:43:18 INFO: GPU2 Accepted share 111ms [A:2, R:0]
21:43:20 INFO: GPU3 Accepted share 112ms [A:2, R:0]
21:43:24 INFO: Detected new work: d22c
21:43:25 INFO: GPU4 Accepted share 112ms [A:2, R:0]
21:43:26 INFO: GPU3 Accepted share 112ms [A:3, R:0]
21:43:27 INFO: GPU4 Accepted share 111ms [A:3, R:0]
21:43:33 INFO: GPU1 Accepted share 112ms [A:1, R:0]
21:43:34 INFO: GPU3 Accepted share 112ms [A:4, R:0]
21:43:35 Temp: GPU0: 64C GPU1: 65C GPU2: 64C GPU3: 64C GPU4: 64C GPU5: 57C
21:43:35 GPU0: 10 Sol/s GPU1: 11 Sol/s GPU2: 9 Sol/s GPU3: 11 Sol/s GPU4: 10 Sol/s GPU5: 0 Sol/s
21:43:35 Total speed: 51 Sol/s
21:43:35 -----------+--------------+
| GPU | Power usage | Efficiency |
+-----+-------------+--------------+
| 0 | 64W | 0.16 Sol/W |
| 1 | 66W | 0.17 Sol/W |
| 2 | 73W | 0.12 Sol/W |
| 3 | 63W | 0.17 Sol/W |
| 4 | 70W | 0.14 Sol/W |
| 5 | 31W | 0.00 Sol/W |
+-----+-------------+--------------+
21:43:36 INFO: GPU4 Accepted share 112ms [A:4, R:0]
21:43:36 INFO: GPU4 Accepted share 112ms [A:5, R:0]
21:43:36 INFO: GPU3 Accepted share 112ms [A:5, R:0]
21:43:36 INFO: GPU0 Accepted share 171ms [A:4, R:0]
21:43:38 INFO: GPU2 Accepted share 112ms [A:3, R:0]
21:43:39 INFO: GPU3 Accepted share 111ms [A:6, R:0]
21:43:40 INFO: GPU4 Accepted share 111ms [A:6, R:0]
21:43:43 INFO: GPU3 Accepted share 112ms [A:7, R:0]
21:43:48 INFO: GPU4 Accepted share 112ms [A:7, R:0]
21:43:48 INFO: GPU0 Accepted share 111ms [A:5, R:0]
21:43:48 INFO: GPU5 Accepted share 182ms [A:1, R:0]
21:43:49 INFO: GPU3 Accepted share 111ms [A:8, R:0]
21:43:50 INFO: GPU4 Accepted share 111ms [A:8, R:0]
21:43:50 INFO: GPU4 Accepted share 112ms [A:9, R:0]
21:43:51 INFO: GPU3 Accepted share 111ms [A:9, R:0]
21:43:52 INFO: GPU4 Accepted share 112ms [A:10, R:0]
21:43:54 INFO: GPU4 Accepted share 112ms [A:11, R:0]
21:43:56 INFO: GPU4 Accepted share 111ms [A:12, R:0]
21:44:01 INFO: GPU5 Accepted share 111ms [A:2, R:0]
21:44:04 INFO: GPU3 Accepted share 111ms [A:10, R:0]
21:44:04 INFO: GPU5 Accepted share 112ms [A:3, R:0]
21:44:05 Temp: GPU0: 65C GPU1: 66C GPU2: 65C GPU3: 64C GPU4: 64C GPU5: 61C
21:44:05 GPU0: 10 Sol/s GPU1: 12 Sol/s GPU2: 10 Sol/s GPU3: 10 Sol/s GPU4: 11 Sol/s GPU5: 11 Sol/s
21:44:05 Total speed: 64 Sol/s
21:44:05 -----------+--------------+
| GPU | Power usage | Efficiency |
+-----+-------------+--------------+
| 0 | 65W | 0.15 Sol/W |
| 1 | 71W | 0.17 Sol/W |
| 2 | 69W | 0.14 Sol/W |
| 3 | 63W | 0.16 Sol/W |
| 4 | 74W | 0.15 Sol/W |
| 5 | 62W | 0.18 Sol/W |
+-----+-------------+--------------+
confirmed working with gtx 1060 3gb cards. this is with PL 75w +150 core and +1000 memory in Hive OS. Lucky, I thought my 1060 3gb cards were gonna not work with this!
on 144_5 I get 110-115 sol/s with the same settings.
Full disclosure. The rig I got this from is odd. I have some gigabyte g1 cards in it that have an 80w limit on how low I can set the power limit. The card can pull up to 200w for some reason. I have overclocked this thing to 2.1 ghz and have only seen a maximum of 120w so basically these cards are gigantic for nothing. And they are micron and cant OC for crap on memory. Mining eth with them going for + 500 to + 1000 on memory gets me an extra 0.25 mh/s. RIP
But this works great! and seems to run a little cooler
Nice work.
Giving you some merit.
I have 13x 1080tis left
And I have 2 1050tis
I will shift some to this newer algo
Quick question
What is a 1080ti earning with this algo
Giving you some merit.
I have 13x 1080tis left
And I have 2 1050tis
I will shift some to this newer algo
Quick question
What is a 1080ti earning with this algo
Jump to: