Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.4 (Windows/Linux)
by
lazyturtle
on 05/06/2017, 17:12:44 UTC
Hello everyone. I have a problem with one of my rigs.

I get the ""WATCHDOG: GPU 0 hangs in OpenCL call, exit" problem after about 20-60 min running the claymore miner. It started tough with that my miner was loosing internet connection after running a while. When i fixed that by installing new network adapter drivers, the connection was stable but the GPU´s started to give 0.00 mh´s after a while, until getting the error message.

I did overclock the rig in the beggining, but i have reseted the MSI afterburner settings to default and i also did a bios mod, but i flashed the cards back to the original bios. I also dont think that the bios mod was the problem, because i have 3 more rigs with rx 470 with the same mod, and they all work great.

Specs:
Intel Celeron G1840 Processor
Asrock H81 Pro BTC motherboard
6x AMD Radeon RX 470 4GB
4GB DDR3 Memory
60GB SDD Harddisk
1000W Gold power supply
Windows 10 operating system

I have already tried to:

- Run the miner with the gser and eser commands and have also tried both dual and solo mining(both have same problems).
- fresh install of both operating system and Gpu drivers (first gpu drivers with DDU and after that operating system).
- Checked every riser, but they all work on a diffrent system so thats not the problem.
- Setting virtual memory to atleast 16000
- Tried old claymore miners, from 6.3 and up, same problem.

I dont really know what to do at this point, would really appreciate help if someone knows what might be causing this. Smiley

leave 1 card only, remove other cards a mine for 2 hours. If the miner does not crash replace the card and repeat the test. If you do not find a "faulty card" by trying all 6 then start adding cards - two for 2 hours, 3 for 2 hours, 4 for 2 hours, 5 for 2 hours and finally 6. Post the results of these tests here.
First thing I would check is to see if Win10 changing virtual mem settings during an update(which I see you checked), or updated the drivers. Both things are on the same pop up. After checking virtual mem on the advance tab, click on the hardware tab and tell winblows to not update drivers. Winblows will update drivers as it boots. Also what are the card temps when they shut down or start spitting out opencl errors?

The temps variate between 62-70 at most at all times. I did solve this issue tough, but thanks for the response, was a weird bug in msi afterburner that would not reset my overclocking properly Smiley Thanks anyway, peace!