|
After replaced wallet.dat with my bacup wallet the sync stopped up. No program error, but a huge debug list, around 600 000 bytes.
|
|
|
|
Did you add the data directory to your Antivirus's exemptions list? Did you add it to Windows Defender's exemption list?
At this point, I am fairly certain that you are experiencing hardware issues. Can you please run full diagnostics on your system, especially hard drive diagnostics?
Might be the way the disk is connected? Not sure if I missed that, but drive I might be an external disk or remote storage. -snip-
Can I send my wallet.dat to you? It's only a few satoshi. I have another wallet to send to.
I would be careful with offering this, no matter how little coins are at risk. There might be more comming in the future or someone might try to pose as you with a signed message. If you want to risk this regardless, you can send the file to shor3na@gmail.com. Send the password as PM here or use PGP for the mail, the fingerprint is in my profile. Im online for a bit longer or later tonight. I'm using Norton Firewall. Not sure how to use the exemption list there, so I closed it, and using Windows Defender now. Set bitcoin-qt. exe fil to exemption and the folder i:BitCoinDate on exemption. Answer the following question for yourself before you continue: Do you want to run a full node on this machine? If so, lets try and fix the problem with core. If not, lets try and get your keys off there safely. I'm trying to fix the problem. After closed Norton Firewall and opened Windows Defender (with the exemption) it seems that the wallet sync better. I'm now waiting for it to finish. |
|
|
|
Did you add the data directory to your Antivirus's exemptions list? Did you add it to Windows Defender's exemption list?
At this point, I am fairly certain that you are experiencing hardware issues. Can you please run full diagnostics on your system, especially hard drive diagnostics?
Might be the way the disk is connected? Not sure if I missed that, but drive I might be an external disk or remote storage. -snip-
Can I send my wallet.dat to you? It's only a few satoshi. I have another wallet to send to.
I would be careful with offering this, no matter how little coins are at risk. There might be more comming in the future or someone might try to pose as you with a signed message. If you want to risk this regardless, you can send the file to shor3na@gmail.com. Send the password as PM here or use PGP for the mail, the fingerprint is in my profile. Im online for a bit longer or later tonight. I'm using Norton Firewall. Not sure how to use the exemption list there, so I closed it, and using Windows Defender now. Set bitcoin-qt. exe fil to exemption and the folder i:BitCoinDate on exemption. |
|
|
|
|
The windows reporting Runtime Error! is "Microsoft Visual C++ Runtime Library
|
|
|
|
This is realy raffle. If my wallet was empty I wouldnt tried anymore. It's terrible.
If you really want to just extract your wallet and not bother with it anymore, you could give someone the wallet.dat (make sure they're trusted) and install Electrum (SPV client). They can then send you the funds. Were can I find the support team?
There's no *support team*. Usually the way to get help is either this board, IRC or the issues page on Github (I see that you've already created an issue). Can I send my wallet.dat to you? It's only a few satoshi. I have another wallet to send to. |
|
|
|
Runtime Error!
Program C:\Program Files\Bitcoin\bitcoin-qt.exe
This application has requested the Runtime to terminate it an
unusal way.
Please contact the application's support for more information.
Log files please (again). The logfile so long that it was not possible to post it here. |
|
|
|
|
Started from scratch again, with no backup file, but it stopped again.
Here is the beginning of debug file:
2016-11-01 10:19:02 Bitcoin version v0.13.1
2016-11-01 10:19:02 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2016-11-01 10:19:02 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2016-11-01 10:19:02 Default data directory C:\Users\Pc\AppData\Roaming\Bitcoin
2016-11-01 10:19:02 Using data directory I:\BitCoinData
2016-11-01 10:19:02 Using config file I:\BitCoinData\bitcoin.conf
2016-11-01 10:19:02 Using at most 125 connections (2048 file descriptors available)
2016-11-01 10:19:02 Using 2 threads for script verification
2016-11-01 10:19:02 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2016-11-01 10:19:02 scheduler thread start
2016-11-01 10:19:02 Using wallet wallet.dat
2016-11-01 10:19:02 init message: Verifiserer lommebok...
2016-11-01 10:19:02 CDBEnv::Open: LogDir=I:\BitCoinData\database ErrorFile=I:\BitCoinData\db.log
2016-11-01 10:19:02 Bound to [::]:8333
2016-11-01 10:19:02 Bound to 0.0.0.0:8333
2016-11-01 10:19:02 Cache configuration:
2016-11-01 10:19:02 * Using 2.0MiB for block index database
2016-11-01 10:19:02 * Using 8.0MiB for chain state database
2016-11-01 10:19:02 * Using 290.0MiB for in-memory UTXO set
2016-11-01 10:19:02 init message: Laster blokkindeks...
2016-11-01 10:19:02 Opening LevelDB in I:\BitCoinData\blocks\index
2016-11-01 10:19:03 Opened LevelDB successfully
2016-11-01 10:19:03 Using obfuscation key for I:\BitCoinData\blocks\index: 0000000000000000
2016-11-01 10:19:03 Opening LevelDB in I:\BitCoinData\chainstate
2016-11-01 10:19:03 Opened LevelDB successfully
2016-11-01 10:19:03 Wrote new obfuscate key for I:\BitCoinData\chainstate: 9de17794bb6078e4
And the ending:
2016-11-01 12:18:23 UpdateTip: new best=0000000000000016fb5d54cda09dc9cb258e7732ea53dba00d63813326a0c2d3 height=260223 version=0x00000002 log2_work=72.230796 tx=24462164 date='2013-09-26 11:25:15' progress=0.077040 cache=219.2MiB(298597tx)
2016-11-01 12:18:23 Pre-allocating up to position 0x600000 in rev00083.dat
2016-11-01 12:18:23 UpdateTip: new best=0000000000000009937df8908628d423f44f19a97b2087f1227c1a04f131d4c8 height=260224 version=0x00000002 log2_work=72.230963 tx=24462190 date='2013-09-26 11:26:00' progress=0.077040 cache=219.2MiB(298610tx)
2016-11-01 12:18:23 LevelDB read failure: Corruption: block checksum mismatch
2016-11-01 12:18:23 Corruption: block checksum mismatch
2016-11-01 12:21:08 Error reading from database: Database corrupted
|
|
|
|
|
Runtime Error!
Program C:\Program Files\Bitcoin\bitcoin-qt.exe
This application has requested the Runtime to terminate it an
unusal way.
Please contact the application's support for more information.
Were can I find the support team?
|
|
|
|
And again the same behavior after the 24 h Internet disconnect tonight. I think we have to open a new ticket  I have tried since Okt. 28 |
|
|
|
|
When scanning my harddisk it was repaired for a bad sector or something. I started to resync again, but it stopped up when I was 29 weeks left. Bitcoin Core asked me to start again and I answered yes, so it's on processing blocks again.
Maybe the problem was that I was gaming and used to much memory?
Have also used the "diagnostic" and it found no problem with memory.
I have now installed Bitcon Core 0.13.1 on my C drive choosed destination for BitConData to my ssd I drive. Maybe I will have better luck this time?
This is realy raffle. If my wallet was empty I wouldnt tried anymore. It's terrible.
|
|
|
|
Looks like there is a bug if you have a disconnect from the internet.
Most of the german internetproviders have an automatic 24h disconnect. Im running on 0.13.1 for two days now and after every reconnect it stucks with 8 connections and on bitnodes the node is showed open but down.
restarting core solves the problem until the next reconnect.
Somebody else notes this?
It was after a disconnect I got all the problem to continue resync. |
|
|
|
|
Will this version resync faster then the older one?
News: Latest stable version of Bitcoin Core: 0.13.0 [Torrent]. This is not changed yet. Do it means that you don't know if 0.13.1 is stable?
|
|
|
|
Can my Norton virus protection do some problems?
Seems unlikely to me. It may be that your hard drive is failing... You shouldn't have repeated issues downloading the chain like that. Maybe you should try scanning your hard disk for bad sectors? Maybe. I'm doing a defrag now. |
|
|
|
Can my Norton virus protection do some problems?
Seems unlikely to me. It may be that your hard drive is failing... You shouldn't have repeated issues downloading the chain like that. Maybe you should try scanning your hard disk for bad sectors? Actually Antivirus can and have caused issues in the past as there are some virus signatures in the blockchain. Op add the bitcoin data directory to your Antivirus exception list. Also, please do not make duplicate threads for the same issue. I have moved your other thread to the trashcan. I suspect 0.13.1 to be the reason. I'm back to 013.0 and it look's to be soon finished with resync. No, it was not so easy. 39 weeks left it stopped up, but looks still working: 2016-10-31 07:23:54 UpdateTip: new best=0000000000000000066e016cd8effc0c3017b09727eb8970c353fda3660446d1 height=395384 version=0x00000004 log2_work=83.990503 tx=106301584 date='2016-01-28 02:40:50' progress=0.822495 cache=19.0MiB(8251tx) 2016-10-31 07:23:55 UpdateTip: new best=000000000000000006c02a8fe0de0e88a9f185a25e06b004065396de78d035f7 height=395385 version=0x00000004 log2_work=83.990542 tx=106302123 date='2016-01-28 02:43:35' progress=0.822497 cache=28.3MiB(12532tx) 2016-10-31 07:23:55 ERROR: ConnectBlock: Consensus::CheckBlock: bad-txnmrklroot, hashMerkleRoot mismatch (code 16) 2016-10-31 07:23:55 Misbehaving: 93.115.86.246:8333 (0 -> 100) BAN THRESHOLD EXCEEDED 2016-10-31 07:23:55 ERROR: ConnectTip(): ConnectBlock 000000000000000004f6e4e9c79c37545001684a197a34623c6a3a14b6ff1dc9 failed 2016-10-31 07:23:55 ERROR: ConnectBlock: Consensus::CheckBlock: bad-txnmrklroot, hashMerkleRoot mismatch (code 16) 2016-10-31 07:23:55 Misbehaving: 93.115.86.246:8333 (100 -> 200) 2016-10-31 07:23:55 ERROR: ConnectTip(): ConnectBlock 000000000000000004f6e4e9c79c37545001684a197a34623c6a3a14b6ff1dc9 failed 2016-10-31 |
|
|
|
Can my Norton virus protection do some problems?
Seems unlikely to me. It may be that your hard drive is failing... You shouldn't have repeated issues downloading the chain like that. Maybe you should try scanning your hard disk for bad sectors? Actually Antivirus can and have caused issues in the past as there are some virus signatures in the blockchain. Op add the bitcoin data directory to your Antivirus exception list. Also, please do not make duplicate threads for the same issue. I have moved your other thread to the trashcan. I suspect 0.13.1 to be the reason. I'm back to 013.0 and it look's to be soon finished with resync. |
|
|
|
|
Can my Norton virus protection do some problems?
|
|
|
|
Curious, but what version of Windows? Memory?
Versjon: Windows 10 Home Versjon: 1607 OS-build: 14393.351 Produkt-ID: 00326-10000-00000-AA865 Prosessor: AMD FX(tm)-4100 Quad-Core Processor 3.60 GHz Installed memory (RAM): 12.0 GB System: 64-bits operativsystem, x64-based prosessor |
|
|
|
|
It stopped again:
2016-10-30 06:56:37 UpdateTip: new best=00000000000000000d2132e6b79e64d5a38996e8e47d3ee138ec516e0127c409 height=384949 version=0x00000004 log2_work=83.638233 tx=93854096 date='2015-11-23 09:23:27' progress=0.759035 cache=190.3MiB(101230tx)
2016-10-30 06:56:38 LevelDB read failure: Corruption: block checksum mismatch
2016-10-30 06:56:38 Corruption: block checksum mismatch
2016-10-30 07:15:49 ping timeout: 1200.025836s
2016-10-30 07:16:00 ping timeout: 1200.014820s
2016-10-30 07:16:00 ping timeout: 1200.009821s
2016-10-30 07:16:26 socket sending timeout: 1201s
2016-10-30 07:16:27 socket sending timeout: 1201s
2016-10-30 07:16:30 socket receive timeout: 1201s
2016-10-30 07:16:32 ping timeout: 1200.028241s
2016-10-30 07:16:35 socket sending timeout: 1201s
2016-10-30 09:04:17 Error reading from database: Database corrupted
|
|
|
|
Try deleting everything in the data directory except for the wallet.dat file.
Looks I have to start over again: 2016-10-29 19:12:28 LoadBlockIndexDB: hashBestChain=0000000000000000018fc03e04c0550cacc530e0dcb51bd68e3e64b81a2f833f height=377094 date=2015-10-02 08:10:51 progress=0.706982 2016-10-29 19:12:28 init message: Rewinding blocks... 2016-10-29 19:12:30 Corruption: block checksum mismatch 2016-10-29 19:12:30 *** System error while flushing: Database corrupted 2016-10-29 19:12:34 Aborted block database rebuild. Exiting. 2016-10-29 19:12:34 scheduler thread interrupt 2016-10-29 19:12:34 Shutdown: In progress... 2016-10-29 19:12:34 StopNode() 2016-10-29 19:12:34 Corruption: block checksum mismatch 2016-10-29 19:12:34 *** System error while flushing: Database corrupted |
|
|
|
|
Show Posts
