Claymore Crashing (WatchDog hang error)

PCRGMPCRGM Member Posts: 46
Hello, recently I've been having some issues with Claymore Crashing. Here's what the problem is
"WATCHDOG: GPU 0 hangs in OpenCL call, exit
08:32:42:037 1adc watchdog - thread 1, hb time 76254
08:32:42:037 1adc WATCHDOG: GPU 0 hangs in OpenCL call, exit
08:32:42:037 1adc watchdog - thread 2, hb time 125
08:32:42:038 1adc watchdog - thread 3, hb time 328
08:32:42:038 1adc watchdog - thread 4, hb time 16
08:32:42:038 1adc watchdog - thread 5, hb time 219
08:32:42:038 1adc watchdog - thread 6, hb time 76222
08:32:42:039 1adc WATCHDOG: GPU 3 hangs in OpenCL call, exit
08:32:42:039 1adc watchdog - thread 7, hb time 76020
08:32:42:039 1adc WATCHDOG: GPU 3 hangs in OpenCL call, exit
08:32:42:039 1adc watchdog - thread 8, hb time 156
08:32:42:040 1adc watchdog - thread 9, hb time 63
08:32:43:100 1adc Restarting OK, exit..."

Whenever this happens, the whole computer freezes (Not using the computer for anything else) It is interesting to note, though, how GPU 4 doesn't hang like the others.

What might be causing this, it wasn't running for very long when it did this. Yesterday it ran for 24 hours and 2 minutes, then did the same thing.
«1

