AMD miner not working
win7 x64 AMD RX 480
Error 0xc000007b
win7 x64 AMD RX 480
Error 0xc000007b
Here gives a dll error
When you find that DLL it still doesn't work.
Topic: [ANN] Zcoin (XZC) - Implementing ZKP privacy without trusted setup - page 253. (Read 663312 times)
February 10, 2017, 07:35:53 AM
Here gives a dll error
When you find that DLL it still doesn't work.
February 10, 2017, 07:34:03 AM
New Port to mine with after the fork to the new Algo will be 1596 on https://xzc.suprnova.cc - only new miners will work, not the old ones. New miners should be posted here shortly
your pool is already working on testnet right? i see accepted hashrate with the new miners and that port
Yes, i'll just switch the ports to mainnet once we've hit that block
small typo on suprnova web page: port: 1569
February 10, 2017, 07:32:36 AM
New Port to mine with after the fork to the new Algo will be 1596 on https://xzc.suprnova.cc - only new miners will work, not the old ones. New miners should be posted here shortly
your pool is already working on testnet right? i see accepted hashrate with the new miners and that port
Yes, i'll just switch the ports to mainnet once we've hit that block
February 10, 2017, 07:18:25 AM
AMD miner not working
win7 x64 AMD RX 480
Error 0xc000007b
win7 x64 AMD RX 480
Error 0xc000007b
Here gives a dll error
when starting demanded libeay32.dll and ssleay32.dll. Missing dll downloaded and now got an error. Where to get normal dll?
February 10, 2017, 06:43:18 AM
After over 18h I still can't get the wallet to sync with the new 0.8.7.4-unk QT Windows build.
This is crazy you need to fix this issue ..without proper syncing it is useless.
This is crazy you need to fix this issue ..without proper syncing it is useless.
yeah, sync takes forever! And there is only the 20000 blocks...
And it looks like wallet needs a lot of time to start with the downloaded blockchain.
don't use the downloaded ones..it causes corrupted wallet.
Even you have a valid blockchain he restarts processing and strumbles over his own feet.
The blockchain is broken badly..so many dead points:
Quote
2017-02-10 11:39:46 trying connection 192.222.191.119:8168 lastseen=385201.9hrs
2017-02-10 11:39:48 COIN SPEND TX DID VERIFY!
2017-02-10 11:39:51 connection timeout
2017-02-10 11:39:51 connection timeout
2017-02-10 11:39:51 trying connection 62.248.241.36:8168 lastseen=11.9hrs
2017-02-10 11:39:51 trying connection 193.69.196.112:8168 lastseen=385201.9hrs
2017-02-10 11:39:56 COIN SPEND TX DID VERIFY!
2017-02-10 11:39:56 connection timeout
2017-02-10 11:39:56 connection timeout
2017-02-10 11:39:57 SetBestChain: new best=9e8904ef860e5bbe4771c0336702df10f1c9b52bf375488e1dd3b84a92978ae0 height=5773 log2_work=43.452176 tx=34659 date=2016-11-01 21:17:19 progress=0.109414
2017-02-10 11:39:57 ProcessBlock: ACCEPTED
2017-02-10 11:39:57 trying connection 13.65.195.137:8168 lastseen=47.7hrs
2017-02-10 11:39:57 trying connection 200.109.29.32:8168 lastseen=385201.9hrs
2017-02-10 11:40:02 connection timeout
2017-02-10 11:40:02 connection timeout
2017-02-10 11:40:02 trying connection 60.51.91.203:8168 lastseen=10.3hrs
2017-02-10 11:40:02 trying connection 203.159.43.87:8168 lastseen=385201.9hrs
2017-02-10 11:40:05 COIN SPEND TX DID VERIFY!
2017-02-10 11:40:07 connection timeout
2017-02-10 11:40:07 connection timeout
2017-02-10 11:40:08 trying connection 188.18.113.162:8168 lastseen=19.6hrs
2017-02-10 11:40:08 trying connection 218.59.124.228:8168 lastseen=385201.9hrs
2017-02-10 11:40:13 connection timeout
2017-02-10 11:40:13 COIN SPEND TX DID VERIFY!
2017-02-10 11:40:13 connection timeout
2017-02-10 11:40:13 trying connection 47.90.17.168:8168 lastseen=8.3hrs
2017-02-10 11:40:13 trying connection 219.235.107.164:8168 lastseen=385201.9hrs
2017-02-10 11:40:13 SetBestChain: new best=941d2dbd25e20117362bfeb44877f3d83085de6b4426bc95ac9c1b45b9d9e2ac height=5774 log2_work=43.452189 tx=34666 date=2016-11-01 21:24:43 progress=0.109436
2017-02-10 11:40:13 ProcessBlock: ACCEPTED
2017-02-10 11:40:13 getblocks 3814 to 6786c7e396883a637355c1810425bedfa01b68cbae46844c1ef28e5000917fb4 limit 2500
2017-02-10 11:40:13 getblocks stopping at 5210 6786c7e396883a637355c1810425bedfa01b68cbae46844c1ef28e5000917fb4
2017-02-10 11:40:14 connected 47.90.17.168:8168
2017-02-10 11:40:14 send version message: version 90020, blocks=5774, us=84.114.102.235:8168, them=47.90.17.168:8168, peer=47.90.17.168:8168
2017-02-10 11:40:14 trying connection 54.67.83.219:8168 lastseen=3167.0hrs
2017-02-10 11:39:48 COIN SPEND TX DID VERIFY!
2017-02-10 11:39:51 connection timeout
2017-02-10 11:39:51 connection timeout
2017-02-10 11:39:51 trying connection 62.248.241.36:8168 lastseen=11.9hrs
2017-02-10 11:39:51 trying connection 193.69.196.112:8168 lastseen=385201.9hrs
2017-02-10 11:39:56 COIN SPEND TX DID VERIFY!
2017-02-10 11:39:56 connection timeout
2017-02-10 11:39:56 connection timeout
2017-02-10 11:39:57 SetBestChain: new best=9e8904ef860e5bbe4771c0336702df10f1c9b52bf375488e1dd3b84a92978ae0 height=5773 log2_work=43.452176 tx=34659 date=2016-11-01 21:17:19 progress=0.109414
2017-02-10 11:39:57 ProcessBlock: ACCEPTED
2017-02-10 11:39:57 trying connection 13.65.195.137:8168 lastseen=47.7hrs
2017-02-10 11:39:57 trying connection 200.109.29.32:8168 lastseen=385201.9hrs
2017-02-10 11:40:02 connection timeout
2017-02-10 11:40:02 connection timeout
2017-02-10 11:40:02 trying connection 60.51.91.203:8168 lastseen=10.3hrs
2017-02-10 11:40:02 trying connection 203.159.43.87:8168 lastseen=385201.9hrs
2017-02-10 11:40:05 COIN SPEND TX DID VERIFY!
2017-02-10 11:40:07 connection timeout
2017-02-10 11:40:07 connection timeout
2017-02-10 11:40:08 trying connection 188.18.113.162:8168 lastseen=19.6hrs
2017-02-10 11:40:08 trying connection 218.59.124.228:8168 lastseen=385201.9hrs
2017-02-10 11:40:13 connection timeout
2017-02-10 11:40:13 COIN SPEND TX DID VERIFY!
2017-02-10 11:40:13 connection timeout
2017-02-10 11:40:13 trying connection 47.90.17.168:8168 lastseen=8.3hrs
2017-02-10 11:40:13 trying connection 219.235.107.164:8168 lastseen=385201.9hrs
2017-02-10 11:40:13 SetBestChain: new best=941d2dbd25e20117362bfeb44877f3d83085de6b4426bc95ac9c1b45b9d9e2ac height=5774 log2_work=43.452189 tx=34666 date=2016-11-01 21:24:43 progress=0.109436
2017-02-10 11:40:13 ProcessBlock: ACCEPTED
2017-02-10 11:40:13 getblocks 3814 to 6786c7e396883a637355c1810425bedfa01b68cbae46844c1ef28e5000917fb4 limit 2500
2017-02-10 11:40:13 getblocks stopping at 5210 6786c7e396883a637355c1810425bedfa01b68cbae46844c1ef28e5000917fb4
2017-02-10 11:40:14 connected 47.90.17.168:8168
2017-02-10 11:40:14 send version message: version 90020, blocks=5774, us=84.114.102.235:8168, them=47.90.17.168:8168, peer=47.90.17.168:8168
2017-02-10 11:40:14 trying connection 54.67.83.219:8168 lastseen=3167.0hrs
It took 10h to get here (Block 5784) ..pff DEV hurry with fixing this.
It always starts again with processing and checking what the crap is this crappy thing doing all over again and again...can't be serious have noone tested this piece of crap before releasing?
Quote
2017-02-10 12:12:17 ZCoin version v0.8.7.4-unk (2017-02-08 02:29:10 +0100)
2017-02-10 12:12:17 Using OpenSSL version OpenSSL 1.0.1j 15 Oct 2014
2017-02-10 12:12:17 Default data directory C:\Users\user1\AppData\Roaming\zcoin
2017-02-10 12:12:17 Using data directory C:\Users\User1\AppData\Roaming\zcoin
2017-02-10 12:12:17 Using at most 800 connections (2048 file descriptors available)
2017-02-10 12:12:17 Using 12 threads for script verification
2017-02-10 12:12:17 scrypt: using scrypt-sse2 as detected.
2017-02-10 12:12:17 init message: Verifying wallet...
2017-02-10 12:12:17 dbenv.open LogDir=C:\Users\user1\AppData\Roaming\zcoin\database ErrorFile=C:\Users\user1\AppData\Roaming\zcoin\db.log
2017-02-10 12:12:17 Bound to [::]:8168
2017-02-10 12:12:17 Bound to 0.0.0.0:8168
2017-02-10 12:12:17 init message: Loading block index...
2017-02-10 12:12:17 Opening LevelDB in C:\Users\user1\AppData\Roaming\zcoin\blocks\index
2017-02-10 12:12:17 Opened LevelDB successfully
2017-02-10 12:12:17 Opening LevelDB in C:\Users\user1\AppData\Roaming\zcoin\chainstate
2017-02-10 12:12:17 Opened LevelDB successfully
2017-02-10 12:12:17 LoadBlockIndexDB(): last block file = 0
2017-02-10 12:12:17 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=5818, size=23574171, heights=0...5817, time=2014-10-31...2016-11-02)
2017-02-10 12:12:17 LoadBlockIndexDB(): transaction index disabled
2017-02-10 12:12:17 LoadBlockIndexDB(): hashBestChain=1d98a112e5a69f87cb7f4621de8b7e82fad3b1dbd573c38939613a077740a566 height=5816 date=2016-11-02 04:41:57
2017-02-10 12:12:17 init message: Verifying blocks...
2017-02-10 12:12:17 Verifying last 288 blocks at level 3
2017-02-10 12:15:33 No coin database inconsistencies in last 289 blocks (2079 transactions)
2017-02-10 12:15:33 block index 195885ms
2017-02-10 12:15:33 init message: Loading wallet...
2017-02-10 12:15:33 PROCESS BLOCK = 0
2017-02-10 12:15:33 PROCESS BLOCK = 1
2017-02-10 12:15:33 PROCESS BLOCK = 2
2017-02-10 12:15:33 PROCESS BLOCK = 3
2017-02-10 12:15:33 PROCESS BLOCK = 4
2017-02-10 12:15:33 PROCESS BLOCK = 5
2017-02-10 12:15:33 PROCESS BLOCK = 6
2017-02-10 12:12:17 Using OpenSSL version OpenSSL 1.0.1j 15 Oct 2014
2017-02-10 12:12:17 Default data directory C:\Users\user1\AppData\Roaming\zcoin
2017-02-10 12:12:17 Using data directory C:\Users\User1\AppData\Roaming\zcoin
2017-02-10 12:12:17 Using at most 800 connections (2048 file descriptors available)
2017-02-10 12:12:17 Using 12 threads for script verification
2017-02-10 12:12:17 scrypt: using scrypt-sse2 as detected.
2017-02-10 12:12:17 init message: Verifying wallet...
2017-02-10 12:12:17 dbenv.open LogDir=C:\Users\user1\AppData\Roaming\zcoin\database ErrorFile=C:\Users\user1\AppData\Roaming\zcoin\db.log
2017-02-10 12:12:17 Bound to [::]:8168
2017-02-10 12:12:17 Bound to 0.0.0.0:8168
2017-02-10 12:12:17 init message: Loading block index...
2017-02-10 12:12:17 Opening LevelDB in C:\Users\user1\AppData\Roaming\zcoin\blocks\index
2017-02-10 12:12:17 Opened LevelDB successfully
2017-02-10 12:12:17 Opening LevelDB in C:\Users\user1\AppData\Roaming\zcoin\chainstate
2017-02-10 12:12:17 Opened LevelDB successfully
2017-02-10 12:12:17 LoadBlockIndexDB(): last block file = 0
2017-02-10 12:12:17 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=5818, size=23574171, heights=0...5817, time=2014-10-31...2016-11-02)
2017-02-10 12:12:17 LoadBlockIndexDB(): transaction index disabled
2017-02-10 12:12:17 LoadBlockIndexDB(): hashBestChain=1d98a112e5a69f87cb7f4621de8b7e82fad3b1dbd573c38939613a077740a566 height=5816 date=2016-11-02 04:41:57
2017-02-10 12:12:17 init message: Verifying blocks...
2017-02-10 12:12:17 Verifying last 288 blocks at level 3
2017-02-10 12:15:33 No coin database inconsistencies in last 289 blocks (2079 transactions)
2017-02-10 12:15:33 block index 195885ms
2017-02-10 12:15:33 init message: Loading wallet...
2017-02-10 12:15:33 PROCESS BLOCK = 0
2017-02-10 12:15:33 PROCESS BLOCK = 1
2017-02-10 12:15:33 PROCESS BLOCK = 2
2017-02-10 12:15:33 PROCESS BLOCK = 3
2017-02-10 12:15:33 PROCESS BLOCK = 4
2017-02-10 12:15:33 PROCESS BLOCK = 5
2017-02-10 12:15:33 PROCESS BLOCK = 6
February 10, 2017, 06:41:22 AM
New Port to mine with after the fork to the new Algo will be 1596 on https://xzc.suprnova.cc - only new miners will work, not the old ones. New miners should be posted here shortly
your pool is already working on testnet right? i see accepted hashrate with the new miners and that port
February 10, 2017, 06:39:01 AM
AMD miner not working
win7 x64 AMD RX 480
Error 0xc000007b
win7 x64 AMD RX 480
Error 0xc000007b
Here gives a dll error
February 10, 2017, 06:25:48 AM
AMD miner not working
win7 x64 AMD RX 480
Error 0xc000007b
win7 x64 AMD RX 480
Error 0xc000007b
February 10, 2017, 06:20:25 AM
@djm34 has released his Windows binary builds for his miners both for Nvidia (ccminer) and AMD (sgminer)
Nvidia miners: https://github.com/djm34/ccminer-msvc2015/releases/
AMD miners: https://github.com/djm34/sgminer-msvc2015/releases
djm34 was engaged by us to do this so his binaries should be clean.
@Tourgasm, a community member has also has released 64 bit version for the Windows
https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4x64
For cpuminer, @aizensou our dev has released this but no binaries:
https://github.com/zcoinofficial/cpuminer-xzc
Nvidia miners: https://github.com/djm34/ccminer-msvc2015/releases/
AMD miners: https://github.com/djm34/sgminer-msvc2015/releases
djm34 was engaged by us to do this so his binaries should be clean.
@Tourgasm, a community member has also has released 64 bit version for the Windows
https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4x64
For cpuminer, @aizensou our dev has released this but no binaries:
https://github.com/zcoinofficial/cpuminer-xzc
what is the differencw with this https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4?
AMD miner not working
February 10, 2017, 06:06:28 AM
for cpu with this new algorithm it is easier to mine or is more difficult?
February 10, 2017, 05:47:22 AM
After over 18h I still can't get the wallet to sync with the new 0.8.7.4-unk QT Windows build.
This is crazy you need to fix this issue ..without proper syncing it is useless.
This is crazy you need to fix this issue ..without proper syncing it is useless.
yeah, sync takes forever! And there is only the 20000 blocks...
And it looks like wallet needs a lot of time to start with the downloaded blockchain.
February 10, 2017, 05:46:14 AM
pending on block 20334
getinfo
{
"version" : 80704,
"protocolversion" : 90020,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 20334,
"timeoffset" : -3,
"connections" : 7,
"proxy" : "",
"difficulty" : 0.02037817,
"testnet" : false,
"keypoololdest" : 1486699429,
"keypoolsize" : 100,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}
getinfo
{
"version" : 80704,
"protocolversion" : 90020,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 20334,
"timeoffset" : -3,
"connections" : 7,
"proxy" : "",
"difficulty" : 0.02037817,
"testnet" : false,
"keypoololdest" : 1486699429,
"keypoolsize" : 100,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}
February 10, 2017, 05:44:25 AM
This coin has no miner amd x64 I'm out of the game good luck when leaving mine amd x64 it will be too late
February 10, 2017, 05:21:13 AM
After over 18h I still can't get the wallet to sync with the new 0.8.7.4-unk QT Windows build.
This is crazy you need to fix this issue ..without proper syncing it is useless.
This is crazy you need to fix this issue ..without proper syncing it is useless.
February 10, 2017, 04:35:19 AM
No one is mining with the new algo yet we are all mining on a testnet.
February 10, 2017, 04:33:45 AM
PLEASE HELP! WHERE ARE ALL OF YOU IS MINING AND HOW TO MINE WITH NVIDIA ! HOW TO CONFIG PLEASE HELP!
February 10, 2017, 03:42:31 AM
@djm34 has released his Windows binary builds for his miners both for Nvidia (ccminer) and AMD (sgminer)
Nvidia miners: https://github.com/djm34/ccminer-msvc2015/releases/
AMD miners: https://github.com/djm34/sgminer-msvc2015/releases
djm34 was engaged by us to do this so his binaries should be clean.
@Tourgasm, a community member has also has released 64 bit version for the Windows
https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4x64
For cpuminer, @aizensou our dev has released this but no binaries:
https://github.com/zcoinofficial/cpuminer-xzc
Nvidia miners: https://github.com/djm34/ccminer-msvc2015/releases/
AMD miners: https://github.com/djm34/sgminer-msvc2015/releases
djm34 was engaged by us to do this so his binaries should be clean.
@Tourgasm, a community member has also has released 64 bit version for the Windows
https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4x64
For cpuminer, @aizensou our dev has released this but no binaries:
https://github.com/zcoinofficial/cpuminer-xzc
what is the differencw with this https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4?
the difference between the x64 version and the x86 version is a few things
1. you get a small increase using the x64 version
2. the x64 binary works with 5.0, 5.2 and 6.1 compute cards (Geforce 7, 8, 9, 10 series)
3. most people are using x64 windows now a days anyways.
i was not talking about that,i thought it was different in the sense of optimization, with better hashrate
well the only real difference is compute 5.0 was added in the x64 version.
February 10, 2017, 02:45:37 AM
Has anyone successfully started the sgminer for amd on windows?
I cannot get it right.
Something mentioning openssl dll-s libeay32 ssleay32.dll...
I cannot get it right.
Something mentioning openssl dll-s libeay32 ssleay32.dll...
February 10, 2017, 02:42:24 AM
@djm34 has released his Windows binary builds for his miners both for Nvidia (ccminer) and AMD (sgminer)
Nvidia miners: https://github.com/djm34/ccminer-msvc2015/releases/
AMD miners: https://github.com/djm34/sgminer-msvc2015/releases
djm34 was engaged by us to do this so his binaries should be clean.
@Tourgasm, a community member has also has released 64 bit version for the Windows
https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4x64
For cpuminer, @aizensou our dev has released this but no binaries:
https://github.com/zcoinofficial/cpuminer-xzc
Nvidia miners: https://github.com/djm34/ccminer-msvc2015/releases/
AMD miners: https://github.com/djm34/sgminer-msvc2015/releases
djm34 was engaged by us to do this so his binaries should be clean.
@Tourgasm, a community member has also has released 64 bit version for the Windows
https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4x64
For cpuminer, @aizensou our dev has released this but no binaries:
https://github.com/zcoinofficial/cpuminer-xzc
what is the differencw with this https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4?
the difference between the x64 version and the x86 version is a few things
1. you get a small increase using the x64 version
2. the x64 binary works with 5.0, 5.2 and 6.1 compute cards (Geforce 7, 8, 9, 10 series)
3. most people are using x64 windows now a days anyways.
i was not talking about that, i thought it was different in the sense of optimization, with better hashrate
February 10, 2017, 02:41:08 AM
@djm34 has released his Windows binary builds for his miners both for Nvidia (ccminer) and AMD (sgminer)
Nvidia miners: https://github.com/djm34/ccminer-msvc2015/releases/
AMD miners: https://github.com/djm34/sgminer-msvc2015/releases
djm34 was engaged by us to do this so his binaries should be clean.
@Tourgasm, a community member has also has released 64 bit version for the Windows
https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4x64
For cpuminer, @aizensou our dev has released this but no binaries:
https://github.com/zcoinofficial/cpuminer-xzc
Nvidia miners: https://github.com/djm34/ccminer-msvc2015/releases/
AMD miners: https://github.com/djm34/sgminer-msvc2015/releases
djm34 was engaged by us to do this so his binaries should be clean.
@Tourgasm, a community member has also has released 64 bit version for the Windows
https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4x64
For cpuminer, @aizensou our dev has released this but no binaries:
https://github.com/zcoinofficial/cpuminer-xzc
what is the differencw with this https://github.com/Tourgasm/xzc-ccminer/releases/tag/1.8.4?
the difference between the x64 version and the x86 version is a few things
1. you get a small increase using the x64 version
2. the x64 binary works with 5.0, 5.2 and 6.1 compute cards (Geforce 7, 8, 9, 10 series)
3. most people are using x64 windows now a days anyways.
Jump to: