I think it is v4 problem. 1.8.1 is better than 1.8.0 but still not 100% stable. It was no problem on other algos in srbminer, eth rock stable, mined beam for weaks rock stable, everything i was trowing at vegas just worked. Then it came v4 and it came problems. I just love srbminer cause it is best miner for vega cards, but when v4 cam and it was unstable, i tried other miners for v4, you have at lleast 4 of them, and they crash even faster, teamredminer crashed under 10min on same settings as srbminer. Tried to underclock gpu,mem for stability and same. Problem is only on v4, other algos are fine  Something is very bad with new algo, just put loop in bat file and it will at least run again when it crashes The whole concept of how v4 works is bad on gpu's. Compiling code on every new block, then need to release that memory, but it is known that the amd cl_release api is buggy and it wont always work as it should. For cpu's this concept of create code + compile is not a problem , but for gpu's it is. I am trying out various things, hope for the best  hi doc v4 algor , designed for cpu not gpu. do you test new amd driver ? it's very good. it's work for few day just few crash .  Haha, no, i test only on 18.6.1 and blockchain. Which new version do you refer to? Radeon-Software-Adrenalin-2019-Edition-19.3.2-Mar14 you don't need soft power table . just overdriventool 0.2.8 . you can edit p0 to p7 and new fan setting. and memory timing .... I use it too with overdriventool and very good stability and more hashes than 18.6.1  U should consider look at it doktor xD |
|
|
|
Guys, Just doned an fresh install of windows and install the 1809 ver. I was in old working good version 1709 and wanted to refresh. When im mining with lol, srb or other miner , if i bloq the copmputer after a while computer restarts.. wtf? I install first last amd driver and 18.6.1 and the symptom is the same.. never happened this, and im using an single gpu on my desktop pc Now i catch the BSOD and appears: whea uncorrectable error Now i disable the turn monitor off after x minutes and seems work. What should i look? |
|
|
|
Why my core i7-8700k,when mine cryptonight sometimes starts with good hashrate ~=400 h/S but sometimes start with 270h/S and i have to do several restarts of miner ( or open multiple instances) to make it to maximum and sometimes i quit and i leave it in the low hashrate..
Yes, that's stange! I had this issue, too, on several i7-8700 "Coffee Lake". Interestingly never on AMD Ryzen and not with "Haswell" based Intel systems. Perhaps a "secret" Coffee Lake hw-prefetching mechanism, which sometimes gets into play and sometimes not?!  Guys, Just doned an fresh install of windows and install the 1809 ver. I was in old working good version 1709 and wanted to refresh. When im mining with lol, srb or other miner , if i bloq the copmputer after a while computer restarts.. wtf? I install first last amd driver and 18.6.1 and the symptom is the same.. never happened this, and im using an single gpu on my desktop pc Now i catch the BSOD and appears: whea uncorrectable error Now i disable the turn monitor off after x minutes and seems work. What should i look? |
|
|
|
Hi jce, Why my core i7-8700k,when mine cryptonight sometimes starts with good hashrate ~=400 h/S but sometimes start with 270h/S and i have to do several restarts of miner ( or open multiple instances) to make it to maximum and sometimes i quit and i leave it in the low hashrate.. Very anoying, with other miners is the same, example the claysmore..  Regards |
|
|
|
Hi, nice miner Just started mining in my rx 580 rig and vega 64 rig, I have some doubts: In rx 580 rig i have 4gb and 8gb cards but the hash is similar between average 11.5 (4gb cards) and 12.5 sol/s (8gb cards). Is this the expectable ? Should be any major diff in the 8gb cards or is normal? In vega 64 i got in average 19-20 sol per card. In manual i read i could change worksize but i dont change anything. Is auto ok? The miner use all available gpu memory in this mode? Im seing is using this kernel for the 8gb card: https://ibb.co/58WZk6D , that appears the same as the 4 gb card Im from cryptnight algos and notice this consume a little more power too. Thanks The 8G vs. 4G should not make a difference here, because the algorithm running on both is the same (currently). The only difference could be in memory timings, because many 8G are per default a bit higher clocked in memory and the bios is tuned for slightly tighter memory timings (in nanoseconds) - that can make a difference, but at same timings & clocks there should not be a difference. Thanks for help and anwser Okapa, i have doned 1 year ago biosmod , just an curious ask And the vega is in the expectable hash too? ; Thanks |
|
|
|
Hi, nice miner Just started mining in my rx 580 rig and vega 64 rig, I have some doubts: In rx 580 rig i have 4gb and 8gb cards but the hash is similar between average 11.5 (4gb cards) and 12.5 sol/s (8gb cards). Is this the expectable ? Should be any major diff in the 8gb cards or is normal? In vega 64 i got in average 19-20 sol per card. In manual i read i could change worksize but i dont change anything. Is auto ok? The miner use all available gpu memory in this mode? Im seing is using this kernel for the 8gb card: https://ibb.co/58WZk6D , that appears the same as the 4 gb card Im from cryptnight algos and notice this consume a little more power too. Thanks |
|
|
|
Hi guys, I'm trying to mine digibyte using sgminer-5.6.1 or 5.5.5 and when i connect to pool i got no submitted or rejected shares. Im using last amd drivers and an vega 64 for testing Got this: http://  [/img] my conf file is: {
"pools" : [
{
"url" : "stratum+tcp://dgbg.suprnova.cc:7978",
"user" : "nept.vega64",
"pass" : "x"
}
]
,
"intensity" : "20",
"worksize" : "256",
"kernel" : "myriadcoin-groestl",
"lookup-gap" : "2",
"thread-concurrency" : "8192",
"shaders" : "0",
"gpu-threads" : "2",
"gpu-engine" : "0-0",
"gpu-fan" : "0-0",
"gpu-memclock" : "0",
"gpu-memdiff" : "0",
"gpu-powertune" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "28",
"failover-switch-delay" : "60",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "7",
"tcp-keepalive" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}
Anyone can help? Thanks |
|
|
|
any new devlopment in this kernel? or any new better miner for digibyte?  Well, this algorithm is being mined by ASICs for a while now, so I don't think it's worth working on a GPU implementation. And, probably FPGAs are on it as well. Thanks for anwser, I have an rig with vega 64, its not profitable? Regards |
|
|
|
any new devlopment in this kernel? or any new better miner for digibyte? |
|
|
|
minehycon.com didn t transact my payments,  Anyone with this problem too? |
|
|
|
|
all pools are dead? red flag...
|
|
|
|
Win wallet soon?
I wouldn't expect it, I suggest you just do a simple vm of Ubuntu and run a wallet that way. Backup the VM entirely for your copy. If i loose my VM i can restore my wallet with my seed, like other crypto right? |
|
|
|
Does anyone know of any alternatives to f2pool, that have payout limits < 5 GRIN ?
Hi BobLawblaw GrinMint is 0.01 Yeah, but I heard that GrinMint is possibly evil. Not honoring payouts ? All BS ? Safe ? grinmint has been fine for me. been there since day one, no probs aside from their front end numbers were off here and there the 1st few days. i use email for payouts. Its ok for me too.. |
|
|
|
Guys, Whats the best form to hodl this coin, save the file that pool send us? Thans Install a wallet and redeem the file. Not sure which pool you're talking about but e.g. grinmint withdrawal files are valid only for an hour and are definitely not the way to "hodl", not to mention that they send it via e-mail so quite vulnerable just for that reason alone. HI thanks for help, wallet 713 is good? Thanks |
|
|
|
Guys, Whats the best form to hodl this coin, save the file that pool send us? Thans |
|
|
|
|
Hi guys,
What this coin try to solve?
Regards
|
|
|
|
|
Hi JCE,
This work with webchain and hycon?
Thanks
|
|
|
|
Nista, vraticu onako kao sto je bilo u 174, s tim da necu prikazati da li je share stale ili ne, posto vidim da stale shareovi uzrujavaju ljude pa nemres na svaku primjedbu reagirat micanjem neceg iz statistike minera. covjel ne napisao 3 posta do sada i to je tebe jako uzrujalo  ma smaraju me na discordu ti za to i ne znas Ja se stvarno izvinjavam ako sam nekog svojim porukama bilo koga uznemiravao, iz najbolje namere sam ostavio postove, SRBMINER je ubedljivo najbolji miner za cryptonote algo svojim postovima smatram da pomazem autoru da resi bagove svog softver-a konkretnim cinjenicama i predlozima nista drugo, ako je drugacije ja se stvarno izvinjavam Ma nisam na tebe mislio druze, ne brini Hi doc, Have you seen my log last post, of the vega rig freeze after v 1.7.0? i can confirm that 1.7.0 work good four hours. Have you look into somethig? Thanks and happy new year |
|
|
|
Same problem reported here since v1.7.1 or more the vega rig became unstable. My rx580 rig have no problems with v1.7.4.
Vega 64 rig with v 1.7.4 get ramdom restarts, and i increase the mv in all gpus, lower intensity , and same problem!!
Driver version, algo, config file? Does the miner restart, and work ok after that, or system freezes? Can you describe ? Maybe i can find out what is happening It was all ok on 1.7.0 ? Also how often is this happening? Is there any specific case you maybe noticed? For me I get some card hashing speed at 0h/s ( sometimes all together ), then miners restart by itself but failed to start , the system freeze ( restart needed) . I get that error more often after 1.7.0. I post the log just above. Windows 10 , Xmr ( V8) , 1.6.1. PS : I tried to increase mV and lower clock speed and mem speed a lot but I still get this error since srb 1.7.1 on all rigs. ( No computing error before the crash , 1/24h for some) Same problem here. exactly. Sometimes some card have 0 hash/s or all together. And now one have a strange pump in hashes. Tried to lower clocks an d increase all mv and intensity and same problem. Check this dok: [2018-12-30 14:32:17] hashrate: GPU0: 1752 H/s [T:54c][BUS:29] [2018-12-30 14:32:17] hashrate: GPU1: 1774 H/s [T:54c][BUS:32] [2018-12-30 14:32:17] hashrate: GPU2: 1778 H/s [T:54c][BUS:26] [2018-12-30 14:32:17] hashrate: GPU3: 1770 H/s [T:47c][BUS:12] [2018-12-30 14:32:17] hashrate: GPU4: 1734 H/s [T:54c][BUS:3] [2018-12-30 14:32:17] hashrate: GPU5: 1769 H/s [T:54c][BUS:6] [2018-12-30 14:32:17] hashrate: GPU6: 1766 H/s [T:54c][BUS:18] [2018-12-30 14:32:17] hashrate: GPU7: 1770 H/s [T:55c][BUS:23] [2018-12-30 14:32:17] hashrate: GPU8: 1949 H/s [T:53c][BUS:9][2018-12-30 14:32:17] hashrate: Total: 16062 H/s [2018-12-30 14:32:28] miner_result: Sending user result to pool [2018-12-30 14:32:28] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"662863462746484","job_id":"426769207075645","nonce":"4ebd8e63","result":"13f2f7ccdf1fed3ae46fece860886d864388a6177e2bf998136e9537d4070000"}} [2018-12-30 14:32:28] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}} [2018-12-30 14:32:28] miner_result: Pool accepted result 0x000007D4 [2018-12-30 14:33:04] miner_result: Sending user result to pool [2018-12-30 14:33:04] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"662863462746484","job_id":"426769207075645","nonce":"b1dd398e","result":"5d5e2db0b56fb9057dbc809eb1fdca6253d5c8bc37e7d1b2ead7d1204a050000"}} [2018-12-30 14:33:04] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}} [2018-12-30 14:33:04] miner_result: Pool accepted result 0x0000054A [2018-12-30 14:34:17] hashrate: GPU0: 1751 H/s [T:55c][BUS:29] [2018-12-30 14:34:17] hashrate: GPU1: 1774 H/s [T:55c][BUS:32] [2018-12-30 14:34:17] hashrate: GPU2: 1778 H/s [T:54c][BUS:26] [2018-12-30 14:34:17] hashrate: GPU3: 1770 H/s [T:47c][BUS:12] [2018-12-30 14:34:17] hashrate: GPU4: 1734 H/s [T:55c][BUS:3] [2018-12-30 14:34:17] hashrate: GPU5: 1768 H/s [T:54c][BUS:6] [2018-12-30 14:34:17] hashrate: GPU6: 1766 H/s [T:54c][BUS:18] [2018-12-30 14:34:17] hashrate: GPU7: 1770 H/s [T:54c][BUS:23] [2018-12-30 14:34:17] hashrate: GPU8: 1092 H/s [T:54c][BUS:9] [2018-12-30 14:34:17] hashrate: Total: 15203 H/s [2018-12-30 14:34:27] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0505f3aea3e10597f109ce1b467661284633cfba9922cbdfea25ea1acce6a87ec8b63146a386bf0 000000053294ec0c8d92887bd6f6d4e4cf9686a31ebab0e8327c9521d0886fb007c51490b","job_id":"309129661896354","target":"2f0b0000"}} [2018-12-30 14:35:12] watchdog: GPU0 [BUS: 29] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU1 [BUS: 32] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU2 [BUS: 26] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU3 [BUS: 12] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU4 [BUS: 3] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU5 [BUS: 6] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU6 [BUS: 18] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU7 [BUS: 23] hashing speed is 0 H/S
[2018-12-30 14:35:12] watchdog: GPU8 [BUS: 9] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU0 [BUS: 29] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU1 [BUS: 32] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU2 [BUS: 26] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU3 [BUS: 12] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU4 [BUS: 3] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU5 [BUS: 6] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU6 [BUS: 18] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU7 [BUS: 23] hashing speed is 0 H/S
[2018-12-30 14:35:23] watchdog: GPU8 [BUS: 9] hashing speed is 0 H/S[2018-12-30 14:35:34] Starting reboot script reboot-windows.bat... Sometimes when restart its ok, but when freezes i have to locally restart the rig.. In v 1.7.0 its ok. Dok see what i highlight in bold in the log. Its strange. Gpu 8 jump to 1949 h/S, almost impossible in my vega 64 mining bittube. Regards It looks to me that GPU8 killed/restarted the video driver, that's why all the others stopped hashing. Interesting that users report this only on Vegas. I will check what changed after 1.7.0 that could cause this. Are you sure 1.7.0 still works ok for you ? Can you test it a day or two ? Hi Dok, This time was the gpu 8, but sometimes is gpu1, when appear in log. And sometimes , i dont have nothing in log, and all the system is freeeze. Yes only for my vega rig and for version superior to 1.7.0. I tested and work for days this version -> here my log of 3 days for example: https://justpaste.it/7qdknThis problem occur only in my vega rig in my rx580 is all good. I have 2 indivudual pcs, and last version with only one vega seems to work good until today. Probably in multi-vega-gpu have some kind of problem in last version. Thanks |
|
|
|
|
Show Posts
