Any plans to release the 1.0.4 version for Linux?
1 Like
Version 1.0.4b will be released soon however it’ll have a slightly worse performance than the Windows version.
1 Like
How many cards? Which version is that?
We are releasing EQM v1.0.4b.
Download:
https://www.nicehash.com/tools/eqm_v1.0.4b_Win64.zip
Linux bins are following shortly.
This version is specially tuned for low TDP and mem OC scenarios. In any case, in our tests, stock GTX 1070 does 400 Sol/s.
Like with all other previous versions, we again used some new tricks. Now, remember what and WHEN we did it. You will see, that competition will just copy these new ideas. When this happens (in following few days), we will release the source.
3 Likes
450 sols with 1070 (2075\9000)
Here are download links for the latest version 1.0.4b:
Up to 400 Sol/s @ stock GTX 1070
DOWNLOAD WINDOWS version (Windows 7+)
DOWNLOAD Linux Ubuntu 14.04 version
DOWNLOAD Linux Ubuntu 16.04 version
Please note that you can set mode 1 for SM52 and SM61 cards, mode 2 for SM50 cards.
1 Like
anyone know of a decent nvidia miner that I can use for solo mining?
Strangely the Linux version works slightly faster (1%) for me than the Windows one despite your warning that it should be slower. 
But then I ran 1.0.4a in Windows and 1.0.4b in Linux.
Latest v1.0.4c downloads (only a few stability patches and 1-2% performance increase):
DOWNLOAD WINDOWS version (Windows 7+)
DOWNLOAD Linux Ubuntu 14.04 version
DOWNLOAD Linux Ubuntu 16.04 version
This would probably be the last closed-source release, we are planning to release sources in the upcoming week.
Keep on hashing
Best regards,
NiceHash team.
Thanks guys for including a way to only run one thread on this.
Running 2 threads i saw 700+sols at 1960mhz on a titan x pascal.
Running 1 thread i can still watch youtube and streams getting 660+sols.
Thanks, but until nicehash miner lets me mine directly to zcash using the pool of my choice and keep bitcoin out of the loop, I’ll stick with EWBF miner.
1 Like
Doesn’t the title tell you it is NH exclusive miner? Sad!
EWBF miner is the best u can mine directly Zcash
Any sugestion for 1070 Brand ? also i want to ask if this is a good option : MSI GeForce® GTX 1070 ARMOR OC, 8GB GDDR5, 256-bit
Thank you
i have 3 of them.5 months already,seems like a good choice.2075\9000 OC stable 24\7 working.
The latest Linux version (1.0.4c) is not stable for me, it regularly (every several hours) crashes with this message:
[11:48:13][0x00007fa0a1e6f700][error] device#0 | CUDA error 'unspecified launch failure' in func 'solve_sync' line 3739
[11:48:13][0x00007fa0a1e6f700][warning] device#0 | Thread detected runtime error, quitting miner...
Any ideas what might cause it? My GPU (GTX 1060 6GB) is not overclocked and all previous versions ran for up to 20 hours without issues.
Edit: Oh, probably there’s a bug either in the miner itself or NVIDIA Linux drivers:
[18995.231265] NVRM: GPU at PCI:0000:01:00: GPU-SERIAL-NUMBER-HIDDEN
[18995.231270] NVRM: GPU Board Serial Number:
[18995.231273] NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 0): Out Of Range Address
[18995.231280] NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x50c648=0xe 0x50c650=0x20 0x50c644=0xd3eff2 0x50c64c=0x17f
[18995.234009] NVRM: Xid (PCI:0000:01:00): 43, Ch 00000020, engmask 00000101
The GPU crashes every 5-45 minutes or so. Damn.
Interestingly NVIDIA says that this issue might be an error with an app:
XID 13: GR: SW Notify Error
This event is logged for general user application faults. Typically this is an out-of-bounds error where the user has walked past the end of an array, but could also be an illegal instruction, illegal register, or other case.
In rare cases, it’s possible for a hardware failure or system software bugs to materialize as XID 13.
When this event is logged, NVIDIA recommends the following:
Run the application in cuda-gdb or cuda-memcheck , or
Run the application with CUDA_DEVICE_WAITS_ON_EXCEPTION=1 and then attach later with cuda-gdb, or
File a bug if the previous two come back inconclusive to eliminate potential NVIDIA driver or hardware bug.
Note: The cuda-memcheck tool instruments the running application and reports which line of code performed the illegal read.
Also there’s this note in drivers 367.43:
5.1. Memory exhaustion can occur with vGPU profiles that have 512 Mbytes or less of frame buffer
Description
Memory exhaustion can occur with vGPU profiles that have 512 Mbytes or less of frame buffer. This issue typically occurs when multiple display heads are used with Citrix XenDesktop or VMware Horizon on a Windows 10 guest VM.
When this error occurs, the NVIDIA host driver reports Xid error 31 and Xid error 43 in the VMware vSphere log file vmware.log in the guest VM’s storage directory.
The following vGPU profiles have 512 Mbytes or less of frame buffer:
‣ Tesla M6-0B, M6-0Q
‣ Tesla M10-0B, M10-0Q
‣ Tesla M60-0B, M60-0Q
‣ GRID K100, K120Q
‣ GRID K200, K220Q
Version
Workaround
Status: Open
Last but not least when I downclocked my GPU VRAM from effective 8000MHz to 7600MHz the error disappeared (so far).
Also is too much to ask from you to create a CUDA/OpenCL memory checker? All the existing ones are dead/unsupported/don’t support GPUs with 4GB of VRAM or more.
Source code?
Yes please.
Does anyone know why the miner starts at 200 Sol/s and gradually drops to 150 Sol/s for me? Using 980m
Throttling? Make sure your clocks stay high at all times. Also there is a bug (in drivers?) - if you have some apps open (like chrome), your clock falls down to non-boosted one.