|
I already did all the suggestions you mention.
If no-one had a similar issue I might check a hardware issue but I really doubt it.
My last resort is re-install windows 10 but I would like to avoid it if possible.
|
|
|
|
|
Hello,
I wanted to know if anyone experienced the following issue on Windows 10.
After the April 10, 2018—KB4093112 (OS Build 16299.371) Windows 10 update, I cannot start any mining on my 3 nVidia 1070 Ti cards.
Everything was working fine before. I have 5 1060 on the same PC and they are not stable as sometimes I experience PC freeze.
I tested different miners that I have on the PC and none work, basically I get a CUDA error which freeze the PC. Fans go to 100%.
I already tried to revert back the updates both Windows and nVidia Driver but nothing is working.
Anyone experienced such issue?
|
|
|
|
anyone willing to share their settings on 1060 and 1070ti nVidia cards
I am at 10 Mhs for 1060 with 95% pwr, +110 core +200 mem.
At the moment my 1070Ti crashes, not related to xaven alog, but Windows 10 latest update (anyone seen this issue?)
10 mhs for a single 1060? sorry, no, 5 1060 at almost 11 Mhs also I am having issue with using the sgminer with AMD cards, it just shutsdown. What is the right sgminer call? |
|
|
|
|
anyone willing to share their settings on 1060 and 1070ti nVidia cards
I am at 10 Mhs for 1060 with 95% pwr, +110 core +200 mem.
At the moment my 1070Ti crashes, not related to xaven alog, but Windows 10 latest update (anyone seen this issue?)
|
|
|
|
Dude, don't panic =) Pool work right now! not panicking just asking. do you know other pools for mining? |
|
|
|
|
new wallet is stuck at block 54399, so how to I fix this? I already re-index the chain.
also which pools are available for mining?
|
|
|
|
|
ok great.
I downloaded the new wallet and re-index the chain, is that enough?
|
|
|
|
Dear Community! We've released an update to fix the blockchain splitting. The update is available at the link - https://github.com/ethereumfuture/ethf/releases/tag/V1.3.3.2 Please update your wallets. We've supported the official chain as the only legit one. All the chains that do not correspond to the official one are discarded as forks. Graviex and CryptoBridge use the official chain. All funds on exchanges are safe and not affected by the split. We strongly recommend using the official node list when configuring your wallets! Please don't use alternative node lists, as this will lead to the inability of working with ETHF. can you contact bsod pool and notify them about this issue and the fix? |
|
|
|
|
with bsod, the developers are saying that is on the wrong chain but did not explain why even though has the highest number of miners.
Also there was no communication to the pool to stop miners from mining as usually is done on this cases.
Any words from developer should explain the situation and fix the issue.
Which chain is the correct one and why since many miners are on the wrong one??
Why they select one chain over another?
bsod pool in the most block mined pool, so why not using this one?
|
|
|
|
Syncing problems? Sync from zero, add these addnodes to your conf file: So i would advice people to stay on the original chain, like most others. Here you can see if you're on the original chain: http://explorer.ethereumfuture.net  are you one off the developers? No he isn't. He shouldn't be telling ppl what chain to use because he doesn't know. We need to wait for the developer. However, he has not responded to the forking issue since Saturday. Maybe the coin is abandoned? No one knows! C. ok that's what I thought. I agree with you that the developers should manage this issue in a better way. Also before chosing which chain is the correct one, they should contact all the available pools to stop the mining. Anyone has direct contact to the developers? |
|
|
|
Syncing problems? Sync from zero, add these addnodes to your conf file: addnode=45.76.154.69 addnode=199.247.21.209 addnode=212.237.37.46 addnode=80.211.174.193 addnode=14.35.193.150 addnode=138.68.251.46 addnode=62.77.155.5 addnode=74.118.139.199 addnode=45.32.17.210 addnode=168.235.108.144 addnode=151.106.14.146 addnode=118.69.36.112 addnode=69.46.16.198 addnode=80.211.162.177 addnode=109.195.250.63 addnode=178.62.65.80 addnode=134.255.216.202 addnode=95.46.8.90 addnode=47.88.156.51 addnode=45.63.104.215 addnode=212.112.105.246 addnode=94.177.175.26 addnode=18.222.39.180 addnode=77.120.109.38 addnode=45.77.226.102 addnode=162.212.156.224 addnode=165.227.91.104 addnode=45.32.130.82 These are all on the correct chain: http://explorer.ethereumfuture.netI tried the BSOD chain but that chain is giving me problems, syncing my wallet will take very long or it won't sync at all. Next tot that, about 80+ percent of all peers are on the original chain and that chain works perfect, syncing is very fast. So i would advice people to stay on the original chain, like most others. Here you can see if you're on the original chain: http://explorer.ethereumfuture.net are you one off the developers? |
|
|
|
I am on bsod pool since it was the one with most miners, the pool is still working but the wallet won't sync beyond 53575 block.
I read that the dev are saying that this is the wrong chain but is the one with most blocks.
So what's going on? Also why noone mention this to the pool ?
I can sync now at block 55434, so can the developers update the situation? which chain is the right one? I am on the bsod pool and many others are mining there. |
|
|
|
|
What is the hashrate I should expect with 1060 and 1070Ti?
Are AMD cards suitable too?
Thx
|
|
|
|
|
I am on bsod pool since it was the one with most miners, the pool is still working but the wallet won't sync beyond 53575 block.
I read that the dev are saying that this is the wrong chain but is the one with most blocks.
So what's going on? Also why noone mention this to the pool ?
|
|
|
|
|
Is already time to add new algorithms for dual mining?
which ones can be added?
|
|
|
|
We are aware that there is an ASIC available for the NIST5 algorithm and are discussing possible solutions internally.
We will have an announcement soon.
Thank you.
Great since the last 2 days have proven that GPU mining for BWK is not profitable anymore and everyone will switch to other coins if nothing change soon. Looking forward to the news. 2 Days? That baikal nist5 Asic doesn't even exist since a day. So you think that a company ships out hardware without testing it? And maybe make some money while testing? Every ASIC miners are tested for weeks while in development and before release, is the norm !!! |
|
|
|
We are aware that there is an ASIC available for the NIST5 algorithm and are discussing possible solutions internally.
We will have an announcement soon.
Thank you.
Great since the last 2 days have proven that GPU mining for BWK is not profitable anymore and everyone will switch to other coins if nothing change soon. Looking forward to the news. |
|
|
|
Aaaaaaand rip GPU miners for Bulwark. Baikal X10 announced a new algorithm Nist5 with 10 GH/s only 250W...... You guys really should do something against it.  do you have a link? It sucks if asic comes too! Here is the link of the bitcointalk thread: https://bitcointalk.org/index.php?topic=2336088.380Thats just sad seriously, the difficulty just spiked 20x times already from 20k to almost 400k yeah this suck big time! Basically GPU mining is worthless. Any information from the team? ASIC taking over the network is not really good ! Attack possible too ! |
|
|
|
|
Show Posts
