 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. |
|
|
|
Anybody using bminer with amd cards? I got an error message says miner died, no cuda device etc etc .. whats the solution?
Same here. I installed the CUDA toolkit, and even copied NVML.dll into the BMiner directory. Now I get " Failed to initialize the CUDA platform: CudaError: Could not initialize the NVML library". Tried copying the library files over, but no dice. |
|
|
|
|
Any ideas on mining this with Vega 64? I have tried every iteration of SGMiner I can find without success....
|
|
|
|
Has anyone had problems with couple of the latest releases?
From 5 cards, it anymore starts 2. If i start one miner per card, 2 of them will stay up and 3 will close right before the first green message.
Cast XMR 1.1.0 still works perfectly, but the later version do no longer work on my setup.
We haven't had much trouble with cards starting, though we have seen that on a few of the FE cards. Our rigs are one of 2 configs: Asus B250 Mining mobo w/G4400 CPU, 8GB RAM, 120GB SSD 6 x Vega 64 2 x EVGA 1000W PS Gigabyte B250 Fintech mobo w/G4400 CPU, 8GB RAM, 120GB SSD 4 x Vega FE 1 x EVGA 1000W PS Yes, I know we could pack more cards in, but these configs have been incredibly stable, and that's worth some bucks to us. What we have seen in recent updates is more random hangs, and some of the Vega 56s we were running would not stay stable, so we replaced them with 64s. Since then, no real issues. Thanks, Gandalph3000 for an amazing piece of code, in spite of all the bitching that goes on here. You'll never please everyone, but our operation is mighty happy with your program! |
|
|
|
How do you get Vega Frontiers to 2,100 hash on CN Heavy? Most I have gotten in 1600
1) Set up standard PowerPlay tables 2) Restart cards with switch-radeon-gpu 3) Disable HBCC and enable large pages through switch-radeon-gpu 4) Double-check the correct values through OverdriveNTool 5) Run Cast with intensity set to 11 That's all I did and I am sustaining 2100+ hash/s |
|
|
|
|
I can't speak for everyone, but I can confirm that on my rigs, the Windows 10 update (which happened while we were traveling) definitely DID re-enable Crossfire on every Vega in our rigs. After editing the registry, reloading the drivers and running OverdriveN, all is back to normal on hashrate.
Just thought I'd mention it.
|
|
|
|
Having issues syncing the new Windows wallet. Have tried GUI and CLI, same problem.
17:20:10.488240 INFO Block with id: <46cdf4fc69e3707fe50267ba1f5a765274077e4b64470ac865e0599ed5b6faa3>
17:20:10.488240 INFO for alternative chain, have not enough proof of work: <c18410ec63e5d83d22cb570d31e28c1c4bd6ddeefe48b742cb779227ea000000>
17:20:10.488240 INFO expected difficulty: 24957155
17:20:17.645219 INFO Block with id: <46cdf4fc69e3707fe50267ba1f5a765274077e4b64470ac865e0599ed5b6faa3>
17:20:17.645219 INFO for alternative chain, have not enough proof of work: <c18410ec63e5d83d22cb570d31e28c1c4bd6ddeefe48b742cb779227ea000000>
17:20:17.645219 INFO expected difficulty: 24957155
17:20:22.614532 INFO [69.30.231.146:39631 INC] Sync data returned unknown top block: 32018 -> 39607 [7589 blocks (10 days) behind]
17:20:22.614532 INFO SYNCHRONIZATION started
17:20:25.255430 INFO [67.8.212.244:17017 OUT] Sync data returned unknown top block: 32018 -> 48748 [16730 blocks (23 days) behind]
17:20:25.255430 INFO SYNCHRONIZATION started
17:20:26.349303 INFO [173.54.206.22:17017 OUT] Sync data returned unknown top block: 32018 -> 48748 [16730 blocks (23 days) behind]
17:20:26.349303 INFO SYNCHRONIZATION started
17:20:32.396784 INFO [165.227.130.90:17017 OUT] Sync data returned unknown top block: 32018 -> 48748 [16730 blocks (23 days) behind]
17:20:32.396784 INFO SYNCHRONIZATION started
17:20:36.350357 INFO [88.206.187.107:17017 OUT] Sync data returned unknown top block: 32018 -> 48748 [16730 blocks (23 days) behind]
17:20:36.350357 INFO SYNCHRONIZATION started
17:20:48.992322 INFO [200.100.238.135:54611 INC] Sync data returned unknown top block: 32018 -> 48748 [16730 blocks (23 days) behind]
17:20:48.992322 INFO SYNCHRONIZATION started
Can't get past this block. I have tried deleting the blocks and resyncing the blockchain, but no success so far. Any ideas?
NVM. Tried deleting existing blocks and p2p, used the CLI daemon and all is good this time! |
|
|
|
|
Having issues syncing the new Windows wallet. Have tried GUI and CLI, same problem.
17:20:10.488240 INFO Block with id: <46cdf4fc69e3707fe50267ba1f5a765274077e4b64470ac865e0599ed5b6faa3>
17:20:10.488240 INFO for alternative chain, have not enough proof of work: <c18410ec63e5d83d22cb570d31e28c1c4bd6ddeefe48b742cb779227ea000000>
17:20:10.488240 INFO expected difficulty: 24957155
17:20:17.645219 INFO Block with id: <46cdf4fc69e3707fe50267ba1f5a765274077e4b64470ac865e0599ed5b6faa3>
17:20:17.645219 INFO for alternative chain, have not enough proof of work: <c18410ec63e5d83d22cb570d31e28c1c4bd6ddeefe48b742cb779227ea000000>
17:20:17.645219 INFO expected difficulty: 24957155
17:20:22.614532 INFO [69.30.231.146:39631 INC] Sync data returned unknown top block: 32018 -> 39607 [7589 blocks (10 days) behind]
17:20:22.614532 INFO SYNCHRONIZATION started
17:20:25.255430 INFO [67.8.212.244:17017 OUT] Sync data returned unknown top block: 32018 -> 48748 [16730 blocks (23 days) behind]
17:20:25.255430 INFO SYNCHRONIZATION started
17:20:26.349303 INFO [173.54.206.22:17017 OUT] Sync data returned unknown top block: 32018 -> 48748 [16730 blocks (23 days) behind]
17:20:26.349303 INFO SYNCHRONIZATION started
17:20:32.396784 INFO [165.227.130.90:17017 OUT] Sync data returned unknown top block: 32018 -> 48748 [16730 blocks (23 days) behind]
17:20:32.396784 INFO SYNCHRONIZATION started
17:20:36.350357 INFO [88.206.187.107:17017 OUT] Sync data returned unknown top block: 32018 -> 48748 [16730 blocks (23 days) behind]
17:20:36.350357 INFO SYNCHRONIZATION started
17:20:48.992322 INFO [200.100.238.135:54611 INC] Sync data returned unknown top block: 32018 -> 48748 [16730 blocks (23 days) behind]
17:20:48.992322 INFO SYNCHRONIZATION started
Can't get past this block. I have tried deleting the blocks and resyncing the blockchain, but no success so far. Any ideas?
|
|
|
|
darn, making almost 11€ a day with 4 Vega 64 and 16€+ a day with 6 Vega 56 (unmodded) using Awesome Miner to mine on Nicehash pool and CryptonightV7.  Vega are ruling again like in the old times! You got that right. Mining with 5 x Vega 64 + 2 x Vega 56 on one rig and 4 x Vega FE on the other and making good money right now - right around $70/day total. |
|
|
|
|
I am having an unusual error problem with V 1.0.0 and have had the problem through the last few iterations.
When mining certain coins (this has happened with Stellite, Plura and Haven that I can remember), the miner will suddenly drop authentication from the pool and keep hashing with no results. The errors read as follows:
[18:47:31] GPU0 Found Nonce, submitting...
[18:47:32] !Rejected by pool! Reason: Unauthenticated
This happens after a period of successful mining, then it will start rejecting. This happens on multiple pools, so I don't think it's the pool, and I've had it on multiple coins. If I were running the wrong variant of the algorithm, I could understand, but that's not the case.
Ideas?
|
|
|
|
|
Just my $.02 worth here...
Habeas is absolutely correct - there is a difference between constructive criticism and being an a-hole. Many are just here to see what rewards they can reap for free, and really don't care about the mission, the technology, or any of the elements that truly make crypto such an unbelievable place to be right now.
The infrastructure that goes into (properly) creating and maintaining a new coin is something that very few understand, and fewer still have experienced. I have had the great fortune to work with a few coin developers and helped them to bulletproof their networks. It's amazing how many people simply want to tear down someone else's hard work, be it technically or verbally. If you haven't ever spent the time to develop something like this, then who are you to flame the dev(s) on this project?
On another note, the new x64 Windows wallet worked perfect and got past the roadblock at block 4978 or 4979.
|
|
|
|
|
Some with large amounts will indeed pump and dump. Some of us who believe (and have large amounts) are HODLing until we see the potential realized. The tech deserves better than a quick pump and dump.
|
|
|
|
|
