Latest posts of: prier

Interesting indeed.

Move the GPU with that error to a different slot with different cables, and see what GPU has the error. If the GPU you moved has the error again, I would assume it could be failing, it's the luck of the silicon lottery..

Sorry for the late reply. I tried to disable GPU 12 and the miner works with GPUs 1-11. Then I tried to disable GPU9 and re-enable GPU 12 and the miner also works with GPU12 now working and GPU9 idle. I swapped the cards a bit too just to rule out hardware.

It appears only 11 GPUs can run at any given time. So this confirms it is not a GPU hardware problem.

I raised the VRAM to min 40GB and max 56GB and all 12 GPUs were humming along just fine. Thank you PhoenixMiner devs for the tip.

Hi there, i basically got the same problem with my 1070s rig (11x) on Win10. Since DAG 200 Phönixminer fails to start some of the GPUs (usually 1-5 are ok, 6-12 failed). In Claymore 11.9 everything is working fine. I tested the hardware and everything is fine.

I did:
- test the graphic cards (no issues in other rig with linux)
- raise the VRAM to 40GB (min) and 56GB (max)
- update Nvidia driver to latest update

Still i got this errors:

Code:

2018.08.10:13:37:38.055: wdog GPU6 not responding
2018.08.10:13:37:38.055: wdog GPU7 not responding
2018.08.10:13:37:38.055: wdog GPU8 not responding
2018.08.10:13:37:38.055: wdog GPU9 not responding
2018.08.10:13:37:38.055: wdog GPU10 not responding
2018.08.10:13:37:38.055: wdog GPU11 not responding
2018.08.10:13:37:38.055: wdog Thread(s) not responding. Restarting.

Im Using win10 with several 1070 and 1070ti's overclocked with nvidiaInspector. Overclocks did work for the last 7 months. And Claymore 11.9 works perfectly fine (less hashrate though).

Would be happy to get some help on this. Will post the solution.

Same problem here, since no recent update i had to switch back to claymore