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]
[email protected]:~/miners/bins/miniZ_miner_v1.0b$ ./miniZ –url [email protected]: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
[email protected]:~/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 [email protected]:8866 --cuda-devices 0then
./miniZ --url [email protected]: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 [email protected]: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 [email protected]: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 [email protected]: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 [email protected]:8866 –log –extra
(edited) Hi hoomanleo,
Thanks for providing your command line.
We have just tested your command line:
miniZ.exe --url [email protected]: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 [email protected]: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 [email protected]:8866 --url [email protected]: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 [email protected]: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/[email protected]” 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/[email protected]It 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://5177c2[email protected]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
I have setup a AION pool (private) but miniZ keeps crashing when connecting to the pool using this command: miniz.exe –user [wallet_addr].worker –server 192.168.x.x –port 3333 –log –extra –pers AION0PoW
any help?
Hi theislander,
try adding
--par=210,9to your command line.Let us know if it helps.
Thanks for contacting us!
Cheers
That fixed the issue. Thanks 🙂
+—————————————————————-+
| GMiner v1.96 |
+—————————————————————-+
Algorithm: Equihash 144,5 “auto”
DevFee: 2%
Stratum server:
host: zhash.eu.nicehash.com:3369
user: 39PLRiKd3ANjcY8azwq8KmJGcqcsCavyiF$0-DKh15PFHhVWSzjnCvP0f6Q
password: x
Power calculator: on
Color output: on
Watchdog: off
API: http://127.0.0.1:4000
Log to file: off
Selected devices: GPU0
Intensity: 100
Temperature limits: 90C
——————————————————————
16:35:13 GPU0 MSI GeForce GTX 1660 Ti 6GB: Selected Normal Solver
16:35:13 Connect to zhash.eu.nicehash.com:3369 Failed: Access is denied
I First time using this
Hi Audrius,
you can mine 144,5 algorithm using miniZ by downloading the miner from our Download page.
If you need further help with setting up and using miniZ you can check “Windows mining with miniZ step-by-step“.
Also, in the FAQ and Usage pages you can find additional information regarding miniZ usage.
However, the problem you are facing seems to be related to your user/wallet, it does not look like a correct wallet address.
We hope this helps and feel free to let us know if you need further help with miniZ miner. 🙂 … not with gminer 🙁
Cheers
Hola buenas noches, quiero aprender a configurar para minar Grimm ya descargue MiniZ GUI Launcher v1.5 no se como configurarlo
Hola Cristian Chasoy,
puedes ver el tutorial aquí. (en ingles)
Es un ejemplo para BTG pero puede adaptarlo para Grimm.
For example to mine Grimm/minar Grimm:
Si quieres minar en Ravepool – https://grimm.ravepool.com/
Server: grimm-us.ravepool.com Port: 3333
Si quieres minar en Sunpool – https://grimm.sunpool.top/
Server: grimm.sunpool.top Port: 3333 (or 3334)
Para más información, visite la página de instrucciones y FAQs (en ingles).
Si hace falta puede contactarnos.
Saludos
Cheers
Hi, I have used MiniZ for about two weeks now, successfully, with no problems. Today, it cut off and now I am unable to even run my bat file (even though yesterday it worked fine). I have not changed or tinkered with anything, except restarting my computer a few times to see if it helps (it didn’t). any suggestions?
Thanks
Hi Crypto,
Thank you for contacting us, sorry for taking a bit longer to reply.
Also sorry about this.
Do you get to see the miniZ header ************ miniZ v1.5t3 ************ ?
Could you paste here your bat file? It looks that maybe something got broken with the file…
Thanks!
Cheers
Windows defender flagged miniz.exe as a virus. Need to go in defender and remove from quarantine and allow for the restore of the miniz.exe.. prob should do the same for the minizgui if you use it..
Windows defender flagged miniz.exe as a virus. Need to go in defender and remove from quarantine and allow for the restore of the miniz.exe.. prob should do the same for the minizgui if you use it..
Hi Bluebird, and Crypto,
It is true that Windows Defender sometimes wrongly flags some software, in this case you need to allow it manually.
It is best to always confirm if the file SHA256 is the one indicated on the website. If the SHA256 is correct then miniZ should be fine. However, we will investigate this further.
Thank you for your contribute to the forum.
Cheers
Hello-
Why is there high latency using Miniz in hiveos when submitting shares, using 192,7.. gminer has latency of 53ms, same website, same config miniz has a latency of 500-600ms.. resulting in stale shares. Miniz in the win10 environment (5 rigs) is 53ms to same website and config. All 4 rigs with hiveos report 500-600ms..
Hi Bluebird,
You may be using the latest miniZ version? We are taking care of this.
Do you also experience this issue with miniz v1.5t2?
Thank you for your feedback.
Cheers
hello, can we use miniZ with a personal block header and nonce, such as block header is 32 byte and nonce is 32 byte?
Hi yellow,
At the moment miniZ does not support that feature. But, it is something to think about in the future.
For which algo were you thinking of adding this? We do not see (yet) how we could implement this in the miner, command-line-wise. Do you have any ideas you care to share?
Thank you for the suggestion!
Cheers
For equihash. there are a lot of public chains choose equihash as pow algorithm, but a lot of them can’t change the input of equihash （they keep input same with zcash witch 140 bytes header with nonce）because a lot of miners only support this input，i found out that miniz is the fatest miner of equihash, so i expect miniz can support general input of equihash， it will be a great help for public chains to define their own block header
Hi yellow,
Thank you for your suggestions.
We have to think about this more carefully (we’ve been a bit busy with Beam’s fork).
It seems interesting 🙂 and we will see if this is doable in the near future.
Cheers
Running miniZ on my old pc just fine. I built a new pc running Windows 10, installed the newest nvidia drivers for my cards and whenever I try to start miniZ it is giving me the “The application was unable to start correctly” accompanied by an error code (0xc000007b). I have tried everything I can find on that error. installed .net framework, update windows, update drivers and still can’t get it to work. Any ideas?
Hi Magoo,
Did you install Windows 64 bits? miniZ requires the 64bit version.
Have you tried other miners? Do they work?
Cheers
Hello,
I do have windows 64bit pro version installed. I’m using gminer just fine but would like to use miniZ. Is there anything that could of not been installed on this fresh install of windows that might be causing miniZ to not run?
Hi Magoo,
“and whenever I try to start miniZ it is giving me the “The application was unable to start correctly” accompanied by an error code (0xc000007b). ”
The only error you get is what you mentioned? miniZ doesn’t print/log any information at all?
Maybe let’s start by asking you about the command line. Could you paste it here?
Together we must be able to find the issue 🙂
Cheers
Good news I got it to work. I installed
Redistributable Packages for Visual Studio 2013 from Microsoft and
Redistributable Packages for Visual Studio 2015 – 2019 from Microsoft
Plus I increased my windows virtual memory initial to match the 6 cards i’m using. Not sure which one of those items fixed it as I did them all at the same time but I’m happy now lol.
Hi Magoo,
Great that you managed to get it to work!
Thank you for the feedback. This information might be useful for others too. 🙂
Cheers
There is a bug in the new v1.6v3 when mining on Nicehash. The miner seems to alter the selected algorithm from “–par=144,5s” to “150,5,3” causing 100% rejected shares on Nicehash:
This is the commandline:
miniZ.exe –telemetry 33000 -cd 0 1 4 –server beamv3.eu.nicehash.com –port 3387 –user 3M73gP6x55C7nws3ie7UwCHpy5tDDVLwHN.GTX1660TIs –pass x –pers Beam-PoW –gpu-line –extra –latency –nocolor –par=144,5s
.. for some rigs it switches to “150,5,3” at the very beginning.
Hi rainbowminer,
We tested your command line and it is working well.
We have an idea about what can be happening: can you confirm that you wrote the ‘s’ in
--par=144,5s? It seems that you may have copied/wrote without the ‘s’.However, if we use
--par=144,5instead of--par=144,5swe have the same output as you have.You can also use
--par=beam3that may be more user friendly.Let us know if this helped.
Thank you for the feedback. We’ll try to make miniZ ‘smarter’ in the next version to help avoid this issues. 🙂
Cheers
ps: We saw your message @ bitcointalk forum, and replied there too.
miniZ v1.6v3:
“Algo equihash125 has closed with Exit Code: -1073741819 Attempting restart in 5 seconds…” error, after running several minutes with “–ocX” option.
Command line: MiniZ.exe –ocX –cleanjobs –par=125_4 –smart-pers –telemetry=42000 –latency –extra –server [Server] –port [Port] –user [User] –pass [Password]
FYI.: With “–oc2”, it runs smoothly.
Hi MiningTaken,
In stock settings usually
--ocXdoes ok. However, when we modify core/memory clocks it can happen that one (or more) of the kernels become unstable. Depends a bit on the settings. Sometimes it happens on one specific kernel (mode). Do you see this? Does it always exits on the same mode?If it persists try to adjust your OCs. Or, if you observe that it seems specific to one mode, then you can try and do it manually.
You can test a specific mode using
--mode. Ex.--mode 0, runs mode 0 on all GPUs.--oc2runs a specific mode (per GPU). It is good to know that that one is stable.In any case, we will have a closer look. Which GPU(s) are you using?
We are trying to improve ocX versatility.
Thanks for the feedback!
Cheers
I’m using v1.6v3 – I run Equihash 125_4. I’ve used previous versions and I’m fairly familiar with your miner. It’s the best I’ve used. However, this version –ocx causes the miner to close whereas the last version did not. I run 2x 1080ti and 1x 1080 with current drivers. I don’t get any codes and the system remains stable, the miner just stops and closes. Once I remove –ocx the miner runs like a champ.
I’d be happy to provide any further information if it’s needed. Just let me know specifics of what else I can provide.
Keep up the great work!
Hi AZ Ronin,
Thank you for your message.
We did not manage to reproduce this behavior.
It is odd that you do not get any error. We’ll investigate.
Could you paste here the start of the log (with the GPUs information)? Could you also paste the log when the miner closes?
We’re making some structural modifications so we expect this to be resolved in the next version.
Cheers
Hello, I’m using miniZ v.1.6v3_cuda10 with RTX 2070 super, Windows10. Mining Beam Coins (BeamHash III).
Why the software only boost the card until [email protected]? Getting 23.5 Sol/s. I know the card can go up to [email protected] on gaming, no manual OC.
Also if I increase the memory clock +650MHz, nothing changes, same result 23.5 Sol/s.
Temps 45C / 113F.
Nvidia drivers v.451.48.
Thank You,
Greetings.
Hi Paul,
miniZ does nothing to the GPUs clocks. It is the driver that manages core clock even when you make manual adjustments to the oc settings.
Possibly performance is limited by core clock, so an increase in memory clock may not help.
Be aware that GPU utilization during gaming is quite different from mining.
At the moment, the only thing we see that we could help is by working for better GPU optimization, by making miniZ better.
So, in the next version you may be able to see better results. 🙂
Cheers
Hi,
It looks like some times a [fee server] share is erroneously reported as a regular share (even when the –all-shares option is not selected).
Specifically it reports the last share found on the last connection to the [fee server] as belonging to the pool server when it is not, it is really a share found while connected to the fee server and not the pool.
This is very noticiable when solo mining.
Please fix on next version.
Many thanks!
Hi Miner,
You are right, this may happen ocasionally. The default output is 10 sec and the stars appear when a switch to the fee-pool, or user-pool, occur in those 10 sec.
We understand your issue, specially in solo mining.
We believe that we managed to fix this. It should be OK in the next version.
Thanks a lot for the feedback!
Cheers
Hi
Can you tell me what the
0.00% refers to - noting that it starts at 100% then shortly goes to0.00%. I don’t know if this is indicating a problem, nor what it could be.Thanks,
************ miniZ v1.6v3 ************
Number of CUDA[10.0] devices found: 1
Algo: EQ[144,5]
Pool#0: user[natfu.natfuzcash1]
server[cn.zec.slushpool.com] port[4444] ssl[no] pers[auto]
Telemetry: [http://localhost:20000]
Optimisation: ocX[0]
Temp. limit: [90°C]
miniZ[06:0:00:5131]: Selecting GPU#0[0] GeForce RTX 2060
[ 0d 0h 0m10s] 0>RTX 2060
100% [59°C/ 0%] 23.63 I/s 48.4(48.4)Sol/s 80( 79.9)W clk=1350MHz mclk=6801MHz Sol/W=0.61- 447ms100% [60°C/ 0%] 24.48 I/s 50.3(50.3)Sol/s 79( 78.9)W clk=1350MHz mclk=6801MHz Sol/W=0.64- 447ms[ 0d 0h 0m20s] 0>RTX 2060
[TRACE ] GPU[0]: Optimisation temperature not stable *T=59+-1.3C*
[ 0d 0h 0m30s] 0>RTX 2060
100% [61°C/ 0%] 24.65 I/s 50.6(50.6)Sol/s 78( 78.4)W clk=1305MHz mclk=6801MHz Sol/W=0.65- 447ms100% [62°C/ 0%] 24.65 I/s 48.2(48.2)Sol/s 78( 78.5)W clk=1335MHz mclk=6801MHz Sol/W=0.61- 447ms[ 0d 0h 0m40s] 0>RTX 2060
[ 0d 0h 0m50s] 0>RTX 2060
100% [62°C/ 0%] 24.64 I/s 47.3(47.3)Sol/s 79( 78.6)W clk=1305MHz mclk=6801MHz Sol/W=0.60- 447ms100% [61°C/ 0%] 24.65 I/s 47.7(47.7)Sol/s 79( 78.6)W clk=1305MHz mclk=6801MHz Sol/W=0.61- 447ms[TRACE ] GPU[0]: Optimisation temperature not stable *T=61+-1.4C*
[ 0d 0h 1m00s] 0>RTX 2060
[ 0d 0h 1m10s] 0>RTX 2060
100% [60°C/ 0%] 24.65 I/s 48.9(48.9)Sol/s 78( 78.2)W clk=1305MHz mclk=6801MHz Sol/W=0.62- 447ms100% [60°C/ 0%] 24.66 I/s 48.9(48.9)Sol/s 78( 78.4)W clk=1305MHz mclk=6801MHz Sol/W=0.62- 447ms[ 0d 0h 1m20s] 0>RTX 2060
[ 0d 0h 1m30s] 0>RTX 2060
0.00% [59°C/ 0%]*24.68 I/s 48.5(48.5)Sol/s 78( 78.3)W clk=1335MHz mclk=6801MHz Sol/W=0.62- 445ms0.00% [59°C/ 0%]*24.69 I/s 49.3(49.3)Sol/s 79( 78.4)W clk=1305MHz mclk=6801MHz Sol/W=0.63- 448ms[TRACE ] GPU[0]: Optimisation temperature not stable *T=60+-1.3C*
[ 0d 0h 1m40s] 0>RTX 2060
[ 0d 0h 1m50s] 0>RTX 2060 `0.00% [59°C/ 0%] 24.71 I/s 48.9(48.9)Sol/s 78( 78.3)W clk=1305MHz mclk=6801MHz Sol/W=0.62- 448ms
Hi Nathan,
Sadly miniZ does not support ZEC algorithm, usually referred as Equihash (without reference to parameters). ZEC usually is mined with asic miner as GPUs are not efficient in this case. This is why miniZ is indicating that you are not submitting good shares to the pool (hence the 0.00%).
miniZ is a Equihash Cuda miner that you can use with your NVIDIA GPUs, and supports most Equihash algorithm variants:
* 144,5 (Zhash)
* 125,4 (ZelHash)
* 150,5,3 (BeamHash II)
* 144,5s (BeamHash III)
* 150,5
* 192,7 (Equihash Heavy)
* 96,5
* 210,9
For example, Equihash 144,5 is appropriate to mine Bitcoin Gold (BTG), BitcoinZ (BTCZ), SnowGem (XSG), and a few other coins.
Hope this helps.
In any case, thank you for your preference. 🙂
Cheers
Thanks so much for the response. All the best!
0>GTX 970
100% [67鳦/58%] 6.27 I/s 12.3(12.3)Sol/s 168(170.2)W clk=1442MHz mclk=3004MHz Sol/W=0.07100% [72鳦/54%] 3.35 I/s 6.7( 6.8)Sol/s 75( 75.0)W clk=1620MHz mclk=3504MHz Sol/W=0.091>GTX 1050 Ti
[FATAL ] GPU[0]: Driver error 999 ‘unknown error’ in line 116
[INFO ] Disconnecting from grimm-us.ravepool.com
[INFO ] Exited GPU#1
[FATAL ] Invalid command line switch
-di!what’s that mean?
GTX 970&1050TI
and my computer reboot …howa can i fix that
Hi jim,
We suspect that this is OC related. It looks like that the driver crashed.
If you applying OC to your GPUs you can try to adjust them a little to see if it solves the issue.
You may like to know that we are finalising a new version with improvements for equihash 150,5 algorithm. It should be out in about 24h. 🙂
Cheers
Hi,
I am running miniZ.exe on Windows 10.
.\miniZ.exe –url=ssl://****@beam-asia.leafpool.com:3333 –par=beam3 –log –extra –latency
************ miniZ v1.6w ************
Number of CUDA[10.0] devices found: 1
Cannot read health status! (is libnvidia-ml.so installed?): No such file or directory
Algo: EQ[beam3]
Pool#0: user[*****]
server[beam-asia.leafpool.com] port[3333] ssl[yes] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Logging:: file[miniZ.log] period[10] delay[0]
Temp. limit: [90°C]
miniZ[06:0:00:6743]: Selecting GPU#0[0] GeForce RTX 2070
[ 0d 0h 0m04s] S: 0/0 0>RTX 2070
100% [0°C/ 0%] 12.70 I/s 25.3(25.3)Sol/s 0( 0.0)W clk=1650MHz mclk=7001MHz Sol/W=inf [beam-asia.leafpool.com]- 372ms (100.0%) (0.0%)100% [0°C/ 0%]*12.90 I/s 25.7(25.7)Sol/s 0( 0.0)W clk=1650MHz mclk=7001MHz Sol/W=inf [beam-asia.leafpool.com]- 373ms (100.0%) (0.0%)[ 0d 0h 0m10s] S: 1/0 0>RTX 2070
————————-
I am getting the warning “Cannot read health status! (is libnvidia-ml.so installed?): No such file or directory”. Still the application able to run, but it is not displaying the temperature.
Below is the result for running nvidia-smi:
Fri Sep 25 21:12:27 2020
+—————————————————————————–+
| NVIDIA-SMI 456.38 Driver Version: 456.38 CUDA Version: 11.1 |
|——————————-+———————-+———————-+
| 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 RTX 2070 WDDM | 00000000:01:00.0 Off | N/A |
| 59% 68C P2 170W / 175W | 4135MiB / 8192MiB | 100% Default |
+——————————-+———————-+———————-+
+—————————————————————————–+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| 0 N/A N/A 7336 C C:\Beam\miniZ\miniZ.exe N/A |
+—————————————————————————–+
Any idea will be helpful.
Hi Saba,
It looks like you are missing the nvidia library nvml.dll.
It could be misplaced, or during driver instalation the antivirus got rid of it.
You’ll need to find/download the file and add it to C:\Program Files\NVIDIA Corporation\NVSMI\, or to miniZ folder (should work too).
You can try to reinstall the driver, possibly this would be enough to solve the issue.
Let us know if this helped.
Cheers
Hi guys, I am getting “Cannot load deviceZ code.” on my RTX 3090. Works fine with RTX 2070s on the same rig though.
Tried v1.6w and v1.6w2
Below is the complete log:
************ miniZ v1.6w ************
Number of CUDA[10.0] devices found: 1
Algo: EQ[144,5s]
Pool#0: user[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.L1]
server[beam-us.leafpool.com] port[3333] ssl[yes] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Temp. limit: [90°C]
miniZ[06:0:00:23336]: Selecting GPU#0[0] GeForce RTX 3090
[FATAL ] Cannot load deviceZ code.
[INFO ] Disconnecting from beam-us.leafpool.com
[INFO ]beam-us.leafpool.com Stopping miner
Hi Achillian,
For the Ampere architectures (RTX 30 series) you need to use Cuda 11.1 versions, and have installed:
* NVIDIA 455.23 driver or later, for version compiled with cuda 11.1 (Linux).
* NVIDIA 456.38 driver or later, for version compiled with cuda 11.1 (Windows).
Just in case: it seems that in some cases miniZ is not loading the best kernel (for Beam mining) so hashrate is lower than expected. If this happens try using
--mode=6. We will try to further optimise Beam for your GPU.Let us know this helped to solve the issue.
Thank you for using miniZ!
Cheers
Hi i keep getting a message cannot load device code on a 680gtx. just wondering if you may be able to help.
Hi Shannon Haslam,
miniZ is not compliled for _sm3X architectures (Kepler), so you will not be able to use it with your GTX680.
To include architectures below _sm35 we would need to make major modifications to the program, so that it would be able to run on those GPUs.
We believe that your GPU is sm30, could you please confirm this by running miniZ with -ci program?:
miniZ.exe -ci
Could you also tell us which algo where you trying to run?
Thank you for your feedback!
Cheers
I ran the script as you suggested and it is sm30.
Simple answer its not supported anymore due to its age. Fair enough. It suck when you have old hardware around that has no use anymore.
My wattage isn’t showing on the command prompt.
Its a GTX 980 and it was fine before but when i went to another miner and came back to this one it didn’t show up anymore.
Hi Cristian,
We suspect that it may be related to the driver, and a reboot may solve it.
Could you try this and let us know if it helped?
Thank you for using miniZ.
Cheers
Hello
When working with the –cleanjobs parameter, after launching and several shares in the working pool, it switches to the fee.server server for more than 10 minutes (after that it is deleted). Without this parameter, the transition to fee.server within 1% and return to the working pool.
thank you
Hi Andy,
Sorry for taking longer than ususal to reply.
--cleanjobsshould be used with care, not all pools support it. In fact most pools do not support this option.After the first job there are no more clean jobs. This can cause high number of stale shares, and pool may disconnect after a while.
We are not aware of any beam pool that support
--cleanjobs, so it is better not use this option 🙂Cheers
Nicehash will not install the plugin to allow me to use MiniZ. Been trying and trying to no avail. Any ideas?
Windows 10 64 bit
i7 9700K
EVGA 3080 FTW3 Ultra
Much thanks!
Hi Sean Morrison,
Thank you for your message.
We contacted Nicehash to try to understand what is going on.
We’ll let you know as soon as we get a response.
Cheers
Thank you!
Any ideas? I’ve down a full uninstall and reinstall. All other plugins install just fine, but this one continues to attempt to install, then goes back to asking me to install.
Hi Seam Morrison,
We made a few modifications to our website security settings that may resolve the issue.
Could you try again, and let us know if it is OK now?
Thanks!
Cheers
No luck! I did a full install and reinstall to verify.
Same, still not working :c
Hi Felipe, Sean Morrison,
We are sorry for this issue.
We contacted Nicehash and we’re working on a way to fix this asap.
Thank you.
Cheers
I am running CUDA 10.2 and CUDA 11 and get the same error running miniz 1.6x with Awesome Miner for BEAM using Windows 10 64-bit on a system with 4 total TESLA V100 16gb cards. I have tried using all GPUs and also stopping all other miners and using a single GPU (ID: 0) and have the same result.
CUDA Driver API error = 0701 from
This takes about 90 – 120 seconds to show up. I have re-installed CUDA 10.2 and will try to install CUDA 10 next in place of 10.2 to see what happens.
Hi SenatorB,
Thank you for the feedback.
Could you try running mniniZ with other kernels? You can use
--mode=n, n={6,11,12,13}.We’ll try to have a closer look at this issue. Also, maybe we’ll be able to optimise miniZ for these GPUs.
Cheers
I use nicehash.com gt1030. my problem is, miniz plugin does not install anymore after around December 2020
Hi Peter Chauke,
Thank you for the feedback.
We made a few modifications to our website security settings that may resolve the issue.
Could you try again, and let us know if it is OK now?
Cheers
Hi, i have a problem since a few days.
If i try to start miniZ i get following error:
[ERROR ] GPU[0] miniZ requires at least 1903MB to run, but only has 1669MB.
There is no other application started.
Any Ideas?
Hi Lucas,
Thanks for the feedback.
It looks that there is something using the GPU. Could it be that you updated the nvidia driver?
Which algo are you trying to mine? And which operating system?
Could you paste here the miniZ log output, the start of the log?
Cheers
Hi miniZ,
thanks for the fast response.
There should nothing be using the GPU. I tried restarting my pc and immediately get the Error.
I am trying to mine Beam3 on Windows 10.
And here is hopefully the right log:
************ miniZ v1.6x ************
Algo: EQ[beam3]
Pool#0: user[censored]
server[beamv3.eu.nicehash.com] port[3387] ssl[no] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Logging:: file[miniZ.log] period[10] delay[0]
Temp. limit: [90øC]
[ERROR ] GPU[0] miniZ requires at least 1903MB to run, but only has 1669MB.
[WARNING] miniZ[-1:0:00:1669]: Not selecting GPU#0[0] GeForce GTX 960
[ 0d 0h 0m06s]
[ 0d 0h 0m10s]
[ 0d 0h 0m20s]
[ 0d 0h 0m30s]
[ 0d 0h 0m40s]
[FATAL ] No devices selected, exiting…
[INFO ] Disconnecting from beamv3.eu.nicehash.com
Best Regards
Lucas
I hope its alright to post the link of the picture
https://i.imgur.com/k0wVFbf.png
VRam is completely empty and I still get the error.
Hi Lucas,
Thank you for the information.
Unfortunately the 2GB GPUs cannot mine beam3 in Windows 10.
We managed to shrink the kernel enough to run on Windows 7 and Linux. Windows 10 only allows using ~82% of the GPU memory.
You should be able to run 144,5 210,9 and 96,5.
(With Linux and Windows 7 you would be able to also mine 125,4 192,7 and 144,5s (beam3) 🙂
Cheers
I downloaded the miniZ program for use on my windows 10, but I got this error message: VCRUNTIME140.dll was not found!
please help.
Thank you
Hi Hay,
Thank you for your message.
miniZ doesn’t seem to be able to find the file. You can try to locate the file in your system and copy it into miniZ folder.
You can find various suggestions on how to fix this. Example here.
However, unless you need it for something else, maybe the best is to find the file and place it next to miniZ. You can download it here.
Let us know if this helped.
Cheers,
miniZ
Thank you for your response.
I managed to start it via the GUI but it does not work.
I have the latest driver installed but I get this error message, please help.
btcz.app:3032 –par=144,5 –pers=BitcoinZ
************ miniZ v1.7×3 ************
miniZ: Excluding GPU#0 GeForce 820M
Number of CUDA[8.0] devices found: 0
No devices selected, exiting…
Hi,
I need help running this miner, using gtx 1650 to mine beam. I keep getting this error on start.
miniZ[00:0:00.0:3326]: Selecting GPU#0[0] GeForce GTX 1650
[FATAL ] GPU[0] has invalid mode 0.
Please help.
Thanks!
Hi Jay,
It looks like the miner is not starting with the right kernel.
Could you try adding
--mode 12to your command line?Also, could you let us know if it works this way? And which operating system are you using?
Thank you for the feedback!
Cheers
Hi miniZ,
Tired adding mode 12, does not work. I am using windows 10 for my os.
************ miniZ v1.7×3 ************
Number of CUDA[8.0] devices found: 1
Algo: EQ[144,5s] [smart-pers]
Pool#0: user[]
server[beam-asia.leafpool.com] port[3333] ssl[yes] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Logging:: file[miniZ.log] period[10] delay[0]
Optimisation: ocX[0]
Temp. limit: [90°C]
[INFO ] Mining fee set to 2.00%
[WARNING] GPU[0] cannot run in mode 12
miniZ[00:0:00.0:3326]: Selecting GPU#0[0] GeForce GTX 1650
[FATAL ] GPU[0] has invalid mode 0.
[INFO ] Disconnecting from beam-asia.leafpool.com
What should I do?
Appreciate your help. Thanks!
Hi jay,
Thank you for the feedback. We’ll have a look at this.
It seems that the 4GB kernel for sm7.5 may have some issue.
We’ll investigate and, if necessary, a correction will be included in the next update.
Cheers
Hi, I have a lenovo flex with an Nvidia GeForce 820M. I want to mine btcz but it’s not working.
I have the latest driver installed (391.35) but I get this error message when I try to use the miner, please help.
btcz.app:3032 –par=144,5 –pers=BitcoinZ
************ miniZ v1.7×3 ************
miniZ: Excluding GPU#0 GeForce 820M
Number of CUDA[8.0] devices found: 0
No devices selected, exiting…
Hi Hay,
Thank you for the feedback.
Try adding to your command line:
-cd n, where n is your GPU number. Kepler GPUs are excluded by default, you need to include them ‘by hand’.Let us know if this works for you.
Cheers
Thank you for your help.
I’m not a programmer, so I will need your help in this. How do I find out what my GPU number is?
I would be very grateful if you could write down exactly what you want me to add.
Thank you
Hay
Hi Hay,
No problem 🙂
To know the GPU number order you can run in the terminal
miniZ.exe -ciThis will list the available GPUs.
You can see the number right next to #. If you only have one GPU the number will be 0.
Then you can run miniZ adding
-cd n(n is the GPU number) to the command line.Something like this should work:
miniZ.exe [email protected]:3032 -cd n --log --extraDo not forget to add your wallet, worker, and GPU number.
Check our FAQ page for more examples on How to mine BitcoinZ?
Let us know if you managed to start the miner.
Cheers
Thanks a lot. I think we are making progress. I have added the GPU number with -cd 0
And this is the error I got:
btcz.app:3032 –par=144,5 –pers=BitcoinZ -cd 0
************ miniZ v1.7×3 ************
Algo: EQ[144,5] [smart-pers]
Pool#0: user[t1ddYmxdLhbEko2H3W5yNUsiPre2xnS6CZf.Optional_ID]
server[mining.btcz.app] port[3032] ssl[no] pers[BitcoinZ]
Telemetry: [http://localhost:20000]
Temp. limit: [90°C]
[INFO ] Mining fee set to 2.00%
miniZ[15:0:00.0:1679]: Selecting GPU#0[0] GeForce 820M
[FATAL ] Cannot load deviceZ code.
[INFO ] Disconnecting from mining.btcz.app
Any idea where to proceed from here, please? What is the deviceZ code?
Thank you very much, I really appreciate your help.
Hay
Hi Hay,
The architecture of your GPU is Fermi, which is not supported by miniZ.
We first thought that it was Kepler, the next architecrure after Fermi… sorry about that.
In any case that GPU would have a very very low hashrate.
Thank you for your interest in miniZ!
Cheers
Thank you for your help.
I’m not a programmer, so I will need your help in this. How do I find out what my GPU number is?
I would be very grateful if you could write down exactly what you want me to add.
Thank you
Hay
Hi, Can miniZ be used with an Intel HD graphics card?
Thank you,
Abulig
Hi Abulig,
Thank you for your interest.
For Intel cards you need an opencl miner.
miniZ is Cuda miner 🙂
Cheers