CCminer(SP-MOD) Modded GPU kernels.

[chrysophylax]

did you try -i 22.9?

no - will try that now ...

tanx ...

#crysx

[Vita1ico]

I use .67 A good result for the GTH 960.





Ps. I do not know how correctly sent to the creator of the beer, let it be income for the day. For _SP transaction ID
7d52b98dc6448bdfdcd64fafc3fffb20a2d641a8e867ac591878cdd4e2b298bc

[serg_25]

did you try -i 22.9?

Seems like lyra2rev2 not working.
finally fixed all issues and no accepted shares:

Code:

./ccminer -a lyra2v2 -o stratum+tcp://coinotron.com:3340 -u *** -p ***
*** ccminer 1.5.67-git(SP-MOD) for nVidia GPUs by sp-hash@github ***
        Built with the 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, tsiv and pallas.

[2015-09-17 10:47:49] Starting Stratum on stratum+tcp://coinotron.com:3340
[2015-09-17 10:47:49] NVML GPU monitoring enabled.
[2015-09-17 10:47:49] 1 miner thread started, using 'lyra2v2' algorithm.
[2015-09-17 10:47:49] Binding thread 0 to cpu 0 (mask 1)
[2015-09-17 10:47:50] Stratum difficulty set to 0.5
[2015-09-17 10:47:51] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:48:17] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:48:17] GPU #0: GeForce GTX 750 Ti, 3992 Temp= 44C Fan= 35%
[2015-09-17 10:48:47] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:48:47] GPU #0: GeForce GTX 750 Ti, 3989 Temp= 50C Fan= 40%
[2015-09-17 10:49:17] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:49:17] GPU #0: GeForce GTX 750 Ti, 3991 Temp= 54C Fan= 43%
[2015-09-17 10:49:47] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:49:47] GPU #0: GeForce GTX 750 Ti, 3989 Temp= 56C Fan= 45%
[2015-09-17 10:50:17] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:50:17] GPU #0: GeForce GTX 750 Ti, 3970 Temp= 58C Fan= 46%
[2015-09-17 10:50:31] coinotron.com:3340 lyra2v2 block 369140
[2015-09-17 10:50:31] GPU #0: GeForce GTX 750 Ti, 3965 Temp= 58C Fan= 46%
[2015-09-17 10:50:49] coinotron.com:3340 lyra2v2 block 369141
[2015-09-17 10:50:49] GPU #0: GeForce GTX 750 Ti, 3942 Temp= 59C Fan= 47%
[2015-09-17 10:51:19] coinotron.com:3340 lyra2v2 block 369141
[2015-09-17 10:51:19] GPU #0: GeForce GTX 750 Ti, 3947 Temp= 59C Fan= 48%
[2015-09-17 10:51:49] coinotron.com:3340 lyra2v2 block 369141
[2015-09-17 10:51:49] GPU #0: GeForce GTX 750 Ti, 3879 Temp= 60C Fan= 48%
[2015-09-17 10:52:19] coinotron.com:3340 lyra2v2 block 369141
[2015-09-17 10:52:19] GPU #0: GeForce GTX 750 Ti, 3880 Temp= 60C Fan= 49%

also maybe you can advice, i try to add "-i 22.9" or "-i 24" error appeared:

Code:

[2015-09-17 10:52:57] Stratum difficulty set to 0.5
Cuda error in func 'scanhash_lyra2v2' at line 134 : out of memory.

p.s. not sure what exactly "memory" used but my pc has 32gb ram

[chrysophylax]

did you try -i 22.9?

Seems like lyra2rev2 not working.
finally fixed all issues and no accepted shares:

Code:

./ccminer -a lyra2v2 -o stratum+tcp://coinotron.com:3340 -u *** -p ***
*** ccminer 1.5.67-git(SP-MOD) for nVidia GPUs by sp-hash@github ***
        Built with the 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, tsiv and pallas.

