[ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX]

[tbearhere]

Try ccminer.

http://ccminer.org/

Look for the bitcointalk links too.

[1714058451]

1714058451

[1714058451]

1714058451

[1714058451]

1714058451

[sam29]

cry for help, at least suggest which direction to dig

a day ago all my 7 nvidia rigs worked fine, yesterday i have changed PSU on 3 rigs from cx750 to kcas 750, and now i got only 4 rig working

other 3 rigs, where psu were changed, dont work with any miner, tried ccminer many different versions, ewbf 034b, claymore zcash&dual. all miners giving some errors in a few minutes on any algo. claymore hangs rig, ccminer and ewbf any version just stops working, but rig continue working normaly.
have many bat files which are working correctly on exactly same rigs, but non of them works on these 3.
i have 1060 3gb ASus&palit, mobo msi z270 a-pro, b85 anniversary and h81.
nothing works even in stock. no bios were edited
i have tried
different driver versions 384.76/80 and the latest one.
reinstalled win 10
updated net framework
updated c++
increase from 16gb to 30gb
delete AB
copy many different vcruntime140.dll to syswow64 and system 32, after reinstalled again win 10

some error that i get on cc after few min,
Cuda error in func 'quark_blake512_cpu_setBlock_80_sp' at line 577 : unknown error.
Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 547 : the launch timed out and was terminated.
GPU#1:invalid argument

honestly dont believe that the problem is just because of PSU? those PSU were working on other rigs with amd cards earlier.

any hints where to search for problem would be great

[dj--alex]

I found how to mine Trezarcoin without unsafe Windows on Linux , Using CCminer trupivot

Step 1.  Get Linux,

I Mining on my own edition Linux Mint 18 x64 with PREINSTALLED Nvidia driver 387 (for GTX 1060,1070,1080)
Sorry no english by default support,  no link.

Step 2.
sudo apt-get install nvidia-cuda-toolkit libcurl4-openssl-dev libssl-dev libjansson-dev automake autotools-dev build-essential gcc-5 g++-5
git clone https://github.com/tpruvot/ccminer.git
cd ccminer

check compactibility here https://github.com/tpruvot/ccminer/wiki/Compatibility

Step 3.
 Makefile.am contatins data about architecture
for me  GTX 1060 - is correct by default, i nothing change ( compute 50)
nvcc_ARCH  = -gencode=arch=compute_50,code=\"sm_50,compute_50\"
nvcc_ARCH += -gencode=arch=compute_52,code=\"sm_52,compute_52\"

Step 4.
./build.sh

Step 5. If all ok
Run miner

create _1_start_Trezarcoin_mine.sh
and fill it

Code:

#!/bin/bash/
./ccminer -a neoscrypt -o stratum+tcp://pool.minertopia.org:4233 -u TdBSh6BY2iU9uadNtDPXiXgMPMSaD4X5ac -p x
#./ccminer -a neoscrypt -o stratum+tcp://eu1.altminer.net:4233 -u TdBSh6BY2iU9uadNtDPXiXgMPMSaD4X5ac -p c=TZC

If you don't like pool select other

Don't forget change wallet to your

Step 6. Optional
Add miner to autoload after oveclocking autoload.
I use standart autorun utility in Linux Mint,  not cron.


I hope this help somebody.

[Huseyinnn]

cry for help, at least suggest which direction to dig

a day ago all my 7 nvidia rigs worked fine, yesterday i have changed PSU on 3 rigs from cx750 to kcas 750, and now i got only 4 rig working

other 3 rigs, where psu were changed, dont work with any miner, tried ccminer many different versions, ewbf 034b, claymore zcash&dual. all miners giving some errors in a few minutes on any algo. claymore hangs rig, ccminer and ewbf any version just stops working, but rig continue working normaly.
have many bat files which are working correctly on exactly same rigs, but non of them works on these 3.
i have 1060 3gb ASus&palit, mobo msi z270 a-pro, b85 anniversary and h81.
nothing works even in stock. no bios were edited
i have tried
different driver versions 384.76/80 and the latest one.
reinstalled win 10
updated net framework
updated c++
increase from 16gb to 30gb
delete AB
copy many different vcruntime140.dll to syswow64 and system 32, after reinstalled again win 10

