Quote from: thereal35 on September 26, 2018, 01:19:04 PM

As i was typing this, LOL stopped hashing. No error displayed, and system did not crash / reboot. It simply stopped hashing. Fired right back up and hashing at about the the same rates as above.

Hu, thats odd ... nothing displayed ... could it be that the text output was just over-scrolled? This some times happening on Windows.
Overall I found out it is likely more stable mining in two Command Lines open, one with --devices 0,1,2 and the second with --devices 3,4,5
I hope to get rid of this instabilities with many GPUs soon.

By the way you still can adjust OC settings maybe a bit. Afaik ETH reacts only to memory, while equihash has a certain clock sensitive part in it. Therefore keeping clocks high - but then with under-volt & lower power target may be worth a try.

Quote from: ljepic on September 26, 2018, 01:29:14 PM

On my other, 390 rig, 0.5 lolminer, when start mining says gpu0 stucked, miner is restarting.. Driver 18.3.4.

Any help?

It seems the 380 does not like the new Minexcoin code ... its always a bit difficult to tune, what makes the one GPU fly can push the other down. Maybe run it for short to see if its also lower on pool. The 0.42 was rather unstable afaik. But I will try to investigate what may have happened there. Regarding the 2nd rig: here I would trs to run two windows. But I will check back again the code if I missed some memory check somewhere there - usually with the new code gen this stucking stuff should have been eliminated. *Search*

Quote from: BigHarryArmsi on September 26, 2018, 01:36:07 PM

I just deleted all the old and downloaded v5 again and same result. Is there a new download I didn't see? Thank you for your hard work!

Thats odd ... Linux or Windows? I was just mining BTCZ with it ...
(this are the current links)
https://www.dropbox.com/s/nu0oe4tv2ncu50c/lolMiner_v05_Win64.zip?dl=1
https://www.dropbox.com/s/p3f2g5w08hs2jlu/lolMiner_v05_Lin64.tar.gz?dl=1

--------------

Ps: I just silently updated the archive again. I added two fields about the accepted shares in the API and created an option for moving the log file (--logfile /some/path/to/file.txt) so you now can move it. Note you need --logs 1 and the new param to see a file created and printed. Also you need write access to the directory you want to have it.