[2015-09-17 10:47:49] Starting Stratum on stratum+tcp://coinotron.com:3340
[2015-09-17 10:47:49] NVML GPU monitoring enabled.
[2015-09-17 10:47:49] 1 miner thread started, using 'lyra2v2' algorithm.
[2015-09-17 10:47:49] Binding thread 0 to cpu 0 (mask 1)
[2015-09-17 10:47:50] Stratum difficulty set to 0.5
[2015-09-17 10:47:51] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:48:17] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:48:17] GPU #0: GeForce GTX 750 Ti, 3992 Temp= 44C Fan= 35%
[2015-09-17 10:48:47] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:48:47] GPU #0: GeForce GTX 750 Ti, 3989 Temp= 50C Fan= 40%
[2015-09-17 10:49:17] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:49:17] GPU #0: GeForce GTX 750 Ti, 3991 Temp= 54C Fan= 43%
[2015-09-17 10:49:47] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:49:47] GPU #0: GeForce GTX 750 Ti, 3989 Temp= 56C Fan= 45%
[2015-09-17 10:50:17] coinotron.com:3340 lyra2v2 block 369139
[2015-09-17 10:50:17] GPU #0: GeForce GTX 750 Ti, 3970 Temp= 58C Fan= 46%
[2015-09-17 10:50:31] coinotron.com:3340 lyra2v2 block 369140
[2015-09-17 10:50:31] GPU #0: GeForce GTX 750 Ti, 3965 Temp= 58C Fan= 46%
[2015-09-17 10:50:49] coinotron.com:3340 lyra2v2 block 369141
[2015-09-17 10:50:49] GPU #0: GeForce GTX 750 Ti, 3942 Temp= 59C Fan= 47%
[2015-09-17 10:51:19] coinotron.com:3340 lyra2v2 block 369141
[2015-09-17 10:51:19] GPU #0: GeForce GTX 750 Ti, 3947 Temp= 59C Fan= 48%
[2015-09-17 10:51:49] coinotron.com:3340 lyra2v2 block 369141
[2015-09-17 10:51:49] GPU #0: GeForce GTX 750 Ti, 3879 Temp= 60C Fan= 48%
[2015-09-17 10:52:19] coinotron.com:3340 lyra2v2 block 369141
[2015-09-17 10:52:19] GPU #0: GeForce GTX 750 Ti, 3880 Temp= 60C Fan= 49%

also maybe you can advice, i try to add "-i 22.9" or "-i 24" error appeared:

Code:

[2015-09-17 10:52:57] Stratum difficulty set to 0.5
Cuda error in func 'scanhash_lyra2v2' at line 134 : out of memory.

p.s. not sure what exactly "memory" used but my pc has 32gb ram

in v67 - lyra2v2 is broken ... you need to use the previous version ...

the intensity levels that you are using are the ones we are trying for quark - not lyra2v2 ...

it seems the best intensity levels for lyra2v2 is using the xintensity -X 15 ... at least - for our cards ( gigabyte 750ti oc lp ) ...

and the 'memory' error is due to the memory allocation ON the card ... not the computer ...

when you set an intensity value - it uses the on-board memory of the video card and max's the memory when increasing the the intensity too much ( increasing the cuda threads it uses to process data inside the video cards memory ) ...

the devs can explain that side a hell of a lot better than i can ...

#crysx

[chrysophylax]

did you try -i 22.9?

no - will try that now ...

tanx ...

#crysx

wow - what a difference going DOWN in intensity on quark ...

-------

[2015-09-17 17:37:13] accepted: 409/414 (98.79%), 35567 kH/s yes!
[2015-09-17 17:37:25] GPU #0: GeForce GTX 750 Ti, 5935 Temp= 79C Fan= 65%
[2015-09-17 17:37:25] accepted: 410/415 (98.80%), 35571 kH/s yes!
[2015-09-17 17:37:33] GPU #4: GeForce GTX 750 Ti, 5960 Temp= 80C Fan= 65%
[2015-09-17 17:37:34] accepted: 411/416 (98.80%), 35574 kH/s yes!
[2015-09-17 17:37:39] GPU #1: GeForce GTX 750 Ti, 5936 Temp= 76C Fan= 62%
[2015-09-17 17:37:40] GPU #2: GeForce GTX 750 Ti, 6031 Temp= 78C Fan= 63%
[2015-09-17 17:37:40] GPU #3: GeForce GTX 750 Ti, 5924 Temp= 79C Fan= 64%
[2015-09-17 17:37:40] GPU #2: GeForce GTX 750 Ti, 6008 Temp= 78C Fan= 63%
[2015-09-17 17:37:41] accepted: 412/417 (98.80%), 35574 kH/s yes!
[2015-09-17 17:37:42] GPU #5: GeForce GTX 750 Ti, 5877 Temp= 78C Fan= 63%
[2015-09-17 17:37:43] quark.eu.nicehash.com:3345 quark block 2190162

-------

thats huge ...

#crysx

[serg_25]

in v67 - lyra2v2 is broken ... you need to use the previous version ...

the intensity levels that you are using are the ones we are trying for quark - not lyra2v2 ...

it seems the best intensity levels for lyra2v2 is using the xintensity -X 15 ... at least - for our cards ( gigabyte 750ti oc lp ) ...

and the 'memory' error is due to the memory allocation ON the card ... not the computer ...

when you set an intensity value - it uses the on-board memory of the video card and max's the memory when increasing the the intensity too much ( increasing the cuda threads it uses to process data inside the video cards memory ) ...

the devs can explain that side a hell of a lot better than i can ...

#crysx

Thanks for reply.
checked -X 15 in x11 algo and seems like it even more slow than without it.

Code:

[2015-09-17 11:07:37] accepted: 36/36 (100.00%), 2789 kH/s yes!
[2015-09-17 11:07:43] GPU #0: GeForce GTX 750 Ti, 2769 Temp= 62C Fan= 49%
[2015-09-17 11:07:44] accepted: 37/37 (100.00%), 2786 kH/s yes!
[2015-09-17 11:07:54] GPU #0: GeForce GTX 750 Ti, 2774 Temp= 62C Fan= 50%

according to this forum with stock kernal i have to receive 3+mh in x11.
Any advices, what config i have to use?

[chrysophylax]

in v67 - lyra2v2 is broken ... you need to use the previous version ...

the intensity levels that you are using are the ones we are trying for quark - not lyra2v2 ...

it seems the best intensity levels for lyra2v2 is using the xintensity -X 15 ... at least - for our cards ( gigabyte 750ti oc lp ) ...

and the 'memory' error is due to the memory allocation ON the card ... not the computer ...

when you set an intensity value - it uses the on-board memory of the video card and max's the memory when increasing the the intensity too much ( increasing the cuda threads it uses to process data inside the video cards memory ) ...

the devs can explain that side a hell of a lot better than i can ...

#crysx

Thanks for reply.
checked -X 15 in x11 algo and seems like it even more slow than without it.

Code:

[2015-09-17 11:07:37] accepted: 36/36 (100.00%), 2789 kH/s yes!
[2015-09-17 11:07:43] GPU #0: GeForce GTX 750 Ti, 2769 Temp= 62C Fan= 49%
[2015-09-17 11:07:44] accepted: 37/37 (100.00%), 2786 kH/s yes!
[2015-09-17 11:07:54] GPU #0: GeForce GTX 750 Ti, 2774 Temp= 62C Fan= 50%

according to this forum with stock kernal i have to receive 3+mh in x11.
Any advices, what config i have to use?

all algos use different settings ...

sp ( as with the othe devs in their fork of ccminer ) has built in intensity settings for each algo ... what they are - well only sp knows .. which is why i want to collate a full document on all settings - not just intensity ...

with x11 - i use -X 28 and that seems to be fine ... at the max hashrate the cards can go ...

with x15 - im not sure as i never mine with x15 ...

you need to change the settings for every algo and see which ones come out best ...

#crysx

[serg_25]

all algos use different settings ...

sp ( as with the othe devs in their fork of ccminer ) has built in intensity settings for each algo ... what they are - well only sp knows .. which is why i want to collate a full document on all settings - not just intensity ...

with x11 - i use -X 28 and that seems to be fine ... at the max hashrate the cards can go ...

with x15 - im not sure as i never mine with x15 ...

you need to change the settings for every algo and see which ones come out best ...

#crysx

seems like misunderstanding.
i also don't mine x15 algo.  it's about XIntensity
You say that for 750 Ti card -X 28 is the best, but with that command
./ccminer -a x11 -o stratum+tcp://drk.ghash.io:3333 -u** -p ** -X 28
i receive

Code:

[2015-09-17 11:22:48] GPU #0: scanhash_x11 out of memory
Cuda error in func 'x11_simd512_cpu_init' at line 791 : out of memory.

so i can use only default Intensity which is hardcoded to miner. but with such default config i can get only 2.8mh  seems like to low.

[chrysophylax]

all algos use different settings ...

sp ( as with the othe devs in their fork of ccminer ) has built in intensity settings for each algo ... what they are - well only sp knows .. which is why i want to collate a full document on all settings - not just intensity ...

with x11 - i use -X 28 and that seems to be fine ... at the max hashrate the cards can go ...

with x15 - im not sure as i never mine with x15 ...

you need to change the settings for every algo and see which ones come out best ...

#crysx

seems like misunderstanding.
i also don't mine x15 algo.  it's about XIntensity
You say that for 750 Ti card -X 28 is the best, but with that command
./ccminer -a x11 -o stratum+tcp://drk.ghash.io:3333 -u** -p ** -X 28
i receive

Code:

[2015-09-17 11:22:48] GPU #0: scanhash_x11 out of memory
Cuda error in func 'x11_simd512_cpu_init' at line 791 : out of memory.

so i can use only default Intensity which is hardcoded to miner. but with such default config i can get only 2.8mh  seems like to low.

ok- i see that i misread about x15 ... but the rules of engagement are the same when it comes to the various algos ...

xintensity -X 28 works for MY cards ... you need to adjust the intensity settings to suit your own cards ...

if you are getting a 'scanhash' error - this 'usually' means that the card has run out of available memory for the process to happen ... drop the -X to 27 ( for example ) ...

this may or may not work well for your card - if you still get those errors - the keep droppign it until it processes the shares ...

the best way to do this is to run ccminer-spmod without ANY intensity settings and see if all is ok with the default settings built in to the card ... THEN start to adjust using -X ...

the -X is NOT static - as it changes with the algo change ... some algos use a higher -X setting - some lower ...

believe it or not - compiling ccminer in cuda 7 actually allows me to up the intensity to -X 29 ... but the hashrate is appalling ...

btw - i get about 2.8MH per card also in x11 - but i DO NOT oc - like many others here including sp ... you are bound to get a lot more hashrate if you adjust clock settings also ...

#crysx

[serg_25]

ok- i see that i misread about x15 ... but the rules of engagement are the same when it comes to the various algos ...

xintensity -X 28 works for MY cards ... you need to adjust the intensity settings to suit your own cards ...

if you are getting a 'scanhash' error - this 'usually' means that the card has run out of available memory for the process to happen ... drop the -X to 27 ( for example ) ...

this may or may not work well for your card - if you still get those errors - the keep droppign it until it processes the shares ...

the best way to do this is to run ccminer-spmod without ANY intensity settings and see if all is ok with the default settings built in to the card ... THEN start to adjust using -X ...

the -X is NOT static - as it changes with the algo change ... some algos use a higher -X setting - some lower ...

believe it or not - compiling ccminer in cuda 7 actually allows me to up the intensity to -X 29 ... but the hashrate is appalling ...

btw - i get about 2.8MH per card also in x11 - but i DO NOT oc - like many others here including sp ... you are bound to get a lot more hashrate if you adjust clock settings also ...

#crysx

Thanks man. know it's clear.

[Grout]

I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.

What is this witchery? Not that I'm complaining...

BTW, it's about time for my donation, so here's a beer SP: 3bb1e5e50d3967cfc8f5e14aa700c316fc69c45380fcad938aed2d67fc62615c

[chrysophylax]

ok- i see that i misread about x15 ... but the rules of engagement are the same when it comes to the various algos ...

xintensity -X 28 works for MY cards ... you need to adjust the intensity settings to suit your own cards ...

if you are getting a 'scanhash' error - this 'usually' means that the card has run out of available memory for the process to happen ... drop the -X to 27 ( for example ) ...

this may or may not work well for your card - if you still get those errors - the keep droppign it until it processes the shares ...

the best way to do this is to run ccminer-spmod without ANY intensity settings and see if all is ok with the default settings built in to the card ... THEN start to adjust using -X ...

the -X is NOT static - as it changes with the algo change ... some algos use a higher -X setting - some lower ...

believe it or not - compiling ccminer in cuda 7 actually allows me to up the intensity to -X 29 ... but the hashrate is appalling ...

btw - i get about 2.8MH per card also in x11 - but i DO NOT oc - like many others here including sp ... you are bound to get a lot more hashrate if you adjust clock settings also ...

#crysx

Thanks man. know it's clear.

no problem mate ...

apologies for confusing you earlier - as i misread your question ...

#crysx

[chrysophylax]

I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.

What is this witchery? Not that I'm complaining...

BTW, it's about time for my donation, so here's a beer SP: 3bb1e5e50d3967cfc8f5e14aa700c316fc69c45380fcad938aed2d67fc62615c

hehehe ... aaand you wonder why i wont change from linux? ...

