Author

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 441. (Read 6590718 times)

member
Activity: 97
Merit: 13
it also happens to me 2 weeks ago.
I changed to genoil and it continue to work , but today again stop work. Same error claymore ( CUDA error 11 cannot allocate DAG) and genoil (lack of memory).
But I have other miner with NVOC and genoil and it is working correctly.
So I imagined it is a problem of my windows 64bit anniversary. I updated nvidia driver to the last version, but still not working.



ok guys it seems 3gb cards have officially stopped working on eth network.  Dag erro etc etc, the 6gb cards in the same rigs are doing fine. surprising though is that under stats its says 2.4gb used for dag.

one by one all the 3gb rigs gave up.

or am i missing something?
newbie
Activity: 30
Merit: 0
ok guys it seems 3gb cards have officially stopped working on eth network.  Dag erro etc etc, the 6gb cards in the same rigs are doing fine. surprising though is that under stats its says 2.4gb used for dag.

one by one all the 3gb rigs gave up.

or am i missing something?
newbie
Activity: 162
Merit: 0
Do you guys dual mine? If, which coin is best?

I mined dual Eth / Sia - But Sia Diff is too high now..

I tried DCR - But then my cards have too low eth-hashrate and if I change the intensity there is very low income from DCR.

What's you opinion on this?

Dual mining with current coins SIA/DCR etc is not worth anymore.

Claymore dev is working on a new set of coins for dual mining.
Not sure which ones yet and which algo but looks like is going to be soon.
newbie
Activity: 42
Merit: 0
When the card is not accessible do you get a yellow triangle sign in your device manager (if you use windows 10 e.g.)?

I hade some gtx 1070, they worked from time to time - then again they didn't.
After some reboot they worked then they didnt etc..

