Updated Ethminer 0.9.41 Nvidia CUDA Version for Windows

9 Sep
2015

new-ethminer-cuda-updated

The developer of the Ethminer fork with Nvidia CUDA support (source) Genoil has released another update and we have compiled a new Windows binary of ethminer with CUDA support. Do note that this Windows binary release is compiled with VS2013 for windows 64-bit and is for CUDA 6.5. The latest version comes with some optimizations and a new command line option cuda-schedule to experiment with that replaces the old cuda-turbo, also note that you may need to manually specify the number of GPUs to use if you have multiple video cards using the cuda-devices command line parameter if the miner fires only on one device by default. Additionally to get better performance you can try adding the following command line parameters to the ethminer:

For OpenCL: --cl-global-work 16384
For CUDA: --cuda-grid-size 8192 --cuda-block-size 128 --cuda-schedule auto

--cuda-schedule Set the schedule mode for CUDA threads waiting for CUDA devices to finish work. Default is sync. Possible values for mode are:
auto – Uses a heuristic based on the number of active CUDA contexts in the process C and the number of logical processors in the system P. If C > P, then yield else spin.
spin – Instruct CUDA to actively spin when waiting for results from the device.
yield – Instruct CUDA to yield its thread when waiting for results from the device.
sync – Instruct CUDA to block the CPU thread on a synchronization primitive when waiting for the results from the device.

It seems that the auto mode for cuda-schedule works best for us providing maybe a bit lower maximum hashrate, but a more stable one than the sync that may produce higher maxes, but also lower. You are free to experiment what will work best on your mining configuration however. The Ethminer CUDA fork should work on Compute 2.0 or newer GPUs, but the performance on older GPUs can be worse, also don’t forget that you can run Ethminer in OpenCL mode as well on Nvidia-based video cards and not only on AMD if you are having trouble with the CUDA support or the hashrate you get is lower as compared to OpenCL.

Download the updated Ethminer CUDA fork compiled for Windows and ready to be used…



Other Similar Publications:

9 Responses to Updated Ethminer 0.9.41 Nvidia CUDA Version for Windows

Reader

September 10th, 2015 at 03:13

So what kind of performance increase are we looking at here? I didn’t seem much of a difference with the last version posted. Thanks.

djsterks

September 10th, 2015 at 07:49

I am having more trouble with this one than I have in a long time. Can’t seem to get 2 GPUs to work smoothly running cuda. One just chills there. Does anyone know the proper command for 2 and an example line for reference? Thanks!

admin

September 10th, 2015 at 09:30

This update might be able to provide a bit higher and more stable hashrate, but not that much.

For running with two video cards you need to add --cuda-devices 0 1 to the command line.

Ferdjones

September 10th, 2015 at 14:57

I’m getting a problem when I either submit a solution or when there is a new block. All of this happens on ethereumpool.net (I don’t use the others), and it happens when I use the cpu mining (when I’m using the computer, 4 of 8 threads), or when I use the cuda mining.

