Nbdy
Newbie
 Offline
Activity: 3
Merit: 0
|
 |
April 29, 2019, 08:44:04 AM
Last edit: April 29, 2019, 12:02:35 PM by Nbdy |
|
Started with 1.3n2 today,will see how it will show trough time ... The 1.3n+ worked for day and 7 hours,and then started crashing and showing false shares ... I'm on sparkpool 2,but the eu part of it,should I change it be cause of ping  The miner crushed again after 3 hours of mining ... Must admit that there is a problem restarting miniZ even on sunpool ... He has some overclocking error,and after 4 restarts,and 2 reboots he finaly got to work on sunpool ... |
|
|
|
|
|
|
|
|
|
|
|
Even if you use Bitcoin through Tor, the way transactions are handled by the network makes anonymity difficult to achieve. Do not expect your transactions to be anonymous unless you really know what you're doing.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
somaton
Jr. Member
Offline
Activity: 204
Merit: 5
|
|
April 29, 2019, 01:04:10 PM |
|
n2 crashed same way like + and ++, usually takes only a few hours to get it. Log is totally useless - there is nothing at all, windows says miniz.exe crashed with module ntdll.dll, version: 6.3.9600.18821
|
|
|
|
|
stzcze
Jr. Member
Offline
Activity: 109
Merit: 1
|
|
April 29, 2019, 03:32:20 PM |
|
Hi, miner running 1-12h ok...after, no share to pool. +/++/n2 w10, G3930, rig 1060 rig 1080ti
|
|
|
|
|
|
miniZ (OP)
|
|
April 29, 2019, 04:24:17 PM |
|
hello
i have 19 GPU in one PC, me launch miniZ:
WTF??? Temp -31455247°C, FAN: 50528255%
after 3 min work me see log:
very long init miner
string launch:
miniZ --par=150,5 --server beam.eu.nicehash.com --port 3370 --user WALLET.CPz000000108 --telemetry=0
if you need access to my pc - no problem, linux + ssh + external ip
Hi artful, Thanks a lot for your logs. If this issue is not fixed we may take your ssh offer later  We have just released miniZ v1.3n3 and this slow init is fixed now. The weird values should be related to the slow start. Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
miniZ (OP)
|
|
April 29, 2019, 04:29:11 PM |
|
also been mining BEAM on sparkpool, latest version (1.3n2?) stil has issues with rejects there, 186 accepted 0 rejects according to miner 5.57% invalid 1% stale on sparkpool with high invalid/delay notification.
rig of mixed cards 2*1080, 2*1080ti 1*1070ti win 10 8GB RAM 64GB Virtual Memory allocated running at 60% power through MSI afterburner no issues noticed at sunpool
Started with 1.3n2 today,will see how it will show trough time ... The 1.3n+ worked for day and 7 hours,and then started crashing and showing false shares ... I'm on sparkpool 2,but the eu part of it,should I change it be cause of ping The miner crushed again after 3 hours of mining ... Must admit that there is a problem restarting miniZ even on sunpool ... He has some overclocking error,and after 4 restarts,and 2 reboots he finaly got to work on sunpool ... Hi AltScope, Nbdy, Thanks you for your feedback. We have just released miniZ v1.3n3 and the sparkpool issue should is fixed now. @Nbdy, the crash may be related to your OC settings. Try to adjust them and see if it persists. Let us know if the new release helped. Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
miniZ (OP)
|
|
April 29, 2019, 04:30:25 PM |
|
n2 crashed same way like + and ++, usually takes only a few hours to get it. Log is totally useless - there is nothing at all, windows says miniz.exe crashed with module ntdll.dll, version: 6.3.9600.18821
Hi somaton, That crash may be related to your OC settings. Try to adjust them and see if it persists. We have just released miniZ v1.3n3 and it should output some error now. If it happens again let us know what it logs. Thanks. Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
miniZ (OP)
|
|
April 29, 2019, 04:31:27 PM |
|
Hi, miner running 1-12h ok...after, no share to pool. +/++/n2 w10, G3930, rig 1060 rig 1080ti
Hi stzcze, could you post here a bit of the console output (or log) of the time when this happened? On what pool were you mining? Thanks. Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
topteam
Newbie
Offline
Activity: 157
Merit: 0
|
|
April 29, 2019, 05:09:14 PM |
|
Latest 1.3n+ still suffer from miner offline in pool just like the previous version. Whatever changes on this version doesn't fix the dreaded offline. Mining on algo 150.5.
Hi ARTRN, We are sorry about that... We really want to get rid of that issue, but it is very hard to replicate. On which pool were you mining? Thanks. Cheers have the same problem on 1.3n+, now run 1.3n2 ubuntu 16 396.82, 144,5, miningpoolhub |
|
|
|
|
psychopatical
Newbie
Offline
Activity: 6
Merit: 0
|
|
April 29, 2019, 05:15:17 PM
Last edit: April 29, 2019, 05:36:12 PM by psychopatical |
|
What the difference between Win cuda 8 and Win cuda 10?
Using 1060 and 1080 gpus
new version 1.3n3 running smoothly
|
|
|
|
|
|
miniZ (OP)
|
|
April 29, 2019, 05:16:50 PM |
|
Latest 1.3n+ still suffer from miner offline in pool just like the previous version. Whatever changes on this version doesn't fix the dreaded offline. Mining on algo 150.5.
Hi ARTRN, We are sorry about that... We really want to get rid of that issue, but it is very hard to replicate. On which pool were you mining? Thanks. Cheers have the same problem on 1.3n+, now run 1.3n2 ubuntu 16 396.82, 144,5, miningpoolhub Hi topteam, Sorry about that, it was solved on v1.3n2, but it is better if you try v1.3n3 Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
rgsnedds
Member
Offline
Activity: 952
Merit: 17
raskul
|
|
April 29, 2019, 05:34:24 PM |
|
is there a final release with fixes ready to go?
i'm a little confused with all the 1.3 versions. unsure which one i need to use.
for info, i've been running 1.3+ on mmpOS for around 50 hours now and it's flawless.
|
|
|
|
|
stzcze
Jr. Member
Offline
Activity: 109
Merit: 1
|
|
April 29, 2019, 05:54:21 PM |
|
Hi, miner running 1-12h ok...after, no share to pool. +/++/n2 w10, G3930, rig 1060 rig 1080ti
Hi stzcze, could you post here a bit of the console output (or log) of the time when this happened? On what pool were you mining? Thanks. Cheers pool: beam.leafpool.com I'm trying now "n3" cpu load 22% nice work, n+=70% - G3930 I didn't have the log on, I turned it on - I'll send him next time .-) Thanks |
|
|
|
|
MineOrDie
Jr. Member
Offline
Activity: 75
Merit: 1
|
|
April 29, 2019, 06:14:49 PM |
|
I still cannot mine BEAM on Hive OS with GTX1060 3GB, 418.56 drivers.
|
|
|
|
|
|
miniZ (OP)
|
|
April 29, 2019, 06:16:41 PM |
|
What the difference between Win cuda 8 and Win cuda 10?
Using 1060 and 1080 gpus
new version 1.3n3 running smoothly
Hi psychopatical, The win cuda 10 version requires a more recent driver, also usually performs better. But feel free to try both! Let's hope that miniZ 1.3n3 keeps running fine :-) We did not find any issues with this version so far. Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
miniZ (OP)
|
|
April 29, 2019, 06:17:36 PM |
|
is there a final release with fixes ready to go?
i'm a little confused with all the 1.3 versions. unsure which one i need to use.
for info, i've been running 1.3+ on mmpOS for around 50 hours now and it's flawless.
Hi rgsnedds, Sorry about all this realtime fixing, but the issue we were facing was very hard to reproduce and it was much faster to solve it with the help of everyone :-) Version 1.3n3 solves the issues that people were facing (offline worker, slow start, sparkpool invalid shares), it should be stable and the one to use, but after that laste few days is hard to be 100% sure! Thanks for letting us know that it is running fine one mmpOS for 50h! That is very relieving :-) Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
miniZ (OP)
|
|
April 29, 2019, 06:18:03 PM |
|
Hi, miner running 1-12h ok...after, no share to pool. +/++/n2 w10, G3930, rig 1060 rig 1080ti
Hi stzcze, could you post here a bit of the console output (or log) of the time when this happened? On what pool were you mining? Thanks. Cheers pool: beam.leafpool.com I'm trying now "n3" cpu load 22% nice work, n+=70% - G3930 I didn't have the log on, I turned it on - I'll send him next time .-) Thanks Hi stzcze, Thanks for reporting the improvements, keep us updated! cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
miniZ (OP)
|
|
April 29, 2019, 06:26:12 PM |
|
I still cannot mine BEAM on Hive OS with GTX1060 3GB, 418.56 drivers.
Hi MineOrDie, We tested it on Hive OS with 418.43, but it should work with your driver as well. What is the error miniZ complains about for not starting? If it is does not have enough memory you can try to add --mode=10 to the command line (this might be a problem if you have different cards models on your rig). Also it may help us to track the problem if you run nvidia-smi without any miners runing and give us the output. Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
MineOrDie
Jr. Member
Offline
Activity: 75
Merit: 1
|
|
April 29, 2019, 08:38:40 PM |
|
I still cannot mine BEAM on Hive OS with GTX1060 3GB, 418.56 drivers.
Hi MineOrDie, We tested it on Hive OS with 418.43, but it should work with your driver as well. What is the error miniZ complains about for not starting? If it is does not have enough memory you can try to add --mode=10 to the command line (this might be a problem if you have different cards models on your rig). Also it may help us to track the problem if you run nvidia-smi without any miners runing and give us the output. Cheers I get this message: Wanted to alloc: 2922 MB
out of memory::CUDA: failed to alloc memory for main data 1.3n3 version with --mode=10 added. +-----------------------------------------------------------------------------+
| NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 106... On | 00000000:01:00.0 On | N/A |
| 50% 41C P0 27W / 70W | 25MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 106... On | 00000000:02:00.0 Off | N/A |
| 50% 34C P0 25W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 106... On | 00000000:03:00.0 Off | N/A |
| 99% 42C P0 26W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 106... On | 00000000:04:00.0 Off | N/A |
| 50% 38C P0 25W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 106... On | 00000000:05:00.0 Off | N/A |
| 50% 38C P0 25W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 106... On | 00000000:07:00.0 Off | N/A |
| 50% 37C P0 23W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 6 GeForce GTX 106... On | 00000000:08:00.0 Off | N/A |
| 49% 38C P0 25W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 7 GeForce GTX 106... On | 00000000:09:00.0 Off | N/A |
| 50% 34C P0 25W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 8 GeForce GTX 106... On | 00000000:0A:00.0 Off | N/A |
| 50% 39C P0 26W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 9 GeForce GTX 106... On | 00000000:0B:00.0 Off | N/A |
| 50% 35C P0 23W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 10 GeForce GTX 106... On | 00000000:0C:00.0 Off | N/A |
| 50% 38C P0 25W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 11 GeForce GTX 106... On | 00000000:0D:00.0 Off | N/A |
| 50% 39C P0 25W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 2607 G /usr/lib/xorg/Xorg 22MiB |
| 1 2607 G /usr/lib/xorg/Xorg 6MiB |
| 2 2607 G /usr/lib/xorg/Xorg 6MiB |
| 3 2607 G /usr/lib/xorg/Xorg 6MiB |
| 4 2607 G /usr/lib/xorg/Xorg 6MiB |
| 5 2607 G /usr/lib/xorg/Xorg 6MiB |
| 6 2607 G /usr/lib/xorg/Xorg 6MiB |
| 7 2607 G /usr/lib/xorg/Xorg 6MiB |
| 8 2607 G /usr/lib/xorg/Xorg 6MiB |
| 9 2607 G /usr/lib/xorg/Xorg 6MiB |
| 10 2607 G /usr/lib/xorg/Xorg 6MiB |
| 11 2607 G /usr/lib/xorg/Xorg 6MiB |
+-----------------------------------------------------------------------------+ |
|
|
|
|
artful
Newbie
Offline
Activity: 59
Merit: 0
|
|
April 29, 2019, 08:55:31 PM |
|
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 |
|-------------------------------+----------------------+----------------------+
| 10 GeForce GTX 106... On | 00000000:0F:00.0 Off | N/A |
| 70% 56C P2 87W / 96W | 3008MiB / 3019MiB | 100% Default |
| 10 1062 G /usr/lib/xorg/Xorg 5MiB |
| 10 2654 C ...ing/calcprofit/miners/miniz/1.3n3/miniZ 2991MiB |
3Gb / 418.56 / miniZ 1.3n3 - working fine |
|
|
|
|
|
miniZ (OP)
|
|
April 29, 2019, 09:11:04 PM |
|
I still cannot mine BEAM on Hive OS with GTX1060 3GB, 418.56 drivers.
Hi MineOrDie, We tested it on Hive OS with 418.43, but it should work with your driver as well. What is the error miniZ complains about for not starting? If it is does not have enough memory you can try to add --mode=10 to the command line (this might be a problem if you have different cards models on your rig). Also it may help us to track the problem if you run nvidia-smi without any miners runing and give us the output. Cheers I get this message: Wanted to alloc: 2922 MB
out of memory::CUDA: failed to alloc memory for main data 1.3n3 version with --mode=10 added. +-----------------------------------------------------------------------------+
| NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 106... On | 00000000:01:00.0 On | N/A |
| 50% 41C P0 27W / 70W | 25MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 106... On | 00000000:02:00.0 Off | N/A |
| 50% 34C P0 25W / 70W | 9MiB / 3019MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 106... On | 00000000:03:00.0 Off | N/A |
Hi MineOrDie, It should run as it looks like there is enough memory to run it (3019-25=2994), but maybe it is still too tight... You still can try two things: 1. --mode=3 (it will be a bit slow, but just to see if it works) 2. exclude the first GPU (that has less free memory) with -cde 0Then we can try to workout a solution for you :-) Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
