 Show Posts
|
|
Pages: [1]
|
А какая помощь вам нужна? Тут уже ничем не помочь. Злоумышленники уже вывели все в первые часы, если не минуты...
например дать вразумительный ответ почему аккаунт был разблокирован так быстро и без особых проверок, соответствуют ли действительности слова пострадавшего. хочется понять присутствует ли вина биржи в утере средств из-за нарушения регламента смены пароля или снятия 2фа. |
|
|
|
That is rather odd and should definitely not be happening. Can you tell us a bit more about your setup?
Which OS version are you using? What version drivers are you running? Which version of the miner are you running?
Do the stats still display when you press 's' ? How do you know if it's just one GPU that crashes? 8 x Vega56 MSI Air (original bios, no software timing mods) Win10 LTSB, 18.6.1 drivers, latest 0.5.7 miner 's' shows only one string as in attached image. one gpu is just a guess. first it began rebooting with "GPU 6: detected DEAD" in log for the last two days. than began hanging like screened. if I reboot in manually, it works for serveral minutes, after that same behaviour again. rig power drops to ~370W. I realize that code is multi-thread, but it seems like it waits for something before giving them next jobs. txt log shows the same thing, nothing special. upd now I've disabled gpu6 using "-d" key - same result some time later  upd2 now another rig shows almost same picture. it has 8 Vega64 liquid. same OS, drivers and miner, same pool. maybe there's something connected to difficulty growth?  sometimes have same problem as upd2 when one card dead, six vegas, monero or conseal. |
|
|
|
|
vega 64 3,5 from wall 280w
vega 56 3,3 from wall 270w
settings like cryptonight r
|
|
|
|
OK. I have been trying over several days to replicate the results from pbfarmer on cnv8_trtl and I can say that I am unable to get the efficiency reported by him. Any attempt to reach close to his reported voltage levels of 805mv to 840mV resulted in random DEAD GPUs(stuck in enqueue) after 20-30 minutes hashing or significant hashrate drop per GPU Even at 870mV, I am still unable to get a stable system running. Dead GPUs and hashrate drop to 15kH/s still occurs after several tens of minutes of mining. And the weird thing is hashrate drops happens to Hynix mem GPUs only.  Somehow CN-TRTL algo is more taxing that CN_R? I am able to run CN_R without failures for a week and with lower voltage settings (850mV - 870mV). I can't seem to do this for CN_TRTL My settings are as below. But the hashrates aren't sustainable GPUs : Ref Vega 64 and Vega 56 reference bios V64 cclk/memclk 1220/1100 @ 870mV L28+28 (Samsung mem) - 19.5kH/s V56 cclk/memclk 1220/940 @ 870mV L24+24 (Samsung mem) - 19.3kH/s (Hynix mem) - 18.7 kH/s ATW power draw 190W per GPU Adrenalin Driver 18.6.1 Kerney/Todd, Any ideas what could possibly be wrong? Unoptimized CN_TRTL code? i have same situation.unstable only on trtl.try different drivers nothing change. Hey guys! Well, unoptimized code isn't the issue, it's rather that it's optimized so much that it's pounding the gpu more than anything we've produced before, especially the memory subsystem. I'm not chasing efficiency to the same degree that you professional tuners are since my rig(s) are a combination of test and more serious mining. However, on my 8 x Vega 56 ref cards flashed to V64, win10, 18.6.1, clocks at 1408@900, 1100@900, I have zero stability issues, it's been mining for 14h straight now in the current run, and much longer before that as well. I've just stopped it to reconfigure things a few times. However, on my Vega 64 Liquid Cooling in my dev workstation, CN-trtl is the first algo I've ever seen that kills that specific card but not my blower Vegas. It dies after 1-2h, also running at 1408@900, 1100@900. Effective clocks+voltages in hwinfo64 look very similar to the V56s. Right now, I'm doing tests with the single-threaded config support that we also added in 0.4.3. This means I'm running --cn_config=L56+0 instead of --cn_config=L28+28. On my V64 LC, hashrate drops from 19.6 kh/s to 18.8 kh/s, same efficiency. The hashrate is expected to drop a little, but this should be more lean on the gpu, it won't be going full throttle on all parts of the hardware at the same time. Theory vs practice is always a bitch though, I'll report back in a few hours on the results. Meanwhile, you're of course free to try the same trick: switch your problematic Vegas to L56+0 and see if it helps, I'd love to get some more data here. 56 on samsung are stable, works since release 0.4.3.crashed only in rigs with hynix. Got it, although I’ve gotten a nr of reports from liquid V64s having issues as well. Regardless, does anything change for you if you try L56+0 on those Hynix V56s? hash drop to 14 and power to 150w.unstable. |
|
|
|
OK. I have been trying over several days to replicate the results from pbfarmer on cnv8_trtl and I can say that I am unable to get the efficiency reported by him. Any attempt to reach close to his reported voltage levels of 805mv to 840mV resulted in random DEAD GPUs(stuck in enqueue) after 20-30 minutes hashing or significant hashrate drop per GPU Even at 870mV, I am still unable to get a stable system running. Dead GPUs and hashrate drop to 15kH/s still occurs after several tens of minutes of mining. And the weird thing is hashrate drops happens to Hynix mem GPUs only. Somehow CN-TRTL algo is more taxing that CN_R? I am able to run CN_R without failures for a week and with lower voltage settings (850mV - 870mV). I can't seem to do this for CN_TRTL My settings are as below. But the hashrates aren't sustainable GPUs : Ref Vega 64 and Vega 56 reference bios V64 cclk/memclk 1220/1100 @ 870mV L28+28 (Samsung mem) - 19.5kH/s V56 cclk/memclk 1220/940 @ 870mV L24+24 (Samsung mem) - 19.3kH/s (Hynix mem) - 18.7 kH/s ATW power draw 190W per GPU Adrenalin Driver 18.6.1 Kerney/Todd, Any ideas what could possibly be wrong? Unoptimized CN_TRTL code? i have same situation.unstable only on trtl.try different drivers nothing change. Hey guys! Well, unoptimized code isn't the issue, it's rather that it's optimized so much that it's pounding the gpu more than anything we've produced before, especially the memory subsystem. I'm not chasing efficiency to the same degree that you professional tuners are since my rig(s) are a combination of test and more serious mining. However, on my 8 x Vega 56 ref cards flashed to V64, win10, 18.6.1, clocks at 1408@900, 1100@900, I have zero stability issues, it's been mining for 14h straight now in the current run, and much longer before that as well. I've just stopped it to reconfigure things a few times. However, on my Vega 64 Liquid Cooling in my dev workstation, CN-trtl is the first algo I've ever seen that kills that specific card but not my blower Vegas. It dies after 1-2h, also running at 1408@900, 1100@900. Effective clocks+voltages in hwinfo64 look very similar to the V56s. Right now, I'm doing tests with the single-threaded config support that we also added in 0.4.3. This means I'm running --cn_config=L56+0 instead of --cn_config=L28+28. On my V64 LC, hashrate drops from 19.6 kh/s to 18.8 kh/s, same efficiency. The hashrate is expected to drop a little, but this should be more lean on the gpu, it won't be going full throttle on all parts of the hardware at the same time. Theory vs practice is always a bitch though, I'll report back in a few hours on the results. Meanwhile, you're of course free to try the same trick: switch your problematic Vegas to L56+0 and see if it helps, I'd love to get some more data here. 56 on samsung are stable, works since release 0.4.3.crashed only in rigs with hynix. |
|
|
|
OK. I have been trying over several days to replicate the results from pbfarmer on cnv8_trtl and I can say that I am unable to get the efficiency reported by him. Any attempt to reach close to his reported voltage levels of 805mv to 840mV resulted in random DEAD GPUs(stuck in enqueue) after 20-30 minutes hashing or significant hashrate drop per GPU Even at 870mV, I am still unable to get a stable system running. Dead GPUs and hashrate drop to 15kH/s still occurs after several tens of minutes of mining. And the weird thing is hashrate drops happens to Hynix mem GPUs only. Somehow CN-TRTL algo is more taxing that CN_R? I am able to run CN_R without failures for a week and with lower voltage settings (850mV - 870mV). I can't seem to do this for CN_TRTL My settings are as below. But the hashrates aren't sustainable GPUs : Ref Vega 64 and Vega 56 reference bios V64 cclk/memclk 1220/1100 @ 870mV L28+28 (Samsung mem) - 19.5kH/s V56 cclk/memclk 1220/940 @ 870mV L24+24 (Samsung mem) - 19.3kH/s (Hynix mem) - 18.7 kH/s ATW power draw 190W per GPU Adrenalin Driver 18.6.1 Kerney/Todd, Any ideas what could possibly be wrong? Unoptimized CN_TRTL code? i have same situation.unstable only on trtl.try different drivers nothing change. |
|
|
|
Hello. After 2 days of mine one of rigs droped connection.all rigs has same ip,config,wallet,worker.another rigs work well.version of mainer 0.3.7.on different pools problem rig work well.   |
|
|
|
confirm, the problem is on lyra2z. On phi2 or any other algorithm 3-4% deviation with calculators but not 27%... And about the fact that the calculators specifically do it - it's not exactly, just the Lira was apparently not designed for such a power network, and now there is an error in the calculation of complexity.... Generally when podseti arrived at лире2з necessary from the final profit take 27%  мутко стайл |
|
|
|
|
glph3k,when you add aditional list pools?
|
|
|
|
the latest AAMD drivers are working fine for now, which is really surprising
Somebody have it tested yet? yes,1300 h\s 18.3.3 |
|
|
|
60 ватт при 20кhs = пиз-шь
7khs = 1500W
20khs будет 4киловата хуя-ть
ждем развития событий) |
|
|
|
|
hello
i send coins to cryptopia.in tx i see: "Cant get tx hash due to parse error..."
Are coins out of MPH?tx id 13999169.
thanks.
|
|
|
|
|
dont connect to pool electronium,socket error. 3 of 11 rigs.same place,router and soft.
|
|
|
|
|