Replaced the card, everything fine.. :-(
newbie
Activity: 6
Merit: 0
I have 3 GPUs (one Vega 64, two RX 580s) and I can only consistently keep the vega 64 and one RX580 connected after reboots.  I've checked the risers (they appear to be good).  I saw on youtube that sometimes the video cards don't work without them thinking that they have a video card attached so I have two monitors (or I can use the HDMI plugin that fakes a monitor).  I have an older MOBO that should have the appropriate requirements but as I mentioned earlier, sometime I can get the rig to see the third card but sometimes I can't. 

Any suggestions?
newbie
Activity: 42
Merit: 0
Claymore's Dual Ethereum AMD v10.6 (Windows)

after an hour of work, a problem appears on the rx 570 cards,

can not get curren- t temperature, error 15

reboot the system and everything is working fine

Maybe OC too high?

Every single failure I had with Claymores - Turned out = too much memory oc Wink
newbie
Activity: 112
Merit: 0
Claymore's Dual Ethereum AMD v10.6 (Windows)

after an hour of work, a problem appears on the rx 570 cards,

can not get curren- t temperature, error 15

reboot the system and everything is working fine
newbie
Activity: 42
Merit: 0
Do you guys dual mine? If, which coin is best?

I mined dual Eth / Sia - But Sia Diff is too high now..

I tried DCR - But then my cards have too low eth-hashrate and if I change the intensity there is very low income from DCR.

What's you opinion on this?
member
Activity: 146
Merit: 10
I got my miner crashing few times over the day with the message "Miner has stop working"

I cant see any errors, I do get sometimes freeze, I have no idea why, I have 4GB ram on the pc, 2 raiser , which I already swap to new one.

I got 580 OC edition, with default settings.

Anyone got the same issue?
i have the same problem with diferents rigs, maybe is a problem with the version 10.6? have you resolve the issue?
sr. member
Activity: 574
Merit: 261



https://unitedcardists.com/download/file.php?id=18090&mode=view

(what's the trick to posting imbedded graphics?   hmmmm...  I hadn't tried)




You can not embed any graphics as you are a Newbie you have to be a "Jr.Member" before you can post with pictures.
full member
Activity: 434
Merit: 107
for 9 cards you need more virtual memory, DAG i 2.3G now ( 9x 2.3 = 20.7g ), set virtual memory initial 24G, max 44G

Thank you valev1.
That fixed the issue.  Cheesy
I set mine to 25,000 - 30,000 for now and its working great. 9 cards hashing away.

Also link below for current dag size:
https://investoon.com/tools/dag_size
newbie
Activity: 182
Merit: 0
If someone knows why the miner won't mine at the right speed:
https://bitcointalksearch.org/topic/m.29675265
newbie
Activity: 6
Merit: 0
@Claymore. Been mining eth for a while with your miner, works perfectly. Tried mining pirl now, and it all works fine until the dev fee starts, after the dev fee ends and the normal mining starts all my cards fall down to 0 hashrate and dont recover. Any idea what it could be?

11:09:12:176   1768   ETH: GPU0 30.062 Mh/s, GPU1 0.000 Mh/s, GPU2 30.072 Mh/s, GPU3 30.048 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
11:09:13:739   638   DevFee: stop mining and disconnect
11:09:14:536   1768   ETH: checking pool connection...
11:09:14:536   1768   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

11:09:14:567   1768   got 237 bytes
11:09:14:567   1768   buf: {"id":3,"jsonrpc":"2.0","result":["0x57ffe285ea553d80437ec715e64f818acc1f4c615e3c53a6edf43d51d5ebe50f","0xb15bb3623092c525165d45efa2d08540708d90d033aaa9fe4be8fd16ff904df0","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"]}

11:09:14:567   1768   parse packet: 236
11:09:14:567   1768   ETH: job is the same
11:09:14:567   1768   new buf size: 0
11:09:21:318   1638   em hbt: 16, fm hbt: 109,
11:09:21:318   1638   watchdog - thread 0 (gpu0), hb time 7328
11:09:21:318   1638   watchdog - thread 1 (gpu0), hb time 7484
11:09:21:318   1638   watchdog - thread 2 (gpu1), hb time 35188
11:09:21:318   1638   watchdog - thread 3 (gpu1), hb time 35188
11:09:21:318   1638   watchdog - thread 4 (gpu2), hb time 7453
11:09:21:318   1638   watchdog - thread 5 (gpu2), hb time 7297
11:09:21:318   1638   watchdog - thread 6 (gpu3), hb time 7375
11:09:21:318   1638   watchdog - thread 7 (gpu3), hb time 7531
11:09:21:318   1638   watchdog - thread 8 (gpu4), hb time 35188
11:09:21:318   1638   watchdog - thread 9 (gpu4), hb time 35188
11:09:21:318   1638   watchdog - thread 10 (gpu5), hb time 35188
11:09:21:318   1638   watchdog - thread 11 (gpu5), hb time 35188
11:09:24:553   1768   ETH: checking pool connection...
11:09:24:553   1768   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

11:09:24:584   1768   got 237 bytes
11:09:24:584   1768   buf: {"id":3,"jsonrpc":"2.0","result":["0x57ffe285ea553d80437ec715e64f818acc1f4c615e3c53a6edf43d51d5ebe50f","0xb15bb3623092c525165d45efa2d08540708d90d033aaa9fe4be8fd16ff904df0","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"]}

11:09:24:584   1768   parse packet: 236
11:09:24:584   1768   ETH: job is the same
11:09:24:584   1768   new buf size: 0
11:09:24:928   1768   got 237 bytes
11:09:24:928   1768   buf: {"id":0,"jsonrpc":"2.0","result":["0x6bbd7947e449a022bdff716e1984981393a072101beaf7b586c46f3fabf6ec11","0xb15bb3623092c525165d45efa2d08540708d90d033aaa9fe4be8fd16ff904df0","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"]}

11:09:24:928   1768   parse packet: 236
11:09:24:928   1768   ETH: job changed
11:09:24:928   1768   new buf size: 0
11:09:24:928   1768   ETH: 02/05/18-11:09:24 - New job from lb.geo.pirlpool.eu:8004
11:09:24:928   1768   target: 0x0000000112e0be82 (diff: 4000MH), epoch 26(1.20GB)
11:09:24:928   1768   ETH - Total Speed: 0.000 Mh/s, Total Shares: 524, Rejected: 0, Time: 03:18
11:09:24:944   1768   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
legendary
Activity: 1146
Merit: 1006
@Claymore

Are you building a AMD GPU miner for X16R (raven coin) algorithm?
hero member
Activity: 840
Merit: 503
Still using 20.5 version on 5 my rigs and everithing working fine. I am too lazy for actual updates
jr. member
Activity: 84
Merit: 1
Odd one for me, a rookie: I am trying to tune my replacement 6GB GTX1060 in my original rig, which started life as an HP Pavilion 580-023w for $495.  The 3GB graphics card was giving me fits, so I replaced it with a Gigabyte Mini ITX "OC" 6GB version.

Right out of the box it gets 14.9-15.3MH/sec but I was able to tune it to give me 20.8-21MH/sec (see graphic below) consistently for 10 hours yesterday, but can't for the life of me figure out what I did - nor can I reproduce it.  It's back to the consistent 15.4MH/sec I had right after setting the pretty normal OC values.

You can see in the graphic that the single card hit a 36MH/s effective rate in the middle of that consistent 20MH/s+ run.

I double-checked the power supply and my Kill-a-Watt meter thinking something was holding it back, but - nada.

Any ideas from the experienced miners?  I was getting 19-20MH/s from my 3GB card before I swapped them, and now it seems unable to stick with it.  It boots, but it won't stay online, the fans kick into high gear after a few seconds of the miner running and the screen blanks out.



(what's the trick to posting imbedded graphics?   hmmmm...  I hadn't tried)

P S - I found it! I retraced my steps yesterday and realized that I had accidentally saved a change in my MSI Afterburner settings trying to see if this YouTube video was right about tuning the core power to 50-55% (instead of 0).

It doesn't work for me, and it results in losing 40% MH/s.  I'm back to 21MH/sec.
Quoting myself, I realize - sorry! I try not to quote entire posts.

Anyway, I am not sure what to think, but after running nearly ten hours overnight at about 21MH/sec, the card is back to 15.5MH/s most of the time.

I have seen (once) it start with barely 7MH/s but when I restarted it went back to 15.5MH/s

Nothing seems to click, but I was constantly over 21MH/s with occasional 22.5MH/s using the generic HP GTX1060 with only 3GB DDR4. This 6GB RAM card holds a 300+ overclock where the old one would not be able to get 270.  Actually it will go 333 but I get constant restarts clocked that high.

At 300 OC it runs an hour or more with no issues, but for some reason seldom lasts longer. I wrote a recursive batch file to archive the log files and restart, but I know that 82° can't be great for the card.

I looked at the temp boundaries for the card and nVidia shows that 99° is the throttle point with 102° = time to punt.
newbie
Activity: 26
Merit: 0
Hey folks,
Wondering if any one has experienced this problem:

Adding 9th GPU only on Windows 10 v1709 I get "Cuda error 11-Cannot build dag file"
Setup: all other cards are polaris RX 580, 480 etc with blockhain drivers. Rig runs perfectly fine with 8 cards.
tried using dstm 0.5.8 and all 9 cards hash perfectly fine (>300 sols/ s).

Ive tried the following steps to troubleshoot with no success:
1) Set virtual memory to 20,000mb in Windows up form 16,000mb
2) -lidag 3 to lower dag intensity.
3) launched multiple instances of the miner (tried launching ethminer and claymore) no help
4) 9th card is running at stock settings no overclock whatsoever (cant adjust in AB since it only shows max 8 cards).
5) Tried Claymore 10.1 and 10.6 both give same Cuda error code 11