some error that i get on cc after few min,
Cuda error in func 'quark_blake512_cpu_setBlock_80_sp' at line 577 : unknown error.
Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 547 : the launch timed out and was terminated.
GPU#1:invalid argument

honestly dont believe that the problem is just because of PSU? those PSU were working on other rigs with amd cards earlier.

any hints where to search for problem would be great

I get same error with line 547. Sometimes after a day sometimes after minutes. Did you find any solution?

[Habieredkill]

call me lazy but i just don't want to read 1000+ pages.. Grin

What would be best miner to use to mine x11?

i got asus gtx 660 OC, i7-4770K and 8gb DDR3 1600mhz.

Thanks.

Edit: and win 8.1 x64

[Bibi187]

call me lazy but i just don't want to read 1000+ pages.. Grin

What would be best miner to use to mine x11?

i got asus gtx 660 OC, i7-4770K and 8gb DDR3 1600mhz.

Thanks.

Edit: and win 8.1 x64

x11 is not a GPU algo, you need some ASIC to mine this one.

Try another algo, no point at all to mine this one.

[SkyDr4k3]

the dowaload link of the last realease doesn t work for me

[polmen]

What is the newest version of cudaminer ?

[Digital Drug Lord]

Is it worth mining scyrpt coin in 2018 if you have a gpu?

[giveen1]

Is it worth mining scyrpt coin in 2018 if you have a gpu?

No.

[sabrine015]

Is it worth mining scyrpt coin in 2018 if you have a gpu?

No.

even if it's somehow lil easy to mine and doesnt have a high difficulty ?

[CryptoCoin101]

Is it worth mining scyrpt coin in 2018 if you have a gpu?

No.

even if it's somehow lil easy to mine and doesnt have a high difficulty ?

I think this depends on the coin you are mining but most and the popular ones are not profitable these days...

This is definitely the best NVIDIA miner with high hash rates and multiple command support.

Seeing to the ccminer commands, how do I implement --cuda-schedule?

[CryptoCoin101]

Seeing to the ccminer commands, how do I implement --cuda-schedule?

Never mind. I already found the answer.

http://cryptomining-blog.com/5684-updated-ethminer-0-9-41-nvidia-cuda-version-for-windows-2/

--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.

[frequencydip]

Hello I'm trying to build ccminer on ubuntu 16.02 and it won't build:

This is the error I get:

Code:

