Quark +50kH on 750Ti
-160kH on 980GTX.
-160kH on 980GTX.
Hmm. Looks like I need to revert the last change on the compute 5.2 devices.
Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 949. (Read 2347664 times)
Hmm. Looks like I need to revert the last change on the compute 5.2 devices.
Quark +50kH on 750Ti
-160kH on 980GTX.
-160kH on 980GTX.
Not sure it's related, but during the last week/couple weeks I, at times, get 1/4 hashrate from every card, on ccminer restart.
Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
When you say "ccminer restart". Is that using ctrl-c to close the miner down? Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
With the 1/4 hashrate, if you go into nvidia-settings are the cards stuck with a 0 performance level (i.e. lowest)?
I was noticing something like the above (one of my 750Ti's {I run two, but of different manufacturers} would get stuck with a 0 performance level after a ctrl-c of ccminer), and I just reverted to using the kill command, instead of ccminer's internal stop command. Haven't had the issue since.
(Also I sent you a message pallas.)
Yes by clicking ctrl-c.
I will look at performance levels when that happens again, didn't think of it, thanks.
I've seen the PM just didn't have time to try it ;-)
I have had cards do that, usually following a crash, both Windows and Linux.
I have also noticed that Ctrl-C can also cause it. Killing the task from a seperate shell seems to have
fewer problems.
I experienced it right now, after ctrl-c.
Cards stay in P8 (power saving, idle state)
-NVLM working in linux (merged by flipclip) (tpruvot's implementation)
-New time limit option (merged by flipclip) (tpruvot's implementation) (mine for a given number of seconds and then exit)
-Corrected hang on stratum failures (T Nelson)
-Fixed multiple -i and -X values. (merged by flipclip) (You can now set individual intensites for each of the gpu's)
-Faster lyra2v2 on compute 5.2 devices.
-Faster quark on 750ti.
1.5.67(sp-MOD) is available here: (14-sep-2015)
https://github.com/sp-hash/ccminer/releases/
The sourcecode is available here:
https://github.com/sp-hash/ccminer
-New time limit option (merged by flipclip) (tpruvot's implementation) (mine for a given number of seconds and then exit)
-Corrected hang on stratum failures (T Nelson)
-Fixed multiple -i and -X values. (merged by flipclip) (You can now set individual intensites for each of the gpu's)
-Faster lyra2v2 on compute 5.2 devices.
-Faster quark on 750ti.
1.5.67(sp-MOD) is available here: (14-sep-2015)
https://github.com/sp-hash/ccminer/releases/
The sourcecode is available here:
https://github.com/sp-hash/ccminer
release 66 had a bug that could cause the miner to hang on stratum failure. (disconnects)
I believe T Nelson fixed it with this commit:
https://github.com/sp-hash/ccminer/commit/331a437d6a0093050eeacd25d1707c1a1b4cd386
I believe T Nelson fixed it with this commit:
https://github.com/sp-hash/ccminer/commit/331a437d6a0093050eeacd25d1707c1a1b4cd386
Not sure it's related, but during the last week/couple weeks I, at times, get 1/4 hashrate from every card, on ccminer restart.
Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
When you say "ccminer restart". Is that using ctrl-c to close the miner down? Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
With the 1/4 hashrate, if you go into nvidia-settings are the cards stuck with a 0 performance level (i.e. lowest)?
I was noticing something like the above (one of my 750Ti's {I run two, but of different manufacturers} would get stuck with a 0 performance level after a ctrl-c of ccminer), and I just reverted to using the kill command, instead of ccminer's internal stop command. Haven't had the issue since.
(Also I sent you a message pallas.)
Yes by clicking ctrl-c.
I will look at performance levels when that happens again, didn't think of it, thanks.
I've seen the PM just didn't have time to try it ;-)
I have had cards do that, usually following a crash, both Windows and Linux.
I have also noticed that Ctrl-C can also cause it. Killing the task from a seperate shell seems to have
fewer problems.
I submitted a bether launchconfig for blake-512. Another quark speedup on the 750ti
building release 67
building release 67
Not sure it's related, but during the last week/couple weeks I, at times, get 1/4 hashrate from every card, on ccminer restart.
Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
it could be due to tasks requiring "some cpu power" are running in the background (anti-virus, botnet (lol), stuff like that...). Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
I usually use an elevated priority (cpu-priority 2 or something) to make sure it doesn't happen)
Not likely in my case: it's a vanilla Ubuntu machine used only for mining, well updated and cared for ;-)
Not sure it's related, but during the last week/couple weeks I, at times, get 1/4 hashrate from every card, on ccminer restart.
Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
it could be due to tasks requiring "some cpu power" are running in the background (anti-virus, botnet (lol), stuff like that...). Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
I usually use an elevated priority (cpu-priority 2 or something) to make sure it doesn't happen)
I forgot to say that its like 50/50 that ccminer stop mining and just stay there. Or it will just crash and close itself.
I need to reboot after either of that happends to get full hashrate again.
I need to reboot after either of that happends to get full hashrate again.
I have some stability problems with two of my "leftovers" nvidia rigs.
One of them are powering down the whole system after mining for a couple of hours and the other one is ccminer just crashing on randomly.
I have identical hardware in all my the rigs (NVIDIA/AMD), mobos, cpu, ram, risers and psus.
In one rig i have one EVGA FTW 750Ti and the other rig i have one EVGA SC 750Ti + Gigabyte Windforce 750Ti.
The one powering down is the rig with two cards.
At the same time i have two rigs running five 750Ti:s each at 36Mhs Quark totally stable for weeks.
This is really annoying because they are also crashing with stock settings on the gpu:s. Temps are really low also so i dont get this.
All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.
Anyone have a clue what could be the problem ?
Can i find logs from ccminer somewhere ?
One of them are powering down the whole system after mining for a couple of hours and the other one is ccminer just crashing on randomly.
I have identical hardware in all my the rigs (NVIDIA/AMD), mobos, cpu, ram, risers and psus.
In one rig i have one EVGA FTW 750Ti and the other rig i have one EVGA SC 750Ti + Gigabyte Windforce 750Ti.
The one powering down is the rig with two cards.
At the same time i have two rigs running five 750Ti:s each at 36Mhs Quark totally stable for weeks.
This is really annoying because they are also crashing with stock settings on the gpu:s. Temps are really low also so i dont get this.
All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.
Anyone have a clue what could be the problem ?
Can i find logs from ccminer somewhere ?
Start swapping hardware one component at a time between a good rig and a bad rig until the good rig goes bad
and the bad rig goes good. Then you've identified the faulty component.
Some more info would be helpfull. Is there any error message when ccminer crashes? Can mining be resumed or
does the system need a reboot?
Here's something that can be added to a bat file to check for a crash.
tasklist /FI "IMAGENAME eq ccminer.exe" 2>NUL | find /I /N "%1">NUL
if "%ERRORLEVEL%" NEQ "0" goto restart_ccminer_becauuse_it_died
If i just close the miner and start it up again i will get really bad hashrate. So a reboot is needed after every "crash"
I have been testing replacing some hardware like psu and ram but still the same problems with these two rigs. I am starting to think that these gpu:s are someway faulty. All these three cards are used cards that i have been buying lately.
And I have been mining with release 66, so far is stable for me.
I am using r61 on all rigs so that build should not be the problem.
I am watching some of my 750Ti cards pushing above 7.3Mhs as we speak. I see no increase in speed with the other releases for my 750Ti cards.
Not sure it's related, but during the last week/couple weeks I, at times, get 1/4 hashrate from every card, on ccminer restart.
Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
When you say "ccminer restart". Is that using ctrl-c to close the miner down? Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
With the 1/4 hashrate, if you go into nvidia-settings are the cards stuck with a 0 performance level (i.e. lowest)?
I was noticing something like the above (one of my 750Ti's {I run two, but of different manufacturers} would get stuck with a 0 performance level after a ctrl-c of ccminer), and I just reverted to using the kill command, instead of ccminer's internal stop command. Haven't had the issue since.
(Also I sent you a message pallas.)
Yes by clicking ctrl-c.
I will look at performance levels when that happens again, didn't think of it, thanks.
I've seen the PM just didn't have time to try it ;-)
Not sure it's related, but during the last week/couple weeks I, at times, get 1/4 hashrate from every card, on ccminer restart.
Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
When you say "ccminer restart". Is that using ctrl-c to close the miner down? Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
With the 1/4 hashrate, if you go into nvidia-settings are the cards stuck with a 0 performance level (i.e. lowest)?
I was noticing something like the above (one of my 750Ti's {I run two, but of different manufacturers} would get stuck with a 0 performance level after a ctrl-c of ccminer), and I just reverted to using the kill command, instead of ccminer's internal stop command. Haven't had the issue since.
(Also I sent you a message pallas.)
I have some stability problems with two of my "leftovers" nvidia rigs.
One of them are powering down the whole system after mining for a couple of hours and the other one is ccminer just crashing on randomly.
I have identical hardware in all my the rigs (NVIDIA/AMD), mobos, cpu, ram, risers and psus.
In one rig i have one EVGA FTW 750Ti and the other rig i have one EVGA SC 750Ti + Gigabyte Windforce 750Ti.
The one powering down is the rig with two cards.
At the same time i have two rigs running five 750Ti:s each at 36Mhs Quark totally stable for weeks.
This is really annoying because they are also crashing with stock settings on the gpu:s. Temps are really low also so i dont get this.
All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.
Anyone have a clue what could be the problem ?
Can i find logs from ccminer somewhere ?
One of them are powering down the whole system after mining for a couple of hours and the other one is ccminer just crashing on randomly.
I have identical hardware in all my the rigs (NVIDIA/AMD), mobos, cpu, ram, risers and psus.
In one rig i have one EVGA FTW 750Ti and the other rig i have one EVGA SC 750Ti + Gigabyte Windforce 750Ti.
The one powering down is the rig with two cards.
At the same time i have two rigs running five 750Ti:s each at 36Mhs Quark totally stable for weeks.
This is really annoying because they are also crashing with stock settings on the gpu:s. Temps are really low also so i dont get this.
All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.
Anyone have a clue what could be the problem ?
Can i find logs from ccminer somewhere ?
Start swapping hardware one component at a time between a good rig and a bad rig until the good rig goes bad
and the bad rig goes good. Then you've identified the faulty component.
Some more info would be helpfull. Is there any error message when ccminer crashes? Can mining be resumed or
does the system need a reboot?
Here's something that can be added to a bat file to check for a crash.
tasklist /FI "IMAGENAME eq ccminer.exe" 2>NUL | find /I /N "%1">NUL
if "%ERRORLEVEL%" NEQ "0" goto restart_ccminer_becauuse_it_died
If i just close the miner and start it up again i will get really bad hashrate. So a reboot is needed after every "crash"
I have been testing replacing some hardware like psu and ram but still the same problems with these two rigs. I am starting to think that these gpu:s are someway faulty. All these three cards are used cards that i have been buying lately.
And I have been mining with release 66, so far is stable for me.
Not sure it's related, but during the last week/couple weeks I, at times, get 1/4 hashrate from every card, on ccminer restart.
Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
Never happened before.
It could be due to the driver, the kernel or whatever; or it could be some recent modification to ccminer...
I have some stability problems with two of my "leftovers" nvidia rigs.
One of them are powering down the whole system after mining for a couple of hours and the other one is ccminer just crashing on randomly.
I have identical hardware in all my the rigs (NVIDIA/AMD), mobos, cpu, ram, risers and psus.
In one rig i have one EVGA FTW 750Ti and the other rig i have one EVGA SC 750Ti + Gigabyte Windforce 750Ti.
The one powering down is the rig with two cards.
At the same time i have two rigs running five 750Ti:s each at 36Mhs Quark totally stable for weeks.
This is really annoying because they are also crashing with stock settings on the gpu:s. Temps are really low also so i dont get this.
All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.
Anyone have a clue what could be the problem ?
Can i find logs from ccminer somewhere ?
One of them are powering down the whole system after mining for a couple of hours and the other one is ccminer just crashing on randomly.
I have identical hardware in all my the rigs (NVIDIA/AMD), mobos, cpu, ram, risers and psus.
In one rig i have one EVGA FTW 750Ti and the other rig i have one EVGA SC 750Ti + Gigabyte Windforce 750Ti.
The one powering down is the rig with two cards.
At the same time i have two rigs running five 750Ti:s each at 36Mhs Quark totally stable for weeks.
This is really annoying because they are also crashing with stock settings on the gpu:s. Temps are really low also so i dont get this.
All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.
Anyone have a clue what could be the problem ?
Can i find logs from ccminer somewhere ?
Start swapping hardware one component at a time between a good rig and a bad rig until the good rig goes bad
and the bad rig goes good. Then you've identified the faulty component.
Some more info would be helpfull. Is there any error message when ccminer crashes? Can mining be resumed or
does the system need a reboot?
Here's something that can be added to a bat file to check for a crash.
tasklist /FI "IMAGENAME eq ccminer.exe" 2>NUL | find /I /N "%1">NUL
if "%ERRORLEVEL%" NEQ "0" goto restart_ccminer_becauuse_it_died
If i just close the miner and start it up again i will get really bad hashrate. So a reboot is needed after every "crash"
I have been testing replacing some hardware like psu and ram but still the same problems with these two rigs. I am starting to think that these gpu:s are someway faulty. All these three cards are used cards that i have been buying lately.
I have some stability problems with two of my "leftovers" nvidia rigs.
One of them are powering down the whole system after mining for a couple of hours and the other one is ccminer just crashing on randomly.
I have identical hardware in all my the rigs (NVIDIA/AMD), mobos, cpu, ram, risers and psus.
In one rig i have one EVGA FTW 750Ti and the other rig i have one EVGA SC 750Ti + Gigabyte Windforce 750Ti.
The one powering down is the rig with two cards.
At the same time i have two rigs running five 750Ti:s each at 36Mhs Quark totally stable for weeks.
This is really annoying because they are also crashing with stock settings on the gpu:s. Temps are really low also so i dont get this.
All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.
Anyone have a clue what could be the problem ?
Can i find logs from ccminer somewhere ?
One of them are powering down the whole system after mining for a couple of hours and the other one is ccminer just crashing on randomly.
I have identical hardware in all my the rigs (NVIDIA/AMD), mobos, cpu, ram, risers and psus.
In one rig i have one EVGA FTW 750Ti and the other rig i have one EVGA SC 750Ti + Gigabyte Windforce 750Ti.
The one powering down is the rig with two cards.
At the same time i have two rigs running five 750Ti:s each at 36Mhs Quark totally stable for weeks.
This is really annoying because they are also crashing with stock settings on the gpu:s. Temps are really low also so i dont get this.
All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.
Anyone have a clue what could be the problem ?
Can i find logs from ccminer somewhere ?
Start swapping hardware one component at a time between a good rig and a bad rig until the good rig goes bad
and the bad rig goes good. Then you've identified the faulty component.
Some more info would be helpfull. Is there any error message when ccminer crashes? Can mining be resumed or
does the system need a reboot?
Here's something that can be added to a bat file to check for a crash.
tasklist /FI "IMAGENAME eq ccminer.exe" 2>NUL | find /I /N "%1">NUL
if "%ERRORLEVEL%" NEQ "0" goto restart_ccminer_becauuse_it_died
I have some stability problems with two of my "leftovers" nvidia rigs.
One of them are powering down the whole system after mining for a couple of hours and the other one is ccminer just crashing on randomly.
I have identical hardware in all my the rigs (NVIDIA/AMD), mobos, cpu, ram, risers and psus.
In one rig i have one EVGA FTW 750Ti and the other rig i have one EVGA SC 750Ti + Gigabyte Windforce 750Ti.
The one powering down is the rig with two cards.
At the same time i have two rigs running five 750Ti:s each at 36Mhs Quark totally stable for weeks.
This is really annoying because they are also crashing with stock settings on the gpu:s. Temps are really low also so i dont get this.
All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.
Anyone have a clue what could be the problem ?
Can i find logs from ccminer somewhere ?
Also having massive rejected speed at NiceHash from time to time:
One of them are powering down the whole system after mining for a couple of hours and the other one is ccminer just crashing on randomly.
I have identical hardware in all my the rigs (NVIDIA/AMD), mobos, cpu, ram, risers and psus.
In one rig i have one EVGA FTW 750Ti and the other rig i have one EVGA SC 750Ti + Gigabyte Windforce 750Ti.
The one powering down is the rig with two cards.
At the same time i have two rigs running five 750Ti:s each at 36Mhs Quark totally stable for weeks.
This is really annoying because they are also crashing with stock settings on the gpu:s. Temps are really low also so i dont get this.
All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.
Anyone have a clue what could be the problem ?
Can i find logs from ccminer somewhere ?
Also having massive rejected speed at NiceHash from time to time:
Hi guys need help how can automaticly ccminer restart if the miner stops is there a program or a comand to control that?
Thx in advance
Thx in advance
The easiest (and dirtiest) way is to have your miner batch file run in a loop:
:start
ccminer.exe ...
goto start
and have another batch loop running which restarts ccminer periodically:
:start
timeout -t 1800
taskkill -t -f /im ccminer.exe
goto start
That will restart ccminer every 1800 seconds (30 minutes).
That's beautiful... If only a program like MultiMiner was compatible with CCminer... Last I checked it was because CCminer doesn't have a API so other programs can't hook into it.
Wouldn't the first batchfile continually start up lots of instances of ccminer as there isn't a timer and it's a loop? Does it check to see if one instance is running?
This is what I use:
set app=ccminer.exe
set algo=quark
set address=stratum+tcp://xxxx:port#
set user1=xxx.x1 (your username and workername for the pool)
set user2=xxx.x2
set password=x (your worker password)
:start
start "gpu0" /min %app% -a %algo% -s 1 -d 0 -i 19 -R 3 -o %address% -u %user1% -p %password%
start "gpu1" /min %app% -a %algo% -s 1 -d 1 -i 19 -R 3 -o %address% -u %user2% -p %password%
timeout 600 /nobreak
taskkill /im %app% /f
goto start
It will autokill and restart every 10 minutes. Very handy for those pools that have a vardiff that doesn't play nice.
I've seen batchfiles with variables before, not sure why you'd do that. There really isn't that much code. I guess you have two different launch files. Everything else is cool. Would be great to be able to use one batchfile instead of two.
Hi guys need help how can automaticly ccminer restart if the miner stops is there a program or a comand to control that?
Thx in advance
Thx in advance
The easiest (and dirtiest) way is to have your miner batch file run in a loop:
:start
ccminer.exe ...
goto start
and have another batch loop running which restarts ccminer periodically:
:start
timeout -t 1800
taskkill -t -f /im ccminer.exe
goto start
That will restart ccminer every 1800 seconds (30 minutes).
actually I tried to instal win10 twice with the latest drivers at that time, and there were problems with mem hard algo (neoscrypt and lyra). Now with privacy issues, I am not even sure that I will install win10 (I really don't agree with the term of the licence and I don't do anything unlawful)
Yeah, I think I'm going to use win7 until the end of times.
(hope they get sued (again...
) so they change that thing... seriously the terms of licence allows to almost spy into the hdd of their competitors or US competitors for that matter, (if they are asked to...) yeah right... US spies are really getting lazy nowadays...)edit: now we understand why they are releasing it for free (already paid or it will paid itself... )
Jump to: