HEAD@windows never submits any shares.
you need to use --diff 128 (if it is related to lyra2re) 
Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 1211. (Read 2347597 times)
HEAD@windows never submits any shares.
Nice, you finally updated your fork 
the good thing with my complicated relationship with github is that I update only when necessary djm your version is the optimized one with 970-980?
It also add an adjustable throughput, which might be able to increase a little the hashrate over that version (in the limitation of memory bandwidt... ) or decrease it if it is plugged into a monitor (my gtx980 were causing some lag when they were plugged into a monitor)
The current implementation is already optimized for 9xx serie (that's the interest of the calculation using uint2 type actually) however because of the memory bandwidth limitation in the 9xx serie, the 780ti is doing better...
what number your version is doing?
with sp version i'm currently at 7800 hash with one 970(1400 core)
oh that's a new algo, a fast google search tells me that is vertcoin releated, it's something anti-asic?
Nice, you finally updated your fork
the good thing with my complicated relationship with github is that I update only when necessary djm your version is the optimized one with 970-980?
It also add an adjustable throughput, which might be able to increase a little the hashrate over that version (in the limitation of memory bandwidt... ) or decrease it if it is plugged into a monitor (my gtx980 were causing some lag when they were plugged into a monitor)
The current implementation is already optimized for 9xx serie (that's the interest of the calculation using uint2 type actually) however because of the memory bandwidth limitation in the 9xx serie, the 780ti is doing better...
what number your version is doing?
with sp version i'm currently at 7800 hash with one 970(1400 core)
Nice, you finally updated your fork
the good thing with my complicated relationship with github is that I update only when necessary djm your version is the optimized one with 970-980?
It also add an adjustable throughput, which might be able to increase a little the hashrate over that version (in the limitation of memory bandwidt... ) or decrease it if it is plugged into a monitor (my gtx980 were causing some lag when they were plugged into a monitor)
The current implementation is already optimized for 9xx serie (that's the interest of the calculation using uint2 type actually) however because of the memory bandwidth limitation in the 9xx serie, the 780ti is doing better...
what number your version is doing?
with sp version i'm currently at 7800 hash with one 970(1400 core)
Nice, you finally updated your fork
the good thing with my complicated relationship with github is that I update only when necessary djm your version is the optimized one with 970-980?
It also add an adjustable throughput, which might be able to increase a little the hashrate over that version (in the limitation of memory bandwidt... ) or decrease it if it is plugged into a monitor (my gtx980 were causing some lag when they were plugged into a monitor)
The current implementation is already optimized for 9xx serie (that's the interest of the calculation using uint2 type actually) however because of the memory bandwidth limitation in the 9xx serie, the 780ti is doing better...
Nice, you finally updated your fork
the good thing with my complicated relationship with github is that I update only when necessary djm your version is the optimized one with 970-980?
The uint2 keccak made x11 20-25 KHASH faster. Checked in now.
I fixed it now. I am currently working with implementing uint2 into some of the hashingfunctions. (idea from DJM34 lyra implementation)
I have merged all the files from tvpouvet (1.5.1git version)
New beta from github: Should support old cards as well. Compute 3.0 or newer.
http://www.filedropper.com/release19
x11 is down a bit, but hope that it is more stable
source
https://github.com/sp-hash/ccminer/
I think you should check your files on github. There's some stuff missing. New beta from github: Should support old cards as well. Compute 3.0 or newer.
http://www.filedropper.com/release19
x11 is down a bit, but hope that it is more stable
source
https://github.com/sp-hash/ccminer/
I have merged all the files from tvpouvet (1.5.1git version)
New beta from github: Should support old cards as well. Compute 3.0 or newer.
http://www.filedropper.com/release19
x11 is down a bit, but hope that it is more stable
source
https://github.com/sp-hash/ccminer/
New beta from github: Should support old cards as well. Compute 3.0 or newer.
http://www.filedropper.com/release19
x11 is down a bit, but hope that it is more stable
source
https://github.com/sp-hash/ccminer/
Nice, you finally updated your fork
the good thing with my complicated relationship with github is that I update only when necessary
Nice, you finally updated your fork
I have merged my branch with the 1.5.1. (tpouvet) It includes the new Vertcoin algorithm (Lyra) implemented by Djm34. x11 hash is down 50-100khash, because I didn't finish the echo merge to support 2 nounces. Building now.
careful it is an older version... (he doesn't listen when someone asks him to wait 
)
I have merged my branch with the 1.5.1. (tpouvet) It includes the new Vertcoin algorithm (Lyra) implemented by Djm34. x11 hash is down 50-100khash on the 750ti, because I didn't finish the echo merge to support 2 nounces. Building now.
Release 17 reports much better hash power in the pool : about 30-40MH/s
Release 18 reports low hash: 15-25MH/s same config
3x980 + 2x750Ti
I will stay with Release 17 for the 980s.
Release 18 reports low hash: 15-25MH/s same config
3x980 + 2x750Ti
I will stay with Release 17 for the 980s.
[2014-12-08 01:13:50] GPU #5: result for 0014cc00 is not in range: a8cf372c > 1f
Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 309 : unspecified launch failure.
restart pc
happened a few more times on about 3 different cards out of the 6, all cards are overclocked so I adjusted the mem clocks down 50mhz and the core on the cards that seem to fail down 10mhz on the core.
I found a memory leak in x13. With the correct intesity x14 is running faster than x13
Newest release still having same problem.
Finally just removed the popup notifications from my miner.
regedit
DWORD HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting\DontShowUI = "1"
will make WER silently report. Then you can set
DWORD HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting\Disabled = "1"
to stop it from talking to MS.
https://stackoverflow.com/questions/396369/how-do-i-disable-the-debug-close-application-dialog-on-windows-vista
According to event viewer ccminer is crashing about every 50 to 75 minutes. x13 is has been the most profitable algo the last 24 hours.
New binary from git:
Includes some more optimalizations by Schleicher and myself. (Bmw, echo, shavite, fugue, shabal, whirlpool)
Faster x11,x14,x13,x15
http://www.filedropper.com/release18
The sourcecode is available here:
https://github.com/sp-hash/ccminer
My gainward 750ti is peaking at 2,800 MHASH /x11 and 2,210MHASH /x13 at base clocks. But when the card go above 70 degrees, performance is going down.
Includes some more optimalizations by Schleicher and myself. (Bmw, echo, shavite, fugue, shabal, whirlpool)
Faster x11,x14,x13,x15
http://www.filedropper.com/release18
The sourcecode is available here:
https://github.com/sp-hash/ccminer
My gainward 750ti is peaking at 2,800 MHASH /x11 and 2,210MHASH /x13 at base clocks. But when the card go above 70 degrees, performance is going down.
[2014-12-08 01:13:50] GPU #5: result for 0014cc00 is not in range: a8cf372c > 1f
Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 309 : unspecified launch failure.
restart pc
happened a few more times on about 3 different cards out of the 6, all cards are overclocked so I adjusted the mem clocks down 50mhz and the core on the cards that seem to fail down 10mhz on the core.
I found a memory leak in x13. With the correct intesity x14 is running faster than x13
testing your 17 release
6x 750ti overclocked
minercontrol on YAAMP on x13
after trying with the intensity 20.5 After hashing for about 5 min I had a ccminer stopped working crash and had to restart.
upon restart the miner would not hash and got the error with the same ccminer stopped working.
changed intensity to 20.3 and started to hash again for about 5-10 min then i get this error
[2014-12-08 01:13:50] GPU #5: result for 0014cc00 is not in range: a8cf372c > 1f
Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 309 : unspecified launch failure.
restart pc
happened a few more times on about 3 different cards out of the 6, all cards are overclocked so I adjusted the mem clocks down 50mhz and the core on the cards that seem to fail down 10mhz on the core.
after about 10 min hashing had a card fail with the error above.
was hashing with your beta 13 release with no issue although the speed is slightly less at 14,445
compared to your 17 release which seems to settle around 14,686
will test some more tomorrow, could be my intensity setting contributing to the instability, what intensity to you set your 750 ti's to when your testing your kernels Sp?
6x 750ti overclocked
minercontrol on YAAMP on x13
after trying with the intensity 20.5 After hashing for about 5 min I had a ccminer stopped working crash and had to restart.
upon restart the miner would not hash and got the error with the same ccminer stopped working.
changed intensity to 20.3 and started to hash again for about 5-10 min then i get this error
[2014-12-08 01:13:50] GPU #5: result for 0014cc00 is not in range: a8cf372c > 1f
Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 309 : unspecified launch failure.
restart pc
happened a few more times on about 3 different cards out of the 6, all cards are overclocked so I adjusted the mem clocks down 50mhz and the core on the cards that seem to fail down 10mhz on the core.
after about 10 min hashing had a card fail with the error above.
was hashing with your beta 13 release with no issue although the speed is slightly less at 14,445
compared to your 17 release which seems to settle around 14,686
will test some more tomorrow, could be my intensity setting contributing to the instability, what intensity to you set your 750 ti's to when your testing your kernels Sp?
The default intensity is abit high with 6 cards. try to set it to 18 or 19.
Jump to: