Trouble running miniZ
If you are experiencing any trouble starting/running miniZ, please leave your comment in the comment box below, for support.
If you are experiencing any trouble starting/running miniZ, please leave your comment in the comment box below, for support.
While attempting to convert my older Maxwell (2GB) rig from zcash to btg, i’m getting a segfault with miniZ:
[115034.317747] miniZ[8379]: segfault at 0 ip 0000000000000000 sp 00007fd5077fdaf8 error 14 in nvidiactl[200000000+100000]
[115048.229614] miniZ[8408]: segfault at 0 ip 0000000000000000 sp 00007f3b7e7fbaf8 error 14 in nvidiactl[200000000+100000]
voodoo@m4a77d:~/miners/bins/miniZ_miner_v1.0b$ ./miniZ –url robertcnelson.m4a77d@btg.suprnova.cc:8866
************ miniZ v1.0b ************
Number of CUDA devices found: 3
Cannot read health status! (is libnvidia-ml.so installed?): Success
miniZ,144,5[2]: Selecting GPU#2 GeForce GTX 750 Ti
miniZ,144,5[2]: Selecting GPU#1 GeForce GTX 960
miniZ,144,5[2]: Selecting GPU#0 GeForce GTX 960
Algo: EQ[144,5]
Pool#0: user[robertcnelson.m4a77d] server[btg.suprnova.cc] port[8866] ssl[no] pers[BgoldPoW]
Telemetry: [http://localhost:20000]
Temp. limit: [90°C]
Segmentation fault
The system is based of Debian Buster, 4.17.x kernel, with nvidia 396.45
voodoo@m4a77d:~/miners/bins/miniZ_miner_v1.0b$ ./miniZ -ci
************ miniZ v1.0b ************
Number of CUDA devices found: 3
#0 GeForce GTX 960 | SM version: 5.2 | SM count: 8 | Memory: 1949
#1 GeForce GTX 960 | SM version: 5.2 | SM count: 8 | Memory: 1949
#2 GeForce GTX 750 Ti | SM version: 5.0 | SM count: 5 | Memory: 1962
Regards,
Hi,
thank you for leaving feedback.
I is a bit late here but could you try the following and report back? We’ll try to get you and answer asap.
1. Run nvidia-smi.
2. Could you run miniZ with each que GPU separately? Or, at least separately for the GTX 750 Ti, and GTX 960?
./miniZ --url robertcnelson.m4a77d@btg.suprnova.cc:8866 --cuda-devices 0then
./miniZ --url robertcnelson.m4a77d@btg.suprnova.cc:8866 --cuda-devices 2and report if you get the same error?
Although nvidia-ml doesn’t seem to be your main problem, it still needs to be solved.
Thank you. Cheers.
I got the same error, but perhaps is related to internet connection ?
All the streams in others computers stoped when recibe this error in the mining machine.
All connected in the same network.
Hi Barto,
from what you describe, it seems that the connection to the internet (or the pool) was lost.
Was this solved? If not, could you paste here the error log?
Thanks.
Cheers
C:\Users\파츠짱\Downloads\miniZ_v1.0i_win-x64 (1)>miniZ.exe –url parts333.1080ti@asia.equihash-hub.miningpoolhub.com:20595
************ miniZ v1.0i++ ************
Number of CUDA devices found: 13
miniZ,144,5[1]: Selecting GPU#0 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#8 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#1 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#3 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#4 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#5 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#6 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#7 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#2 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#9 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#10 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#11 GeForce GTX 1080 Ti
miniZ,144,5[1]: Selecting GPU#12 GeForce GTX 1080 Ti
Algo: EQ[144,5]
Pool#0: user[parts333.1080ti] server[asia.equihash-hub.miningpoolhub.com] port[20595] ssl[no] pers[BgoldPoW]
Telemetry: [http://localhost:20000]
Temp. limit: [90? <<cursor
No more no progress
Hi PARTS, do you have enough memory available for those 13 GPUs? You can try to increase the pagefile and see if it helps. Also, can you run the miniZ with less GPUs? This may help understand what is happening.
Thank you for the feedback.
Cheers
Hi there!
Is there a ‘proper’ API available? Preferrably Ccminer compatible 🙂
Thanks
UG
Hi UselessGuru,
Thanks for your message. We have some kind of “standard” json api, which is fully compatible with the EWBF miner.
Example (Linux):
curl --silent rig2:20000 -X '{"id":"0", "method":"getstat"}'returns:
{"id":0, "method":"getstat", "error":null, "start_time":1544548916, "current_server":"zhash.eu.nicehash.com:3369", "server_latency":62.4, "available_servers":1, "server_status":1, "result":[{"gpuid":0, "cudaid":0, "busid":"busid", "name":"GeForce GTX 1050", "gpu_status":2, "solver":-1, "temperature":66, "gpu_fan_speed":35, "gpu_power_usage":75.0, "gpu_clock_core_max":1695, "gpu_clock_memory":3504, "speed_sps":16.1, "accepted_shares":23, "rejected_shares":0, "start_time":1544548916},{"gpuid":1, "cudaid":1, "busid":"busid", "name":"GeForce GTX 1050 Ti", "gpu_status":2, "solver":-1, "temperature":71, "gpu_fan_speed":38, "gpu_power_usage":75.0, "gpu_clock_core_max":1594, "gpu_clock_memory":3504, "speed_sps":18.6, "accepted_shares":22, "rejected_shares":0, "start_time":1544548916},{"gpuid":2, "cudaid":2, "busid":"busid", "name":"GeForce GTX 1070 Ti", "gpu_status":2, "solver":-1, "temperature":69, "gpu_fan_speed":49, "gpu_power_usage":172.1, "gpu_clock_core_max":1759, "gpu_clock_memory":3802, "speed_sps":59.0, "accepted_shares":69, "rejected_shares":0, "start_time":1544548916}]}Let us know if you need further help.
Cheers!
Heya, I was trying to access the api and just querying the base address/port returns the html text, not a json or json-like output. Is there another endpoint I should be using?
Nevermind, got it working now.
Hi Bathmat,
great that you managed to get it working.
Let us know it you need anything else.
Cheers
Thank you!
Could you give me an example for PowerShell (I am a Windows guy)?
I googled to no avail…
Hi UselessGuru,
you can try this PowerShell script
$server = "localhost"
$port = 20000
$Message = '{"id":"0", "method":"getstat"}'
$Client = $Null
$Client = New-Object System.Net.Sockets.TcpClient $server, $port
$Writer = New-Object System.IO.StreamWriter $Client.GetStream()
$Reader = New-Object System.IO.StreamReader $Client.GetStream()
$client.SendTimeout = 10000
$client.ReceiveTimeout = 10000
$Writer.AutoFlush = $true
$Writer.WriteLine($Message)
$Request = $Reader.ReadLine()
$Data = $Request | ConvertFrom-Json
Write-Host $Data
Write-Host $Data.result
Returns:
@{id=0; method=getstat; error=; start_time=1546129190; current_server=zhash.eu.nicehash.com:3369; server_latency=73.8; available_servers=-2; server_status=1; result=System.Object[]}@{gpuid=0; cudaid=0; busid=busid; name=GeForce GTX 1060 3GB; gpu_status=2; solver=-1; temperature=71; gpu_fan_speed=43; gpu_power_usage=117.2; gpu_clock_core_max=1771; gpu_clock_memory=3802; speed_sps=33.1; accepted_shares=66; rejected_shares=1; start_time=1546129190}
Cheers
Thank you – works like a charm!
I’ve added you miner to MultiPoolMiner (www.multipoolminer.io)
Thanks! That is great.
Good luck with your nice project!
Keep getting cuda devices not found error. What am I doing wrong:
Here is a copy of my .sh file. I am running Bionic Beaver Ubuntu:
!bin/bash
./miniZ –url Ge31GZvBuMje6zhiKu6dNQaBbGPg9sTd4b.Miner2@us-btg.2miners.com:4040 –log –gpu-line 0 1 2 3 4
Hi Mathew,
it seems you are missing the option that is required to specify the devices
-cdor--cuda-devices(before the device(s) number). Try the following:!bin/bash./miniZ --url Ge31GZvBuMje6zhiKu6dNQaBbGPg9sTd4b.Miner2@us-btg.2miners.com:4040 --log --gpu-line -cd 0 1 2 3 4
For other usage information and examples check https://miniz.ch/usage/
Let us know how it goes.
Cheers
Thank you, that fixed the original problem, awesome, but now the miner fires up and begins to mine but then hangs/freezes/crashes whatever term you prefer and I have to kill power and restart.
Using assorted nvidia cards, eleven of them, 1070, 1070ti and 1080. Updated drivers to 410 cuda version 10.0
Thanks again. Any help greatly appreciated!
Matteo
Hi Matteo,
we are sorry about this.
On a first approach this may be related with the OC settings of the cards, if you did some OC. If so, do you have this issue with stock settings too?
If the previous does not apply, could you let us know if the problem also exists with v1.0h? Maybe this can help us figure out what’s going on.
Cheers
Hello miniZ,
Yes, I run an OC script before I start the miner, should I not do that?
I am now traveling for the week but feel free to communicate any other ideas. I really like your miniZ Miner from what I can see and am excited to give it a try.
Thank you for your help, greatly appreciated
Okay, so I tried without running the OC script and it still froze up.
Any other thoughts on what could be causing the problem?
Thank You for any help, greatly appreciated….
Hi Matthew,
Thank you for the feedback!
We’ve just released a new miniZ version v1.0j.
Try this new version, and let us know how did it go.
Try also cuda 8.0 variant.
Cheers
This is just insane why this miner continues to freeze.
Can we please communicate via email?
Hi Matthew,
we are sorry about the persistent freeze.
We have just contacted you.
Cheers
hi,
i got error on running miniz miner
CUDA ERROR[1970-01-02 05:59:21]: GPU[0]: CUDA error ‘CUDA driver version is insufficient for CUDA runtime version’ in func ‘cE;aB43dE<E7:bb::getinfo' line 255
GPU[0]: CUDA error 'CUDA driver version is insufficient for CUDA runtime version' in func 'cE;aB43dE<E7:bb::getinfo' line 255
Can you help me ?
Thanks
Hi Leo,
maybe you need to update the NVIDIA driver.
Which miniZ and Cuda version are you using? And which OS and NVIDIA driver version?
Could you paste here the output of nvidia-smi?
Cheers
Hi
the version of miniz : miniZ_v1.2m_cuda10_win-x64
the version of OS : windows 10
Wed Apr 17 09:16:30 2019
+—————————————————————————–+
| NVIDIA-SMI 388.59 Driver Version: 388.59 |
|——————————-+———————-+———————-+
| GPU Name TCC/WDDM | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 108… WDDM | 00000000:01:00.0 Off | N/A |
| 85% 70C P2 152W / 152W | 1935MiB / 11264MiB | 100% Default |
+——————————-+———————-+———————-+
| 1 GeForce GTX 108… WDDM | 00000000:02:00.0 Off | N/A |
| 78% 69C P2 193W / 204W | 1935MiB / 11264MiB | 100% Default |
+——————————-+———————-+———————-+
| 2 GeForce GTX 108… WDDM | 00000000:05:00.0 Off | N/A |
| 79% 66C P2 187W / 204W | 1935MiB / 11264MiB | 100% Default |
+——————————-+———————-+———————-+
| 3 GeForce GTX 108… WDDM | 00000000:06:00.0 Off | N/A |
| 78% 67C P2 172W / 177W | 1934MiB / 11264MiB | 100% Default |
+——————————-+———————-+———————-+
| 4 GeForce GTX 108… WDDM | 00000000:08:00.0 Off | N/A |
| 79% 66C P2 178W / 198W | 1935MiB / 11264MiB | 100% Default |
+——————————-+———————-+———————-+
| 5 GeForce GTX 108… WDDM | 00000000:0C:00.0 Off | N/A |
| 78% 70C P2 178W / 175W | 1935MiB / 11264MiB | 100% Default |
+——————————-+———————-+———————-+
| 6 GeForce GTX 108… WDDM | 00000000:0D:00.0 On | N/A |
| 78% 62C P2 178W / 198W | 2047MiB / 11264MiB | 100% Default |
+——————————-+———————-+———————-+
| 7 GeForce GTX 108… WDDM | 00000000:0E:00.0 Off | N/A |
| 77% 65C P2 171W / 172W | 1934MiB / 11264MiB | 100% Default |
+——————————-+———————-+———————-+
| 8 GeForce GTX 108… WDDM | 00000000:0F:00.0 Off | N/A |
| 85% 73C P2 166W / 175W | 1935MiB / 11264MiB | 100% Default |
+——————————-+———————-+———————-+
| 9 GeForce GTX 108… WDDM | 00000000:10:00.0 Off | N/A |
| 78% 62C P2 189W / 212W | 1935MiB / 11264MiB | 100% Default |
+——————————-+———————-+———————-+
+—————————————————————————–+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 7352 C C:\winsys\gminer_1_37_windows64\miner.exe N/A |
| 1 7352 C C:\winsys\gminer_1_37_windows64\miner.exe N/A |
| 2 7352 C C:\winsys\gminer_1_37_windows64\miner.exe N/A |
| 3 7352 C C:\winsys\gminer_1_37_windows64\miner.exe N/A |
| 4 7352 C C:\winsys\gminer_1_37_windows64\miner.exe N/A |
| 5 7352 C C:\winsys\gminer_1_37_windows64\miner.exe N/A |
| 6 224 C+G Insufficient Permissions N/A |
| 6 1400 C+G …mmersiveControlPanel\SystemSettings.exe N/A |
| 6 1956 C+G Insufficient Permissions N/A |
| 6 3208 C+G …x64__8wekyb3d8bbwe\Microsoft.Photos.exe N/A |
| 6 6604 C+G C:\Windows\explorer.exe N/A |
| 6 6616 C+G …t_cw5n1h2txyewy\ShellExperienceHost.exe N/A |
| 6 6920 C+G …dows.Cortana_cw5n1h2txyewy\SearchUI.exe N/A |
| 6 7352 C C:\winsys\gminer_1_37_windows64\miner.exe N/A |
| 6 7500 C+G …11411.0_x64__8wekyb3d8bbwe\Video.UI.exe N/A |
| 7 7352 C C:\winsys\gminer_1_37_windows64\miner.exe N/A |
| 8 7352 C C:\winsys\gminer_1_37_windows64\miner.exe N/A |
| 9 7352 C C:\winsys\gminer_1_37_windows64\miner.exe N/A |
Please reply my on my email. i dont get any notification here
thanks.
Hi Leo,
we have just sent you an email.
Thanks for reaching us and reporting the information.
For your driver (388.59) you must use miniZ Cuda 8 version. Alternatively, to be able to use Cuda 10 version, you need to update your driver to the latest version (>=418 recommended).
Let us know how it goes.
Cheers
Telemetry doesn’t work.
My command line is:
miniZ.exe –oc2 –par=192_7 –pers auto -a 192.168.1.201:42000 –server [Server] –port [Port] –user [User] –pass [Password]
Miner works like charm, but when I open browser (Google Chrome) and type “192.168.1.201:42000” or “http://localhost:42000”, none of those works.
Chrome only shows “This site can’t be reached” message after try to Connecting for a while.
Hi MiningTaken,
You are right,
-ais not working as documented. We will fix this for the next version.Try
-a 42000or--telemetry 192.168.1.201:42000(or--telemetry 42000)Cheers
hi my miniz work well but i hav note any accept share from suprnova pool :(((
Hi hoomanleo,
miniZ should work very well with Suprnova. It could be that, in your case, the algo or the personalisation string are note well specified.
Could you post here your command line?
Cheers
miniZ.exe –url hoomanleo.rig1@btg.suprnova.cc:8866 –log –extra
(edited) Hi hoomanleo,
Thanks for providing your command line.
We have just tested your command line:
miniZ.exe --url hoomanleo.rig1@btg.suprnova.cc:8866 --log --extraand it works! (Just in case, check for the double dash
--instead of-)Let us know if you manage to solve the issue.
Cheers,
miniZ
hi the problem solved but after 1 day mining or less the mining stop and get this error
CCMINER HAS STOPED WORKING
aproblem caused the program to stop working correctly
windows will close the program and notify you if a solution is available
ccminer is incorrect miniz.exe has stopped working
and the last command line is warning parse response failed
can i use task scheduler for this error?
Hi hoomaleo,
This could be related to your OCs, but could you provide the console output (or the logfile) just before the crash?
Try also the new miniZ v1.3n3 that has a few fixes and should be more stable.
Let us know if this helped.
Cheers
hi i use miniz ver 1.3n4 but i have no share with green star
Hi hoomanleo,
could you provide here some details such as:
1. your command line,
2. the beginning of console output, including when the miner detects GPUs. (Or logfile output).
Thank you!
Cheers
hi
miniZ.exe –url hoomanleo.rig1@btg.suprnova.cc:8866 –log –extra
this command line already work well whit ver 1.3n3
but from yesterday till now this version and version 1.3n4 dos not have share imean green star near fan speed
aftre header listing show up after 5 minutes mining start but without green star our share
and after 20 min say with red color can not connect to any mining pool
Hi hoomanleo,
we’ve tested your line and we had good shares. You seem to be unable to connect to suprnova. This may be something temporary. Are you still experiencing this? If so, we suggest you to try another pool and see if it persists.
Let us know how it goes.
Cheers
i test with funakooshi miner and it work well
but miniz!!!!!!! 2 weeks works good and then error cannot connect to any mininig pool :(((
Hi hoomanleo,
we have just answered to your other messages.
It seems that it lost connection to suprnova and could not reconnect again. Does it work if you restart miniZ?
Cheers
no i restart miniz many times and chek everything but dos not work
[ 0d 0h22m18s] S: 0/0 231(227.5)Sol/s 621(544.0)W [fee.server] (9.3%) (90.7%)
0>GTX 1070
100% [65øC/65%] 27.64 I/s 55.4(54.7)Sol/s 135(119.5)W clk=1771MHz mclk=3802MHz Sol/W=0.46100% [69øC/69%] 29.06 I/s 58.2(57.6)Sol/s 160(139.7)W clk=1847MHz mclk=3802MHz Sol/W=0.411>GTX 1070
2>GTX 1070
100% [65øC/65%] 29.05 I/s 58.3(57.4)Sol/s 162(138.2)W clk=1835MHz mclk=3802MHz Sol/W=0.42100% [65øC/65%] 29.47 I/s 58.4(57.8)Sol/s 165(139.5)W clk=1885MHz mclk=3802MHz Sol/W=0.413>GTX 1070
[ERROR ] Cannot connect to any mining pool!!!
[ 0d 0h22m28s] S: 0/0 230(227.5)Sol/s 627(545.4)W [fee.server] (9.2%) (90.8%)
0>GTX 1070
100% [65øC/65%] 27.64 I/s 55.4(54.7)Sol/s 140(119.8)W clk=1771MHz mclk=3802MHz Sol/W=0.46100% [70øC/69%] 29.07 I/s 58.2(57.6)Sol/s 162(140.0)W clk=1847MHz mclk=3802MHz Sol/W=0.411>GTX 1070
2>GTX 1070
100% [66øC/65%] 29.06 I/s 58.2(57.4)Sol/s 162(138.5)W clk=1847MHz mclk=3802MHz Sol/W=0.41100% [65øC/65%] 29.47 I/s 58.4(57.8)Sol/s 163(139.7)W clk=1898MHz mclk=3802MHz Sol/W=0.413>GTX 1070
[ 0d 0h22m38s] S: 0/0 230(227.5)Sol/s 387(538.8)W [fee.server] (9.2%) (90.8%)
0>GTX 1070
100% [60øC/62%] 27.64 I/s 55.4(54.7)Sol/s 88(118.8)W clk=1632MHz mclk=3802MHz Sol/W=0.46100% [63øC/66%] 29.07 I/s 58.2(57.6)Sol/s 100(138.7)W clk=1632MHz mclk=3802MHz Sol/W=0.411>GTX 1070
2>GTX 1070
100% [58øC/61%] 29.06 I/s 58.2(57.4)Sol/s 99(137.3)W clk=1632MHz mclk=3802MHz Sol/W=0.42100% [56øC/59%] 29.47 I/s 58.4(57.8)Sol/s 99(138.5)W clk=1632MHz mclk=3802MHz Sol/W=0.423>GTX 1070
[ 0d 0h22m49s] S: 0/0 230(227.5)Sol/s 213(530.6)W [fee.server] (9.2%) (90.8%)
0>GTX 1070
100% [58øC/60%] 27.64 I/s 55.4(54.7)Sol/s 51(117.6)W clk=139MHz mclk=405MHz Sol/W=0.46100% [60øC/63%] 29.07 I/s 58.2(57.6)Sol/s 55(137.2)W clk=139MHz mclk=405MHz Sol/W=0.421>GTX 1070
2>GTX 1070
100% [55øC/58%] 29.06 I/s 58.2(57.4)Sol/s 54(135.7)W clk=139MHz mclk=405MHz Sol/W=0.42100% [53øC/56%] 29.47 I/s 58.4(57.8)Sol/s 54(136.9)W clk=139MHz mclk=405MHz Sol/W=0.423>GTX 1070
Hi hoomanleo,
we are sorry about this. It looks like it lost connection to the mining pool and could not reconnect again.
If you define a different pool, or if you define a second mining pool, does the problem persist?
You can define a second pool like this:
miniZ.exe --url hoomanleo.rig1@btg.suprnova.cc:8866 --url YourWalletAddress.WorkerName@SecondPoolServer:PortNumber --log --extraCould you confirm which miniZ version you are using? (You can also check this by running miniZ.exe –version)
Thanks.
Cheers
i use 3 different pool and non of them dosnot work
and i already use ver1.2m ver 1.3n3 ver 1.3n4
but 2 weeks earlier my rigs work well with ver 1.3n.3
suddenly every rigs getting error that cannot connect to any pool
tnx for your replying
Hi hoomanleo,
at the moment we do not fully understand the problem you are experiencing.
It seems to be related to poor network connectivity, but we will investigate further and we will try to reproduce some scenarios.
Cheers
hi
when i push telemetry on GUI launcher chrome can not open page
and say localhost refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
i disable fire wall already and nothimg change
maybe this is my connection problem????????
Hi hoomanleo,
It looks like that telemetry could not bind the 20000 port.
You can run resmon command on Windows, to check if the port is being used.
Go to tab : “Network”->”Listening Ports”, and check which process is using 20000 port, in “Port” column.
You can follow the instructions on this post: https://bitcointalk.org/index.php?topic=4767892.msg50204311#msg50204311
Let us know if this helped.
Cheers
This miner works fine but terminates every 1-2 hours. I wonder if that’s when it mines for fee. There appears to be no logfile? NV drivers 419.17 cuda 10 win10.
Hi Brian997,
we have improved stability and these problems should be solved in the next version (will be out very soon).
Regarding the logfile, if you run miniZ with
--log, which creates a miniZ.log file, does it work?Cheers
I ran with –log below is output after 26 minutes it crashed. The script forces restart, but the ramping up time is a little slow. The miner is 1-2% faster than gminer, but it crashes and ramps up to peak slower than gminer. I have been using same overclaock settings for about 6 months. FYI below…pasted log at time of crash.
0>GTX 1070 Ti
100% [56øC/56%] 18.55 I/s 37.8(36.9)Sol/s 108(105.3)W clk=1632MHz mclk=4303MHz Sol/W=0.35100% [55øC/55%] 18.24 I/s 36.4(36.2)Sol/s 111(107.2)W clk=1607MHz mclk=4303MHz Sol/W=0.341>GTX 1070 Ti
2>GTX 1060 6GB
100% [61øC/61%] 10.75 I/s 21.3(21.5)Sol/s 88( 91.3)W clk=1708MHz mclk=4252MHz Sol/W=0.24100% [56øC/55%] 18.32 I/s 36.4(36.9)Sol/s 105(105.4)W clk=1607MHz mclk=4303MHz Sol/W=0.353>GTX 1070 Ti
4>GTX 1070 Ti
93.3% [51øC/51%] 17.28 I/s 34.7(34.4)Sol/s 114(112.5)W clk=1544MHz mclk=4303MHz Sol/W=0.31100% [50øC/49%] 16.84 I/s 34.2(33.8)Sol/s 113(112.2)W clk=1455MHz mclk=4303MHz Sol/W=0.305>GTX 1070 Ti
6>GTX 1070 Ti
100% [60øC/60%] 18.27 I/s 36.0(36.3)Sol/s 102(105.1)W clk=1607MHz mclk=4303MHz Sol/W=0.35100% [57øC/56%] 18.31 I/s 36.4(36.3)Sol/s 108(106.0)W clk=1607MHz mclk=4303MHz Sol/W=0.347>GTX 1070 Ti
8>GTX 1060 6GB ` 100% [54øC/54%] 11.08 I/s 22.6(22.3)Sol/s 89( 92.4)W clk=1784MHz mclk=4252MHz Sol/W=0.24
CUDA ERROR[1970-01-02 03:28:32]: GPU[8]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
CUDA ERROR[1970-01-02 03:28:32]: GPU[6]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
GPU[8]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
GPU[0]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
CUDA ERROR[1970-01-02 03:28:32]: GPU[4]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
GPU[6]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
CUDA ERROR[1970-01-02 03:28:32]: GPU[5]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
CUDA ERROR[1970-01-02 03:28:32]: GPU[3]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
CUDA ERROR[1970-01-02 03:28:32]: GPU[2]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
GPU[4]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
GPU[5]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
GPU[3]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
CUDA ERROR[1970-01-02 03:28:32]: GPU[7]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
GPU[2]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
CUDA ERROR[1970-01-02 03:28:32]: GPU[1]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
GPU[7]: CUDA error ‘an illegal memory access was encountered’ in func ‘eq;~>[4~c2BBa,x81424~8a6:>00:cBB~5;>,,c;c~_5e7a,a]]solve’ line 1925
Hi brian997,
Thanks for the feedback and for reporting the errors.
The ramp up you refer may be an artifact of the mean. We use a 3 minute exponential moving average for “instant” calculations to remove noise, providing a value easy to read.
By examining the log file, it looks like some memory addresses are messed up due to the overclock settings. To some extent the miner can try to recover and eventually produce a bad share instead of crashing. We have just released a new version of miniZ, that will try harder to deal with your issues, but there are no guarantees 🙂
Keep in mind that different miners require different overclock settings for best efficiency. You can check our suggested overclock for best efficiency on our website https://miniz.ch/1927-2/. If you are using MSI Afterburner on Windows, remember to divide our suggested memory overclock settings by a factor of two.
Also be try the
--oc1/--oc2for best performance.Cheers,
miniZ
Hi Dev,
I set “–telemetry 0.0.0.0:42000” and it only works at the rig’s local computer.
What should I put to “–telemetry” if I want to monitor it from other computer in the same LAN ?
I had tried “–telemetry 192.168.1.201:42000”, but it doesn’t work out.
Thank you.
Hi MiningTaken,
At the moment miniZ always binds the telemetry to 0.0.0.0, so there is no need to add your ip address.
Something like –telemetry 42000 would work.
If you can connect locally but not from other computer on the same LAN it may be due firewall settings… did you check this?
Cheers
Again having trouble starting miner on 3 gb cards … 3n5 version,3n3 version all the same …
All startet after a restart of mining OS …
Hi Darko,
Thanks for reporting this.
It seems that your OS is using more memory on the GPUs.
Our 3GB implementation is a bit tight so if there are other applications running on the card (like vga adapter, for example) it may not fit.
We’ll see what we can do about it.
Cheers
I’m on mmpos, on hive it started ok
Must admitt that gminer starts with no problems …
Can mini-z just exit if api port is in use?
Mini-z just do nothing on linux platform.
Hi P,
On Linux, when the port is in use, miniZ gives a warning and moves to the next availabe port. Are you using Linux?
Could you clarify “just do nothing”? Do you mean that miniZ does not start mining?
Could you paste here your command line?
Could you run
./miniz -ciand paste here the output?Thanks.
Cheers
Is there any way to detect mining errors and auto restart miner? miniZ isn’t as stable as it should be
esolve’ line 5880;[Bc;b49c65 6 ‘the launch timed out and was terminated’ in func ‘eq_64B4a
Hi Max,
this error seems to be related to your OC settings.
If this doesn’t happen too often you can restart the miner by defining a loop.
Are you using Windows OS? You can create a bat file like this (do not forget to customize your wallet address, worker name, server and port number):
:loopminiZ.exe --url=YourWallet.worker@server:port --log --extra
timeout /t 5
goto loop
Cheers
I’ve tried this but it does not restart when this error happens.
OS settings are exactly the same on different computers, but I get error only on one of them.
Hi Max,
if the program cannot exit, the nvidia driver must have crashed.
We suggest that you try to adjust the OC settings for that computer, to check if still crashes. Different computers (different power supply, different motherboard…) may require some OC settings adjustment.
Let us know if adjusting the OCs helps.
Cheers
Every time I go to run the batch file it instantly closes. I added a pause in there and it shows it’s not recognizing the GPUs even though all my other miners do.
It says “0 CUDA devices found” but my other software recognizes them.
Hi Jay,
It looks like the NVIDIA driver that you are using is not compatible with the miniZ CUDA version you are using.
Did you try both miniZ Cuda 8 and miniZ Cuda 10?
Which NVIDIA driver version are you using? And which GPUs?
Cheers
So CUDA 8 is recognizing the GPUs but I instantly get an error that I have a GPU “out of memory”
Hi Jay,
Could you paste here your command line?
What are you mining and whith which GPUs?
Cheers
I am using 1060s and 1070s. I got miniz to work on my other miner cannot get it to work on this one though.
Hi Jay,
it is likely that one of your 1060 3GB (?) does not have enough memory available to mine. What are you mining? What OS are you using?
Could you paste here your command line?
Cheers
I’m having trouble mining Beam on Leaf pool, they want an email address to send notifications if the miner goes down. The format is “beam_address.worker/my@email.com” When I include that in the command line, it parses the server address incorrectly and includes “email.com” into the server address. Any way around this? I would like to be notified by the pool if the miner goes down.
Hi Jeff,
miniZ will not parse the url correctly because of the @ symbol. In this case you have to use the alternative syntax.
miniZ --server=ssl://beam-eu.leafpool.com:3333 --user=beam_address.worker/my@email.comIt should work fine like this, let us know how it goes.
Cheers
Awesome, that worked. thank you.
Great! 🙂
I have a GTX 780 with 3072 MB of ram and miniz wont load the GPU, it loads the other 1050ti’s just fine. I used the command line to load one GPU at a time.
Hi Matt,
we will need to know what is the error miniZ is writing to the console output (or log file). Probably this is a memory problem but we need to know.
Could you paste here the error?
Cheers
Number of CUDA devices found: 3
GPU[1] miniZ requires at least 2.78GB to run.
C:\Users\PapaPerks\Desktop\miniZ_v1.3n5_cuda10_win-x64>timeout /t 5
Waiting for 0 seconds, press a key to continue …
Hi Matt,
it seems you are trying to run 150,5 algorithm, on Windows 10. The 3GB GPUs cannot run 150,5 on Windows 10.
It is possible on Windows 7, but you have to run with
--mode=3option.Windows does not allow miniZ to use all GPU memory. On Linux this limitation does not exist and miniZ will run at full speed.
Beam will introduce a few changes in the algo, we will try to look at this in the future. Maybe we can shrink it a bit more so that it can fit also on Windows 10. (No guarantees though).
Cheers
Hey , u wrote that at algo 192_7 GPUs 1063 worked , but it seems didnt. It wrote that needed 2.7 gb video by Windows.
Sorry just saw the previous comment, so i understand i have the same problem… Thanks a lot.
Hi Jarek,
no problem. Indeed 3GB is a bit tight for this algorithm and mining 192,7 is not possible on Windows 10 since it does not allow miniZ to use all GPU memory.
We will check it out and see if it is worth making this work.
Cheers
The first time using miniZ on ARWthe worker does now show on the pool, it appears to be hashing, but doesn’t show in the worker list on icemining.ca. If I reconnect after that, its fine (GMiner and others work fine on the first connection)
./miniZ –par 192,7 –pers ZcashPoW –server eu.icemining.ca –port 3890 –user WALLET.MINR-11
Any ideas?
actually please disregard, its working now
Every time i try using miniz on hiveos (150,50,3) after about a minute of hashing I get a very high rate of invalids. I’ve tried using OC settings and stock settings with the same results.
I’m using the latest version of miniz
Hi Terence,
Does this happen also after that? Or is it only at start up?
Also, could you let us know what is your GPU? And to which pool are you connecting?
Are you using the beta v1.5q4?
Thanks!
Cheers
It happens all the time. I have all NVIDIA with mixture of GTX and RTX.
=== /hive/miners/miniz/1.5q-cuda100/miniz.conf =================================================
–par=150,5,3 –url=ssl://5177c2950849d5533563fcfcf46abc6bf373659aa0366a080fb105ecb8e91752.Rig1@beam.sunpool.top:3334
[ 0d 0h 2m05s] 328(328.4)Sol/s 1365(1342.9)W
0>GTX 1070
100% [68°C/49%] 19.08 I/s 38.2(38.2)Sol/s 150(148.1)W clk=1822MHz mclk=4050MHz Sol/W=0.2625.0% [71°C/48%]*18.99 I/s 36.3(36.3)Sol/s 145(141.9)W clk=1797MHz mclk=4050MHz Sol/W=0.261>GTX 1070
2>GTX 1070 Ti
87.5% [67°C/40%] 21.41 I/s 42.6(42.6)Sol/s 176(175.4)W clk=1746MHz mclk=4303MHz Sol/W=0.24100% [66°C/55%] 19.82 I/s 38.9(38.9)Sol/s 177(177.6)W clk=1885MHz mclk=5508MHz Sol/W=0.223>P104-100
4>GTX 1070
0.00% [64°C/44%] 18.95 I/s 37.2(37.2)Sol/s 149(148.0)W clk=1822MHz mclk=4050MHz Sol/W=0.25100% [68°C/65%] 19.78 I/s 39.6(39.6)Sol/s 163(161.1)W clk=1898MHz mclk=4050MHz Sol/W=0.255>GTX 1070
6>GTX 1080 Ti
100% [65°C/34%] 30.23 I/s 59.2(59.2)Sol/s 273(263.6)W clk=1949MHz mclk=5508MHz Sol/W=0.2266.7% [67°C/65%]*18.25 I/s 37.0(37.0)Sol/s 130(127.4)W clk=1733MHz mclk=4050MHz Sol/W=0.297>GTX 1070
[ 0d 0h 2m15s] 330(329.5)Sol/s 1347(1340.9)W
0>GTX 1070
100% [68°C/49%] 19.08 I/s 38.3(38.3)Sol/s 144(146.5)W clk=1822MHz mclk=4050MHz Sol/W=0.2625.0% [71°C/49%] 18.98 I/s 36.9(36.9)Sol/s 145(142.4)W clk=1809MHz mclk=4050MHz Sol/W=0.261>GTX 1070
2>GTX 1070 Ti
87.5% [67°C/40%] 21.40 I/s 42.7(42.7)Sol/s 178(176.0)W clk=1746MHz mclk=4303MHz Sol/W=0.24100% [66°C/56%] 19.82 I/s 38.2(38.2)Sol/s 180(178.1)W clk=1885MHz mclk=5508MHz Sol/W=0.213>P104-100
4>GTX 1070
0.00% [64°C/44%] 18.94 I/s 37.3(37.3)Sol/s 147(147.4)W clk=1822MHz mclk=4050MHz Sol/W=0.2566.7% [69°C/65%]*19.79 I/s 39.9(39.9)Sol/s 161(160.7)W clk=1898MHz mclk=4050MHz Sol/W=0.255>GTX 1070
6>GTX 1080 Ti
100% [65°C/34%] 30.23 I/s 59.8(59.8)Sol/s 268(263.4)W clk=1949MHz mclk=5508MHz Sol/W=0.2366.7% [67°C/65%] 18.26 I/s 37.8(37.8)Sol/s 125(126.3)W clk=1733MHz mclk=4050MHz Sol/W=0.307>GTX 1070
[ 0d 0h 2m25s] 330(330.1)Sol/s 1329(1337.1)W
0>GTX 1070
100% [69°C/50%] 19.07 I/s 38.7(38.7)Sol/s 142(145.6)W clk=1822MHz mclk=4050MHz Sol/W=0.2725.0% [71°C/49%] 18.98 I/s 36.7(36.7)Sol/s 144(142.5)W clk=1809MHz mclk=4050MHz Sol/W=0.261>GTX 1070
2>GTX 1070 Ti
87.5% [67°C/40%] 21.40 I/s 42.8(42.8)Sol/s 176(175.7)W clk=1746MHz mclk=4303MHz Sol/W=0.24100% [66°C/56%] 19.82 I/s 37.9(37.9)Sol/s 176(177.5)W clk=1885MHz mclk=5508MHz Sol/W=0.213>P104-100
4>GTX 1070
0.00% [64°C/44%] 18.94 I/s 37.4(37.4)Sol/s 149(148.0)W clk=1822MHz mclk=4050MHz Sol/W=0.2566.7% [69°C/65%] 19.79 I/s 39.6(39.6)Sol/s 164(161.7)W clk=1898MHz mclk=4050MHz Sol/W=0.255>GTX 1070
6>GTX 1080 Ti
100% [64°C/34%] 30.23 I/s 60.0(60.0)Sol/s 260(261.8)W clk=1949MHz mclk=5508MHz Sol/W=0.2366.7% [67°C/65%] 18.26 I/s 37.9(37.9)Sol/s 118(124.3)W clk=1733MHz mclk=4050MHz Sol/W=0.317>GTX 1070
[ 0d 0h 2m35s] 330(329.6)Sol/s 1325(1335.0)W
0>GTX 1070
100% [69°C/50%] 19.07 I/s 38.8(38.8)Sol/s 148(146.6)W clk=1835MHz mclk=4050MHz Sol/W=0.2625.0% [71°C/50%] 18.97 I/s 36.9(36.9)Sol/s 144(142.7)W clk=1809MHz mclk=4050MHz Sol/W=0.261>GTX 1070
2>GTX 1070 Ti
87.5% [67°C/41%] 21.40 I/s 42.7(42.7)Sol/s 170(174.2)W clk=1759MHz mclk=4303MHz Sol/W=0.2583.3% [67°C/56%]*19.82 I/s 38.2(38.2)Sol/s 181(178.5)W clk=1898MHz mclk=5508MHz Sol/W=0.213>P104-100
4>GTX 1070
0.00% [65°C/44%] 18.94 I/s 37.0(37.0)Sol/s 146(147.3)W clk=1822MHz mclk=4050MHz Sol/W=0.2566.7% [69°C/65%] 19.79 I/s 39.6(39.6)Sol/s 160(161.0)W clk=1898MHz mclk=4050MHz Sol/W=0.255>GTX 1070
6>GTX 1080 Ti
100% [64°C/34%] 30.23 I/s 59.8(59.8)Sol/s 252(259.6)W clk=1974MHz mclk=5508MHz Sol/W=0.2366.7% [67°C/65%] 18.26 I/s 37.7(37.7)Sol/s 124(125.0)W clk=1733MHz mclk=4050MHz Sol/W=0.307>GTX 1070
Hi Terence,
thanks a lot for the information.
We think to have found the cause of this.
We are doing some further checking at the moment and will release a fix soon.
Cheers
Got the update and works good now.
Thanks
Hi, on my rigs (RTX 2070,RTX2080S) miniz show information about shares, speed and etc so slowly,(on beamv2)
I updated/back drivers nvidia 430-436 versions. Back to default clocks on cards, but it doesn’t help.
I mine on nicehash, with gminer for example everything working fine.
Used miniz 1.5q2-q6. Could you check?
Also, I see that CPU load is very high 99-100%
Hi Alex,
thank you for letting us know.
We’ll look into this. It may be slow because of CPU usage. Which miniZ version are you using?
Does this happen only with beamv2?
Cheers
Using last versions 1.5q2-q6. Right, Problems with miniz on BeamV2 algo.
I tested Zhash 144,5 and it working fine.
Hi Alex,
sorry for taking a bit longer than usual to respond.
Thank you for the information. We would like to share some information that another miner shared with us and might help the cpu high usage, in the case you are using the latest nvidia driver. When he went back to 430.86 it solved the cpu issue.
Hope this helps.
Cheers
I back old driver and now all working fine!
thanks for support! wish u best
Hi Alex,
Good that it worked for you.
Thanks for the feedback!
Cheers
Hi, I’m running a little bit of an unusual config. 24GB system memory, windows 10 running from USB key, no swap file.
You seem to be attempting to malloc 2GB RAM per GPU, which has a hidden requirement in windows that there be 2x the asked-for memory available. So your ~12GB actual usage balloons into slightly more than the amount of RAM I have, which means I can’t start.
I confirmed all this by limiting to 5 CUDA devices (works), and adding physical RAM (works).
Do you have a workaround? Either to make windows not do this, or to use slightly less RAM?
************ ←[01;31mminiZ←[22;37m v1.5q6 ************
Algo: EQ[150,5]
Pool#0: user[omitted]
server[beamv2.usa.nicehash.com] port[3378] ssl[no] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Temp. limit: [90°C]
miniZ[1:1:00:6787]: Selecting GPU#3[3] GeForce GTX 1070
miniZ[1:1:00:6787]: Selecting GPU#5[5] GeForce GTX 1070
miniZ[1:1:00:6787]: Selecting GPU#1[1] GeForce GTX 1070
miniZ[1:1:00:6787]: Selecting GPU#2[2] GeForce GTX 1070
miniZ[1:1:00:6787]: Selecting GPU#4[4] GeForce GTX 1070
miniZ[1:1:00:6787]: Selecting GPU#0[0] GeForce GTX 1070
[FATAL ] CUDA: failed to alloc 1973 MB for main data
[INFO ] Disconnecting from beamv2.usa.nicehash.com
[INFO ]beamv2.usa.nicehash.com Stopping miner
Hi john7797,
you have 6 1070 GPUs, 8GB each, for this you will need more memory that what you have at the moment. Depending on the algorithm you are using the miner needs to allocate 1.7-4.2 GB memory on each GPU, there is not much we can do about this. Additionally, Windows allocates a bit more for its functioning…we cannot do anything about this either. For windows you’ll need to increase your virtual memory, you have a tight fit there.
We can only suggest you to try to use Linux OS, since it is less demanding on memory. It will solve your problem.
We noticed that you want to mine Beam in Nicehash. It seems that you specified the algorithm as 150,5. However, Beam made a few changes to its algorithm, if you specify the algorithm you need to write
--par=150,5,3. If you do not specify the algorithm it should work too. You can always confirm this with miniZ, it shows the information in the console/logfile output. For Beam you should read: Algo: EQ[150,5,3].Cheers
It looks like miniZ_gui.exe (version 1.5r, Windows x64 Cuda 10) has Trojan:Win32/Tiggre!plock
How can this happen?
Hi Carl Zhou,
thanks for your message.
It is best to always confirm if the file SHA256 is the one indicated on the website. If the SHA256 is correct then miniZ_gui.exe should be fine. This is is a false positive, and only part of the engines detect it.
This kind of problem is annoying, but not new. In our case this is due to the function frombase64string that we use to encode our .ico images appearing on GUI. Also from the fact that there is someone/rule (always the same person/company) that keeps marking miniZ_gui as suspicious, as it can be seen in virustotal.com.
We are working on an alternative to that function so we will figure out a way to solve this soon. 🙂
To exclude a file from Defender (if this is your case), you need to open the Windows security window.
Then go to “Virus and threat protection settings” under the “Virus & threat protection” tab. And in “Exclusions” you can add or remove exclusions.
We hope this information is helpful to you.
Thanks for using miniZ.
Cheers
Hey guys, huge fan of your miner!
I have an issue mining the coin $EXCC. The coin is already a big deal with over $1,000,000 in revenue / day, and looks to be getting bigger. Problem is, apparently according to their team, since the coins is hybrid PoW and PoS, it can’t just be mined by any regular Equihash 144,5 miners, but needs to be coded specially – so supposedly LOL miner is the only one that will work with this coin.
Is there any way you could make miniZ mine this coin? Your miner is the FASTEST and hands down the BEST equihash miner there is….
Here’s a link to their website – https://excc.co
Thanks!
Hi Dovi,
thanks for reaching us and for the suggestion.
At the moment we are working on improvements for the current supported algorithms.
We had a look at it before and end up putting it aside. It was not obvious what we need to do to support EXCC (stratum, header size…), we did not find this information.
We’ll try again soon and see what we can do about it. 🙂
Cheers
hi guys! thank you for your work. two questions i’ve got:
1. when i access telemetry page, no colored gauge meters appears down the screen
2. not the subject of this teme, but if i’m here, why not. could you please flush STDOUT each time you print the log string on console, something like –boff as EWBF miner does: “–boff disable output buffering”
**i run latest miniZ_v1.5r_cuda10_linux-x64 on ubuntu server 16.04, watching telemetry with Google Chrome 78.0.3904.97 on ubuntu 16.04 workstation
Thank you so much, wish you luck and stay the best!!
Hi fvgenn,
thank you for your message, and for your preference!
On the next version miniZ will flush STDOUT every line.
Regarding telemetry, it would be great if you can use another browser. We tested it on falkon and firefox, and it works.
We will see if we can fix this in the future. Sorry but this has low priority at the moment 🙂
Happy mining!
Cheers
Hello.
I am running miniZ 1.5s with the Nicehash Miner v1.9.2.17
miniZ is the only miner I am running, there is no profit/algo switching. The algo is EQ 150,5,3
The miner keeps restarting (or crashing and re-opening) randomly. Sometimes it does this after just a few minutes (~3-5mins) and sometimes after ~20-30 minutes.
I can’t find any error messages/logs on windows Event viewer related to this problem.
All software and drivers are up to date.
Windows 10 Pro
i5-4670, 16gigs DDR3 mem
GTX 1080 on nvidia 441.08 drivers.
Any idea what is causing this or how to fix this?
Hi Sleobo,
Are you applying some OC to your GPUs?
From what you describe it looks that this might be related to OC settings, seems that is causing some instability.
If this is the case try to adjust them a bit and check if it gets better.
Let us know how it goes. 🙂
Thanks for using miniZ!
Cheers
I do run my cards OC’ed. But I’ve also tried this with stock clocks and even underclocked. Doesn’t matter, the behavior continues. Temps are ok (around 60C). I have tried PL between 60 and 100, no change.
I did download the 1.5s as a stand-alone and tried it. It doesn’t crash or restart so the problem must be with the Nicehash miner and not with miniZ.
Sorry to have bothered with this as the problem is somewhere else than miniZ, but I hope this small tidbit might help anyone else having similar problem.
Hi Sleobo,
It is no bother at all, as you wrote the information can be useful for someone else. 🙂
Also, it is definitely good to know that it is not a miniZ problem. Maybe a bug with miniZ integration into Nicehash miner.
Thanks a lot for the feedback and happy mining!
Cheers
Hi,
getting “segmentation fault (core dumped)” randomly, when starting MiniZ v1.5s on Ubuntu 19. When this occurs, I tried launching with one GPU without success. Only Reboot seems to fix this issue. I tried launching GMiner which works normally on such occurrence (never had this issue with any other miner). RIG has 9 GPUs, 1070s 1080s and 1070TIs. I even created 50GB SWAP, and tried different driver versions. What could be the issue?
Thanks
Hi The MIner,
could you paste here the program output just before this crash occurs?
Which algo are you mining?
Thanks!
Cheers
hi
I use miniz to mine beam and the program use 100% of cpu although should just use gpu.
os: win10 x64
gpu:nvidia 1070
driver:441.66
Hi Bahram,
thank you for your message.
Does this happen everytime you start the miner?
Does this happen when mining other algorithms?
Could you paste here the output of
miniZ.exe -ci?Cheers
Same thing happened to me when I updated drivers.
Roll back your driver to 441.41 until it’s patched.
Hi CryptoSifu,
thanks a lot for the information!
Cheers
MiniZ 1.5s keeps restarting on me.
Running x1 1070. Log doesn’t report any error. It just stops and restarts.
Happening about once every 10-15 mins.
I have —log enabled in command line.
Any ideas?
Hi Crypto Sifu,
could you paste here the program output a little bit before the restart occurs?
Which algo are you mining?
This might not be related but just in case: do you you OC your GPUs? If so does this also happens when no OCs are applied?
Thanks!
Cheers