Can anyone help or know any steps I can try to get this card to hash in claymore.

Thanks.
  

for 9 cards you need more virtual memory, DAG i 2.3G now ( 9x 2.3 = 20.7g ), set virtual memory initial 24G, max 44G
newbie
Activity: 42
Merit: 0
Hey folks,
Wondering if any one has experienced this problem:

Adding 9th GPU only on Windows 10 v1709 I get "Cuda error 11-Cannot build dag file"
Setup: all other cards are polaris RX 580, 480 etc with blockhain drivers. Rig runs perfectly fine with 8 cards.
tried using dstm 0.5.8 and all 9 cards hash perfectly fine (>300 sols/ s).

Ive tried the following steps to troubleshoot with no success:
1) Set virtual memory to 20,000mb in Windows up form 16,000mb
2) -lidag 3 to lower dag intensity.
3) launched multiple instances of the miner (tried launching ethminer and claymore) no help
4) 9th card is running at stock settings no overclock whatsoever (cant adjust in AB since it only shows max 8 cards).
5) Tried Claymore 10.1 and 10.6 both give same Cuda error code 11

Can anyone help or know any steps I can try to get this card to hash in claymore.

Thanks.
  

Set drivers to compute mode
full member
Activity: 434
Merit: 107
Hey folks,
Wondering if any one has experienced this problem:

Adding 9th GPU only on Windows 10 v1709 I get "Cuda error 11-Cannot build dag file"
Setup: all other cards are polaris RX 580, 480 etc with blockhain drivers. Rig runs perfectly fine with 8 cards.
tried using dstm 0.5.8 and all 9 cards hash perfectly fine (>300 sols/ s).

Ive tried the following steps to troubleshoot with no success:
1) Set virtual memory to 20,000mb in Windows up form 16,000mb
2) -lidag 3 to lower dag intensity.
3) launched multiple instances of the miner (tried launching ethminer and claymore) no help
4) 9th card is running at stock settings no overclock whatsoever (cant adjust in AB since it only shows max 8 cards).
5) Tried Claymore 10.1 and 10.6 both give same Cuda error code 11

