Bitcoin Forum
May 22, 2019, 06:03:12 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 [1155] 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 ... 1304 »
  Print  
Author Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.5 (Windows/Linux)  (Read 6322100 times)
leonix007
Sr. Member
****
Offline Offline

Activity: 826
Merit: 282


Grow with community


View Profile
April 05, 2018, 09:24:28 AM
 #23081

Maybe ignorant question, but how are the ASICs going to work? I thought the whole point of DAGs was to prevent ASICs. How do the ASICs fit the DAG file on their chips affordably?

Its not actually an ASIC, its FPGA board

https://bitcointalk.org/index.php?topic=2182826.0
1558548192
Hero Member
*
Offline Offline

Posts: 1558548192

View Profile Personal Message (Offline)

Ignore
1558548192
Reply with quote  #2

1558548192
Report to moderator
1558548192
Hero Member
*
Offline Offline

Posts: 1558548192

View Profile Personal Message (Offline)

Ignore
1558548192
Reply with quote  #2

1558548192
Report to moderator
PLAY OVER 3000 GAMES
LIGHTNING FAST WITHDRAWALS
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1558548192
Hero Member
*
Offline Offline

Posts: 1558548192

View Profile Personal Message (Offline)

Ignore
1558548192
Reply with quote  #2

1558548192
Report to moderator
1558548192
Hero Member
*
Offline Offline

Posts: 1558548192

View Profile Personal Message (Offline)

Ignore
1558548192
Reply with quote  #2

1558548192
Report to moderator
Lunga Chung
Newbie
*
Online Online

Activity: 181
Merit: 0


View Profile
April 05, 2018, 10:56:28 AM
 #23082


Search this pattern in log
ETH: Stratum - Failed to connect, retry

Also ethermine's new UI might highlight rig that's offline in red if they don't get any update within 20 minutes. Most of them are false alarm. That's normal, nothing to worry as long as ethermine gets the update in the next round.

Just checked, i don't have this pattern, the strange thing is that submitted shares seem to be in order. According to ethermine one miner was down for 5 hours (and appeared at one point before going offline once more)

https://i.gyazo.com/7ba77ddc0eb838c711d940ee0bab3276.png

I think this could be related to dev fee switching (i see claymor sometime uses SSL conection sometimes just a regular)
juanichiloco
Full Member
***
Offline Offline

Activity: 237
Merit: 101



View Profile
April 05, 2018, 11:12:07 AM
 #23083

Been on v11.4 for a few weeks now and it's been very stable with very little stale shares, will try out the newest v11.6 soon. Cool

★ ★ ★ ★ ★   DeepOnion    Anonymous and Untraceable Cryptocurrency    TOR INTEGRATED & SECURED   ★ ★ ★ ★ ★
› › › › ›  JOIN THE NEW AIRDROP ✈️        VERIFIED WITH DEEPVAULT  ‹ ‹ ‹ ‹ ‹
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬   ANN  WHITEPAPER  FACEBOOK  TWITTER  YOUTUBE  FORUM   ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
Premiermine
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile WWW
April 05, 2018, 12:25:12 PM
 #23084

The attack on Verge XVG coin does not look good. Where are we going now? What currency do we go to for dual mining?

Blake2s Neva, Taj, Info, Shield?
Keccak smartcash?

 Huh
big_daddy
Full Member
***
Offline Offline

Activity: 742
Merit: 226


Free Crypto in Stake.com Telegram t.me/StakeCasino


View Profile WWW
April 05, 2018, 12:40:59 PM
 #23085

is any XVG pool online?  Shocked
when we can continue to mine in dual XVG?

Premiermine
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile WWW
April 05, 2018, 12:56:27 PM
 #23086

is any XVG pool online?  Shocked
when we can continue to mine in dual XVG?

XVG are with problems since yesterday, it is speculating with a possible verge fork, there is no official information from dev team of what is happening, only, they are working on it, nothing more.

Maybe it's time to give an opportunity to other currencies with dual mining.
heko
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
April 05, 2018, 02:13:00 PM
 #23087

Is there any way to mine XVG as a single currency? Which miner is best to mine XVG with GPU?
nitrobg
Member
**
Offline Offline

Activity: 415
Merit: 16


View Profile
April 05, 2018, 02:46:28 PM
 #23088

Dual mining stopped being profitable more than a month ago. Run your cards on solo mining and save yourself the electric bill.
trader1a
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
April 05, 2018, 04:05:49 PM
 #23089

The attack on Verge XVG coin does not look good. Where are we going now? What currency do we go to for dual mining?

Blake2s Neva, Taj, Info, Shield?
Keccak smartcash?

 Huh

Keccak maxcoin
Bigdrago
Newbie
*
Offline Offline

Activity: 298
Merit: 0


View Profile
April 05, 2018, 04:23:04 PM
 #23090

Hi Claymore.
If phoenix really is faster (as he claims) u should lower fee to 0.60% (he have 0.65%.)
That would make you steal his customers.
panosvo
Newbie
*
Offline Offline

Activity: 25
Merit: 0


View Profile
April 05, 2018, 04:38:45 PM
 #23091

The attack on Verge XVG coin does not look good. Where are we going now? What currency do we go to for dual mining?

Blake2s Neva, Taj, Info, Shield?
Keccak smartcash?

 Huh

Keccak maxcoin

Maxcoin is almost dead, Volume (24h): today 1$  !!!!!!!
WhackOBill
Jr. Member
*
Offline Offline

Activity: 41
Merit: 2


View Profile
April 05, 2018, 05:29:23 PM
 #23092

V11.6 has eliminated the "incorrect shares" that I was getting in prior versions.  Was running just over 1% ... now none.  No other changes than moving from 11.5 to 11.6.  Thanks Claymore.
WhackOBill
Jr. Member
*
Offline Offline

Activity: 41
Merit: 2


View Profile
April 05, 2018, 05:46:57 PM
Merited by vapourminer (1)
 #23093

Maybe ignorant question, but how are the ASICs going to work? I thought the whole point of DAGs was to prevent ASICs. How do the ASICs fit the DAG file on their chips affordably?

They don't ... they have DDR3 memory attached to the ASICs / FPGAs.  If you look on the Bitmain site, you can see that the device is a) twice the size of their other miners and b) is about the hash equivalent of 4x 580's.  If you consider the 800 watts of draw, it uses more Watts/MH than a rig with 4x 580s.  About the only attractive thing about it is the price ... $800.

The only decent way to attack the Ethash mechanism is to take advantage of the 64 DAG lookup steps in the algorithm.  If you broke your DAG storage into 64 or 128 or 256 separately accessible pieces, you could pipeline the 64 lookup's and take advantage of the random nature of the lookup addresses.  The point is to do 64 lookup's at the same time taking advantage of their being in separate pieces of memory ... usually.  In this way you could pipeline the Ethash and have 64 going on at the same time with each at one point along the 64 step process ... ignoring the pre and post processing.  Occasionally, you would have a collision when two or more lookup's needed the same DAG section and so you'd stall for that step.  It's difficult to get all of that address and data bus space hooked into an ASIC or FPGA.  So it's still a hard problem ... not impossible though.
blockaudit
Jr. Member
*
Offline Offline

Activity: 34
Merit: 2

Helping the blockchain world build secure++ stuff!


View Profile WWW
April 05, 2018, 06:39:38 PM
 #23094

1. CVE-2017-16929 works only if you specified -mport > 0 and don't use password (-mpsw). Also it can crash miner:

From History.txt:

...
v10.2
- fixed critical issues in remote management feature (attacker could crash miner even in read-only mode).
...

That was the last known security issue and it was fixed in v10.2 and above.

Here is my opinon:
Yes my miners have "remote management" feature that allows administrators to upload files, restart miners etc. It's not a vulnerability itself. Also I know that this feature can be used by attackers, therefore by default miner uses "read-only" mode which ignores all commands except "miner_getstat1" (I mean recent versions of my miners, very old versions have no "read-only mode"). User must specify "-mport" option and positive port manually to enable potentially dangerous commands. Also I added "-mpsw" option that allows users to set a password for remote management. Also miner shows warning during startup if "read-only" mode is disabled and -mpsw is missed. Also I added necessary information to Readme file. And, of course, it's bad idea to make these ports public, they must be used in local network only, "-mport" option can expose the port to specified network interface only.
To make this feature dangerous, user must do the following:
1. Disable "read-mode", ignore miner warning.
2. Ignore "-mpsw", i.e. don't set a password, again ignore miner warning.
3. Expose the port(s) to internet.
So, in my opinion, I did everything to make this feature safe as much as possible, but some users have no idea/knowledge what they do when they change default settings.

  • cve-2017-16929 - authenticated directory traversal - as statet in the advisory (link) requires remote mgmt enabled (write) and you need the password if set
  • cve-2017-16930 - unauthenticated buffer overflow - as statet in the advisory (link) requires remote mgmt enabled; read-only is also affected; attacker does not need to have a password; This case "could cause a crash" (best case) whereas one would likely aim for remote code execution to hijack the process (shellcode -> exploit; worst case; consider your machine compromised if your vulnerable version was reachable from the internet).



Yep, it would be easier to reason about the security of the code if it were open source, or at least had a formal code audit.

https://www.blockaudit.org
z0n0
Legendary
*
Offline Offline

Activity: 1274
Merit: 1006



View Profile
April 05, 2018, 07:47:01 PM
Last edit: April 05, 2018, 08:06:17 PM by z0n0
 #23095

v11.6:

- improved hashrate for weak Nvidia cards by about 1%.
- zero devfee for 3GB cards in Windows 10, same as for all 2GB cards.
- applied some tricks to increase available memory for 3GB cards in Windows 10 so you can mine ETH a bit longer.
- now you can press "y" key to turn on "Compute Mode" in AMD drivers for all cards (Windows only).
- Linux version: removed openssl library dependency.
- improved "-logfile" option, now you can use it to specify a folder for log files, use slash at the end to do it, for example, "-logfile logs\".
- added "-epoolsfile" and "-dpoolsfile" options.
- remote management: now "miner_getstat2" command also returns PCI bus index for every GPU.
- a few minor bug fixes and improvements.

Thanks Claymore, for bringing life back to 3GB cards, worked right off the bat!

+1, I can mine Eth on 1060 3GB cards in W10 only with Claymore, all other miners fail now. Also 0% developer fee Cool

No luck on Win7 though...  Undecided
Lunga Chung
Newbie
*
Online Online

Activity: 181
Merit: 0


View Profile
April 05, 2018, 07:48:46 PM
 #23096

Does anyone have random disconnects from ethermine?

I noticed that some miners appear offline on the pools side but when i log in i see they are submitting shares, only thing I noticed that the latency doubled (from 60 to 120ms in my case). Using 11.5 version previously 10.6 never had this...

Can someone point me for what to look in a claymor log file maybe i missed something.

Search this pattern in log
ETH: Stratum - Failed to connect, retry

Also ethermine's new UI might highlight rig that's offline in red if they don't get any update within 20 minutes. Most of them are false alarm. That's normal, nothing to worry as long as ethermine gets the update in the next round.

I did find this actually, maybe some more experienced can have a look:

02:40:40:115   1164   ETH: checking pool connection...
02:40:40:115   1164   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

02:40:40:209   1164   buf: {"jsonrpc":"2.0","id":0,"result":["0x658de68c04f3cb57c14378332bccf71f9cca302c1db3e52ed587090636422c54","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

02:40:40:678   11d0   em hbt: 15, fm hbt: 93,
02:40:40:678   11d0   watchdog - thread 0 (gpu0), hb time 547
02:40:40:678   11d0   watchdog - thread 1 (gpu0), hb time 234
02:40:40:678   11d0   watchdog - thread 2 (gpu1), hb time 297
02:40:40:678   11d0   watchdog - thread 3 (gpu1), hb time 609
02:40:40:678   11d0   watchdog - thread 4 (gpu2), hb time 297
02:40:40:678   11d0   watchdog - thread 5 (gpu2), hb time 609
02:40:40:678   11d0   watchdog - thread 6 (gpu3), hb time 140
02:40:40:678   11d0   watchdog - thread 7 (gpu3), hb time 453
02:40:40:678   11d0   watchdog - thread 8 (gpu4), hb time 609
02:40:40:678   11d0   watchdog - thread 9 (gpu4), hb time 297
02:40:40:678   11d0   watchdog - thread 10 (gpu5), hb time 297
02:40:40:678   11d0   watchdog - thread 11 (gpu5), hb time 609
02:40:41:444   c8   srv_thr cnt: 1, IP: 192.168.1.5
02:40:41:444   c8   recv: 51
02:40:41:444   c8   srv pck: 50
02:40:41:444   c8   srv bs: 0
02:40:41:444   c8   sent: 335
02:40:45:772   1164   sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xadd3ef8", "0x0000000000000000000000000000000000000000000000000000000033ef23e2"]}

02:40:46:522   fc4   srv_thr cnt: 1, IP: 192.168.1.5
02:40:46:522   fc4   recv: 51
02:40:46:522   fc4   srv pck: 50
02:40:46:522   fc4   srv bs: 0
02:40:46:522   fc4   sent: 335
02:40:50:132   1164   ETH: checking pool connection...
02:40:50:132   1164   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

02:40:50:226   1164   buf: {"jsonrpc":"2.0","id":0,"result":["0x658de68c04f3cb57c14378332bccf71f9cca302c1db3e52ed587090636422c54","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

02:40:50:554   1164   buf: {"jsonrpc":"2.0","id":0,"result":["0xaeef20c127f6068a2e4c19681e2ee97ddd2aeed92ecf84fe7ee95f30363cafb9","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

02:40:50:554   1164   ETH: 04/05/18-02:40:50 - New job from eu1.ethermine.org:4444
02:40:50:554   1164   target: 0x000000006df37f67 (diff: 10000MH), epoch 179(2.40GB)
02:40:50:554   1164   gpu #2 dt 0.15 (0%, good)
02:40:50:554   1164   gpu #3 dt 0.15 (0%, good)
02:40:50:554   1164   ETH - Total Speed: 182.312 Mh/s, Total Shares: 17089, Rejected: 0, Time: 108:18
02:40:50:554   1164   ETH: GPU0 30.318 Mh/s, GPU1 30.471 Mh/s, GPU2 30.483 Mh/s, GPU3 30.095 Mh/s, GPU4 30.487 Mh/s, GPU5 30.458 Mh/s
02:40:51:570   e54   srv_thr cnt: 1, IP: 192.168.1.5
02:40:51:570   e54   recv: 51
02:40:51:570   e54   srv pck: 50
02:40:51:570   e54   srv bs: 0
02:40:51:570   e54   sent: 335
02:40:52:211   1334   checked ETH share on CPU, spent 4ms
02:40:52:211   1334   sent: {"id":13,"method":"eth_submitWork","params":["0x4b1517000258e5ad","0xaeef20c127f6068a2e4c19681e2ee97ddd2aeed92ecf84fe7ee95f30363cafb9","0x8b6339c1548718a413840e2f41a2142556c527b58dbd7b1fd1235826ee16520b"]}

02:40:52:211   1334   ETH: put share nonce 4b1517000258e5ad
02:40:52:226   1164   ETH: 04/05/18-02:40:52 - SHARE FOUND - (GPU 3)
02:40:52:320   1164   buf: {"jsonrpc":"2.0","id":13,"result":true}

02:40:52:320   1164   ETH: Share accepted (109 ms)!

02:40:56:258   12d8   checked ETH share on CPU, spent 6ms
02:40:56:258   12d8   sent: {"id":12,"method":"eth_submitWork","params":["0x9ab71b640a2f8dea","0xaeef20c127f6068a2e4c19681e2ee97ddd2aeed92ecf84fe7ee95f30363cafb9","0xa5f9f9f145952fb2644f5d7e0e656d060a1df6fa127fa1c0a2b685aa3cfe0384"]}

02:40:56:258   12d8   ETH: put share nonce 9ab71b640a2f8dea
02:40:56:273   1164   ETH: 04/05/18-02:40:56 - SHARE FOUND - (GPU 2)
02:40:56:367   1164   buf: {"jsonrpc":"2.0","id":12,"result":true}

02:40:56:367   1164   ETH: Share accepted (110 ms)!

02:40:56:680   1440   srv_thr cnt: 1, IP: 192.168.1.5
02:40:56:680   1440   recv: 51
02:40:56:680   1440   srv pck: 50
02:40:56:680   1440   srv bs: 0
02:40:56:680   1440   sent: 335
02:40:57:492   11d4   GPU0 t=59C fan=37%, GPU1 t=58C fan=36%, GPU2 t=55C fan=36%, GPU3 t=59C fan=36%, GPU4 t=59C fan=41%, GPU5 t=58C fan=36%
02:41:00:149   1164   ETH: checking pool connection...
02:41:00:149   1164   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

02:41:00:243   1164   buf: {"jsonrpc":"2.0","id":0,"result":["0xaeef20c127f6068a2e4c19681e2ee97ddd2aeed92ecf84fe7ee95f30363cafb9","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

02:41:01:727   844   srv_thr cnt: 1, IP: 192.168.1.5
02:41:01:727   844   recv: 51
02:41:01:727   844   srv pck: 50
02:41:01:727   844   srv bs: 0
02:41:01:727   844   sent: 335
02:41:05:790   1164   sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xadd23c5", "0x0000000000000000000000000000000000000000000000000000000033ef23e2"]}

02:41:06:915   fa8   srv_thr cnt: 1, IP: 192.168.1.5
02:41:06:915   fa8   recv: 51
02:41:06:915   fa8   srv pck: 50
02:41:06:915   fa8   srv bs: 0
02:41:06:915   fa8   sent: 335
02:41:10:166   1164   ETH: checking pool connection...



I can see the only dev fee getting connected in the span of 5 hourse
qnarkill
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
April 05, 2018, 08:44:45 PM
 #23097

Does anybody know or have idea what would work for when -tstop is reached and i would want to reboot entire miner?

I have the -r 1 to reboot and it works ok if a gpu fails but in this case when the gpu is just switched off the claymore will just stop mining having me to restart miner manually to get it going again.
QuintLeo
Legendary
*
Offline Offline

Activity: 1372
Merit: 1025


View Profile
April 05, 2018, 09:59:31 PM
 #23098

Maybe ignorant question, but how are the ASICs going to work? I thought the whole point of DAGs was to prevent ASICs. How do the ASICs fit the DAG file on their chips affordably?

They don't ... they have DDR3 memory attached to the ASICs / FPGAs.  If you look on the Bitmain site, you can see that the device is a) twice the size of their other miners and b) is about the hash equivalent of 4x 580's.  If you consider the 800 watts of draw, it uses more Watts/MH than a rig with 4x 580s.  About the only attractive thing about it is the price ... $800.


180 Mhash/sec is at least 6 RX 470/480/570/580 even with BIOS straps and all other optimizations. (widely reported in the 28-30 Mhash range for best optimized cards, sometimes a bit less).
It's also a HAIR less than 6 x GTX 1070 (31-32 Mhash common numbers, rarely under 31).

Power usage is pretty much a tossup with a well-optimized 6 card rig - bit higher than the Nvidia option, right around the same vs the AMD option.

The size IS interesting, and has led to some speculation that it's somehow a GPU rig - but the PRICE makes it unlikely to be GPU based.

I'm no longer legendary just in my own mind!
Like something I said? Donations gratefully accepted. LYLnTKvLefz9izJFUvEGQEZzSkz34b3N6U (Litecoin)
1GYbjMTPdCuV7dci3iCUiaRrcNuaiQrVYY (Bitcoin)
leonix007
Sr. Member
****
Offline Offline

Activity: 826
Merit: 282


Grow with community


View Profile
April 05, 2018, 10:43:34 PM
 #23099

Hi,

I apologize, I am newbie here.  I read and follow all the directions.
I am experience problems with 2 of my PCs, using Claymore Miner 11.6
I have a Nvidia Card.

First PC:  Windows 7 pro 64-bit
I got error message that "DCR: 0 pool specificed.
No AMD or Nvidia card found ..

Check if your GPU's are properly installed and has a correct driver, it should be detected by your system before firing up miners.

Quote
2nd PC:  Windows 10 pro 64-bit
This app cannot run on this PC.

I am testing on my older PC, I know it is not efficient.  I want to get to know at least the setup first.

any suggestion would be appreciated.

Thanks

Ensure that your Windows defender is not hampering the .exe file, exempt this and turn off the defender
Coroto
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
April 06, 2018, 02:02:40 AM
Last edit: April 06, 2018, 03:01:25 AM by Coroto
 #23100

Hello, i will throw this here, thanks in advance for your kindly answers.

Been mining for a while with 5x 1060 3GB on Win 10. Sometimes the driver crash, but i have been able to solve the issue by downclocking mem in one of the GPUs (i always check logs and find the problematic GPU). Im currently on 11.6 and the miner restarted. Since most of you are far more experienced than me, i will appreciate a possible troubleshooting.

Code:
20:51:59:545 1730 ETH: 04/05/18-20:51:59 - New job from eth-us.dwarfpool.com:8008
20:51:59:545 1730 target: 0x0000000225c17d04 (diff: 2000MH), epoch 179(2.40GB)
20:51:59:545 1730 ETH - Total Speed: 124.580 Mh/s, Total Shares: 2006, Rejected: 0, Time: 08:52
20:51:59:545 1730 ETH: GPU0 25.328 Mh/s, GPU1 25.250 Mh/s, GPU2 24.408 Mh/s, GPU3 24.852 Mh/s, GPU4 24.742 Mh/s
20:51:59:561 19e8 GPU 4, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:561 19e8 GPU 4, GpuMiner kx failed 1
20:51:59:561 19e8 Set global fail flag, failed GPU4
20:51:59:561 19e8 GPU 4 failed
20:51:59:577 1740 GPU 4, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:577 1740 GPU 4, GpuMiner kx failed 1
20:51:59:577 1840 GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:577 1740 Set global fail flag, failed GPU4
20:51:59:577 1840 GPU 0, GpuMiner kx failed 1
20:51:59:577 1740 GPU 4 failed
20:51:59:577 1840 Set global fail flag, failed GPU0
20:51:59:577 185c GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:577 1840 GPU 0 failed
20:51:59:577 185c GPU 0, GpuMiner kx failed 1
20:51:59:577 185c Set global fail flag, failed GPU0
20:51:59:577 185c GPU 0 failed
20:51:59:608 1834 GPU 1, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:609 1834 GPU 1, GpuMiner kx failed 1
20:51:59:610 1834 Set global fail flag, failed GPU1
20:51:59:611 1838 GPU 1, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:612 1834 GPU 1 failed
20:51:59:613 1838 GPU 1, GpuMiner kx failed 1
20:51:59:614 1838 Set global fail flag, failed GPU1
20:51:59:614 1838 GPU 1 failed
20:51:59:646 8d8 GPU 2, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:646 8d8 GPU 2, GpuMiner kx failed 1
20:51:59:646 8d8 Set global fail flag, failed GPU2
20:51:59:646 1830 GPU 2, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:646 8d8 GPU 2 failed
20:51:59:646 1830 GPU 2, GpuMiner kx failed 1
20:51:59:646 1830 Set global fail flag, failed GPU2
20:51:59:646 1830 GPU 2 failed
20:51:59:661 19dc GPU 3, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:661 19dc GPU 3, GpuMiner kx failed 1
20:51:59:661 19dc Set global fail flag, failed GPU3
20:51:59:661 19e0 GPU 3, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:661 19dc GPU 3 failed
20:51:59:661 19e0 GPU 3, GpuMiner kx failed 1
20:51:59:661 19e0 Set global fail flag, failed GPU3
20:51:59:661 19e0 GPU 3 failed
20:52:04:321 12c0 srv_thr cnt: 1, IP: 192.168.137.3
20:52:04:321 12c0 recv: 51
20:52:04:321 12c0 srv pck: 50
20:52:04:321 12c0 srv bs: 0
20:52:04:321 12c0 sent: 187
20:52:07:557 1730 buf: {"result":["0xb6a6c7f1b78cb48b5d1660ec5a167361bd257d5c57f4641c744dd5dd59a1deed","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


20:52:07:557 1730 ETH: 04/05/18-20:52:07 - New job from eth-us.dwarfpool.com:8008
20:52:07:557 1730 target: 0x0000000225c17d04 (diff: 2000MH), epoch 179(2.40GB)
20:52:07:557 1730 ETH - Total Speed: 0.000 Mh/s, Total Shares: 2006, Rejected: 0, Time: 08:53
20:52:07:557 1730 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
20:52:08:743 1730 ETH: checking pool connection...
20:52:08:743 1730 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

20:52:08:922 1730 buf: {"result":["0xb6a6c7f1b78cb48b5d1660ec5a167361bd257d5c57f4641c744dd5dd59a1deed","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


20:52:09:326 1d74 srv_thr cnt: 1, IP: 192.168.137.3
20:52:09:327 1d74 recv: 51
20:52:09:327 1d74 srv pck: 50
20:52:09:328 1d74 srv bs: 0
20:52:09:328 1d74 sent: 187
20:52:12:179 19b0 GPU0 t=49C fan=49%, GPU1 t=52C fan=56%, GPU2 t=50C fan=50%, GPU3 t=51C fan=50%, GPU4 t=53C fan=59%
20:52:14:313 14b4 srv_thr cnt: 1, IP: 192.168.137.3
20:52:14:313 14b4 recv: 51
20:52:14:313 14b4 srv pck: 50
20:52:14:328 14b4 srv bs: 0
20:52:14:329 14b4 sent: 187
20:52:14:582 c98 em hbt: 16, fm hbt: 94,
20:52:14:582 c98 watchdog - thread 0 (gpu0), hb time 15031
20:52:14:582 c98 watchdog - thread 1 (gpu0), hb time 15031
20:52:14:582 c98 watchdog - thread 2 (gpu1), hb time 15031
20:52:14:582 c98 watchdog - thread 3 (gpu1), hb time 15031
20:52:14:582 c98 watchdog - thread 4 (gpu2), hb time 15031
20:52:14:582 c98 watchdog - thread 5 (gpu2), hb time 15031
20:52:14:582 c98 watchdog - thread 6 (gpu3), hb time 15031
20:52:14:582 c98 watchdog - thread 7 (gpu3), hb time 15031
20:52:14:582 c98 watchdog - thread 8 (gpu4), hb time 15016
20:52:14:582 c98 watchdog - thread 9 (gpu4), hb time 15234
20:52:14:582 c98 WATCHDOG: GPU error, you need to restart miner :(
20:52:15:798 c98 Restarting OK, exit...

As you can see, it was about after 9 hours of mining. The miner restarted and its mining just fine. Again, appreciate some troubleshooting. Kind regards...
Pages: « 1 ... 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 [1155] 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 ... 1304 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!