CC Miner freezes with several coins

[LasnierCrews]

Hello there,

I'm just getting started in the world of mining and read myself into it. I already mined some coins using the Tribus algo and had no problems so far. The problems started when I tried different algos like "bitcore" or "X16R". After around 30 seconds my system freezes completely.  I'm using in my bat file ccminer -a bitcore -i 18 -o stratum+tcp://bitcorepool.cc:1111 -u MyWalletAdress -p x

My system:
Win 10
I7-8700k
Zotac 1080 GTX Ti
32 GB Ram
Samsung 850 Evo

What I registered was when using MSI Afterburner, that when mining, my CoreFreq starts to get to around 2000MHz without having changed anything. Normally it should stay at 1645 MHz and Boost to 1759 MHz [Default]. Changing the Intensity didn't help at all. Also I tried turning off the Energy System Management completely. So I would be happy for any further suggestions.

Thank you for your help.

[cpmcgrat]

Hello there,

I'm just getting started in the world of mining and read myself into it. I already mined some coins using the Tribus algo and had no problems so far. The problems started when I tried different algos like "bitcore" or "X16R". After around 30 seconds my system freezes completely.  I'm using in my bat file ccminer -a bitcore -i 18 -o stratum+tcp://bitcorepool.cc:1111 -u MyWalletAdress -p x

My system:
Win 10
I7-8700k
Zotac 1080 GTX Ti
32 GB Ram
Samsung 850 Evo

What I registered was when using MSI Afterburner, that when mining, my CoreFreq starts to get to around 2000MHz without having changed anything. Normally it should stay at 1645 MHz and Boost to 1759 MHz [Default]. Changing the Intensity didn't help at all. Also I tried turning off the Energy System Management completely. So I would be happy for any further suggestions.

Thank you for your help.

You most likely need to lower your intensity. The intensity means how many concurrent blocks are scheduled into the GPU memory in a given cycle. Different algorithms use different block sizes. Tribus most likely has a smaller block size than bitcore or x16r by default. I would recommend starting with an intensity of 1 then slowly increasing it until the system crashes, then step back down 1 (max intensity for given algorithm for your system).

[LasnierCrews]

Thank you so far. I tried it with lower intensities and it run a while. Though, I had a freeze with -I 15, but my system went on after a few seconds.

However, now I can see the error message, which is telling me "Cuda error in func 'cuda_check_cpu_target' at line 41 : unspecified launch failure."
Any Ideas how to prevent this?

[LasnierCrews]

Since it was telling me about the cpu I also added --cpu-priority 3 now. In MSI Afterburner I lowered my Power Limit to 80%. In return I overclocked my core and shader frequencies a little. Running now for 2 hours.

Seemed to do the trick.

[cpmcgrat]

Since it was telling me about the cpu I also added --cpu-priority 3 now. In MSI Afterburner I lowered my Power Limit to 80%. In return I overclocked my core and shader frequencies a little. Running now for 2 hours.

Seemed to do the trick.

Awesome, glad it worked out!