make[3]: Leaving directory '/home/prospector/tpruvot/ccminer/compat'
make[2]: Leaving directory '/home/prospector/tpruvot/ccminer/compat'
make[2]: Entering directory '/home/prospector/tpruvot/ccminer'
gcc -DHAVE_CONFIG_H -I.  -fopenmp  -pthread -fno-strict-aliasing -I./compat/jansson -I/usr/local/cuda/include -DUSE_WRAPNVML    -g -O2 -MT ccminer-crc32.o -MD -MP -MF .deps/ccminer-crc32.Tpo -c -o ccminer-crc32.o `test -f 'crc32.c' || echo './'`crc32.c
gcc -DHAVE_CONFIG_H -I.  -fopenmp  -pthread -fno-strict-aliasing -I./compat/jansson -I/usr/local/cuda/include -DUSE_WRAPNVML    -g -O2 -MT ccminer-hefty1.o -MD -MP -MF .deps/ccminer-hefty1.Tpo -c -o ccminer-hefty1.o `test -f 'hefty1.c' || echo './'`hefty1.c
g++ -DHAVE_CONFIG_H -I.  -fopenmp  -pthread -fno-strict-aliasing -I./compat/jansson -I/usr/local/cuda/include -DUSE_WRAPNVML    -O3 -march=native -D_REENTRANT -falign-functions=16 -falign-jumps=16 -falign-labels=16 -MT ccminer-ccminer.o -MD -MP -MF .deps/ccminer-ccminer.Tpo -c -o ccminer-ccminer.o `test -f 'ccminer.cpp' || echo './'`ccminer.cpp
g++ -DHAVE_CONFIG_H -I.  -fopenmp  -pthread -fno-strict-aliasing -I./compat/jansson -I/usr/local/cuda/include -DUSE_WRAPNVML    -O3 -march=native -D_REENTRANT -falign-functions=16 -falign-jumps=16 -falign-labels=16 -MT ccminer-pools.o -MD -MP -MF .deps/ccminer-pools.Tpo -c -o ccminer-pools.o `test -f 'pools.cpp' || echo './'`pools.cpp
mv -f .deps/ccminer-crc32.Tpo .deps/ccminer-crc32.Po
g++ -DHAVE_CONFIG_H -I.  -fopenmp  -pthread -fno-strict-aliasing -I./compat/jansson -I/usr/local/cuda/include -DUSE_WRAPNVML    -O3 -march=native -D_REENTRANT -falign-functions=16 -falign-jumps=16 -falign-labels=16 -MT ccminer-util.o -MD -MP -MF .deps/ccminer-util.Tpo -c -o ccminer-util.o `test -f 'util.cpp' || echo './'`util.cpp
ccminer.cpp:49:26: fatal error: cuda_runtime.h: No such file or directory
compilation terminated.
Makefile:1775: recipe for target 'ccminer-ccminer.o' failed
make[2]: *** [ccminer-ccminer.o] Error 1
make[2]: *** Waiting for unfinished jobs....
mv -f .deps/ccminer-pools.Tpo .deps/ccminer-pools.Po
mv -f .deps/ccminer-hefty1.Tpo .deps/ccminer-hefty1.Po
mv -f .deps/ccminer-util.Tpo .deps/ccminer-util.Po
make[2]: Leaving directory '/home/prospector/tpruvot/ccminer'
Makefile:2201: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/prospector/tpruvot/ccminer'
Makefile:654: recipe for target 'all' failed
make: *** [all] Error 2

I have Cuda 8 already installed, help please

EDIT I searched for cuda_runtime.h and it is in

/usr/local/cuda-8.0/targets/x86_64-linux/include/cuda_runtime.h

Code:

stat /usr/local/cuda-8.0/targets/x86_64-linux/include/cuda_runtime.h
  File: '/usr/local/cuda-8.0/targets/x86_64-linux/include/cuda_runtime.h'
  Size: 84245           Blocks: 168        IO Block: 4096   regular file
Device: fd00h/64768d    Inode: 43953       Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2017-07-05 19:11:45.069047189 +0100
Modify: 2017-01-26 23:48:33.000000000 +0000
Change: 2017-07-05 19:05:48.496727332 +0100
 Birth: -

You have to edit build.sh and change
# export PATH="$PATH:/usr/local/cuda/bin/"
to your location so it would be
# export PATH="$PATH:/usr/local/cuda-8.0/"

and

edit configure.sh and make sure cuda points to your install
--with-cuda=/usr/local/cuda-8.0

[tbearhere]

Seeing to the ccminer commands, how do I implement --cuda-schedule?

Never mind. I already found the answer.

http://cryptomining-blog.com/5684-updated-ethminer-0-9-41-nvidia-cuda-version-for-windows-2/

--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.

What use is this plz?  Any increase in hashrates? thx
PS I still don't understand this command. Any help plz.

[HashAuger]

Seeing to the ccminer commands, how do I implement --cuda-schedule?

Never mind. I already found the answer.

http://cryptomining-blog.com/5684-updated-ethminer-0-9-41-nvidia-cuda-version-for-windows-2/

--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.

What use is this plz?  Any increase in hashrates? thx
PS I still don't understand this command. Any help plz.

This setting determines how the CCMiner process interacts with the CPU and other processes (including those that belong to the operating system) running on your system.  Whether it improves your hash rate depends on how many GPUs you have, how fast they are and the speed and number of cores your CPU has.  CCMiner uses the CPU to validate results from your GPUs, so if CCMiner cannot validate results as quickly as your GPUs are creating them, your hash rates will suffer a little.  Changing this setting can give CCMiner more access to your CPU, which can increase the speed at which results are processed.  However, changing this setting will increase CPU utilization and may decrease system responsiveness because other processes will have to wait longer to use the CPU.

