Topic: Claymore Miner randomly stops mining. (Read 200 times)
I decreased core and memory clock and for now it's stable.
It could be a bad connection between the x1 PCI-E connector from the riser and the slot or the USB cable. Make sure the connectors are pushed in well or try replacing them. Normally that would cause the GPU not to show up though.
Adjusting the power limit up can also help. The most common reason for a GPU hang is too little power or too much overclock. What I do when a GPU hangs, in order until it's stable is:
1/. Increase the core/vram voltage by 50mv.
2/. Increase the power limit by 5%
3/. Decrease the core and/or memory clock by 50 MHz
The first two may increase the GPU hash rate, power consumption and heat. The last will decrease the hash rate.
1/. Increase the core/vram voltage by 50mv.
2/. Increase the power limit by 5%
3/. Decrease the core and/or memory clock by 50 MHz
The first two may increase the GPU hash rate, power consumption and heat. The last will decrease the hash rate.
What i did is, i changed GPU slots. I plug GPU 3 in slot 4 and GPU 4 in slot 3 just to see will it now be problem with GPU 4 because i changed GPU 3 position.
Half hour later again problem with GPU 3... So now i know it's not problem with GPU or riser.
Only thing now is left to play with adjusting the power limit...
Can it be that my motherboard GPU 3 slot is bad ?
you may also want to consider and try to replace the riser used in GPU 3, more often risers are the culprit, I have those extras on the pocket once I need it.
Adjusting the power limit up can also help. The most common reason for a GPU hang is too little power or too much overclock. What I do when a GPU hangs, in order until it's stable is:
1/. Increase the core/vram voltage by 50mv.
2/. Increase the power limit by 5%
3/. Decrease the core and/or memory clock by 50 MHz
The first two may increase the GPU hash rate, power consumption and heat. The last will decrease the hash rate.
1/. Increase the core/vram voltage by 50mv.
2/. Increase the power limit by 5%
3/. Decrease the core and/or memory clock by 50 MHz
The first two may increase the GPU hash rate, power consumption and heat. The last will decrease the hash rate.
The error comes from GPU3. First try running the miner with GPU3 disabled and see if the problem continues. To disable a GPU use the -di option in claymore. If it doesn't happen again then we are sure the problem is with GPU3. Try to run GPU3 at default core clock and memory clock.
if increasing the voltage / decreasing clocks does not stabilize GPU3?
Hmmm, will try that. Thanks.
Same thing here. Works fine using PhoenixMiner.
Can you dual mine on PhoenixMiner ?
if increasing the voltage / decreasing clocks does not stabilize GPU3?
Same thing here. Works fine using PhoenixMiner.
Me too, already 1 week my Claymore gone unusual, it went restarting randomly, but i dunno what happened. Same thing too when i switch to mine ETC.
Would be gladly if someone can tell me what happened and how to fix this.
Would be gladly if someone can tell me what happened and how to fix this.
I'm mining ETH+ DCR with 6 RX580 and my miner randomly stops mining. I'm using latest version of Claymores miner.
I get this error.
11:30:07:180 153c ETH: job is the same
11:30:07:180 153c new buf size: 0
11:30:07:664 a88 em hbt: 15, dm hbt: 15, fm hbt: 78,
11:30:07:664 a88 watchdog - thread 0 (gpu0), hb time 109
11:30:07:679 a88 watchdog - thread 1 (gpu0), hb time 47
11:30:07:679 a88 watchdog - thread 2 (gpu1), hb time 94
11:30:07:679 a88 watchdog - thread 3 (gpu1), hb time 16
11:30:07:679 a88 watchdog - thread 4 (gpu2), hb time 109
11:30:07:695 a88 watchdog - thread 5 (gpu2), hb time 32
11:30:07:695 a88 watchdog - thread 6 (gpu3), hb time 90032
11:30:07:695 a88 WATCHDOG: GPU 3 hangs in OpenCL call, exit
11:30:07:695 a88 watchdog - thread 7 (gpu3), hb time 89938
11:30:07:711 a88 WATCHDOG: GPU 3 hangs in OpenCL call, exit
11:30:07:711 a88 watchdog - thread 8 (gpu4), hb time 125
11:30:07:711 a88 watchdog - thread 9 (gpu4), hb time 47
11:30:07:711 a88 watchdog - thread 10 (gpu5), hb time 0
11:30:07:726 a88 watchdog - thread 11 (gpu5), hb time 94
11:30:07:945 a88 Quit, please wait...
11:30:19:225 a88 Restarting OK, exit...
http://prntscr.com/if1s35
Does anyone have the same problem ?
I get this error.
11:30:07:180 153c ETH: job is the same
11:30:07:180 153c new buf size: 0
11:30:07:664 a88 em hbt: 15, dm hbt: 15, fm hbt: 78,
11:30:07:664 a88 watchdog - thread 0 (gpu0), hb time 109
11:30:07:679 a88 watchdog - thread 1 (gpu0), hb time 47
11:30:07:679 a88 watchdog - thread 2 (gpu1), hb time 94
11:30:07:679 a88 watchdog - thread 3 (gpu1), hb time 16
11:30:07:679 a88 watchdog - thread 4 (gpu2), hb time 109
11:30:07:695 a88 watchdog - thread 5 (gpu2), hb time 32
11:30:07:695 a88 watchdog - thread 6 (gpu3), hb time 90032
11:30:07:695 a88 WATCHDOG: GPU 3 hangs in OpenCL call, exit
11:30:07:695 a88 watchdog - thread 7 (gpu3), hb time 89938
11:30:07:711 a88 WATCHDOG: GPU 3 hangs in OpenCL call, exit
11:30:07:711 a88 watchdog - thread 8 (gpu4), hb time 125
11:30:07:711 a88 watchdog - thread 9 (gpu4), hb time 47
11:30:07:711 a88 watchdog - thread 10 (gpu5), hb time 0
11:30:07:726 a88 watchdog - thread 11 (gpu5), hb time 94
11:30:07:945 a88 Quit, please wait...
11:30:19:225 a88 Restarting OK, exit...
http://prntscr.com/if1s35
Does anyone have the same problem ?
Jump to: