 Show Posts
|
|
Pages: [1]
|
Anyone Claymore suddenly with DAG error? just now?
My rig down with this error for all card, all sudden can't mine eth now?
GPU# - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
Same here ! With 8GB GPU cards. Do we really need to change miner ? Claymore has been a really good help till now |
|
|
|
|
Hi !
Am I the only one to see very big fluctuations in my hashrate since about 7 hours
I'm mining ethereum with nanopool for several months and it's the first time I can see that...
EDIT : sorry I just figured out what was going wrong, I have an IOTA node running on my miner and hashrate came back to regular basis when I stopped it...
|
|
|
|
|
Liqui asked 5 MGO as a fee to withdraw some MGO on January 2018, they ask 20 MGO today when everybody has no other choice than withdraw !!!...
|
|
|
|
|
Thank you tyKiwanuka ! I'm on it !
|
|
|
|
|
Hello guys and girls ! I'm pretty interested in IOTA and I just ran my full node, I'm looking for neighbors...
I already post in forum.helloiota.com and on reddit nodesharing section but I have no answer for the moment. I'd be happy to share my full node, please mp me if you're interested too.
|
|
|
|
hello,
nicehash issues can be workedaround by adding this line to your hosts file:
127.0.0.1 cryptonight.usa.nicehash.com
claymore will quickly fail on this one and switch to miningpoolhub
Great ! This worked for me, I removed -nofee and wrote this line in my hosts file, here is the result when devfee comes :  It's not very nice but it works ! Thank you carafleur ! |
|
|
|
|
@biker it's not the same problem, I recognized vexermeister's bug because I had the same one but it's not like yours. -nofee will probably not solve your problem. I never encountered this one but try to check in logs, you can also try -dbg 1 parameter to see more details in your log files.
|
|
|
|
i also experience gpu0 with 0 hashrate after few minutes of having like 600+ hash.
gpu 0 hangs in opencl call exit
then miner will restart again. only restarting pc will make the gpu0 mine again with 600+ hashrate and will repeat same error.
Try with -nofee 1, it's due to nicehash devfee mining, Hope it will be fixed soon... |
|
|
|
I see I'm not alone with this error each time devfee tries to connect to cryptonight.usa.nicehash.com, here are my log files if anyone can help... Everything seems to be OK at the beginning, then the devfee comes : 15:29:18:608 8bfff700 DevFee: XMR: Stratum - connecting to 'cryptonight.usa.nicehash.com' <169.45.93.83>
port 3355
...
15:29:18:697 b9466740 GPU0 t=58C fan=60%, GPU1 t=59C fan=60%, GPU2 t=63C fan=35%, GPU3 t=62C fan=27%, GP$
15:29:18:697 b9466740 em hbt: 0, fm hbt: 332,
15:29:18:697 b9466740 watchdog - thread 0, hb time 8613
15:29:18:697 b9466740 watchdog - thread 1, hb time 4161
15:29:18:697 b9466740 watchdog - thread 2, hb time 6386
15:29:18:697 b9466740 watchdog - thread 3, hb time 1935
...
15:29:48:705 b9466740 GPU0 t=58C fan=60%, GPU1 t=57C fan=53%, GPU2 t=60C fan=40%, GPU3 t=62C fan=27%, GP$
15:29:48:705 b9466740 em hbt: 1, fm hbt: 30340,
15:29:48:705 b9466740 watchdog - thread 0, hb time 2996
15:29:48:705 b9466740 watchdog - thread 1, hb time 7452
15:29:48:705 b9466740 watchdog - thread 2, hb time 771
15:29:48:705 b9466740 watchdog - thread 3, hb time 5226
...
15:29:59:891 ac0a4700 got 242 bytes
15:29:59:891 ac0a4700 buf: {"jsonrpc":"2.0","method":"job","params":{"blob":"0101e7e6afd10595cb75c09d497$
15:29:59:891 ac0a4700 parse packet: 241
15:29:59:891 ac0a4700 new buf size: 0
15:29:59:891 ac0a4700 XMR: 12/09/17-15:29:59 - New job from etn-eu1.nanopool.org:13433
15:29:59:891 ac0a4700 target: 0x00008bcf (diff: 1380615203H)
15:29:59:891 ac0a4700 XMR - Total Speed: 808 H/s, Total Shares: 4, Rejected: 0, Time: 00:14
15:29:59:891 ac0a4700 XMR: GPU0 808 H/s
...
15:30:01:290 ae0a8700 Job changed, drop current round
15:30:01:290 ad0a6700 Job changed, drop current round
15:30:01:290 ad8a7700 Job changed, drop current round
...
15:30:18:713 b9466740 GPU0 t=58C fan=60%, GPU1 t=61C fan=22%, GPU2 t=58C fan=40%, GPU3 t=62C fan=27%, GP$
15:30:18:713 b9466740 em hbt: 1, fm hbt: 60348,
15:30:18:713 b9466740 watchdog - thread 0, hb time 3898
15:30:18:713 b9466740 watchdog - thread 1, hb time 8354
15:30:18:713 b9466740 watchdog - thread 2, hb time 1672
15:30:18:713 b9466740 watchdog - thread 3, hb time 6123
...
15:30:48:722 b9466740 GPU0 t=58C fan=60%, GPU1 t=64C fan=64%, GPU2 t=58C fan=40%, GPU3 t=62C fan=27%, GP$
15:30:48:722 b9466740 em hbt: 1, fm hbt: 90357,
15:30:48:722 b9466740 watchdog - thread 0, hb time 7199
15:30:48:722 b9466740 watchdog - thread 1, hb time 2747
15:30:48:722 b9466740 watchdog - thread 2, hb time 4973
15:30:48:722 b9466740 watchdog - thread 3, hb time 519
...
15:30:59:901 ac0a4700 got 242 bytes
15:30:59:901 ac0a4700 buf: {"jsonrpc":"2.0","method":"job","params":{"blob":"0101a3e7afd10595cb75c09d497$
15:30:59:901 ac0a4700 parse packet: 241
15:30:59:901 ac0a4700 new buf size: 0
15:30:59:902 ac0a4700 XMR: 12/09/17-15:30:59 - New job from etn-eu1.nanopool.org:13433
15:30:59:902 ac0a4700 target: 0x00008bcf (diff: 1380615203H)
15:30:59:902 ac0a4700 XMR - Total Speed: 808 H/s, Total Shares: 4, Rejected: 0, Time: 00:15
15:30:59:902 ac0a4700 XMR: GPU0 808 H/s
15:30:59:943 ad0a6700 Job changed, drop current round
15:30:59:943 ad8a7700 Job changed, drop current round
15:30:59:943 ac8a5700 Job changed, drop current round
15:30:59:943 ae0a8700 Job changed, drop current round
...
15:31:18:730 b9466740 GPU0 t=58C fan=60%, GPU1 t=59C fan=60%, GPU2 t=58C fan=40%, GPU3 t=62C fan=27%, GP$
15:31:18:730 b9466740 watchdog - fminer thread hangs
15:31:18:730 b9466740 em hbt: 0, fm hbt: 120365,
15:31:18:730 b9466740 Miner thread hangs, need to restart miner!
15:31:18:730 b9466740 GPU 0 temp = 58, old fan speed = 60, new fan speed = 60
So the miner tries to restart and here are the lines that are not in the same state than previous starting : GPU #0: Ellesmere, 748 MB available, 36 compute units
card 0, m1 748, m2 512 w 288
0 m = 0
Bad performance mode, you need to set GPU_MAX_ALLOC_PERCENT 100
GPU #0 algorithm ASM, -h 900, -dmem 1 (Memory used: 3780MB)
OpenCL error 0 #101 - -61, cannot create GPU memory buffer
OpenCL error 0 #101a - -61, cannot create GPU memory buffer
Here is what I can read for the first start : GPU #0: Ellesmere, 8055 MB available, 36 compute units
card 0, m1 8055, m2 4048 w 288
0 m = 2
GPU #0 algorithm ASM, -h 1800, -dmem 1 (Memory used: 7560MB)
I tried with overclocked bios, with stock ones, tried to remove -dmem 1, tried with other pools... Still the same error... Last week with exactly the same args, I had no problem... I thonk it's due to devfee mining pool but I'm not sure, I have to use -nofee 1 for the moment but I'd prefer find a solution... Oups I forgot, I mine electroneum ETN with that card |
|
|
|
Hello everybody ! Just checked every links here to leave my pool : eupool.electroneum.com Finally choose this one : electromine.frMade a short preference list : 1. electromine.fr 2. http://www.electroneum.space/3. easyhash.io 4. http://electroneum.ovh/5. eupool.electroneum.com Based on figures I could read today and every advice I could read on the web... Happy Hash ! |
|
|
|
|