Comments

  • Dr_House86Dr_House86 Member Posts: 566 ✭✭✭
    Undervolted or overclocked to much.
  • PCRGMPCRGM Member Posts: 46
    Neither, they are both on stock settings. Radeon Doesn't detect the temperatures, neither does Claymore "Create GPU buffer for GPU #1
    12:35:58:062 1784 Create GPU buffer for GPU #4
    12:35:58:742 14bc Cannot get Overdrive capabilities for adapter 0
    12:35:58:749 14bc Cannot get Overdrive capabilities for adapter 6
    12:35:58:757 14bc Cannot get Overdrive capabilities for adapter 12
    12:35:58:762 14bc Cannot get Overdrive capabilities for adapter 13
    12:36:01:799 14bc Cannot get Overdrive capabilities for adapter 0
    12:36:01:806 14bc Cannot get Overdrive capabilities for adapter 6
    12:36:01:814 14bc Cannot get Overdrive capabilities for adapter 12
    12:36:01:819 14bc Cannot get Overdrive capabilities for adapter 13
    12:36:03:864 1784 GPU 4 DAG creation time 5635 ms
    12:36:03:865 1784 Setting DAG epoch #76 for GPU #4 done
    12:36:03:971 1738 GPU 2 DAG creation time 5789 ms
    12:36:03:972 1738 Setting DAG epoch #76 for GPU #2 done
    12:36:03:984 170c GPU 1 DAG creation time 5784 ms
    12:36:03:984 170c Setting DAG epoch #76 for GPU #1 done
    12:36:03:989 1714 GPU 0 DAG creation time 5784 ms
    12:36:03:990 1714 Setting DAG epoch #76 for GPU #0 done
    12:36:03:996 1730 GPU 3 DAG creation time 5783 ms
    12:36:03:997 1730 Setting DAG epoch #76 for GPU #3 done
    12:36:04:862 14bc Cannot get Overdrive capabilities for adapter 0
    12:36:04:868 14bc Cannot get Overdrive capabilities for adapter 6
    12:36:04:876 14bc Cannot get Overdrive capabilities for adapter 12
    12:36:04:881 14bc Cannot get Overdrive capabilities for adapter 13"

    Now it freezes right away when it starts. I'm going to re-download it.
  • Sequoia93Sequoia93 Member Posts: 130
    I am having the same issue, even had it happen after both 12 hours and 20 minutes....

    Did you ever figure out a solution?
  • CoreolCoreol Member Posts: 30
    Which version of claymore are you using? I had an occasional watchdog error on v7.0 beta which led to the miner auto restarting after a while. On v7.1 I've yet to see this error
  • Sequoia93Sequoia93 Member Posts: 130
    I'm running 7.1.

    As @PCRGM says, it restarts then freezes.

    specifically, at least for me, the new log file created after claymore restarts, stops at "GPU 0 hangs in OpenCL call" then the PC freezes....This never happens when I start the miner normally.
  • cvipercviper Member Posts: 132 ✭✭
    use driver 16.9.1 and claymore 6.3
  • CalivetCalivet Member Posts: 194 ✭✭
    How much virtual memory do you have? At least 16gb set? Sometimes what helps is entering this option in your command line -gser 2. I also would enter -eres. Both these commands help with this issue your having.
  • Sequoia93Sequoia93 Member Posts: 130
    I have 18gb virtual mem, and am running 16.9.1. I may try downgrading Claymore. Although I meant to try -gser today and totally forgot. I'll try that overnight tonight.
  • master2neomaster2neo Member Posts: 3
    i have same problem, but with my 6 gpus msi 390, any solution?
  • Sequoia93Sequoia93 Member Posts: 130
    I added -gser and still had the problem occur a few hours later. Right now its been running for almost 24hrs without issue, but I have a feeling it will re-occur.

    @master2neo What driver version and what version of claymore are you running?
  • master2neomaster2neo Member Posts: 3
    @Sequoia93 i have the claymore 7.1 and driver fglrx-updates on ubuntu 14.04.5 and my mobo is the 990fxa-ud3
  • Sequoia93Sequoia93 Member Posts: 130
    interesting, I'm running 7.1 as well, but on win10. I was running 16.9.2 ( I was wrong in my earlier post), but I just downgraded back to 16.9.1, and now I lost about 2MH/s per card! No idea why, but I'm thinking I'll downgrade Claymore if I cant get the MH/s back or if Claymore crashes when restarting again....
  • hasherhasher Member Posts: 642 ✭✭✭
    I've noticed some of my rigs don't like the new 7.1, so I downgraded the problematic rigs to 7.0 - stability has returned.
  • Paul12345Paul12345 Member Posts: 2
    edited October 2016
    PCRGM said:

    Hello, recently I've been having some issues with Claymore Crashing. Here's what the problem is
    "WATCHDOG: GPU 0 hangs in OpenCL call, exit
    08:32:42:037 1adc watchdog - thread 1, hb time 76254
    08:32:42:037 1adc WATCHDOG: GPU 0 hangs in OpenCL call, exit
    08:32:42:037 1adc watchdog - thread 2, hb time 125
    08:32:42:038 1adc watchdog - thread 3, hb time 328
    08:32:42:038 1adc watchdog - thread 4, hb time 16
    08:32:42:038 1adc watchdog - thread 5, hb time 219
    08:32:42:038 1adc watchdog - thread 6, hb time 76222
    08:32:42:039 1adc WATCHDOG: GPU 3 hangs in OpenCL call, exit
    08:32:42:039 1adc watchdog - thread 7, hb time 76020
    08:32:42:039 1adc WATCHDOG: GPU 3 hangs in OpenCL call, exit
    08:32:42:039 1adc watchdog - thread 8, hb time 156
    08:32:42:040 1adc watchdog - thread 9, hb time 63
    08:32:43:100 1adc Restarting OK, exit..."

    Whenever this happens, the whole computer freezes (Not using the computer for anything else) It is interesting to note, though, how GPU 4 doesn't hang like the others.

    What might be causing this, it wasn't running for very long when it did this. Yesterday it ran for 24 hours and 2 minutes, then did the same thing.


    Did you got a solution? I have the same problem into a Win10 AMD Rig with 6 MSI R9 390X, which is a clone of a second one running very well for a long time! The only HW difference is the CPU (malfunction RIG with one Intel Core i3 and the other has a Core I5).

    The Claymore version V7.0 or V7.1, V7,2 does not change anything neither intensity or powerlimit parameters. All temperature sensors where also checked and no OC is beeing used.

    The only difference I have found until now between the two Rigs it was a Error in some counters when running the Command "PERFMON". Also solved it with the command line "lodctr /r". (http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/perfmon-problems-unable-to-add-counters/e90f231d-0014-457d-8b1f-5f342971597a)

    I have exchanged DRAM's (no difference) and the Motherboard. I'm making the final tests.
  • murendiemurendie Member Posts: 3
    Im having the same problem. 4X Sapphire Raedon RX 480 8GB OC. 1200 Power supply, Windows 10, 64GB SSD, 4GB Ram. Watchdon GPU0 hangs after 10 Mins of running
  • Paul12345Paul12345 Member Posts: 2
    Regarding the issue type "WATCHDOG: GPU ... hangs in OpenCL call, exit" with Claymore dual mining, I can now confirm the issue was solved after a fresh Windows 10 install.

    Check also the USB Riser, since any malfunction of the cable/connector or riser board can also cause this hangs issue according with complete testing I have done and after change all the hardware (CPU, DRAM, motherboard, PSU's).
  • mayhemfreakmayhemfreak Member Posts: 2
    Got the same issue. Running windows 7, claymore 7.2, 2x RX480 and 1x R380 all stock setting and bios.
    I have determined that it is not risers or gpu's.
    Not that technical minded on software related, but to obvious to ignore was that the crash started together with the first attack on eth. Can that be an issue?
    I am pool mining, but this is a low spec rig. It however did mine flawlessly before the attacks.
    Any insights to that being the issue or why it cant be?
  • LickMyNvidiaLickMyNvidia Member Posts: 36
    I have had all kinds of problems with my system and Claymore's miner crashing. The best solution I have found is to rum Claymor's Miner v6.3. That version seams to never quit, but you don't get to see GPU temps.
  • mayhemfreakmayhemfreak Member Posts: 2
    edited October 2016
    -gser and -eser fixed it thus far.. running for 2h now. Claymore 7.2 and 16.8.2. Claymore 6.3 crashed on startup for me.

    EDIT: Ran 5 hours then crash.
    Post edited by mayhemfreak on
  • Sequoia93Sequoia93 Member Posts: 130
    For me, this issue ended up being a faulty riser. However watchdog still freezes the pc if there is an error... seems to me that it just needs work.
    i use -wd 0 so it will keep mining with the other 5 cards if something does happen, which is only occasionally as I have nearly pinned down my ideal settings for each card.
  • SWDude26SWDude26 Member Posts: 132 ✭✭
    edited October 2016
    I feel like this could be my current issues.

    Updated drivers to 10.9.2 (I think) and running either 7.1 or 7.2 of claymore. Can't make it passed 12 hours without my rig freezing up. No ping, No remote connection, and no hashrates... It being 40 mins away at work kills me. Lost 2 weekends of mining now.

    Going to go back to go back to pre 7.0 and see if that solves it.

    If that doesn't work I'm going to buy this:

    https://www.amazon.com/dp/B00WV7GMA2/ref=wl_it_dp_o_pC_nS_ttl?_encoding=UTF8&colid=16D4161QGSS4Q&coliid=IDG4ZUVF69ER6

    And hook up my Pi rev 1 to control it so I can remote hard restart my machine and get it back going.
  • mikeminermikeminer Member Posts: 38
    SWDude26 said:

    I feel like this could be my current issues.

    Updated drivers to 10.9.2 (I think) and running either 7.1 or 7.2 of claymore. Can't make it passed 12 hours without my rig freezing up. No ping, No remote connection, and no hashrates... It being 40 mins away at work kills me. Lost 2 weekends of mining now.

    Going to go back to go back to pre 7.0 and see if that solves it.

    If that doesn't work I'm going to buy this:

    https://www.amazon.com/dp/B00WV7GMA2/ref=wl_it_dp_o_pC_nS_ttl?_encoding=UTF8&colid=16D4161QGSS4Q&coliid=IDG4ZUVF69ER6

    And hook up my Pi rev 1 to control it so I can remote hard restart my machine and get it back going.

    I using those Smartplug adapter. Can remote power down as long as the plug connected to Internet. They make by Dlink or Tplink. The cheapest one so far are from Xiaomi.
  • SWDude26SWDude26 Member Posts: 132 ✭✭
    mikeminer said:

    SWDude26 said:

    I feel like this could be my current issues.

    Updated drivers to 10.9.2 (I think) and running either 7.1 or 7.2 of claymore. Can't make it passed 12 hours without my rig freezing up. No ping, No remote connection, and no hashrates... It being 40 mins away at work kills me. Lost 2 weekends of mining now.

    Going to go back to go back to pre 7.0 and see if that solves it.

    If that doesn't work I'm going to buy this:

    https://www.amazon.com/dp/B00WV7GMA2/ref=wl_it_dp_o_pC_nS_ttl?_encoding=UTF8&colid=16D4161QGSS4Q&coliid=IDG4ZUVF69ER6

    And hook up my Pi rev 1 to control it so I can remote hard restart my machine and get it back going.

    I using those Smartplug adapter. Can remote power down as long as the plug connected to Internet. They make by Dlink or Tplink. The cheapest one so far are from Xiaomi.
    Xiaomi is also recalling a lot of their products due to the DDoS attacks originating from millions of their IoT being infected lol. That's just a side note though.

    Came into work today and I either have a dead GPU or powered riser. Hoping its the riser. Ordered 2 more. (1 for a backup). Hopefully have the 6th GPU back and running Wednesday. I know I could plug in the card into a working riser to test, but I didn't feel like cutting more zip ties.

    Running 6.3 Claymore. 3 hrs stable so far.
  • mikeminermikeminer Member Posts: 38
    SWDude26 said:

    mikeminer said:

    SWDude26 said:

    I feel like this could be my current issues.

    Updated drivers to 10.9.2 (I think) and running either 7.1 or 7.2 of claymore. Can't make it passed 12 hours without my rig freezing up. No ping, No remote connection, and no hashrates... It being 40 mins away at work kills me. Lost 2 weekends of mining now.

    Going to go back to go back to pre 7.0 and see if that solves it.

    If that doesn't work I'm going to buy this:

    https://www.amazon.com/dp/B00WV7GMA2/ref=wl_it_dp_o_pC_nS_ttl?_encoding=UTF8&colid=16D4161QGSS4Q&coliid=IDG4ZUVF69ER6

    And hook up my Pi rev 1 to control it so I can remote hard restart my machine and get it back going.

    I using those Smartplug adapter. Can remote power down as long as the plug connected to Internet. They make by Dlink or Tplink. The cheapest one so far are from Xiaomi.
    Xiaomi is also recalling a lot of their products due to the DDoS attacks originating from millions of their IoT being infected lol. That's just a side note though.

    Came into work today and I either have a dead GPU or powered riser. Hoping its the riser. Ordered 2 more. (1 for a backup). Hopefully have the 6th GPU back and running Wednesday. I know I could plug in the card into a working riser to test, but I didn't feel like cutting more zip ties.

    Running 6.3 Claymore. 3 hrs stable so far.
    Hmm.. did you have any news link regarding this xiaomi recall their IoT devices? Hope my xm devices not contribute to any ddos attacks. :cold_sweat:

  • BTCUserBTCUser Member Posts: 23
    was there a solution? i did a fresh install and checked the risers...
  • iJordaniJordan Member Posts: 1
    BTCUser said:

    was there a solution? i did a fresh install and checked the risers...

    Try to decrease memory clock a little bit on the card that crashes.
  • jwchongjwchong Member Posts: 1
    Hi,

    Since i have similar problem, I do not plan to create another thread to make the issue more complex. Instead, I will discuss the issue in this thread.

    Click the Spoiler button below to see my log file (I have simplified it / omitted some not important logs, so that you can check more easily.

    Notice the time between the time 07:13:54:946 and 11:48:42:889? The Watchdog restarted the miner, but was stop at 07:13:54:946, when I notice it, I remote login to the rig via teamviewer at 11:48:42:889. Without doing anything, the Claymore just continue loading and started mining. I did not do anything else.

    I need to troubleshoot 2 issues:
    1) What cause my GPU2 always hang randomly around once every 2 or 3 days. I can find fix this issue, then issue below is not relevant anymore.
    2) What cause this Watchdog restarting miner stop. Only resume when I login to the rig.

    07:13:47:478 1518 watchdog - thread 4 (gpu2), hb time 69203
    07:13:47:478 1518 WATCHDOG: GPU 2 hangs in OpenCL call, exit
    07:13:47:478 1518 watchdog - thread 5 (gpu2), hb time 69047
    07:13:47:478 1518 WATCHDOG: GPU 2 hangs in OpenCL call, exit
    07:13:47:478 1518 watchdog - thread 6 (gpu3), hb time 94
    07:13:47:478 1518 watchdog - thread 7 (gpu3), hb time 234
    07:13:47:478 1518 watchdog - thread 8 (gpu4), hb time 156
    07:13:47:478 1518 watchdog - thread 9 (gpu4), hb time 15
    07:13:47:478 1518 watchdog - thread 10 (gpu5), hb time 219
    07:13:47:478 1518 watchdog - thread 11 (gpu5), hb time 62
    07:13:47:510 1518 OC v7, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst
    07:13:47:510 1518 OC v7, Reset control for GPU 1, close miner right now if you want to use default control from Catalyst
    07:13:47:510 1518 OC v7, Reset control for GPU 2, close miner right now if you want to use default control from Catalyst
    07:13:47:525 1518 OC v7, Reset control for GPU 3, close miner right now if you want to use default control from Catalyst
    07:13:47:525 1518 OC v7, Reset control for GPU 4, close miner right now if you want to use default control from Catalyst
    07:13:47:525 1518 OC v7, Reset control for GPU 5, close miner right now if you want to use default control from Catalyst
    07:13:48:666 1518 Restarting OK, exit...

    07:13:51:930 1c34
    07:13:52:055 1c34 …ÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕª
    07:13:52:071 1c34 ∫ Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.5 ∫
    07:13:52:102 1c34 »ÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕº
    07:13:52:118 1c34
    07:13:53:913 1c34 OpenCL platform: AMD Accelerated Parallel Processing
    07:13:53:914 1c34 OpenCL initializing...
    07:13:53:914 1c34 AMD Cards available: 6
    07:13:53:915 1c34 GPU #0: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:915 1c34 GPU #0 recognized as Radeon RX 470/570
    07:13:53:915 1c34 GPU #1: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:916 1c34 GPU #1 recognized as Radeon RX 470/570
    07:13:53:916 1c34 GPU #2: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:917 1c34 GPU #2 recognized as Radeon RX 470/570
    07:13:53:917 1c34 GPU #3: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:917 1c34 GPU #3 recognized as Radeon RX 470/570
    07:13:53:918 1c34 GPU #4: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:918 1c34 GPU #4 recognized as Radeon RX 470/570
    07:13:53:919 1c34 GPU #5: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:919 1c34 GPU #5 recognized as Radeon RX 470/570
    07:13:53:919 1c34 POOL/SOLO version
    07:13:53:920 1c34 b351
    07:13:53:920 1c34 Platform: Windows
    07:13:53:944 1c34 start building OpenCL program for GPU 0...
    07:13:54:219 1c34 done
    07:13:54:443 1c34 start building OpenCL program for GPU 1...
    07:13:54:724 1c34 done
    07:13:54:946 1c34 start building OpenCL program for GPU 2...
    11:48:42:889 1c34 done
    11:48:43:094 1c34 start building OpenCL program for GPU 3...
    11:48:43:430 1c34 done
    11:48:43:638 1c34 start building OpenCL program for GPU 4...
    11:48:44:022 1c34 done
    11:48:44:225 1c34 start building OpenCL program for GPU 5...
    11:48:44:492 1c34 done
  • PCRGMPCRGM Member Posts: 46
    BTCUser said:

    was there a solution? i did a fresh install and checked the risers...

    I reinstalled windows to windows 10 pro, and disabled windows updates. This fixed the problem
    jwchong said:

    Hi,

    Since i have similar problem, I do not plan to create another thread to make the issue more complex. Instead, I will discuss the issue in this thread.

    Click the Spoiler button below to see my log file (I have simplified it / omitted some not important logs, so that you can check more easily.

    Notice the time between the time 07:13:54:946 and 11:48:42:889? The Watchdog restarted the miner, but was stop at 07:13:54:946, when I notice it, I remote login to the rig via teamviewer at 11:48:42:889. Without doing anything, the Claymore just continue loading and started mining. I did not do anything else.

    I need to troubleshoot 2 issues:
    1) What cause my GPU2 always hang randomly around once every 2 or 3 days. I can find fix this issue, then issue below is not relevant anymore.
    2) What cause this Watchdog restarting miner stop. Only resume when I login to the rig.

    07:13:47:478 1518 watchdog - thread 4 (gpu2), hb time 69203
    07:13:47:478 1518 WATCHDOG: GPU 2 hangs in OpenCL call, exit
    07:13:47:478 1518 watchdog - thread 5 (gpu2), hb time 69047
    07:13:47:478 1518 WATCHDOG: GPU 2 hangs in OpenCL call, exit
    07:13:47:478 1518 watchdog - thread 6 (gpu3), hb time 94
    07:13:47:478 1518 watchdog - thread 7 (gpu3), hb time 234
    07:13:47:478 1518 watchdog - thread 8 (gpu4), hb time 156
    07:13:47:478 1518 watchdog - thread 9 (gpu4), hb time 15
    07:13:47:478 1518 watchdog - thread 10 (gpu5), hb time 219
    07:13:47:478 1518 watchdog - thread 11 (gpu5), hb time 62
    07:13:47:510 1518 OC v7, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst
    07:13:47:510 1518 OC v7, Reset control for GPU 1, close miner right now if you want to use default control from Catalyst
    07:13:47:510 1518 OC v7, Reset control for GPU 2, close miner right now if you want to use default control from Catalyst
    07:13:47:525 1518 OC v7, Reset control for GPU 3, close miner right now if you want to use default control from Catalyst
    07:13:47:525 1518 OC v7, Reset control for GPU 4, close miner right now if you want to use default control from Catalyst
    07:13:47:525 1518 OC v7, Reset control for GPU 5, close miner right now if you want to use default control from Catalyst
    07:13:48:666 1518 Restarting OK, exit...

    07:13:51:930 1c34
    07:13:52:055 1c34 …ÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕª
    07:13:52:071 1c34 ∫ Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.5 ∫
    07:13:52:102 1c34 »ÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕº
    07:13:52:118 1c34
    07:13:53:913 1c34 OpenCL platform: AMD Accelerated Parallel Processing
    07:13:53:914 1c34 OpenCL initializing...
    07:13:53:914 1c34 AMD Cards available: 6
    07:13:53:915 1c34 GPU #0: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:915 1c34 GPU #0 recognized as Radeon RX 470/570
    07:13:53:915 1c34 GPU #1: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:916 1c34 GPU #1 recognized as Radeon RX 470/570
    07:13:53:916 1c34 GPU #2: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:917 1c34 GPU #2 recognized as Radeon RX 470/570
    07:13:53:917 1c34 GPU #3: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:917 1c34 GPU #3 recognized as Radeon RX 470/570
    07:13:53:918 1c34 GPU #4: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:918 1c34 GPU #4 recognized as Radeon RX 470/570
    07:13:53:919 1c34 GPU #5: Ellesmere, 4096 MB available, 32 compute units
    07:13:53:919 1c34 GPU #5 recognized as Radeon RX 470/570
    07:13:53:919 1c34 POOL/SOLO version
    07:13:53:920 1c34 b351
    07:13:53:920 1c34 Platform: Windows
    07:13:53:944 1c34 start building OpenCL program for GPU 0...
    07:13:54:219 1c34 done
    07:13:54:443 1c34 start building OpenCL program for GPU 1...
    07:13:54:724 1c34 done
    07:13:54:946 1c34 start building OpenCL program for GPU 2...
    11:48:42:889 1c34 done
    11:48:43:094 1c34 start building OpenCL program for GPU 3...
    11:48:43:430 1c34 done
    11:48:43:638 1c34 start building OpenCL program for GPU 4...
    11:48:44:022 1c34 done
    11:48:44:225 1c34 start building OpenCL program for GPU 5...
    11:48:44:492 1c34 done
  • eFiJyeFiJy Member Posts: 7
    Hi. My rig runs on Win10 Pro 64bit. I have 60 GB of VM, and 2 Corsair HX1200i PSUs. Claymore version is 11.8
    It consists of 8 Vega 64s, which I managed to set them all properly in terms of power consumption as well as hashrate.
    I have been mining for several weeks now with it.

    At first I mined cryptonight coins, especially Monero, but after a while I realized that it is best for me to try Ethereum maybe.
    I did that and after all the tweaks I did in overdrive and reg, I get 44 mhs/card.
    A few days ago I started having this issue with one card, that caused the hanging in opencl error for me too, showing at first 0 mhs and then blocking the miner.

    The good thing is that I know what is the exact card which causes the problems.
    The bad thing is that I replaced riser, power cable, reinstalled drivers after DDU, reapplied PPTs, disabled Crossfire and UIps and the card is still hanging after about 10-15 minutes of mining, and the miner freezes, even though I also added in the batch file -wd 0 -gser 1 and -gser2.

    I did this thing one day after I got the hanging issues. While the gpus were working, not mining, but still working, I pulled out the 2 power cables from this one gpu and then reinstalled them. An interesting behaviour was seen after this, more exactly, the rgb lighting is solid white all the way. It doesn't matter if I put the rgb lighting to off or change colors for all the cards, this one stays solid white.
    I imagine this might have something to do with the hanging, probably I have broken something in it, don't know exactly.
    Even though it still works and mines, until it stops.

    Worth mentioning (maybe) that the other 7 cards have a Samsung memory and this one doesn't, according to GPU-Z. Maybe this one can't be underclocked and undervolted as the others. But I have taken this into consideration also, and put 1402/925, 1100/905 and 0 power limit. Still nothing. I will try to put maybe a little less on the gpu clock, but not too less.

    My overdrive settings are 852/800, 1100/800, 3500-4900 RPM, -25 power limit.
    I know, you will say that they are way underclocked and undervolted, but until this issue, all worked just perfectly, with a 1490W consumption. I did this because, as you know, Vegas are power hungry, and I had like 2000W consumption without these settings. My lightbulb was flickering in the room. Cheesy

    I checked all the forums and read this whole topic, but can't seem to find a solution.
Sign In or Register to comment.