So I've run into something interesting in using the beta 2.2.1, using cuda 9.
I originally ran the following command line in a bat file.
- ccminer-x64 -a lyra2v2 -d 0 -o stratum+tcp://18.85.34.148:9171 -u Vg39fRFWf2CwAuAXuXzMTs99Jh1ZTaCUDJ -p workwork -t 1 -b 0
After a period of time, it would fail out saying that the result
did not validate with the cpuI messed around with various settings for intensity as well as overclocking (memory, gpu, memory+gpu, various voltage adjustments) and the result always ended with the same error. I noticed that the rate was also slowly decreasing over time.
I also tried --cuda-schedule spin. It actually lasted a bit longer with a higher rate, but it still eventually errored out, the same quickly repeating did not validate with the cpu error message.
So in messing around more, I did the thing you're not supposed to... changed multiple things at once and it resolved the validation check but showed
json-rpc call failed: method not found. As I'm seeing my rates on the server page, I'm guessing (and by a stretch) that this is not a huge problem.
I changed the command line to:
- ccminer-x64 -a lyra2v2 -d 0 -o 18.85.34.148:9171 -u Vg39fRFWf2CwAuAXuXzMTas99Jh1ZTaCUDJ -p workwork -t 1 -b 0 -D 1 (and I just noticed that I added an a to my wallet address for this one... oh well)
- I set my i5-6600k back to stock voltage from lower multipliers, voltage, etc. (trying to reduce overall wattage as kwh here is 0.21)
I wanted to try out adding the NSIGHT_CUDA_DEBUGGER, but I know nothing about coding at the moment so I have no idea where I would put that.
I'm guessing that it was reverting the settings on the cpu back to normal, but I figured I'd mention it in case others were experiencing similar issues
In case it helps I'm currently running that last command line without issue so far connecting to p2pool (18.85.34.148:9171 Cambridge US) at around 37.25 MH/s:
- i5-6600k
- 16 gb ram
- gigabyte z170x gaming 7
- msi sea hawk ek x gtx 1070
(yes, temp never breaks 45) - driver v 384.94
with afterburner currently set to:
- 65% power
- 85 temp limit
- +176 core clock
- +940 memory clock
next testing, hopefully useful is:
- revert command line
- enable spin
- update drivers to 385.69
If things seem to work, it will be at least a few hours between changes.