For example, the Spin option gives CCMiner the fastest access to the CPU because it keeps the process active on the CPU as it waits for new GPU results.  This prevents other background processes from interrupting it and can improve CCMiner performance at the expense of the operating system and anything else also running on the computer. Yield is a compromise because it gives CCMiner a bit more access to the CPU than sync, but it allows other processes to interrupt it when it isn't doing anything. Sync tends to be the most friendly towards other background processes so the system remains responsive during mining, but it also means that the CCMiner process may be interrupted a lot, which might affect your performance if you have several fast GPUs in a system with a slow CPU.

Some variants of CCMiner, such as Klaust and Tpruvot, may use a different default setting then the one described above.  For example, sync might be the default setting for those versions. In those cases, it may be worth trying yield instead even if you have a relatively fast CPU as it will give the miner process better access to the CPU while not blocking other background processes. I find that yield gives more consistent hash rates than sync on a i7 running 1080 and 1070 ti cards.

[tbearhere]

Seeing to the ccminer commands, how do I implement --cuda-schedule?

Never mind. I already found the answer.

http://cryptomining-blog.com/5684-updated-ethminer-0-9-41-nvidia-cuda-version-for-windows-2/

--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.

What use is this plz?  Any increase in hashrates? thx
PS I still don't understand this command. Any help plz.

This setting determines how the CCMiner process interacts with the CPU and other processes (including those that belong to the operating system) running on your system.  Whether it improves your hash rate depends on how many GPUs you have, how fast they are and the speed and number of cores your CPU has.  CCMiner uses the CPU to validate results from your GPUs, so if CCMiner cannot validate results as quickly as your GPUs are creating them, your hash rates will suffer a little.  Changing this setting can give CCMiner more access to your CPU, which can increase the speed at which results are processed.  However, changing this setting will increase CPU utilization and may decrease system responsiveness because other processes will have to wait longer to use the CPU.

For example, the Spin option gives CCMiner the fastest access to the CPU because it keeps the process active on the CPU as it waits for new GPU results.  This prevents other background processes from interrupting it and can improve CCMiner performance at the expense of the operating system and anything else also running on the computer. Yield is a compromise because it gives CCMiner a bit more access to the CPU than sync, but it allows other processes to interrupt it when it isn't doing anything. Sync tends to be the most friendly towards other background processes so the system remains responsive during mining, but it also means that the CCMiner process may be interrupted a lot, which might affect your performance if you have several fast GPUs in a system with a slow CPU.

Some variants of CCMiner, such as Klaust and Tpruvot, may use a different default setting then the one described above.  For example, sync might be the default setting for those versions. In those cases, it may be worth trying yield instead even if you have a relatively fast CPU as it will give the miner process better access to the CPU while not blocking other background processes. I find that yield gives more consistent hash rates than sync on a i7 running 1080 and 1070 ti cards.

Thx HashAuger Now I understand.

So how would the command go.. like this?       --cuda-schedule yield

[HashAuger]

Seeing to the ccminer commands, how do I implement --cuda-schedule?

Never mind. I already found the answer.

http://cryptomining-blog.com/5684-updated-ethminer-0-9-41-nvidia-cuda-version-for-windows-2/

--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.

What use is this plz?  Any increase in hashrates? thx
PS I still don't understand this command. Any help plz.

This setting determines how the CCMiner process interacts with the CPU and other processes (including those that belong to the operating system) running on your system.  Whether it improves your hash rate depends on how many GPUs you have, how fast they are and the speed and number of cores your CPU has.  CCMiner uses the CPU to validate results from your GPUs, so if CCMiner cannot validate results as quickly as your GPUs are creating them, your hash rates will suffer a little.  Changing this setting can give CCMiner more access to your CPU, which can increase the speed at which results are processed.  However, changing this setting will increase CPU utilization and may decrease system responsiveness because other processes will have to wait longer to use the CPU.

