w7, nvidia gpus
algo aeon, get error duplicate shares
any ideea?
Topic: CryptoGen NVidia GPU Miner (Read 8534 times)
This can be a scam like many other new miners. Check your computers for RATs or Backdoors.
gonna try this miner
HiDid you try ?
Note that CryptoGen is valid for a lot of algorithms : phi2, phi, Lyra2z, and more
You can check and compare its benchmark rates on the pools, for example :
- https://bsod.pw/bench?algo=phi2&chip=0
- http://yiimp.eu/bench?algo=phi2&chip=0
gonna try this miner
HiDid you try ?
Note that CryptoGen is valid for a lot of algorithms : phi2, phi, Lyra2z, and more
You can check and compare its benchmark rates on the pools, for example :
- https://bsod.pw/bench?algo=phi2&chip=0
- http://yiimp.eu/bench?algo=phi2&chip=0
gonna try this miner
Hi guys
A new version v3.0.6 is available here :
https://github.com/genminer/cryptogen/releases/tag/v3.0.6
- Added ability to use pool's benchmarks with "stats" in pass
- Compiled with CUDA 9.1
- Tested with last nVidia driver 398.36
- Versions w32 + x64
Happy mining !
A new version v3.0.6 is available here :
https://github.com/genminer/cryptogen/releases/tag/v3.0.6
- Added ability to use pool's benchmarks with "stats" in pass
- Compiled with CUDA 9.1
- Tested with last nVidia driver 398.36
- Versions w32 + x64
Happy mining !
In this case it easy thing since it is Windows 10 x64 1709 and it just siomply detect any card ..
just not gpu device found which leads to the point it can't find any with the cuda device query.
Well the is no OC or algo involved in this error - just can't simply find a device - wanted to keep it simple.
just not gpu device found which leads to the point it can't find any with the cuda device query.
Well the is no OC or algo involved in this error - just can't simply find a device - wanted to keep it simple.
That's strange.
All my tests on Win 10 x64 are corrects so far, with Cuda 7.5, 9.0, 9.1, and for platforms win32 and x64.
I'm also preparing a x64 release, maybe it'll be ok for you.
In this case it easy thing since it is Windows 10 x64 1709 and it just siomply detect any card ..
just not gpu device found which leads to the point it can't find any with the cuda device query.
Well the is no OC or algo involved in this error - just can't simply find a device - wanted to keep it simple.
just not gpu device found which leads to the point it can't find any with the cuda device query.
Well the is no OC or algo involved in this error - just can't simply find a device - wanted to keep it simple.
Hi
First test campaign with last nVidia driver 398.36 :
All is good. No problem encountered.
Keep testing for a while on different configurations & pools.
First test campaign with last nVidia driver 398.36 :
All is good. No problem encountered.
Keep testing for a while on different configurations & pools.
Well the 397.xx are okay but i find the new one very stable.
I have no problem with alexis or any other ccminer, EWBF or such..they all run stable and reliable and a bit faster..
Sure people have problems because they oc the way they don't know what they did or do.. you should test and see what is wrong with the newest driver and your build given the fact that the years old alexis still work like a charm even with the newest
There is no excuse to not do it...
SureI have no problem with alexis or any other ccminer, EWBF or such..they all run stable and reliable and a bit faster..
Sure people have problems because they oc the way they don't know what they did or do.. you should test and see what is wrong with the newest driver and your build given the fact that the years old alexis still work like a charm even with the newest
There is no excuse to not do it...
Anyway, to test this new driver, I would like to know in which configuration you encounter problems : algo, oc settings, intensity, etc.
Otherwise, it's like looking for a needle in a haystack :-)
Well the 397.xx are okay but i find the new one very stable.
I have no problem with alexis or any other ccminer, EWBF or such..they all run stable and reliable and a bit faster..
Sure people have problems because they oc the way they don't know what they did or do.. you should test and see what is wrong with the newest driver and your build given the fact that the years old alexis still work like a charm even with the newest
There is no excuse to not do it...
I have no problem with alexis or any other ccminer, EWBF or such..they all run stable and reliable and a bit faster..
Sure people have problems because they oc the way they don't know what they did or do.. you should test and see what is wrong with the newest driver and your build given the fact that the years old alexis still work like a charm even with the newest
There is no excuse to not do it...
It simply just report no cards found.
and then instantly crashes...
I have 1080Ti's in various rigs..
Well, it's obviously a problem with the last driver.and then instantly crashes...
I have 1080Ti's in various rigs..
As I said before, I didn't start testing with this driver, but I've heard of problems with it.
I can just recommend to keep driver up to 397.x
In all cases, when a rig is full operational and in production, I recommend to keep its configuration as is, unless you're sure you get a big advantage in upgrading.
It simply just report no cards found.
and then instantly crashes...
I have 1080Ti's in various rigs..
and then instantly crashes...
I have 1080Ti's in various rigs..
Doesn't work with the latest nvidia driver for me 398.58 while alexis miner with Cuda 7.5 32bit does..
Any ideas?
HiAny ideas?
I didn't test last driver, it seems quite unstable.
What is your configuration ? Cards, OC settings and intensity, virtual memory sizing, algo, pool ?
Doesn't work with the latest nvidia driver for me 398.58 while alexis miner with Cuda 7.5 32bit does..
Any ideas?
Any ideas?
Hey.
After a couple of hours mining Phi2, when switching back from devfee mining I receive an error all CUDA-capable devices are busy or unavailable. Randomly, but occasionally on several machines. Any suggestions? thanks
HiAfter a couple of hours mining Phi2, when switching back from devfee mining I receive an error all CUDA-capable devices are busy or unavailable. Randomly, but occasionally on several machines. Any suggestions? thanks
What is your configuration ? Cards, OC settings and intensity, virtual memory sizing ?
And obv, do you use last 3.0.5 version ?
Hey.
After a couple of hours mining Phi2, when switching back from devfee mining I receive an error all CUDA-capable devices are busy or unavailable. Randomly, but occasionally on several machines. Any suggestions? thanks
After a couple of hours mining Phi2, when switching back from devfee mining I receive an error all CUDA-capable devices are busy or unavailable. Randomly, but occasionally on several machines. Any suggestions? thanks
Generally, a stratum connection interruption comes from the pool, or from your Internet connection.
But the miner reconnects (except if the pool is down, in this case after 5 attempts it switches to the next pool in the list)
But the miner reconnects (except if the pool is down, in this case after 5 attempts it switches to the next pool in the list)
Agreed, still having stratum connection interruptions occasionally it is noticable on the hashrate.
I think pickaxe is better with auto diff (and not only with auto diff, imo)
You should try and compare.
You should try and compare.
The automatic difficulty is not reliable for my tests on bsod atleast. It was too low and was getting horrible hashrate poolside.
Thank you for the release.
I think this miner performs well and on par with Cryptodredge if you setup the stratum difficulty manually.
I think this miner performs well and on par with Cryptodredge if you setup the stratum difficulty manually.
Two things to focus on :
- Fine tuning of intensity : for example, an intensity of 19 or 19.5 if fine for 1080 Ti
- Difficulty : best way is to run with automatic diff from pool, then after stabilization, examine choosen diff from pool and force it in pool parameters
To force manually difficulty, change the "pass" parameter by adding a "d=" item :
- in config file : "pass": "c=COIN,d=XX"
- in command line : -p c=COIN,d=XX
replace COIN by coin code (ex: LUX) and XX by the wanted difficulty (ex: 48)
By the way, don't forget to define several pools in the coin config file : if a pool fails or can't be reached, CryptoGen automatically switches to the next pool in the list.
This way, you never lose money !
Thank you for the release.
I think this miner performs well and on par with Cryptodredge if you setup the stratum difficulty manually.
I think this miner performs well and on par with Cryptodredge if you setup the stratum difficulty manually.
Hi guys
A new version v3.0.5 is available here :
https://github.com/genminer/cryptogen/releases/tag/v3.0.5
Happy mining !
A new version v3.0.5 is available here :
https://github.com/genminer/cryptogen/releases/tag/v3.0.5
- Improvement on stratum disconnect management
- Reinforcement of pool switching processing
- Some optimizations for best hashrates
Happy mining !
I'm testing this miner, but I have a problem. When it starts mining the dev fee and connects to the dev pool it cannot restore to mine pool after that is the connection always goes to timeout.
Hmm. First time I see this.
What is the pool ?
pickaxe
I'm testing this miner, but I have a problem. When it starts mining the dev fee and connects to the dev pool it cannot restore to mine pool after that is the connection always goes to timeout.
Hmm. First time I see this.
What is the pool ?
pickaxe
I'm testing this miner, but I have a problem. When it starts mining the dev fee and connects to the dev pool it cannot restore to mine pool after that is the connection always goes to timeout.
Hmm. First time I see this.
What is the pool ?
I'm testing this miner, but I have a problem. When it starts mining the dev fee and connects to the dev pool it cannot restore to mine pool after that is the connection always goes to timeout.
I tried on 3 different yiimp based pools. I have 2 small rigs and it's also possible that the dev fee starts to mine not in sync at different times and makes it look like a lower average hashrate on the pool side.
That's probable : dev fee starts randomly during first hour of mining.
I tried on 3 different yiimp based pools. I have 2 small rigs and it's also possible that the dev fee starts to mine not in sync at different times and makes it look like a lower average hashrate on the pool side.
I tested this miner for 24 hours and I actually got better results with coolminer and ccminer 2.3 . The cryptogen displayed hashrate is higher but the real pool rate is lower. On the other side coolminer and tpruvot ccminer show a little lower on comp but the real on the hash on pool is higher.
Which algo / coin / pool did you test ?Some combinations are better than others.
I tested this miner for 24 hours and I actually got better results with coolminer and ccminer 2.3 . The cryptogen displayed hashrate is higher but the real pool rate is lower. On the other side coolminer and tpruvot ccminer show a little lower on comp but the real on the hash on pool is higher.
3.0.4 is still slow poolside on bsod.pw. I saw 3.0.5 being used on pickaxe.pro but couldnt find it in github. any worthy changes?
3.0.5 still in test. Not yet released 
3.0.4 is still slow poolside on bsod.pw. I saw 3.0.5 being used on pickaxe.pro but couldnt find it in github. any worthy changes?
Hi guys
A new version v3.0.4 is available here :
https://github.com/genminer/cryptogen/releases/tag/v3.0.4
A new version v3.0.4 is available here :
https://github.com/genminer/cryptogen/releases/tag/v3.0.4
- Some improvements on x17 algo
- Fixed bug on reported pool hashrate
We dont have all infos on pool fees.
But dont worry guys.
If I find a bug, I'll push a new release on github
But dont worry guys.
If I find a bug, I'll push a new release on github
I'm facing the same issue, my local hashrate is 32-33 Mh/s, but at BSOD pool reported 17-22 Mh/s (2x GTX1080Ti and 5x GTX1070).
Just thinking, it may be related to the dev pool fee. It's probably when the miner connected to the dev pool, the reported hashrate to the main pool may decrease due to delayed time.
Just thinking, it may be related to the dev pool fee. It's probably when the miner connected to the dev pool, the reported hashrate to the main pool may decrease due to delayed time.
I'm investigating.
Currently tracking a possible sneaky bug on shares validation.
Currently tracking a possible sneaky bug on shares validation.
I can confirm that pool and miner hashrate are not consistent.
I tested for several hours although on the miner it shows really good numbers with 17mh for 2x 1080ti and 1x 1070. but on the pool it is at least 30% lower consistently.
I tested for several hours although on the miner it shows really good numbers with 17mh for 2x 1080ti and 1x 1070. but on the pool it is at least 30% lower consistently.
Same here
Guys can you tell me on what pools ?
I'll test on them.
I'll test on them.
I can confirm that pool and miner hashrate are not consistent.
I tested for several hours although on the miner it shows really good numbers with 17mh for 2x 1080ti and 1x 1070. but on the pool it is atleast 30% lower consistently.
I tested for several hours although on the miner it shows really good numbers with 17mh for 2x 1080ti and 1x 1070. but on the pool it is atleast 30% lower consistently.
There is something horribly wrong with this miner.
I tested with PHI2 Lux
I tested on 3 different pools
My local hashrate is 51.8Mh. The reported hashrate at the pool is always between 8 and 16Mh/s
Tested and re tested. Different pools and also on 3 of my rigs. Always the same.
Something is terribly wrong with it
That's normal.I tested with PHI2 Lux
I tested on 3 different pools
My local hashrate is 51.8Mh. The reported hashrate at the pool is always between 8 and 16Mh/s
Tested and re tested. Different pools and also on 3 of my rigs. Always the same.
Something is terribly wrong with it
Pools calculate hashrate depending on submitted shares during last 5 minutes. And so, hashrate is not linear and regular.
All miners do the same.
With a hashrate of 38 MH/s, the pool can show me 20 or 60.
You should test for a while to have an good idea of incomes.
By the way, 51 MH/s ? What's your config ? 7-8 x 1080 Ti ?
There is something horribly wrong with this miner.
I tested with PHI2 Lux
I tested on 3 different pools
My local hashrate is 51.8Mh. The reported hashrate at the pool is always between 8 and 16Mh/s
Tested and re tested. Different pools and also on 3 of my rigs. Always the same.
Something is terribly wrong with it
I tested with PHI2 Lux
I tested on 3 different pools
My local hashrate is 51.8Mh. The reported hashrate at the pool is always between 8 and 16Mh/s
Tested and re tested. Different pools and also on 3 of my rigs. Always the same.
Something is terribly wrong with it
Quote
On phi2 I get :
TDP 60%, +100 core, -500 mem, intensity 20 : 6.5 to 6.9 kH/s, temp 40-45°
Same with TDP max : 7.2 to 7.5 kH/s, temp 52-56°
just raise slowly intensity, maybe 19.5 can be the max, depends on cards
TDP 60%, +100 core, -500 mem, intensity 20 : 6.5 to 6.9 kH/s, temp 40-45°
Same with TDP max : 7.2 to 7.5 kH/s, temp 52-56°
just raise slowly intensity, maybe 19.5 can be the max, depends on cards
and 6.5 to 6.9 Mh/s ?
Lol yes, MH/s, not kH/s
Im quite tired, time to find a coffee
Quote
On phi2 I get :
TDP 60%, +100 core, -500 mem, intensity 20 : 6.5 to 6.9 kH/s, temp 40-45°
Same with TDP max : 7.2 to 7.5 kH/s, temp 52-56°
just raise slowly intensity, maybe 19.5 can be the max, depends on cards
TDP 60%, +100 core, -500 mem, intensity 20 : 6.5 to 6.9 kH/s, temp 40-45°
Same with TDP max : 7.2 to 7.5 kH/s, temp 52-56°
just raise slowly intensity, maybe 19.5 can be the max, depends on cards
and 6.5 to 6.9 Mh/s ?
Quote
On phi2 I get :
TDP 60%, +100 core, -500 mem, intensity 20 : 6.5 to 6.9 kH/s, temp 40-45°
Same with TDP max : 7.2 to 7.5 kH/s, temp 52-56°
just raise slowly intensity, maybe 19.5 can be the max, depends on cards
TDP 60%, +100 core, -500 mem, intensity 20 : 6.5 to 6.9 kH/s, temp 40-45°
Same with TDP max : 7.2 to 7.5 kH/s, temp 52-56°
just raise slowly intensity, maybe 19.5 can be the max, depends on cards
what video card?
on MSI GTX 1080 Ti Gaming X 11G
Its a few better than Aorus GTX 1080 Ti Xtreme 11G
Quote
On phi2 I get :
TDP 60%, +100 core, -500 mem, intensity 20 : 6.5 to 6.9 kH/s, temp 40-45°
Same with TDP max : 7.2 to 7.5 kH/s, temp 52-56°
just raise slowly intensity, maybe 19.5 can be the max, depends on cards
TDP 60%, +100 core, -500 mem, intensity 20 : 6.5 to 6.9 kH/s, temp 40-45°
Same with TDP max : 7.2 to 7.5 kH/s, temp 52-56°
just raise slowly intensity, maybe 19.5 can be the max, depends on cards
what video card?
there are the results of testing on phi2?
On phi2 I get :TDP 60%, +100 core, -500 mem, intensity 20 : 6.5 to 6.9 kH/s, temp 40-45°
Same with TDP max : 7.2 to 7.5 kH/s, temp 52-56°
just raise slowly intensity, maybe 19.5 can be the max, depends on cards
there are the results of testing on phi2?
PHI2? it not profit, i tested
Not phi2, phi. But it may change.
PHI2? it not profit, i tested
This looks a lot like ccminer, which is licensed under GPLv3, which means you need to also include the source code with your release.
someone did some test? in lyra2z?
Thanhtamtg seemed satisfied :
Great miner for lyra2z!
someone did some test? in lyra2z?
on what algo is dev fee
dev fee too high! How to reduce dev fee to 1% Sir?
Simple : just launch with option --donate=1
Great miner for lyra2z!
Hi
Min dev fee is capped to 1.0.
Glad lyra2z is ok for you.
dev fee too high! How to reduce dev fee to 1% Sir?
Simple : just launch with option --donate=1
Great miner for lyra2z!
dev fee too high! How to reduce dev fee to 1% Sir?
Simple : just launch with option --donate=1
dev fee too high! How to reduce dev fee to 1% Sir?
Looks good I'll give it a try. Will see if I can get some benchmarks setup to compare.
This is the best method, indeed.
it is always the same hashrate as other miners. so why ?
Hmm did you try, with the same config : algo, intensity, OC settings (my examples are for 70% power) ?Last but not least, my miner is quite good for new phi2 algo. Lux miners know :-)
Looks good I'll give it a try. Will see if I can get some benchmarks setup to compare.
it is always the same hashrate as other miners. so why ?
New miner, great. Do you have any benchmark for 10xx cards?
Well, it depends on the card, the intensity, the algo, the oc settings and the chip lottery.
Some are better than others.
For example, with a 1080ti 70% TDP, +100 Core, -400 Mem :
x17 algo gives around 18-21 MH/s
Phi algo gives around 33-36 MH/s
With a 1050ti 90% TDP,+0 Core, -200 Mem :
x17 gives around 4.5-5.0 MH/s
phi gives around 6.5-7.5 MH/s
Personally I prefer stability and low temperatures to save the hardware.
New miner, great. Do you have any benchmark for 10xx cards?
Yeah benchmarks would be a good thing which would probably me persuade me to use this.
Simply claiming "this hashes faster" than other miners might not enough to sway the public. Don't get me wrong, like what other posters have said, I really also do admire the effort you've put into making this, it's just that we need more tangible evidence.
Great! Allow me to be the first to congratulate you on launching your miner.
I really haven't personally tried this yet but everything looks in order and professionally done. Doesn't seem like this much effort was done just to scam people. I wish you nothing but the best for the success of your miner.
I really haven't personally tried this yet but everything looks in order and professionally done. Doesn't seem like this much effort was done just to scam people. I wish you nothing but the best for the success of your miner.
Thank you !
New miner, great. Do you have any benchmark for 10xx cards?
Great! Allow me to be the first to congratulate you on launching your miner.
I really haven't personally tried this yet but everything looks in order and professionally done. Doesn't seem like this much effort was done just to scam people. I wish you nothing but the best for the success of your miner.
I really haven't personally tried this yet but everything looks in order and professionally done. Doesn't seem like this much effort was done just to scam people. I wish you nothing but the best for the success of your miner.
____ ____ _ ____ ____ ____ ____ ____ __
| __\| o \||_/\| o \|_ _\| || _\| __\| \|\
| \__| <_| __/| __/ || | o || [ \| ]_| \|
|___/|/\_/|/ |/ |/ |___/|___/|___/|/\_/
Latest version is v3.0.5
Supports phi2 Luxcoin new algo
DOWNLOAD :
* Windows : https://github.com/genminer/cryptogen/releases
* Linux : not yet
HARDWARE / SYSTEM NEEDED :
- OS : Windows 10 x64 (pro or enterprise recommended)
- GPUs : 98x / 10xx cards (1080ti 8GB+ recommended :-)
- Recent nVidia drivers up to versions 397.x, with compute capability 5.0 and beyond.
Avoid version 398.x as it seems to create problems.
FEATURES :
- Built for nVidia with CUDA 7.5, 32bits version (anyway faster than 64bits version)
- New optimized code with special portions. Effective hashrate is higher, without power overkill.
- Up to 16 GPUs can be used.
- Supports Stratum versions
- Shows detailed mining information and hashrate for each card.
SPECIAL FEATURES :
- Supplied batch file allows easier choice for mining.
- You may create configuration files with pools, one file for each coin. Much simple to manage.
- Up to 16 pools in each configuration file.
- Automatic watchdog, auto-terminate if too many errors occurs (--max-rejects, default=7)
- Inactivity watchdog, auto-terminate if program stucks more than 120s.
- Automatic failover to next pool if current doesn't work.
- Miner can be restarted if too many blocks pass without submission (-M, --max-blocks-null)
- Special parameters can be used in the configuration file / pools zone (%WORKER%, %DIFF%)
INSTALLATION GUIDE :
- Unzip downloaded file into desired folder
- Update cryptogen.*.conf files with your own information (pools, wallet addresses, etc)
- Feel free to add new pools in .conf files
- Feel free to add new conf files for your preferred coins.
- Update file CRYPTOGEN-MINE.bat to choose coin to mine.
- Execute (double-click) CRYPTOGEN-MINE.bat
CONFIGURATION FILES :
The batch file CRYPTOGEN-MINE.bat uses one configuration file for each coin to mine.
These files must be in JSON format, some are provided as examples.
Some options (like -w or -z) define "tags" values usable in config file.
FREE SOFTWARE :
Using this software is free, however, a default developer fee of 2% is applied. During each cycle of 6000 seconds (100 minutes),
the software will mine 120s for the developer. One don't know in advance when the developer mining will occur during the cycle.
You can reduce the fee, anyway your contribution is highly appreciated. If you don't agree with this, don't use this software.
COMMAND LINE OPTIONS :
-a, --algo=ALGO Specify the algorithm to use
bastion Hefty bastion
bitcore Timetravel-10
blake Blake256-14rounds(SFR)
blake2s Blake2s (NEVA/XVG/XSH)
blakecoin Blake256-8rounds (BLC)
bmw BMW 256
cryptolight AEON cryptonight(MEM / 2)
cryptonight XMR cryptonight
c11 C11/flax (AXS/CHC/SPD/IMC/JLG/DXC/ANU)
decred Blake256-14rounds(DCR)
deep Deepcoin
dmd-gr Diamond - Groestl
equihash Zcash Equihash
fresh Freshcoin(shavite 80)
fugue256 Fuguecoin
groestl Groestlcoin
hmq1725 Doubloons/Espers
hsr X13+SM3 (Hshare)
jackpot JHA v8
keccak keccak256 (Maxcoin)
keccakc Keccak - 256 (CreativeCoin)
lbry Lbry (Library Credits)
luffa Joincoin
lyra2 CryptoCoin
lyra2v2 VertCoin
lyra2z ZeroCoin(3rd impl)
myr-gr Myriad-Groestl (SFR/AUR/DGB/XVG/MYR)
neoscrypt Neoscrypt (FTC/PXC/UFO)
nist5 NIST5 (Talkcoin/Power)
penta Pentablake hash(5x Blake 512)
phi PHI1612 (LUX/FLM/SERA)
phi2 PHI v2 (LUX since block 300K)
polytimos Politimos
quark Quark (Quarkcoin)
qubit Qubit
sha256d SHA256d (bitcoin)
sha256t SHA256 x3
sia Sia (SIAcoin)
sib X11+gost (Sibcoin)
scrypt Scrypt
scrypt-jane Scrypt-jane Chacha
skein Skein SHA2 (AUR/DGB/SKC)
skein2 Double Skein (Woodcoin)
vcash Blake256-8rounds (XVC)
skunk Skein Cube Fugue Streebog
s3 S3 (1Coin)
timetravel Machinecoin permuted x8
tribus Denarius
vanilla Blake256-8 (VNL)
veltor Thorsriddle streebog
whirlcoin Old Whirlcoin (Whirlpool algo)
whirlpool Whirlpool (JoinCoin)
x11 X11 (DarkCoin)
x11evo Permuted x11 (Revolver)
x12 X12 (GalaxyCash)
x13 X13 (MaruCoin)
x14 X14 (BernCoin)
x15 X15 (Joincoin)
x15 X15
x16r X16R (Raven)
x16s X16S
x17 X17 (XVG)
wildkeccak Boolberry
zr5 ZR5 (ZiftrCoin)
--api-remote Allow remote control, like pool switching
-b, --api-bind=port IP:port for the miner API (ex: 127.0.0.1:4068),
0=disabled (default disabled)
-B, --background Run the miner in the background
--benchmark Run in offline benchmark mode
--cert=FILE Certificate for mining server using SSL
-c, --config=FILE Load a JSON-format configuration file
--cputest Debug hashes from cpu algorithms
--cpu-affinity Set process affinity to cpu core(s), mask 0x3 for cores 0 and 1
--cpu-priority Set process priority (default: 3) 0 idle, 2 normal to 5 highest
--cuda-schedule Set device threads scheduling mode (default: auto)
-D, --debug Enable debug output
-d, --devices Comma separated list of CUDA devices to use.
Device IDs start counting from 0!Alternatively takes
string names of your cards like gtx780ti or gt640#2
(matching 2nd gt640 in the PC)
-f, --diff-factor Divide difficulty by this factor (default 1.0)
--donate Percentage of time to donate to the developer
-h, --help Display this help text and exit
-i, --intensity=N[,N] GPU intensity 8.0-25.0 (default: auto)
Decimals are allowed for fine tuning
-m, --diff-multiplier Multiply difficulty by this value (default 1.0)
-M, --max-blocks-null Maximum quantity of blocks without submit before
terminating (default no limit)
--max-rejects Maximum quantity of rejected blocks before terminating
(value between 3 and 32, default=7).
--max-temp=N Only mine if gpu temp is less than specified value
--max-rate=N[KMG] Only mine if net hashrate is less than specified value
--max-diff=N Only mine if net difficulty is less than specified value
Can be tuned with --resume-diff=N to set a resume value
-n, --ndevs List cuda devices
-N, --statsavg Number of samples used to compute hashrate (default: 30)
--no-color Disable colored output
--no-extranonce Disable extranonce subscribe on stratum
--no-gbt Disable getblocktemplate support (height check in solo)
--no-longpoll Disable X-Long-Polling support
--no-stratum Disable X-Stratum support
-o, --url=URL URL of mining server
-O, --userpass=U:P username:password pair for mining server
-p, --pass=PASSWORD Password for mining server
-P, --protocol-dump Verbose dump of protocol-level activities
-q, --quiet Disable per-thread hashmeter output
-R, --retry-pause=N Time to pause between retries, in seconds (default: 30)
-r, --retries=N Number of times to retry if a network call fails
(default: retry indefinitely)
-s, --scantime=N Upper bound on time spent scanning current work when
long polling is unavailable, in seconds (default: 60)
-T, --timeout=N Network timeout, in seconds (default: 300)
-t, --threads=N Number of miner threads (default: number of nVidia GPUs)
--time-limit Maximum time (seconds) to mine before exiting the program.
--trust-pool Trust the max block reward vote (maxvote) sent by the pool
-u, --user=USERNAME Username for mining server
--vote=VOTE Vote (for decred and HeavyCoin)
-V, --version Display version information and exit
-x, --proxy=[PROTOCOL://]HOST[:PORT] Connect through a proxy
-z, --diff=0.0 Set wanted difficulty, to be used in pool file as DIFF
When reach, end program
--watch-timeout Timeout in seconds for inactivity. Value between 30 and 3600,
default=120, 0 to disable inactivity watchdog.
--watch-quiet Dont display watchdog living messages
-w, --worker=name Set worker name, to be used in pool file as WORKER
default : computer name.
GPUs options :
--mem-clock=3505 Set the gpu memory boost clock
--gpu-clock=1150 Set the gpu engine boost clock
--plimit=100 Set the gpu power limit in percentage
--tlimit=80 Set the gpu thermal limit in degrees
--led=100 Set the logo led level (0=disable, 0xFF00FF for RVB)
VERSION HISTORY :
See details on https://github.com/genminer/cryptogen
Jump to: