CCminer(SP-MOD) Modded GPU kernels.

[scryptr]

QUARK HASH--
750ti FTW - 6.25-6.4Mh/s
970 FTW+ - 15Mh/s
I have no GTX 980 to test.  Others have posted rates, and I am guessing 20Mh/s with proper tuning.  My hash rates are on Ubuntu 14.04, with no overclocking, and in headless rigs.  My Win 7 system is a single card working computer.
--scryptr

The hash was broken. Get the latest version and build. You will get lower rates.

small contribution--

I sent you, KlausT, and tpruvot each a bit.  I have to mow the lawn, I will get back to "git and compile" this evening.  I am still running the release build of v46 on all my rigs.  The release behaved well, the charts on the pool were trending up.

Please don't lower my rates...       --scryptr

[sp_]

I have the same issue as 5w00p on both 750ti's (Asus and Palit). PSU 1000W. The same on Quark and x11, on ccminer-1.6.2-git-tpruvot too,
but on dmd-gr algo all ok!

I think the code has drastically changed regarding the load/power consumption factors....Here are my observations about it:
- I always run binary releases from sp directly,
- on quark my miner of choice was old sp mod 3.1 release,
- have 1 comp for testing and two rigs 6x750 ti gigabytes all OC,
- 3.1 release gave me best hashrate until latest release 4.6 which gave significant boost,
- look at graph recorded with nvidia inspector, running different miners on same machine,
- each miner was running quark for about one minute,...didn't count exactly
- but pay attention to gpu load/power consumption:


gifs upload

- see how the graph on 3.1 miner is almost flat!...while newest release (4.6) is quite an improvement regarding the older (4.4)

The problem with NVIDIA cards is that they have a dynamic clockrate. If you push the card too much, it will downclock automaticly. Base clock vs boost clock. In the latest mods I have tried to reduce the number of gpu-threads to increase the boost, and reduce the power consumption.

[sp_]

small contribution--
I sent you, KlausT, and tpruvot each a bit.  I have to mow the lawn, I will get back to "git and compile" this evening.  I am still running the release build of v46 on all my rigs.  The release behaved well, the charts on the pool were trending up.
Please don't lower my rates...       --scryptr

Thanks

When you build directly from github, there might be bugs.
But it helps alot to have betatesters. 
Keep up the good work.

[tbearhere]

#46
QUARK HASH 750ti FTW - 6.35-6.6Mh/s  Showing on command window..about 1mh/s more for my rig...but at pool 1mh/s less..staying with #43 the best so far. And the 3 750ti on this computer with #46 drags down the computer.
Keep up the good work sp. 

[Slava_K]

Latest git keccak is broken. Testet on yaamp.

[tbearhere]

The as-compiled by sp_ release 45 is a nightmare on my rig, mining Quark

GTX 970
i7 4770
16GB
Win 8.1

Unsteady hashrate with -i 20, and most any other intensity setting crashes.

After a crash, the GPU goes into a low power mode and I have to restart the machine. I suspect that if I used an older version of Afterburner or Precision X that has the K-Boost button, I might be able to wake it up after the crash without restarting .

Either way, it is very buggy and that makes me

download nvidia inspector

Use bat-file with

nvidiaInspector -restartDisplayDriver

Nvidia inspector is an  OverClocking application. Does it have anything to do with recovering from a crash?

[sp_]

Latest git keccak is broken. Testet on yaamp.

Seems to be a pool problem...

Works on nicehash.com

tried with different diff patameters like -d 0.01 etc.

[hashbrown9000]

I forget where on Google I found this quick code to put in a .bat file to quickly reboot the GPU without restarting windoze:

Code:

@echo off
echo.
echo *** Restarting GPU  
timeout /t 2 /nobreak >nul
devmanview.exe /disable_enable "NVIDIA GeForce GTX 750 Ti" 
echo. 
echo *** DoNe 
timeout /t 2 /nobreak >nul
taskkill /f /IM explorer.exe
explorer.exe

I made a shortcut and pinned it to the start menu and it works every time when I go past the overclock limit on my card.

[scryptr]

The as-compiled by sp_ release 45 is a nightmare on my rig, mining Quark

GTX 970
i7 4770
16GB
Win 8.1

Unsteady hashrate with -i 20, and most any other intensity setting crashes.

After a crash, the GPU goes into a low power mode and I have to restart the machine. I suspect that if I used an older version of Afterburner or Precision X that has the K-Boost button, I might be able to wake it up after the crash without restarting .

Either way, it is very buggy and that makes me

download nvidia inspector

Use bat-file with

nvidiaInspector -restartDisplayDriver

Nvidia inspector is an  OverClocking application. Does it have anything to do with recovering from a crash?

DRIVER CRASH--

I am often able to overcome a driver crash with EVGA PrecisionX 16, an overclocking utility.  If you drive the card to hard, and the driver crashes, the card can be reset by turning "Boost Clock" off and on and then re-applying the clocking settings.  The desktop display may also need to be reset, as well.       --scryptr

[5w00p]

The as-compiled by sp_ release 45 is a nightmare on my rig, mining Quark

GTX 970
i7 4770
16GB
Win 8.1

Unsteady hashrate with -i 20, and most any other intensity setting crashes.

After a crash, the GPU goes into a low power mode and I have to restart the machine. I suspect that if I used an older version of Afterburner or Precision X that has the K-Boost button, I might be able to wake it up after the crash without restarting .

Either way, it is very buggy and that makes me

download nvidia inspector

Use bat-file with

nvidiaInspector -restartDisplayDriver

Nvidia inspector is an  OverClocking application. Does it have anything to do with recovering from a crash?

That specific command restarts the display driver. I was informed of it and have now begun to use it -- Works great.
nVidiaInspector is a multi-function piece of software. Yay.

[tbearhere]

The as-compiled by sp_ release 45 is a nightmare on my rig, mining Quark

GTX 970
i7 4770
16GB
Win 8.1

Unsteady hashrate with -i 20, and most any other intensity setting crashes.

After a crash, the GPU goes into a low power mode and I have to restart the machine. I suspect that if I used an older version of Afterburner or Precision X that has the K-Boost button, I might be able to wake it up after the crash without restarting .

Either way, it is very buggy and that makes me

download nvidia inspector

Use bat-file with

nvidiaInspector -restartDisplayDriver

Nvidia inspector is an  OverClocking application. Does it have anything to do with recovering from a crash?

DRIVER CRASH--

I am often able to overcome a driver crash with EVGA PrecisionX 16, an overclocking utility.  If you drive the card to hard, and the driver crashes, the card can be reset by turning "Boost Clock" off and on and then re-applying the clocking settings.  The desktop display may also need to be reset, as well.       --scryptr

Thanks scryptr. But what I just installed was TdrDelaySetTo40 that I found in nvminer zip folder. It hasn't crashed yet. But when renting hash and not able to monitor all the time I needed something to restart the miner right away. Here is the problem I was having or still maybe have.
 At that time the command window was still open and if I clicked the warning window off the miner would start mining again without any problem.



thx

EDIT: This happened a lot when the stratum failed and at the goto loop. Tested it by disconnecting the ithernet.

:loop
ccminer.exe -r 1 -R 5 -a quark   -o stratum+tcp://us-west01.miningrigrentals.com:3333 -u me -p x  -d 0,1,2
ccminer.exe -r 1 -R 5 -a quark   -o stratum+tcp://us-central01.miningrigrentals.com:3333 -u me  -p x  -d 0,1,2
goto loop

[tbearhere]

I forget where on Google I found this quick code to put in a .bat file to quickly reboot the GPU without restarting windoze:

Code:

@echo off
echo.
echo *** Restarting GPU  
timeout /t 2 /nobreak >nul
devmanview.exe /disable_enable "NVIDIA GeForce GTX 750 Ti" 
echo. 
echo *** DoNe 
timeout /t 2 /nobreak >nul
taskkill /f /IM explorer.exe
explorer.exe

I made a shortcut and pinned it to the start menu and it works every time when I go past the overclock limit on my card.

hashbrown9000 You mean that if it crashes it with auto restart the miner right away?
thx
ps Please look at my post right above this.

[hashbrown9000]

Code:

hashbrown9000 You mean that if it crashes it with auto restart the miner right away?
thx
ps Please look at my post right above this.

No, this just restarts the nvidia driver without restarting the computer. My main display runs on an old AMD 6850, and the other GPU in the system is the 750ti.

I never tried restarting the driver using precisionX.

[hashbrown9000]

To the linux guys: what version of CUDA are you compiling with?

[tbearhere]

Code:

hashbrown9000 You mean that if it crashes it with auto restart the miner right away?
thx
ps Please look at my post right above this.

No, this just restarts the nvidia driver without restarting the computer. My main display runs on an old AMD 6850, and the other GPU in the system is the 750ti.

I never tried restarting the driver using precisionX.

Ok thx

[DougB62]

The problem with NVIDIA cards is that they have a dynamic clockrate. If you push the card too much, it will downclock automaticly. Base clock vs boost clock. In the latest mods I have tried to reduce the number of gpu-threads to increase the boost, and reduce the power consumption.

nvidiaInspector.exe -forcepstate ??

[chrysophylax]

To the linux guys: what version of CUDA are you compiling with?

6.0 ...

we have been playing with 6.5 and it seems to work quite well ...

our miners are now all running 6.5 compiled ccminer and they seem to be stable ...

but the moment a major crash happens - we revert back to the 6.0 compiled miners and they just work ...

#crysx

[scryptr]

To the linux guys: what version of CUDA are you compiling with?

6.0 ...

we have been playing with 6.5 and it seems to work quite well ...

our miners are now all running 6.5 compiled ccminer and they seem to be stable ...

but the moment a major crash happens - we revert back to the 6.0 compiled miners and they just work ...

#crysx

CUDA 6.5 --

The stuff from SP_ compiles on CUDA 6.5.  I believe  that tpruvot moved to CUDA 7.0, but he takes pains to keep his miners compatible with older nVidia cards.  I don't personally know if CUDA 7.0 can compile programs built for 6.5 properly, although I am curious.  I would install CUDA Toolkit 7.0 on my system if it would work well with the code SP_ produces. CBuchner's CudaMiner was written for CUDA 5.5, tpruvot has a version re-written for 6.5.

I'm looking forward to moving to CUDA 7.0, especially if it produces more hash.       --scryptr

[rednoW]

I'm looking forward to moving to CUDA 7.0, especially if it produces more hash.       --scryptr

sp_ ccminer compiled with CUDA 7.0 produces incorrect hash ... i tried it some time ago on windows

[rednoW]

#46
QUARK HASH 750ti FTW - 6.35-6.6Mh/s  Showing on command window..about 1mh/s more for my rig...but at pool 1mh/s less..staying with #43 the best so far. And the 3 750ti on this computer with #46 drags down the computer.

I just compared again #43 and #46 with equal -i parameters. -i 19.8 was the best for #43 and with such intensity #43 is faster then #46 with -i 19.8.

But default intensity for #46 is  -i 22. #43 just didn't work with -i 22.
And with -i 22 (or without -i) #46 is faster then #43 with -i 19.8 (or without i).
My conclusion is that #43 is more efficient per thread but as it cannot pass -i 20 border it is slower.
If you will count hashes per watt then it maybe becomes that #43 is more efficient as in my case #43 never takes more 58% TDP but #46 takes up to 65% TDP