Can anyone help or know any steps I can try to get this card to hash in claymore.

Thanks.
  
newbie
Activity: 16
Merit: 0
Dear all, need your advice on my new rig. I constantly get the following error message and the miner restarts itself, which is a good thing instead of just hanging and sit idle. This happens as short as 2 hours or up to 5 hours. Tried searching around but yet to find any solutions. Thanks.

quote
21:09:47:912   16b8   ETH: checking pool connection...
21:09:47:991   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:09:48:288   16b8   got 243 bytes
21:09:48:397   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:09:48:491   16b8   parse packet: 242
21:09:48:569   16b8   ETH: job is the same
21:09:48:662   16b8   new buf size: 0
21:09:51:397   18b8   ETH: put share nonce 31272c01dbf3959
21:09:51:491   9b0   GPU 3, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:569   1b34   GPU 0, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:663   2a8   GPU 6, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:757   d18   GPU 4, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:835   226c   GPU 5, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:491   18b8   ETH round found 1 shares
21:09:52:007   16b8   ETH: 02/05/18-21:09:51 - SHARE FOUND - (GPU 5)
21:09:52:085   16b8   send: {"id":15,"method":"eth_submitWork","params":["0x031272c01dbf3959","0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb1c8e687425ef63e31ab56f46f302ed8f5c949eba43483f0f118681f19b06c97"]}

21:09:52:178   2d10   GPU 1, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:272   1e5c   GPU 7, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:350   9b0   GPU 3, GpuMiner kx failed 1
21:09:52:429   1b34   GPU 0, GpuMiner kx failed 1
21:09:52:522   2a8   GPU 6, GpuMiner kx failed 1
21:09:52:600   d18   GPU 4, GpuMiner kx failed 1
21:09:52:694   226c   GPU 5, GpuMiner kx failed 1
21:09:52:772   16bc   GPU 2, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:866   2d10   GPU 1, GpuMiner kx failed 1
21:09:52:944   1e5c   GPU 7, GpuMiner kx failed 1
21:09:52:397   16b8   got 40 bytes
21:09:53:116   16b8   buf: {"jsonrpc":"2.0","id":15,"result":true}

21:09:53:194   16b8   parse packet: 39
21:09:53:272   16b8   ETH: Share accepted (1094 ms)!

21:09:53:366   16b8   new buf size: 0
21:09:52:772   226c   Set global fail flag, failed GPU5
21:09:53:522   16bc   GPU 2, GpuMiner kx failed 1
21:09:52:944   2d10   Set global fail flag, failed GPU1
21:09:53:022   1e5c   Set global fail flag, failed GPU7
21:09:52:429   9b0   Set global fail flag, failed GPU3
21:09:52:522   1b34   Set global fail flag, failed GPU0
21:09:52:600   2a8   Set global fail flag, failed GPU6
21:09:52:694   d18   Set global fail flag, failed GPU4
21:09:54:116   18b8   GPU 5, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:194   226c   GPU 5 failed
21:09:53:616   16bc   Set global fail flag, failed GPU2
21:09:54:366   1984   GPU 1, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:460   2d10   GPU 1 failed
21:09:54:538   2a7c   GPU 7, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:616   1e5c   GPU 7 failed
21:09:54:710   20cc   GPU 3, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:788   9b0   GPU 3 failed
21:09:54:882   208   GPU 0, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:960   1b34   GPU 0 failed
21:09:55:038   28b8   GPU 6, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:132   2a8   GPU 6 failed
21:09:55:210   2cb0   GPU 4, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:288   d18   GPU 4 failed
21:09:55:382   18b8   GPU 5, GpuMiner kx failed 1
21:09:55:460   2b90   GPU 2, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:538   16bc   GPU 2 failed
21:09:55:632   1984   GPU 1, GpuMiner kx failed 1
21:09:55:710   2a7c   GPU 7, GpuMiner kx failed 1
21:09:55:804   20cc   GPU 3, GpuMiner kx failed 1
21:09:55:882   208   GPU 0, GpuMiner kx failed 1
21:09:55:976   28b8   GPU 6, GpuMiner kx failed 1
21:09:56:054   2cb0   GPU 4, GpuMiner kx failed 1
21:09:55:460   18b8   Set global fail flag, failed GPU5
21:09:56:226   2b90   GPU 2, GpuMiner kx failed 1
21:09:55:710   1984   Set global fail flag, failed GPU1
21:09:55:804   2a7c   Set global fail flag, failed GPU7
21:09:55:882   20cc   Set global fail flag, failed GPU3
21:09:55:976   208   Set global fail flag, failed GPU0
21:09:56:054   28b8   Set global fail flag, failed GPU6
21:09:56:132   2cb0   Set global fail flag, failed GPU4
21:09:56:820   18b8   GPU 5 failed
21:09:56:304   2b90   Set global fail flag, failed GPU2
21:09:56:991   1984   GPU 1 failed
21:09:57:070   2a7c   GPU 7 failed
21:09:57:148   20cc   GPU 3 failed
21:09:57:242   208   GPU 0 failed
21:09:57:320   28b8   GPU 6 failed
21:09:57:398   2cb0   GPU 4 failed
21:09:57:492   2b90   GPU 2 failed
21:09:57:085   4fc   srv_thr cnt: 1, IP: 127.0.0.1
21:09:57:648   4fc   recv: 60
21:09:57:742   4fc   srv pck: 59
21:09:57:835   4fc   srv bs: 0
21:09:57:913   4fc   sent: 241
21:09:57:929   16b8   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x00000000000000000000000000000000000000000000000000000000d2e3fbe7"]}

