 Show Posts
|
|
Pages: [1]
|
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. 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... |
|
|
|
Mate, again, if you are mining Ubiq, use "-allcoins exp". It will mine Ubiq for devfee, same pool, same dag. I have tested myself in 3 different ubiq pools and the devfee works in all of them (dont use -allpools). I didn't see your first post where you explain this, but I did I apologize upfront if this was covered in one of the previous 900+ pages in this thread. Also, UBQ and EXP are different coins with different DAGs, so it seems weird that setting "-allcoins exp" would work when mining UBQ, but it does, so I'm not going to complain. Thanks for the help. You're welcome, im glad to help. I know that EXP and UBQ are different coins, but if you think about "-allcoins exp" like just a simple parameter, and not about it has to compulsory mine EXP coin, you will be opening your mind. Expanse has a couple of years in in the ecosystem, Ubiq genesis block is less than a year old. It may be prolly that Claymore was aware of Expanse as a <2GB dag when he added that parameter. Cheers. |
|
|
|
Are you using Simple mining ti mine UBIQ?
Im trying and cant get it to work.
Question in other forum:
Hello all and Happy New Year.
To save me reading through 1000's of posts - which i will start doing - can anyone give me pointers on mining other Ethash coins on my AMD rig currently running claymore-eth-v10.2 mining Etherium?
-wd 1 -r 1 -epool stratum+tcp://eth-eu.dwarfpool.com:8008 -ewal $walletETH/$rigName -esm 0 -epsw x -allpools 1 -mport -3333 -asm 1
And NeoScrypt on my Nvidea Rig currently running ewbf-0.3.4b mining Z Cash.
--server eu1-zcash.flypool.org --user xxxxxxxxxxxxxxxxxxxxxxxxxxx.$rigName --pass x --port 3333
I've tried changing things and i can't get anything to work.
A few pointers would be greatly received.
Thanks
W
So i just tried using my claymore miner in SmOS to mine Ubiq and i get nothing.
Basically changing -epool address and using an UBQ address:
-wd 1 -r 1 -epool stratum+tcp://eu.ubiqpool.io:8008 -ewal 0x000000000000000000000000000000/$rigName -esm 0 -epsw x -allpools 1 -mport -3333 -asm 1
I get:
ETH: Stratum - connecting to 'eu.ubiqpool.io' <209.222.30.133> port 8008
ETH: Stratum - Connected (eu.ubiqpool.io:8008)
ETH: Authorization failed
: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalidlogin"}}
Stratum - reading socket failed, disconnect
ETH: Job timeout, disconnect, retry in 20 sec...
Please read my posts from the last 2-3 pages on this thread. If you are mining Ubiq, you need to set "-allcoins exp" parameter. Also, read the entire readme.txt file, it will help you a lot, more than any of us. Cheers. |
|
|
|
For ubiq (as a fork) you need to have -allcoins 1 in your bat. I have -allcoins -1 because it generates the ETH DAG first, and this is supposed to reduce the time it takes to do devfee switching, but I admit I may not understand this option correctly. I just checked and it looks like claymore promised to include dag re-creation into devfee:
...
I personally am not aware if that works as promised, but your results seem to suggest that it doesn't.
May be someone else, e.g. claymore, can contribute to this discussion... Hmmm... I'll try to pay closer attention next devfee round and put a stop watch to it rather than just scroll back through the timestamps, but I know for sure the process took > 1 minute, and not 36 seconds. Mate, again, if you are mining Ubiq, use "-allcoins exp". It will mine Ubiq for devfee, same pool, same dag. I have tested myself in 3 different ubiq pools and the devfee works in all of them (dont use -allpools). |
|
|
|
(or w/e built that for you and charged you PREMIUM COSTS, hence the ad)
Nobody charged him premium costs. The post was just an advert of his small business: posted by Marcinprv (where "prv" I guess stands for "first" in polish) and you can find the same name on the advertised website (firstever.eu). BTW two risers per sata is probably OK; more than 2 is a problem. It looks pretty nice. And you are right, maybe 2 risers per SATA cable at the PSU is fine. But you have to admit that we enter in a "unknown" territory using molex to sata connectors, bc we cannot ensure the proper quality of the connectors (SATA side). It would be nice that risers were straight SATA to connect direct to PSU. Ok, it's sometimes a bit hard to pinpoint a build "issue" without sounding rude. |
|
|
|
Can you add support fo 12+ GPU's? It is working but I can turn on/off cards 11,12+ (only 0-9). You can change it to two digits 00-99 or 0-9, a-z. I can't see temperature and most options doesn't work (OC, Power Level etc). BTW, MSI Afterburner also doesn't support 12+ GPU's (it can support 7 or 8 GPU's).  My Mining Rigs:   -GPUs in claymore are seen in hex. So, the index goes 0-9, then a-f. Your 11 and 12st GPU should be a and b respectively. -Claymore supports way over 12+ GPUs. But it becomes a headache for the Operating Systems. Your best shot here is adding Nvidias. Please read the entire "readme.txt" file. -Don't use MSI AB then, just use Wattman instead, or w/e software suits better for you. I don't know if those were real questions or a excuse to brag about your rigs haha. As mentioned by OP, you (or w/e built that for you and charged you PREMIUM COSTS, hence the ad) made the worst choice about risers and cables. It seems that some1 needs to stop throwing the money and thinking about the health of the rig lol (you have a fire hazzard using that rig, or in the best case, melted risers and/or GPU hazzard). Nice building overall tho. |
|
|
|
Quote from: rmoore95 on January 01, 2018, 01:25:54 AM
Trying to mine some UBIQ using Claymore's and keep getting this error message. Anyone smarter than me (won't take much) know how to fix this?
ETH: Stratum - Connected (us.ubiqpool.io:8008)
ETH: Authorization failed
: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalidlogin"}}
Stratum - reading socket failed 10038, disconnect
ETH: Job timeout, disconnect, retry in 20 sec...
@rmoore95 for you and the OP that tried to help you without luck. 1. Make sure you read the whole "readme.txt" file before start mining. It takes a few minutes and can save you ton of time. 2. The answer to your question is: Since Ubiq is an ETH clone; you NEED to use "-allcoins 1" or "-allcoins exp" parameter in your .bat file. Try with "-allcoins exp" so it wont switch DAGs while mining devfee. |
|
|
|
|