miner 08:52:21|main Header-hash: 2cc8387cf841e4bdf56f67eb74c3100a4b84bee8dc4fff2f9bd58330b0450386
miner 08:52:21|main Seedhash: 6d29f6dd1270e49744bd5377ec86395b2de2abbe54bae16281b8e39b35538dcd
miner 08:52:21|main Target: 000001ad7f29abcaf485787a6520ec08d23699194119a5c37387b71906614310
i 08:52:21| Full DAG loaded
miner 08:52:21|main Mining on PoWhash #2cc8387c… : 35466 H/s = 26600 hashes / 0.75 s
miner 08:52:22|main Mining on PoWhash #2cc8387c… : 479016 H/s = 477100 hashes / 0.996 s
miner 08:52:23|main Mining on PoWhash #2cc8387c… : 481818 H/s = 519400 hashes / 1.078 s
miner 08:52:24|main Mining on PoWhash #2cc8387c… : 470456 H/s = 442700 hashes / 0.941 s
miner 08:52:25|main Mining on PoWhash #2cc8387c… : 483262 H/s = 456200 hashes / 0.944 s
miner 08:52:26|main Mining on PoWhash #2cc8387c… : 489979 H/s = 479200 hashes / 0.978 s
miner 08:52:27|main Mining on PoWhash #2cc8387c… : 477234 H/s = 448600 hashes / 0.94 s
miner 08:52:28|main Mining on PoWhash #2cc8387c… : 486029 H/s = 462700 hashes / 0.952 s
miner 08:52:29|main Mining on PoWhash #2cc8387c… : 483524 H/s = 463700 hashes / 0.959 s
miner 08:52:30|main Mining on PoWhash #2cc8387c… : 469618 H/s = 456000 hashes / 0.971 s
miner 08:52:31|main Mining on PoWhash #2cc8387c… : 488831 H/s = 472700 hashes / 0.967 s
miner 08:52:32|main Mining on PoWhash #2cc8387c… : 486744 H/s = 499400 hashes / 1.026 s
miner 08:52:33|main Mining on PoWhash #2cc8387c… : 478442 H/s = 528200 hashes / 1.104 s
miner 08:52:34|main Mining on PoWhash #2cc8387c… : 491780 H/s = 466700 hashes / 0.949 s
i 08:52:35|main Solution found; Submitting to http://ethereumpool.co/?miner=.2@0xb89e64f8feffdeadd40d06b60856b1edfbfd1b0c
i 08:52:35|main Nonce: ad85340884f65a47
i 08:52:35|main Mixhash: 0ad33957cd1714c38703b7852528fccdf5cec668c0f0c4d7892435e6e978ff2a
i 08:52:35|main Header-hash: 2cc8387cf841e4bdf56f67eb74c3100a4b84bee8dc4fff2f9bd58330b0450386
i 08:52:35|main Seedhash: 6d29f6dd1270e49744bd5377ec86395b2de2abbe54bae16281b8e39b35538dcd
i 08:52:35|main Target: 000001ad7f29abcaf485787a6520ec08d23699194119a5c37387b71906614310
i 08:52:35|main Ethash: 0000004f165fd28ff9f316fda6449df3cfac3b2963a7ddd30e46319f06cf231b
JSON-RPC problem. Probably couldn’t connect. Retrying in 1…
miner 08:53:23|main Mining on PoWhash #2cc8387c… : 840 H/s = 40800 hashes / 48.54 s
miner 08:53:24|main Mining on PoWhash #2cc8387c… : 0 H/s = 0 hashes / 1.003 s
miner 08:53:25|main Mining on PoWhash #2cc8387c… : 0 H/s = 0 hashes / 0.981 s
miner 08:53:26|main Mining on PoWhash #2cc8387c… : 0 H/s = 0 hashes / 1.051 s

I’m not sure if this is a pool problem (notice the extra hash sigs), or if it’s this version of the miner. I have tried all of the cuda-schedule options, and get the same results, after new block or submission (failure I’m guessing), it goes to 0 hashes/sec.

Anyone know if it’s me or the miner or the site, and what if anything I can do about it? TIA

remember

September 10th, 2015 at 20:41

You name of miners set has a problem, your name miners should be 2 or other letters or Numbers at the beginning

remember

September 10th, 2015 at 20:44

You should use mine pool is miners name must be numeric, and must be greater than or equal to 1

Genoil

September 11th, 2015 at 10:44

If you compile with CUDA 6.5, you will *NOT* get the added performance that is built into it for Maxwell. With CUDA 7.5, you can expect up to 5% added performance on GTX750Ti.

davidrentao

September 12th, 2015 at 01:30

hi, genoil, i am using 750ti to mining, please teach me how to using ethminer to mining, it’s is show something worry over here.

