Quote from: EvilHamster on March 06, 2018, 08:23:56 PM

Quote from: cryptoillusion1 on March 06, 2018, 12:31:26 AM

Quote from: GabryRox on March 05, 2018, 11:49:46 PM

Quote from: EvilHamster on March 04, 2018, 05:13:19 PM

Firstly, thank you all for your help so far (messages and so on)

My rig - now 4 weeks old, ALL new kit.

Tried 11.2 today and apart from virus guards kicking off all over the place (until I disabled them all) failed to work.

I have now kind of got the rig working thanks to some help, however...

Starts at 64 Mh/s then reduces down and down...

ETH: GPU0 21.917 Mh/s, GPU1 10.142 Mh/s, GPU2 10.124 Mh/s, GPU3 21.923 Mh/s

ETH: GPU0 0.000 Mh/s, GPU1 10.132 Mh/s, GPU2 10.176 Mh/s, GPU3 21.906 Mh/s

Followed shortly by:

WATCHDOG: GPU 0 hangs in OpenCL call, exit
WATCHDOG: GPU 0 hangs in OpenCL call, exit
Quit, please wait...
Restarting OK, exit...

Then rig comes to a complete stand still...Wont go further.

Virtual memory 16gb, virus guard disabled...

Please any thoughts - this is killing me now...

Rig

Celeron - K170 board - 4gb ram - Msata HDD - 2 x rx570 4gb - 2 x RX550 4gb - Thermaltake 850psu...Windows 10 64bit.

yup... i posted the exact same issue a few days back but never saw a reply with fix suggested. Here's the thing... this is happening on all 4 of my 6x470 rigs... and really only since that last major W10 update. So, I am saying it is NOT a hardware issue because what are the odds that on 4 rigs, there is an actual problem with GPU0 on all 4? It never happens on any other GPU, so this means it is a software/settings issue, but I have not been able to figure it out. On Claymore Cryptonite miner, the solution to fix a lagging GPU0 was to manually designate the "-h" value in the .bat file, but no such option existing in this miner, at least not -h but maybe something else can be tweaked only on GPU0 to fix this... that has been what i've tried to discover for the past weeks but no solution yet. I actually had to disable GPU0 on 1 of my rigs that it got so bad, and looks like another 1 is headed that direction as well.

The one difference with mine is that they don't actually crash/freeze, but they get stuck in a non-stop look of resarting the miner due to that hanging GPU0 issue. So it restarts every couple minutes, usually with GPU0 at zero speed.

Claymore... or anyone else that knows of this issue... please advise. Thanks!

Windows 10 Pro - 8GB RAM - 16-32GB virtual memory - Claymore dual miner versions 10.2/10.5/10.6

Do you have a dummy plug or a monitor connected to GPU0 ? I have noticed this behavior when you remote and don't have a monitor/dummy plug connected

Nope - I have now stripped rig back to 2 x RX570;s nothing plugged in - no windows update - it ran perfect on 10.6 - jumped 11 and 11.1 now tried 11.2 - blat..

Tried re-installing drivers and all sorts.

GPU0 was doing 0 MHS so I now have taken GPU 1 which was running around 21-22.

ETH: GPU0 0.000 Mh/s
GPU0 t=54C fan=23%%
ETH: 03/06/18-20:21:44 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:01
ETH: GPU0 0.000 Mh/s
ETH: 03/06/18-20:21:46 - New job from eu1.ethermine.org:4444
WATCHDOG: GPU 0 hangs in OpenCL call, exit
GPU0 t=54C fan=0%%
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:02
ETH: GPU0 0.000 Mh/s
Quit, please wait...

So now feck all is happening in GPU0 regardless of whichever card you try.

Try it with Claymore 11.1 and see if you get the same results. My rig's did something similar because my bios settings min-max everything and the changes in 11.2 are just enough to push it off the cliff.
There are two ways to fix it 1) stop overclocking/undervolting manually and use the default bios and it works but with sub-par results compared to my own OC/UV settings or option 2) ...use Claymore 11.1