and its a damn site easier to compile stuff too ...

which distro did you use? ... redhat based or debian based? ...

#crysx

[sp_]

I use .67 A good result for the GTH 960.


Ps. I do not know how correctly sent to the creator of the beer, let it be income for the day. For _SP transaction ID
7d52b98dc6448bdfdcd64fafc3fffb20a2d641a8e867ac591878cdd4e2b298bc

Thanks for your support.

I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.
What is this witchery? Not that I'm complaining...
BTW, it's about time for my donation, so here's a beer SP: 3bb1e5e50d3967cfc8f5e14aa700c316fc69c45380fcad938aed2d67fc62615c

Thanks for your support.

[sp_]

so i can use only default Intensity which is hardcoded to miner. but with such default config i can get only 2.8mh  seems like to low.

The speed depends on the clock on the on the Card, and if you have a 6 pin power adapter on the card.
Some cards are clock higher as default. X11 will perform above 3MHASH with a core of 1350Mz and up to 3400-3500 with 1500 Mz

[sp_]

I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.

I usually use the internal gpu of the motherboard to do the display in windows, and the cards 100% for mining.

[chrysophylax]

I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.

I usually use the internal gpu of the motherboard to do the display in windows, and the cards 100% for mining.

which simply means you require two gpus to do that - where as we only need the one ... ...

anyway ... i have reverted back to x11 sp ... v67 doesnt seem to have any issues whatsoever with the algo - even compiled in cuda 7 ...

is there any way you could supply methe table of default intensities and special command paramaters ( if there are any - as i know scrypt and another algo use more parameters ( like thoughput and so forth ) ) ? ...

i can compile them and collate them in one place so that everyone can use them as a reference for the different cards they use ...

#crysx

[sp_]

I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.

I usually use the internal gpu of the motherboard to do the display in windows, and the cards 100% for mining.

which simply means you require two gpus to do that - where as we only need the one ... ...
anyway ... i have reverted back to x11 sp ... v67 doesnt seem to have any issues whatsoever with the algo - even compiled in cuda 7 ...
is there any way you could supply methe table of default intensities and special command paramaters ( if there are any - as i know scrypt and another algo use more parameters ( like thoughput and so forth ) ) ? ...
i can compile them and collate them in one place so that everyone can use them as a reference for the different cards they use ...

-i 22.9 is good. I think scryptr is using -i 23.5 on linux.

The problem is that the optimal intensity is different from card to card and build to build.

[serg_25]

is there any way you could supply methe table of default intensities and special command paramaters ( if there are any - as i know scrypt and another algo use more parameters ( like thoughput and so forth ) ) ? ...

i can compile them and collate them in one place so that everyone can use them as a reference for the different cards they use ...

#crysx

Seems like this question was asked by you several time to sp_ already, but i think it's not difficult to check by yourself.
what i did to check it in linux:

Code:

grep -rnw '/you/path/to/folder/ccminer-1.5.67/' -e "pattern"
where pattern - intensity

in input you will see that this info (ofcourse different files for different algo.  example for lyra2v2)

Code:

/lyra2/lyra2REv2.cu:85:        uint32_t intensity = 256 * 256 * 8;

lets check this file lyra2REv2.cu

Code:

 if (strstr(props.name, "970"))
        {
                intensity = 256 * 256 * 18;
                tpb = 9;
        }
        else if (strstr(props.name, "980"))
        {
                intensity = 256 * 256 * 18;
                tpb = 7;
        }
        else if (strstr(props.name, "750 Ti"))
        {
                intensity = 256 * 256 * 16;
                tpb = 16;
        }
        else if (strstr(props.name, "750"))
        {
                intensity = 256 * 256 * 5;
                tpb = 7;
        }
        else if (strstr(props.name, "960"))
        {
                intensity = 256 * 256 * 16;
                tpb = 7;
        }

i think this can be an answer about default intensity settings.
P.S. i'm not dev, just lot of years with linux. maybe this info wrong.

P.P.S.  i'm super amator in mining, only for 2-3 days, but already find that it's really interesting.  Thanks for dev that support that ccminer project.

[flipclip]

Can anyone else build the latest on git and test it. lyra2v2 (linux)

Just pulled (latest commit is t-nelson logger stuff), hashing to nicehash and nothing submitted:

