https://www.dropbox.com/s/hydf3jj7mx0agyr/IMG_2289.MOV?dl=0Now I have a problem with another one of the failures of the program, which has already happened to me several times and I never find a solution.
In this case it is the RIG5, I choose a Neoscrypt coin as Zcore, I teach you in the video that NEoscrypt does with Klaust since basically it is the only good miner of neo, when there are hundreds of coins for this something.
And when I launch it fails, it refers to Neo, to Klaust and I do not know why it also refers to BSD in PHI. In the RIG5 team, Klaust really opens but fails. Now I leave you under the diagnosis. When this happens, it is difficult to fix, and I do not feel like formatting the computer again.
In the rest of RIGS with Neoscrypt and Klaust I have no problems. Other times it has been another RIG and another Something, but sometimes it crosses the information of two coins at a time and fails. because it is clear that what I have chosen from Zcore currency, and I show you the miner and everything.
Let's see if you can dedicate a little time to solve these problems because they become very annoying and they particularly make me lose a lot of time and I only have 5 rigs
DIAGNOSTIC
Initialize diagnostics (20)
Starting Diagnostics. Awesome Miner Remote Agent version: 5.3
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: CcKlaustMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Set clocking start profile: 36, 80 100--150 (when stopping, the following will be used: 5, type: Single, Use: False)
C:\Users\truco\AppData\Roaming\AwesomeMinerService\ccminer-821-cuda91-x64_1\ccminer.exe -i 15 --p d=1024 -a neoscrypt -o stratum+tcp://eu.bsod.pw:2130 -u GWS3EYWeoHPv8TkoxPv1YhB3qhJgy6Djvd.rig4 -b 0.0.0.0:4028 (WindowMode: ConsoleFormat, EngineType: CcKlaustMiner, IsProfitMiner: True)
Configuration:
Configured command line:
-i 15 --p d=1024
Mining Engine Process started, PID: 3260
====================================================================================================
> [2018-07-10 21:35:43] Intensity set to 15, 32768 cuda threads[0m
> ambiguous option -- p
> ccminer 8.21-KlausT (64bit) for nVidia GPUs
> Compiled with Visual Studio 2015 using Nvidia CUDA Toolkit 9.1
>
> Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
> CUDA support by Christian Buchner, Christian H. and DJM34
> Includes optimizations implemented by sp-hash, klaust, tpruvot and tsiv.
>
> Usage: ccminer [OPTIONS]
> Options:
> -a, --algo=ALGO specify the hash algorithm to use
> bitcoin Bitcoin
> blake Blake 256 (SFR/NEOS)
> blakecoin Fast Blake 256 (8 rounds)
> c11 X11 variant
> deep Deepcoin
> dmd-gr Diamond-Groestl
> fresh Freshcoin (shavite 80)
> fugue256 Fuguecoin
> groestl Groestlcoin
> jackpot Jackpot (JHA)
> keccak Keccak-256 (Maxcoin)
> luffa Doomcoin
> lyra2v2 VertCoin
> myr-gr Myriad-Groestl
> neoscrypt neoscrypt (FeatherCoin)
> nist5 NIST5 (TalkCoin)
> penta Pentablake hash (5x Blake 512)
> quark Quark
> qubit Qubit
> sia Siacoin (at pools compatible to siamining.com)
> skein Skein SHA2 (Skeincoin)
> s3 S3 (1Coin)
> x11 X11 (DarkCoin)
> x13 X13 (MaruCoin)
> x14 X14
> x15 X15
> x17 X17 (peoplecurrency)
> vanilla Blake 256 8 rounds
> whirl Whirlcoin (old whirlpool)
> whirlpoolx Vanillacoin
> -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)
> -i --intensity=N GPU intensity 8-31 (default: auto)
> Decimals are allowed for fine tuning
> -f, --diff-factor Divide difficulty by this factor (default 1.0)
> -m, --diff-multiplier Multiply difficulty by this value (default 1.0)
> -o, --url=URL URL of mining server
> -O, --userpass=U:P username:password pair for mining server
> -u, --user=USERNAME username for mining server
> -p, --pass=PASSWORD password for mining server
> --cert=FILE certificate for mining server using SSL
> -x, --proxy=... [PROTOCOL://]HOST[:PORT] connect through a proxy
> -t, --threads=N number of miner threads (default: number of nVidia GPUs)
> -r, --retries=N number of times to retry if a network call fails
> (default: retry indefinitely)
> -R, --retry-pause=N time to pause between retries, in seconds (default: 30)
> -T, --timeout=N network timeout, in seconds (default: 270)
> -s, --scantime=N upper bound on time spent scanning current work when
> long polling is unavailable, in seconds (default: 5)
> -n, --ndevs list cuda devices
> -N, --statsavg number of samples used to display hashrate (default: 30)
> --no-gbt disable getblocktemplate support (height check in solo)
> --no-longpoll disable X-Long-Polling support
> --no-stratum disable X-Stratum support
> -e disable extranonce
> -q, --quiet disable per-thread hashmeter output
> --no-color disable colored output
> -D, --debug enable debug output
> -P, --protocol-dump verbose dump of protocol-level activities
> --cpu-affinity set process affinity to cpu core(s), mask 0x3 for cores 0 and 1
> --cpu-priority set process priority (default: 0 idle, 2 normal to 5 highest)
> --cuda-schedule set CUDA scheduling option:
> 0: BlockingSync (default)
> 1: Spin
> 2: Yield
> -b, --api-bind=... IP address and port number for the miner API (example: 127.0.0.1:4068)
> --logfile=FILE create logfile
> -S, --syslog use system log for output messages
> --syslog-prefix=... allow to change syslog tool name
> -B, --background run the miner in the background
> --benchmark run in offline benchmark mode
> --no-cpu-verify don't verify the found results
> -c, --config=FILE load a JSON-format configuration file
> -V, --version display version information and exit
> -h, --help display this help text and exit
> --mem-clock=N Set the gpu memory max clock (346.72+ driver)
> --gpu-clock=N Set the gpu engine max clock (346.72+ driver)
> --pstate=N (not for 10xx cards) Set the gpu power state (352.21+ driver)
> --plimit=N Set the gpu power limit (352.21+ driver)
====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration
Diagnostics completed
and to clarify that I have it right, I'm going to mine it with another RIG and I show you the Zcore configuration, or any NEO currency, so you can see that it's a rare failure, in the same diagnosis there are weird things. I am losing precious time lately with so many failures.
You must find the fault, because this is very sporadic. will see in the video, the same currency in another rig without problems, in rig5, failure. And klaust is a miner by default. I'm going to have to add it separately as mine to try to fix this.
Between the problems with the OC and this, they make me waste a lot of time and therefore money. It seems that I am the only one who finds mistakes or mistakes.
https://www.dropbox.com/s/qvynqh58j6y50v5/IMG_2290.MOV?dl=0