For example, the Spin option gives CCMiner the fastest access to the CPU because it keeps the process active on the CPU as it waits for new GPU results.  This prevents other background processes from interrupting it and can improve CCMiner performance at the expense of the operating system and anything else also running on the computer. Yield is a compromise because it gives CCMiner a bit more access to the CPU than sync, but it allows other processes to interrupt it when it isn't doing anything. Sync tends to be the most friendly towards other background processes so the system remains responsive during mining, but it also means that the CCMiner process may be interrupted a lot, which might affect your performance if you have several fast GPUs in a system with a slow CPU.

Some variants of CCMiner, such as Klaust and Tpruvot, may use a different default setting then the one described above.  For example, sync might be the default setting for those versions. In those cases, it may be worth trying yield instead even if you have a relatively fast CPU as it will give the miner process better access to the CPU while not blocking other background processes. I find that yield gives more consistent hash rates than sync on a i7 running 1080 and 1070 ti cards.

Thx HashAuger Now I understand.

So how would the command go.. like this?       --cuda-schedule yield

Most of the variants of CCMiner that I have seen that support this parameter use a number to represent the desired setting. For example, on Klaust 8.21, you would use --cuda-schedule 2 for yield. Refer to each miner's readme.txt file to see how they use this parameter. It is worth mentioning again that different versions of CCMiner use different default schedule settings. Klaust, for instance, defaults his miner to use block sync whereas Tpruvot uses the Cuda SDK's "auto" setting.  According to the Cuda developer documentation, auto switches between yield and spin based on the the number of GPUs compared to CPU cores; when there are more GPUs than cores it uses yield.

[tbearhere]

Seeing to the ccminer commands, how do I implement --cuda-schedule?

Never mind. I already found the answer.

http://cryptomining-blog.com/5684-updated-ethminer-0-9-41-nvidia-cuda-version-for-windows-2/

--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.

What use is this plz?  Any increase in hashrates? thx
PS I still don't understand this command. Any help plz.

This setting determines how the CCMiner process interacts with the CPU and other processes (including those that belong to the operating system) running on your system.  Whether it improves your hash rate depends on how many GPUs you have, how fast they are and the speed and number of cores your CPU has.  CCMiner uses the CPU to validate results from your GPUs, so if CCMiner cannot validate results as quickly as your GPUs are creating them, your hash rates will suffer a little.  Changing this setting can give CCMiner more access to your CPU, which can increase the speed at which results are processed.  However, changing this setting will increase CPU utilization and may decrease system responsiveness because other processes will have to wait longer to use the CPU.

For example, the Spin option gives CCMiner the fastest access to the CPU because it keeps the process active on the CPU as it waits for new GPU results.  This prevents other background processes from interrupting it and can improve CCMiner performance at the expense of the operating system and anything else also running on the computer. Yield is a compromise because it gives CCMiner a bit more access to the CPU than sync, but it allows other processes to interrupt it when it isn't doing anything. Sync tends to be the most friendly towards other background processes so the system remains responsive during mining, but it also means that the CCMiner process may be interrupted a lot, which might affect your performance if you have several fast GPUs in a system with a slow CPU.

Some variants of CCMiner, such as Klaust and Tpruvot, may use a different default setting then the one described above.  For example, sync might be the default setting for those versions. In those cases, it may be worth trying yield instead even if you have a relatively fast CPU as it will give the miner process better access to the CPU while not blocking other background processes. I find that yield gives more consistent hash rates than sync on a i7 running 1080 and 1070 ti cards.

Thx HashAuger Now I understand.

So how would the command go.. like this?       --cuda-schedule yield

Most of the variants of CCMiner that I have seen that support this parameter use a number to represent the desired setting. For example, on Klaust 8.21, you would use --cuda-schedule 2 for yield. Refer to each miner's readme.txt file to see how they use this parameter. It is worth mentioning again that different versions of CCMiner use different default schedule settings. Klaust, for instance, defaults his miner to use block sync whereas Tpruvot uses the Cuda SDK's "auto" setting.  According to the Cuda developer documentation, auto switches between yield and spin based on the the number of GPUs compared to CPU cores; when there are more GPUs than cores it uses yield.

Yes I see that in their readme files....thx again.

[Andrey123]

Hey.
And where to download this miner?
Links do not work.