 Show Posts
|
|
Pages: [1]
|
I have the same problem on 4 rigs with 4 various Vega 56 cards (ref with samsun g and asus/powercolor with hynix, with timings and without timings ). The card runs for an hour or two and then the hash rate drops to zero or to 1400 h/s with a DEAD message. I have observed in several rigs, but for some reason problems always with the first PCI slot (PCIe 3:0.0). If you do not stick the card into the first PCI slot (PCI 16x), then the problem disappears. Now I just do not use 16x pci slot  I am using all 1x slots and am having the same behavior. I am seriously thinking that this is a driver compatibility issue with Win10 for a couple of reasons: 1) It is always (in my case) the first card enumerated on the PCIe bus 2) It doesn't matter what motherboard I'm using (have tried on 7 different) 3) Starting ANY other applications on the same system slows down ONLY the affected GPU, and it shouldn't affect anything, historically. 4) In digging through logs and in the rare cases of a BSOD, there are consistently "stuck thread" issues 5) This phenomenon is not isolated to TRM - I am having the same issue with SRB, Phoenix, Claymore and others I did not have this problem with earlier builds, but since the latest Windows and AMD updates, I can't get rid of it. I have tried rolling back through every iteration all the way back to Blockchain drivers without success. I should mention that I am using a mix of V64 and V56 cards in my rigs, but all have Samsung memory. Hi! Just curious, did you have time to test 0.5.2 yet? It has a first wave of changes that only aim to stabilize the miner. No real guarantees, only some changes that theoretically should be nicer to the hardware. Otherwise, I agree, we’re dealing with some very delicate issues, and the software/driver/hardware interaction here is not all hunky dory. Apparently the new release didnot fix the issue.. still have the same error  |
|
|
|
Hey all.
I have problem with my 7x xfx vega 64 rig.
Im using 1050 mem 1175 core clocks and registery edited my rig and using 19.4.1 driver.
When i mine one of my gpus going down (lights off but still working but not mining) im using 14*14:aaa
It is happening after a day or two after i run Team red miner (using 0.5.0)
Hi! Is it always the same gpu? Have you tried reducing clocks/increasing voltage just a little for that gpu? I have the same issue with 2 of my rigs, and always happen with GPU 4. Tried lower the clocks and increase the voltage but same error occured. Cannot mine for 24 hours without error Yeah its happening to me too. Always one gpu making all rig crashed (rest of gpus working with all lights up but one of them working lights off and ofc,not mining) Hmm. A little weird this one. Is this for CN/r or some other algo? Or any algo? Does running an older version solve the problem, ie you can run stable for a long time? We have one small bugfix on the way out, can’t really see that it would be the issue here though, but who knows. I am mining cn_saber, tried both 5.0 version and 5.1 version, all have the same result.... error with GPU no 4 |
|
|
|
Hey all.
I have problem with my 7x xfx vega 64 rig.
Im using 1050 mem 1175 core clocks and registery edited my rig and using 19.4.1 driver.
When i mine one of my gpus going down (lights off but still working but not mining) im using 14*14:aaa
It is happening after a day or two after i run Team red miner (using 0.5.0)
Hi! Is it always the same gpu? Have you tried reducing clocks/increasing voltage just a little for that gpu? I have the same issue with 2 of my rigs, and always happen with GPU 4. Tried lower the clocks and increase the voltage but same error occured. Cannot mine for 24 hours without error |
|
|
|
Can anyone share the best config to mine CN Heavy for RX Vega 56??
Thanks
you can try below config with driver 18.6.1. { "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":992 }, { "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":992 }, Thank you... Can you also share for Bittube?? Really appreciate... |
|
|
|
|
Can anyone share the best config to mine CN Heavy for RX Vega 56??
Thanks
|
|
|
|
Are you undervolting?
Also check your intensities on the miner software. Miner software can affect how far you can clock
Unfortunately all vegas are different. Every single one of mine has a different max clock on memory.
I dont think it have anything with undervolting or intensities, because if i am able to use Mem clock up to 950 if its only 1 vega per rig... But if i add another vega, i need to lower both Mem clock to 935... and if i add another vega... i need to lower all vegas again to 920, and if add another vega.. i need to lower all the vegas to 910.. thats way its odd.... and it happen to both rigs that i have... |
|
|
|
|
Hi,
I have 2 mining rigs :
1st rig = 4 RX 580 8 GB (MSI) and 2 RX Vega 56 (Power Color Red Devil)
2nd rig = 5 RX Vega 56 (Power Color Red Devil)
Both installed win 10 1709, AMD driver 18.5.1, using Hard disk & mining normal_v7, why in rig 1 (2 Vegas), I can set my Vega 56 with Mem P3 Clock to 920, but in Rig 2(5 Vegas), the max Mem P3 Clock I can only set is 895 without any error with Overdriventool??
Any ideas why this is happening??
Any help appreciated.
Thanks
|
|
|
|
|
Hi can anyone share the setting for vega 56?
Onething i notice from srb that jce uses 10 watts higher than srb.
|
|
|
|
Hi, I have 2 mining rigs : 1. 4 RX 580 8 GB (MSI) and 2 RX Vega 56 (Power Color Red Devil) 2. 5 RX Vega 56 (Power Color Red Devil) Both installed win 10 1709, AMD driver18.5.1 & mining normal_v7, but why in rig 1, I can set RX Vega with MC 920, but in Rig 2, the max MC I can set is 895 without any error?? 1. Rig 1 SS: GPU0 : 1131 H/s [T: 58c, RPM: 3105, CC: 1366 MHz, MC: 2050 MHz]
GPU1 : 1001 H/s [T: 58c, RPM: 3155, CC: 1366 MHz, MC: 2050 MHz]
GPU2 : 1123 H/s [T: 60c, RPM: 3091, CC: 1366 MHz, MC: 2050 MHz]
GPU3 : 1128 H/s [T: 60c, RPM: 3172, CC: 1366 MHz, MC: 2050 MHz]
GPU4 : 1878 H/s [T: 57c, RPM: 2368, CC: 1408 MHz, MC: 920 MHz]
GPU5 : 1885 H/s [T: 53c, RPM: 2349, CC: 1408 MHz, MC: 920 MHz]2. Rig 2 SS: GPU0 : 1838 H/s [T: 57c, RPM: 2368, CC: 1408 MHz, MC: 895 MHz]
GPU1 : 1824 H/s [T: 60c, RPM: 2358, CC: 1408 MHz, MC: 895 MHz]
GPU2 : 1836 H/s [T: 54c, RPM: 2402, CC: 1408 MHz, MC: 895 MHz]
GPU3 : 1835 H/s [T: 62c, RPM: 2391, CC: 1408 MHz, MC: 895 MHz]
GPU4 : 1841 H/s [T: 59c, RPM: 2652, CC: 1408 MHz, MC: 895 MHz]Any ideas why this is happening?? Also, need help how to flash my Vegas from 56 to 64, already tried with the rom provided https://www.techpowerup.com/vgabios/196853/Powercolor.RXVega64.8192.171114.rom, but still cannot flash, if im not mistaken the error is different file size. Any help appreciated. Thanks |
|
|
|
|
