Re: [ANN] CoinShield -SK-1024 | 11 New Features |CPU Launched| GPU Launch Date Set

the 780 is this compute 30 or 35 ?

My 780ti works well on it.
I think too, it is a problem with the gpu not working properly on your card, if it always return, it means it doesn't work properly.
however, the 750ti shouldn't have any problem.

Any of your cards attached to a monitor ?

For info it was compiled with vs2013
and boost 1_56 (the others dependencies being those of ccminers, except for pthread which isn't needed. )

also make sure you have the latest drivers and compiled with cuda 6.5

The miner still doesn't works here.
I'm also using VS2013. I've downloaded and installed the latest driver and CUDA Toolkit today. I'm on Windows 8.1 if that makes any difference. The Nvidia card is the only card in the system and it's attached to the main monitor.

I am also on 8.1, try to go sk1024.cu and replace const int throughput = 512*8 * 512 * 4; by const int throughput = 512*8 * 512 * 2;

Ok. Modifying the throughput parameter did the trick but I had to go down to 512*8 * 512 * 1. (RAM usage on the video card goes up about 1G+). Now the miner started to work reporting about 16000 kHash/s.I'm running the miner against testnetbut still no block was found after about 20min. I guess this is not good.

Did you build the miner with a compute-level, that is supported by your gpu?

My card supports 5.0 and it seams that the project parameters indicates that it's set to 5

it is set to compute 3.0; 3.5 and 5.0 (with the current version don't try to use 5.2, I have finally one version which works with compute 5.2, will update soon... no difference though...)

Hi,
After all the miner is working, I've succeed to find blocks both on testnet and main net but it takes some time. The trick is that the above mentioned throughput parameter has to be lowered or the number of threads (which was hard coded to 4) must be lowered. Currently with a single 750ti I can get about 16Mhash/s which was enough to get around 1 block/hour after running 3-4h.
In case someone else want to give a try, here is an updated binary where the number of threads can be specified as a parameter after the port number.

actually it is a bug and shouldn't be a free parameter (well not yet actually and not like that) it should be "num_processors" ie in the context, the numbers of cards (put it in the printf but forgot to put it in the routine). putting a number smaller than the actual number of card will run on a fewer number of cards
and a larger number will rise cpu usage...