CCminer(SP-MOD) Modded GPU kernels.

[sp_]

Try without overclocking. What is the quark rate? and check the cpu usage, is it high?

[Zels]

Try without overclocking. What is the quark rate? and check the cpu usage, is it high?

0 Oc = 4500kh on quark.  CPU usage: between 7 - 10% (intel celeron g1820 @ 2.70 Ghz)

My bad!! Was using rlz 17 
Forgot to change folder in minercontrol since age!!

Now: 0 Oc = 5200kh on Quark

[sp_]

what is the rate with overclocking. try f.ex

core +150
mem +400

or

core +200
mem +400

you can also experiment with the -i (intesity parameter).

for x11: Try -i 18.5, -i 19, -20 -21 etc.

for quark, a higher -i is accepted. try -i 24 or more until it crashes.

[Zels]

core +200 / mem +100: 5950kh
core +150 / mem +400: 5780kh
core +200 / mem +400: 5950 - 6000

[sp_]

core +200 / mem +100: 5950kh
core +150 / mem +400: 5780kh
core +200 / mem +400: 5950 - 6000

With higher memspeed, try to increase the intensity with the -i parameter. does it help?

[Grim]

Spreadcoin has a turnover on the exchange of around 1BTC/Day. If I flood the market with my 40% faster miner, the coin will crash.

yes but only because optimized AMD miner isn't released the same day ...
otherwise it's a zero sum game which non the less is very much needed cuz a few private miners (mostly large farms) hurt the coin WAY more.

i think the spread community is willing to pay for faster miners anyway (for once they are smart...)

[Zels]

core200 / mem400:
with i19, 5600
i20: 5950
i21: crash
*** ccminer 1.5.29-git(SP-MOD) for nVidia GPUs by sp-hash@github ***
        Built with VC++ 2013 and nVidia CUDA SDK 6.5

  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 , klaust, tpruvot and tsiv.

[2015-01-13 17:00:57] Intensity set to 21, 2097152 cuda threads
[2015-01-13 17:00:57] Starting Stratum on stratum+tcp://yaamp.com:4033
[2015-01-13 17:00:57] NVAPI GPU monitoring enabled.
[2015-01-13 17:00:57] 1 miner thread started, using 'quark' algorithm.
[2015-01-13 17:00:57] Stratum difficulty set to 0.01
Cuda error in func 'cuda_check_cpu_setTarget' at line 28 : unspecified launch failure.

[Bombadil]

i think the spread community is willing to pay for faster miners anyway (for once they are smart...)

The nature of the spread coin community, way more small scale miners, does this, I guess

[Zels]

With +200core / +400mem
------------------------
x11", "hashrate": 3200
x13", "hashrate": 2540
x14", "hashrate": 2480
x15", "hashrate": 2200
nist5", "hashrate": 9650
quark", "hashrate": 6050

But driver crash after around 2 hours 

[sp_]

core200 / mem400:
with i19, 5600
i20: 5950
i21: crash
*** ccminer 1.5.29-git(SP-MOD) for nVidia GPUs by sp-hash@github ***
        Built with VC++ 2013 and nVidia CUDA SDK 6.5
  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 , klaust, tpruvot and tsiv.
[2015-01-13 17:00:57] Intensity set to 21, 2097152 cuda threads
[2015-01-13 17:00:57] Starting Stratum on stratum+tcp://yaamp.com:4033
[2015-01-13 17:00:57] NVAPI GPU monitoring enabled.
[2015-01-13 17:00:57] 1 miner thread started, using 'quark' algorithm.
[2015-01-13 17:00:57] Stratum difficulty set to 0.01
Cuda error in func 'cuda_check_cpu_setTarget' at line 28 : unspecified launch failure.

You can try i -20.1 -i 20.2 -i 20.3 until it crashes ... To check the maximum speed

+200 core and +400 mem is abit high

[flipclip]

I have two different nvidia 750Ti's in my rig.  I was trying to adjust the intensity of the cards (just to see if it made any hashing difference) individually using -d 0,1 -i 19,21 (also --devices 0,1 --intensity 19,21) but when I checked the api call of "threads" the "I" value was 19 for both cards.  I tried a few different number combos and whatever was the first number for -i was the "I" value for both cards.  Also when I placed a high number as the first intensity (example: 28), ccminer would crash out, but if that number was the second one ccminer would work fine.  It seems the second value is being skipped.  What should the command be for setting intensity per card?

+++++++++++++++++++++++++++++

Edit 1/15/15:
Learned this is a per rig and not a per card setting:

indeed this syntax is not yet supported, i will try to do it...

[hefty]

Hi, can i mine hefty1 coins with 29 realase.

Thanks

[sp_]

yes you can

[hefty]

Thank You

[bluejam00]

Still getting errors with OC settings:

[2015-01-14 20:32:19] GPU #0: result for 016e7268 does not validate on CPU!
[2015-01-14 20:32:19] GPU #0: result for 016e7268 does not validate on CPU!
[2015-01-14 20:32:19] GPU #0: GeForce GTX 980, 76020 kH/s
Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 482 : the launch tim
ed out and was terminated.
Press any key to continue . . .

Tried changing the -i settings as suggested - to no avail and tried various gpu and mem OC settings but just crashes the kernal and the command window. Hashes to 10+kh/s for maybe 3-4 times then crashes.

Hope we can work out good overclcok and .bat settings for the GTX980 that doesn't crash it?

I've test various variations in Precisionx but can't get it to work unless at default settings. Grrr

Will keep trying...anyone else with a GTX 980 had any luck with their settings?

[sp_]

Wich algorithm are you mining?  76020 KH/s is high. What is the temps on the card? (use gpuz)

[sp_]

The Groestl improvements I am working on seems to be gain 50khash, but below 100khash x11 (750ti), but i need to debug it more.

[pokeytex]

The Groestl improvements I am working on seems to be gain 50khash, but below 100khash x11 (750ti), but i need to debug it more.

SP - does the miner do diamond groestl?

[Bombadil]

The Groestl improvements I am working on seems to be gain 50khash, but below 100khash x11 (750ti), but i need to debug it more.

SP - does the miner do diamond groestl?

-a dmd-gr

[bluejam00]

Wich algorithm are you mining?  76020 KH/s is high. What is the temps on the card? (use gpuz)

Haha that's not the real hash (I wish!!) - it seems the last figure it spits out is an error - it hashes OC around 10MHz+ - but then falls over. I can see quite a few people here are getting the same error. Temps fine just before it crashes - it's a hefty system custom built nothing goes over 71C during gaming or normal mining - and it's currently 35C in Aus and humid so temps not the issue.