C:\Users\A999\Desktop\ethminer-cuda-0.9.41-new2>ethminer -G –opencl-platform 1 -t 6 -F http://198.11.179.9
30c4e88a929bba0ee3dce284866a9937b609/A024
Found suitable OpenCL device [GeForce GTX 750 Ti] with 2147483648 bytes of GPU memory
miner 18:34:30|main Getting work package…
miner 18:34:31|main Grabbing DAG for #6d29f6dd鈥
miner 18:34:32|main Got work package:
miner 18:34:32|main Header-hash: 7e6dc6082b9548790ae9b59378782b7244ab47246148164908fb3c59876f9eb0
miner 18:34:32|main Seedhash: 6d29f6dd1270e49744bd5377ec86395b2de2abbe54bae16281b8e39b35538dcd
miner 18:34:32|main Target: 00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e
i 18:34:32| Loading full DAG of seedhash: #c307e562鈥
i 18:34:32|gpuminer0 workLoop 0 #00000000鈥?#6d29f6dd鈥
i 18:34:32|gpuminer1 workLoop 0 #00000000鈥?#6d29f6dd鈥
i 18:34:32|gpuminer0 Initialising miner…
i 18:34:32|gpuminer1 Initialising miner…
i 18:34:32|gpuminer2 workLoop 0 #00000000鈥?#6d29f6dd鈥
i 18:34:32|gpuminer3 workLoop 0 #00000000鈥?#6d29f6dd鈥
i 18:34:32|gpuminer2 Initialising miner…
i 18:34:32|gpuminer3 Initialising miner…
i 18:34:32|gpuminer4 workLoop 0 #00000000鈥?#6d29f6dd鈥
i 18:34:32|gpuminer4 Initialising miner…
i 18:34:32|gpuminer5 workLoop 0 #00000000鈥?#6d29f6dd鈥
i 18:34:32|gpuminer5 Initialising miner…
miner 18:34:33|main Mining on PoWhash #7e6dc608鈥?: 0 H/s = 0 hashes / 0.5 s
Using platform: NVIDIA CUDA
Using platform: NVIDIA CUDA
Using device: GeForce GTX 750 Ti(OpenCL 1.1 CUDA)
Using platform: NVIDIA CUDA
Using platform: NVIDIA CUDA
Using platform: NVIDIA CUDA
Using device: GeForce GTX 750 Ti(OpenCL 1.1 CUDA)
Using device: GeForce GTX 750 Ti(OpenCL 1.1 CUDA)
Using platform: NVIDIA CUDA
Using device: GeForce GTX 750 Ti(OpenCL 1.1 CUDA)
Using device: GeForce GTX 750 Ti(OpenCL 1.1 CUDA)
Using device: GeForce GTX 750 Ti(OpenCL 1.1 CUDA)
miner 18:34:34|main Mining on PoWhash #7e6dc608鈥?: 0 H/s = 0 hashes / 1.38 s
miner 18:34:35|main Got work package:
miner 18:34:35|main Header-hash: dea512c02cc7bec84dd0d28e4fca3a19f3cfc5cfcdf83939e2cabd6e1bdca5a1
miner 18:34:35|main Seedhash: 6d29f6dd1270e49744bd5377ec86395b2de2abbe54bae16281b8e39b35538dcd
miner 18:34:35|main Target: 00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e
Printing program log

Creating one big buffer for the DAG
Loading single big chunk kernels
Mapping one big chunk.
Printing program log

Creating one big buffer for the DAG
Loading single big chunk kernels
Mapping one big chunk.
Printing program log

Creating one big buffer for the DAG
Loading single big chunk kernels
Mapping one big chunk.
Printing program log

Creating one big buffer for the DAG
Loading single big chunk kernels
Mapping one big chunk.
Printing program log

Creating one big buffer for the DAG
Loading single big chunk kernels
Mapping one big chunk.
Printing program log

Creating one big buffer for the DAG
Loading single big chunk kernels
Mapping one big chunk.
Creating buffer for header.
Creating mining buffer 0
Creating mining buffer 1
Creating buffer for header.
Creating mining buffer 0
Creating mining buffer 1
Creating buffer for header.
Creating buffer for header.
Creating mining buffer 0
Creating mining buffer 0
Creating buffer for header.
Creating mining buffer 1
Creating mining buffer 0
Creating mining buffer 1
Creating mining buffer 1
Creating buffer for header.
Creating mining buffer 0
Creating mining buffer 1
i 18:35:52|gpuminer0 workLoop 1 #6d29f6dd鈥?#6d29f6dd鈥
clEnqueueMapBuffer(-36)
i 18:44:07| Full DAG loaded

davidrentao

September 12th, 2015 at 01:34

at the same time, the 750ti driver will be losting and miner will system halted in the process,i need restart again. i don know what happen,

Leave a Reply

Your email address will not be published. Required fields are marked *

top