[2015-09-17 08:34:35] Stratum difficulty set to 2
[2015-09-17 08:34:36] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:34:59] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:34:59] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:34:59] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:34:59] GPU #0: GeForce GTX 750 Ti, 3994 Temp= 46C Fan= 90%
[2015-09-17 08:34:59] GPU #1: GeForce GTX 750 Ti, 4499 Temp= 47C Fan= 90%
[2015-09-17 08:35:24] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:35:24] GPU #1: GeForce GTX 750 Ti, 4498 Temp= 48C Fan= 90%
[2015-09-17 08:35:24] GPU #0: GeForce GTX 750 Ti, 3991 Temp= 47C Fan= 90%
[2015-09-17 08:35:25] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:35:25] GPU #1: GeForce GTX 750 Ti, 4486 Temp= 48C Fan= 90%
[2015-09-17 08:35:25] GPU #0: GeForce GTX 750 Ti, 3952 Temp= 47C Fan= 90%
[2015-09-17 08:35:46] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:35:46] GPU #0: GeForce GTX 750 Ti, 3969 Temp= 47C Fan= 90%
[2015-09-17 08:35:46] GPU #1: GeForce GTX 750 Ti, 4498 Temp= 49C Fan= 90%
[2015-09-17 08:36:06] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:36:06] GPU #0: GeForce GTX 750 Ti, 3969 Temp= 48C Fan= 90%
[2015-09-17 08:36:06] GPU #1: GeForce GTX 750 Ti, 4498 Temp= 50C Fan= 90%
[2015-09-17 08:36:35] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:36:35] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:36:35] GPU #0: GeForce GTX 750 Ti, 3953 Temp= 48C Fan= 90%
[2015-09-17 08:36:35] GPU #1: GeForce GTX 750 Ti, 4497 Temp= 50C Fan= 90%
[2015-09-17 08:36:35] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:36:35] GPU #0: GeForce GTX 750 Ti, 3917 Temp= 48C Fan= 90%
[2015-09-17 08:36:35] GPU #1: GeForce GTX 750 Ti, 4486 Temp= 50C Fan= 90%
[2015-09-17 08:37:01] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:37:01] GPU #1: GeForce GTX 750 Ti, 4498 Temp= 50C Fan= 90%
[2015-09-17 08:37:01] GPU #0: GeForce GTX 750 Ti, 3968 Temp= 48C Fan= 90%
[2015-09-17 08:37:02] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:37:02] GPU #1: GeForce GTX 750 Ti, 4496 Temp= 50C Fan= 90%
[2015-09-17 08:37:02] GPU #0: GeForce GTX 750 Ti, 3895 Temp= 48C Fan= 90%
[2015-09-17 08:37:03] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:03] GPU #0: GeForce GTX 750 Ti, 3902 Temp= 48C Fan= 90%
[2015-09-17 08:37:03] GPU #1: GeForce GTX 750 Ti, 4496 Temp= 50C Fan= 90%
[2015-09-17 08:37:27] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:27] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:27] GPU #1: GeForce GTX 750 Ti, 4497 Temp= 50C Fan= 90%
[2015-09-17 08:37:27] GPU #0: GeForce GTX 750 Ti, 3937 Temp= 48C Fan= 90%
[2015-09-17 08:37:35] Stratum difficulty set to 1
[2015-09-17 08:37:53] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:53] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:53] GPU #1: GeForce GTX 750 Ti, 4497 Temp= 51C Fan= 90%
[2015-09-17 08:37:53] GPU #0: GeForce GTX 750 Ti, 3978 Temp= 48C Fan= 90%
[2015-09-17 08:37:53] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:53] GPU #0: GeForce GTX 750 Ti, 3880 Temp= 49C Fan= 90%
[2015-09-17 08:37:53] GPU #1: GeForce GTX 750 Ti, 4490 Temp= 50C Fan= 90%
[2015-09-17 08:37:53] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:54] GPU #1: GeForce GTX 750 Ti, 4495 Temp= 50C Fan= 90%
[2015-09-17 08:37:54] GPU #0: GeForce GTX 750 Ti, 3889 Temp= 48C Fan= 90%
[2015-09-17 08:38:04] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369268
[2015-09-17 08:38:04] GPU #0: GeForce GTX 750 Ti, 3965 Temp= 48C Fan= 90%
[2015-09-17 08:38:04] GPU #1: GeForce GTX 750 Ti, 4498 Temp= 51C Fan= 90%

Is the block number supposed to repeat like that?

To answer my own question: No it is not.