Quote from: Just_a_miner on March 18, 2018, 09:00:44 AM

Quote from: L0c0 on March 18, 2018, 02:56:39 AM

I gotta back MrPlus on this one, Excavator and HSRminer are the best for neoscrypt, giving 5-8% more than KlausT, but for people like myself with weak GPUs (Celeron 3930) and using +50/+600 OC and not having that much time to fine tune every setting, KlausT is way more stable (both Excavator and HSR would crash out of the blue).

Celeron 3930 is okay CPU for any decent rig with at least 8 x 1070 GTX.

Saying that miner crashes or unstable is incorrect - it's like saying that Windows 7 is unstable OS and often BSOD for no reason - and the only reasons why it can give you blue screen are that you either have faulty hardware (ram, cpu, gpu, etc), overclocked too much cpu/ram/gpu or you've installed some buggy driver that forced kernel to BSOD.

You should understand that crash is not software-related. It's not hsrminer that crash - it's your hardware (GPU) can't handle load from compute-intensive algo like neoscrypt with your current overclocking settings and fails - so cuda kernel that executes on GPU fails too - you get "crash". Reason why ccminer klaust seems "more stable" is very simple - it just doesn't load gpu as much as hsrminer or excavator due to lower default intensity (or not that intensive cuda kernel) and therefore you get lower hashrate.

In classic overclocking, where people push hardware to the limit and just want to pass 1 single 3dmark test, or complete 1 single run of SuperPi to screenshot it and post on site with OC records, it's okay to stress hardware, because it's like sprint - hardware suffer from exremly high load but for short period of time.

In case of mining it doesn't work, I think that mining is more like marathon, so I set medium and stable OC settings as GPUs gonna work for months.
As for balance beetwen high OC/medium load from software or medium OC/high load from software I choose second one because high OC settings will kill hardware faster.

My apologies, that did come out wrong, your miner by itself is not unstable, I've used it before without profit switching and it worked great.

What I meant by weak CPUs is that when used it in conjunction with NPM, specifically when using the "plus" option, then there's a problem. CcminerAlexis78 still has the problem of a long "warmup" time when running more than 3-4 cards, so I'm running 2 copies of NPM, and as much as I like the "plus" option, running 2 instances of that just punishes my CPU (even after the delay increase from 10 to 60s and changing priority to "below normal"), so when HSRminer kicks in while the CPU is already running at 100% causes it to sometimes crash. I have a friend running the same setup with an i3, he doesn't have this problem.

So just to reiterate, nothing wrong with HSRminer, it is just a casualty of that particular issue, not the cause. It is indeed faster than KlausT.