Quote from: Amph on May 08, 2016, 06:43:09 PM

Quote from: joblo on May 08, 2016, 05:55:07 PM

Quote from: Amph on May 08, 2016, 12:06:23 PM

Quote from: tbearhere on May 08, 2016, 10:49:10 AM

Quote from: Amph on May 05, 2016, 10:08:16 AM

ok, i've found how to reset to p2 state without rebooting your computer and without using inspector, just this nvidia-smi -rac

very useful, was a pain in the ass to reset each time i need to use other algo, which otherwise would result in a drivers crash with p0 state, like quark...probably due to the high overclock...

quark is the one with the most problems and then neoscrypt and lyra2v2 ... but quark is the worst.. even with no oc'ing.
There was a command in cuda mining - C 0 - C 1 -C 2 but there not in ccminer and I don't know if that would help in the oc'ing or not.

yeah when i shift from ethereum to quark with the same oc(+150 core/mem) i always get a crash, qubit is the same, there is a bug on the miner maybe? i don't remember such thing with 750ti and i had 10 of those baby...well there was not ethereum back then...

Do you use different intensities for different algos? The default -i may be too high when combined with OC on some
algos.

all at default, but i set p0 state for etheruem, maybe is that the problem? also the tdp is limted to 60%

I don't know if the p state has anything to do with the problem but I would recommend test algos that crash
with different intesnsities to find what is stable..

The intensity can be set on a per algo basis because it is a ccminer parameter but p state, tdp, OC etc are per
GPU so changing them would affect all algos. That way you can optimize each algo individually for each rig.

Another point is that different cards have different intensity limits so if you have different cards in the same rig
you will have to set it to a value that works on all cards which may not be optimum on some cards.