Linux command line to change clocks on my laptop, GTX850M, this is in my launch script.
optirun nvidia-settings -c :8 -a [gpu:0]/GPUGraphicsClockOffset[2]=80 -a [gpu:0]/GPUMemoryTransferRateOffset[2]=300

If you dont run optimus/bumblebee to switch on the second graphics card you dont need optirun, :8 is the display number, you need to have coolbits set in your config for it to work.

latest source on git compiles and runs fine here
changed x15/whirlpoolx.cu line 47 to:   uint32_t throughput = pow(2,23);
23 was the highest that works on my GTX850M
was getting about 63Mh
overclocked GPU +105 memory +800

optirun nvidia-settings -c :8 -a [gpu:0]/GPUGraphicsClockOffset[2]=105 -a [gpu:0]/GPUMemoryTransferRateOffset[2]=800

[2015-03-09 17:28:29] GPU #0: GeForce GTX 850M, 69457 kH/s
[2015-03-09 17:28:29] accepted: 907/908 (99.89%), 69475 khash/s yay!!!
[2015-03-09 17:28:42] GPU #0: GeForce GTX 850M, 69404 kH/s
[2015-03-09 17:28:42] accepted: 908/909 (99.89%), 69474 khash/s yay!!!

zero rejects and card is running quite cool 64C

Could I suggest that the location specific information that is currently at the bottom of the text be moved to the top

qubit has slowed from 3609 kH/s on the previous version to 3571 kH/s on the current one - GTX 850M Linux, using "git pull" to update, build.sh has -O3 passed to configure

Thanks for that sample, I can see there it is 1st flagged in CTxOut line OP_DUP. I dont seem to have an error in that place:
2015-02-09 15:07:31 proof-of-work found 
  block-hash: 527bc46a2753ce77be6cd5a146acd765c25ce7c0845485fae3a5046978f02b11
  pow-hash: 0000000000432d1440bafa716127de2e73ff97f36cee52c46277011728112c97
target: 0000000001c5b100000000000000000000000000000000000000000000000000
2015-02-09 15:07:31 CBlock(hash=527bc46a2753ce77be6cd5a146acd765c25ce7c0845485fae3a5046978f02b11, ver=2050, pow_algo=4, pow_hash=0000000000432d1440bafa716127de2e73ff97f36cee52c46277011728112c97, hashPrevBlock=6c3e2b53057d6e1487f054b920ce2f89ac9a9145b440a50bb0cf74ba020c4f47, hashMerkleRoot=cd3a70434310485b6835d1a4206d76846a4b25012fa5f20bafbc4a4ae95a54cb, nTime=1423494446, nBits=1c01c5b1, nNonce=1770140417, vtx=1)
2015-02-09 15:07:31   CTransaction(hash=cd3a704343, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, 4294967295), coinbase 036cc508011a062f503253482f)
    CTxOut(nValue=2385.96524100, scriptPubKey=0348029581a6ca059c601739a3b8c9)
2015-02-09 15:07:31   vMerkleTree: cd3a70434310485b6835d1a4206d76846a4b25012fa5f20bafbc4a4ae95a54cb
2015-02-09 15:07:31 generated 2385.965241
2015-02-09 15:07:31 keypool keep 2
2015-02-09 15:07:31   nActualTimespan = 1490 before bounds
2015-02-09 15:07:31 GetNextWorkRequired RETARGET
2015-02-09 15:07:31 nTargetTimespan = 8640    nActualTimespan = 1490
2015-02-09 15:07:31 Before: 1c021652  0000000002165200000000000000000000000000000000000000000000000000
2015-02-09 15:07:31 After:  1c01c5b1  0000000001c5b1be9334f0a869f533c65c354a25acf5519ac7dffec1d0d8e298
2015-02-09 15:07:31 AddToWallet cd3a70434310485b6835d1a4206d76846a4b25012fa5f20bafbc4a4ae95a54cb  new

not sure if I can tell what it is, is there an accepted failure rate, what % is the norm?

 am solo mining DGB in the hope that they go up in value.
I got one "yay" this morning and this went into my wallet which is the official version and I got 2386.045241 DBG
I got another "yay" this afternoon but nothing went to my wallet, I can see things like "AddToWallet" and "ProcessBlock: ACCEPTED" and "generated 2385.965241"  in the debug file for the wallet
I am using ccminer sp version from a few days ago from git which I compiled myself,
My question is what do I look for in the log to tell me what the problem is?
Does my wallet need to be unlocked during mining, although I am fairly sure it was locked when I got the 1st "yay" this morning
I've spent a couple of hours googling this issue and not found anything relevant, apologies if this is a noob question that I should know.

I am solo mining DGB in the hope that they go up in value.
I got one "yay" this morning and this went into my wallet which is the official version and I got 2386.045241 DBG
I got another "yay" this afternoon but nothing went to my wallet, I can see things like "AddToWallet" and "ProcessBlock: ACCEPTED" and "generated 2385.965241"
I am using ccminer sp version from git which I compiled myself,
My question is what do I look for to tell me what the problem is?
Does my wallet need to be unlocked during mining, although I am fairly sure it was locked when I got the 1st "yay" this morning
I've spent a couple of hours googling this issue and not found anything relevant, apologies if this is a noob question that I should know.

When I 1st started on yaamp last week it seemed to switch through the algos quite alot then slowed down and switched between a few less frequently. I assumed that my hashrate was being measured and then it moved to switching based on profitability. If thats the case I dont understand the need for an option to provide a "factor to normalize profitability" as documented on your yaamp's multi algo page? Anyway I have input my own factors as they are a bit different than the defaults just in case, eg my hashrate on quark is about 15 times what it is on lyra2.
Also my miner had a "sleep 10" on exit which delayed switching so I have comented that out and recompiled it, now for me switching incurrs little overhead.

before asking for change it would be handy to know what the current switching methodology is?
for reference this is what I use on linux:

while :
do
./ccminer -r 0 -a x11   -o stratum+tcp://yaamp.com:3533 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
./ccminer -r 0 -a x13   -o stratum+tcp://yaamp.com:3633 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
./ccminer -r 0 -a x14   -o stratum+tcp://yaamp.com:3933 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
./ccminer -r 0 -a x15   -o stratum+tcp://yaamp.com:3733 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
./ccminer -r 0 -a lyra2 -o stratum+tcp://yaamp.com:4433 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
../ccminer-1.5.31/ccminer -r 0 -a quark -o stratum+tcp://yaamp.com:4033 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
./ccminer -r 0 -a fresh -o stratum+tcp://yaamp.com:4133 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
done

As an aside there were some issues with 503 service not available on the website earlier this morning and the miner getting "connection refused", was there a DoS going on?

Thanks, now added to my multi algo script for yaamp

I am finding that quark is not as fast as build 31
build 33:
[2015-02-02 13:55:51] accepted: 19/20 (95.00%), 4810 khash/s yay!!!
[2015-02-02 13:55:53] yaamp.com:4033 quark block 430232
[2015-02-02 13:55:53] GPU #0: GeForce GTX 850M, 4806 kH/s

build 31
[2015-02-02 14:03:58] accepted: 33/34 (97.06%), 4920 khash/s yay!!!
[2015-02-02 14:04:06] yaamp.com:4033 quark block 1686456
[2015-02-02 14:04:06] GPU #0: GeForce GTX 850M, 4920 kH/s


both compiled from git on linux. No intensity is being set as in my limited testing the default is  optimum or very close

I have commented out this line (441) in proper_exit() in ccminer.cpp on my system:
sleep(10);                      //make sure that the gpu threads are stopped when updating the stats.
When yaamp closes my miner to move to a different algo it adds a delay before moving to the next one, I have not seen any detrimental effects, is this a bad thing to do?

<--- look at my stats, I'm a newbie. This is the 1st day. I will try single algos and see what difference I get, my wallet is not synced yet. I'd assume that the pool calculates what profitable and switches you to it. At the moment its X14 (alipaycoin) and quark (a mixture) no idea they really are the best, though I see many more people are on X11, going to try a few different things over the next few days and see what happens.

I'm running a script that cycles through different algos on YAAMP so that in theory the pool gets me to mine the most profitable using  "-p x11,x13,x14,x15,quark,lyra2"  to tell the pool what I can do
earlier today I was getting lots of rejects on quark, sometimes down to 10% accept rate main reason was "job not found", now its much better, 90% accept and higher,  the rejects are "duplicate share" so I assume the earlier problem was not down to my miner but more a fault of the pool/network that has been fixed.
 The only other algos YAAMP wanted me to mine were X13 and X14 the others were skipped, I get less rejects with those.
Now it still disconnects with stratum_recv_line failed every so often on quark ,5-30 mins range, skips all the other algos and goes right back to quark. I might as well just run quark only to get rid of the delays induced by failing the others.

yes it was from git, that explains it. thanks, just playing with this stuff, not sure I can do anything worthwhile on a laptop anyway

Compiled 1.5.32 on linux OK after changing the realtime stuff for windows only as descibed a few pages back. Also had to stop cuda complaining about my gcc being > 4.8, just changed the include file to accept a minor rev of 9 instead of 8

works fine on quarkcoin, got 6 coins in few hours this morning - GTX850M at around 4600 khash/s

spreadcoin mining not working:
[2015-01-27 12:42:53] 1 miner thread started, using 'spread' algorithm.
[2015-01-27 12:42:53] JSON inval data
[2015-01-27 12:42:53] 127.0.0.1:41677 spread block 241465
[2015-01-27 12:42:53] json_rpc_call failed, retry after 30 seconds

compiled tsiv's spreadminer 0.1 that seems to be working, so my wallet must be ok?
[2015-01-27 12:40:26] 1 miner threads started, using 'spreadx11' algorithm.
[2015-01-27 12:40:27] GPU #0: GeForce GTX 850M, 1173 khash/s

commandline options for both miners was the same other than "-a spread" for sp_hash's miner

I'm completely new to this, so feel free to tell me to go off and read whatever if thats what I need to do