21:09:58:085   1dcc   GPU0 t=51C fan=75%, GPU1 t=57C fan=75%, GPU2 t=56C fan=75%, GPU3 t=57C fan=74%, GPU4 t=52C fan=74%, GPU5 t=54C fan=75%, GPU6 t=57C fan=74%, GPU7 t=52C fan=74%
21:09:58:101   16b8   ETH: checking pool connection...
21:09:58:257   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:09:58:539   16b8   got 243 bytes
21:09:58:617   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:09:58:695   16b8   parse packet: 242
21:09:58:789   16b8   ETH: job is the same
21:09:58:867   16b8   new buf size: 0
21:10:08:352   16b8   ETH: checking pool connection...
21:10:08:430   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:10:08:727   16b8   got 243 bytes
21:10:08:805   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:10:08:883   16b8   parse packet: 242
21:10:08:977   16b8   ETH: job is the same
21:10:09:055   16b8   new buf size: 0
21:10:09:102   ae0   got 484 bytes
21:10:09:227   ae0   buf: {"method":"mining.notify","params":["7d5","0000000000000000000000000000000000000000000000000000000000000000","32AF0200CA02200042B6D71C8BDD83EB6DAB79713BCFCFF330C4AB5BA2BB7B7C02A30882B54E31E 62000CA1FF7B7804CE8BC3AFA0C5A7F7F72E372C30A3A3FFAC81563C67672781D2DFD40420F0000 00000002000200E02B0736","0FC510114C3C9EC4B844C4DFF39C4A2018F413126F58AF73F62D818C467355B7E3B0C44298FC1C1 49AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000",[],"00000000","24000000","5a7857b0",true],"id":null}

21:10:09:305   ae0   parse packet: 483
21:10:09:383   ae0   new buf size: 0
21:10:09:477   ae0    PASC: 02/05/18-21:10:09 - New job from pasc-asia1.nanopool.org:15555
21:10:09:555   ae0   target: 0x000000000ffff000 (diff: 68GH)
21:10:10:540   52c   em hbt: 16, dm hbt: 16, fm hbt: 78,
21:10:10:618   52c   watchdog - thread 0 (gpu0), hb time 19266
21:10:10:696   52c   watchdog - thread 1 (gpu0), hb time 19234
21:10:10:790   52c   watchdog - thread 2 (gpu1), hb time 19328
21:10:10:868   52c   watchdog - thread 3 (gpu1), hb time 19516
21:10:10:962   52c   watchdog - thread 4 (gpu2), hb time 19594
21:10:11:040   52c   watchdog - thread 5 (gpu2), hb time 19578
21:10:11:118   52c   watchdog - thread 6 (gpu3), hb time 19750
21:10:11:212   52c   watchdog - thread 7 (gpu3), hb time 19938
21:10:11:290   52c   watchdog - thread 8 (gpu4), hb time 19953
21:10:11:368   52c   watchdog - thread 9 (gpu4), hb time 19938
21:10:11:446   52c   watchdog - thread 10 (gpu5), hb time 20125
21:10:11:540   52c   watchdog - thread 11 (gpu5), hb time 19532
21:10:11:618   52c   watchdog - thread 12 (gpu6), hb time 20188
21:10:11:712   52c   watchdog - thread 13 (gpu6), hb time 20375
21:10:11:790   52c   watchdog - thread 14 (gpu7), hb time 20328
21:10:11:884   52c   watchdog - thread 15 (gpu7), hb time 20531
21:10:11:962   52c   WATCHDOG: GPU error, you need to restart miner Sad
21:10:15:056   52c   Restarting OK, exit...
unquote
Jump to: