Topic: 0.13.1 sync problems, nearly finished, but stopped up several times - page 3. (Read 5099 times)

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?

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.

This is somewhat anecdotal, but it may be helpful anyways.

I had similar problems a few years back, and it turned out to be bad RAM.

I wasn't having any other PC-related problems; no crashing, no problems when gaming, just problems w/core. I eventually ran memtest86+, and discovered a single bit error (in all 16GB) which matched up perfectly with the single-bit error (in terms of its position in a 64-bit word) I had also tracked down in my block files.

Although I was surprised, perhaps I shouldn't have been. Unlike most software, Bitcoin does a whole lot of checking/hashing of its block data, so it's much more likely to uncover hardware problems on a PC than most any other non-diagnostic software.

Win 10 has a memory diagnostic tool built-in. Just click the Start, and type "diagnostic", and should show up (it will require a reboot). Memtest86+ is probably more thorough; it's a little harder to set up, but worth the effort IMO.

Maybe. I'm doing a defrag now.

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

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.

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.

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?

Can my Norton virus protection do some problems?

That looks fine.

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

Curious, but what version of Windows? Memory?

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

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

Ok. Also tell you that I'm useing datadir=e:\BitcoinData because I don't like to fill up the c disk.

Have done what you told me and it's downloading now, but it will take some hours

Try deleting everything in the data directory except for the wallet.dat file.

I deleted the "Blocks) folder, but still problems:

2016-10-28 12:53:57 Bitcoin version v0.13.1
2016-10-28 12:53:57 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2016-10-28 12:53:57 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2016-10-28 12:53:57 Default data directory C:\Users\Pc\AppData\Roaming\Bitcoin
2016-10-28 12:53:57 Using data directory E:\BitcoinData
2016-10-28 12:53:57 Using config file E:\BitcoinData\bitcoin.conf
2016-10-28 12:53:57 Using at most 125 connections (2048 file descriptors available)
2016-10-28 12:53:57 Using 2 threads for script verification
2016-10-28 12:53:57 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-10-28 12:53:57 scheduler thread start
2016-10-28 12:53:57 Using wallet wallet.dat
2016-10-28 12:53:57 init message: Verifiserer lommebok...
2016-10-28 12:53:57 CDBEnv::Open: LogDir=E:\BitcoinData\database ErrorFile=E:\BitcoinData\db.log
2016-10-28 12:53:58 Bound to [::]:8333
2016-10-28 12:53:58 Bound to 0.0.0.0:8333
2016-10-28 12:53:58 Cache configuration:
2016-10-28 12:53:58 * Using 2.0MiB for block index database
2016-10-28 12:53:58 * Using 8.0MiB for chain state database
2016-10-28 12:53:58 * Using 290.0MiB for in-memory UTXO set
2016-10-28 12:53:58 init message: Laster blokkindeks...
2016-10-28 12:53:58 Opening LevelDB in E:\BitcoinData\blocks\index
2016-10-28 12:53:58 Opened LevelDB successfully
2016-10-28 12:53:58 Using obfuscation key for E:\BitcoinData\blocks\index: 0000000000000000
2016-10-28 12:53:58 Opening LevelDB in E:\BitcoinData\chainstate
2016-10-28 12:53:58 Opened LevelDB successfully
2016-10-28 12:53:58 Using obfuscation key for E:\BitcoinData\chainstate: 5e68e69cbe6cd8f9
2016-10-28 12:53:58 LoadBlockIndexDB: last block file = 0
2016-10-28 12:53:58 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2016-10-28 12:53:58 Checking all blk files are present...
2016-10-28 12:53:58 LoadBlockIndexDB: transaction index disabled
2016-10-28 12:53:58 Initializing databases...
2016-10-28 12:53:58 init message: Verifiserer blokker...
2016-10-28 12:53:58  block index             237ms
2016-10-28 12:53:58 init message: Laster lommebok...
2016-10-28 12:53:58 nFileVersion = 130100
2016-10-28 12:53:58 Keys: 0 plaintext, 267 encrypted, 63 w/ metadata, 267 total
2016-10-28 12:53:58  wallet                  212ms
2016-10-28 12:54:18 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x00000001 log2_work=32.000022 tx=1 date='2009-01-03 18:15:05' progress=0.000000 cache=0.0MiB(0tx)
2016-10-28 12:54:18 mapBlockIndex.size() = 1
2016-10-28 12:54:18 nBestHeight = 0
2016-10-28 12:54:18 setKeyPool.size() = 100
2016-10-28 12:54:18 mapWallet.size() = 321
2016-10-28 12:54:18 mapAddressBook.size() = 12
2016-10-28 12:54:18 init message: Laster adresser...
2016-10-28 12:54:18 torcontrol thread start
2016-10-28 12:54:18 Loaded 26218 addresses from peers.dat  188ms
2016-10-28 12:54:18 init message: Loading banlist...
2016-10-28 12:54:18 init message: Starting network threads...
2016-10-28 12:54:18 AddLocal([2001:0:5ef5:79fb:34cd:34c4:a322:8ce1]:8333,1)
2016-10-28 12:54:18 Discover: DESKTOP-KKQMMP0 - 2001:0:5ef5:79fb:34cd:34c4:a322:8ce1
2016-10-28 12:54:18 dnsseed thread start
2016-10-28 12:54:18 net thread start
2016-10-28 12:54:18 addcon thread start
2016-10-28 12:54:18 opencon thread start
2016-10-28 12:54:18 msghand thread start
2016-10-28 12:54:18 init message: Ferdig med lasting
2016-10-28 12:54:18 GUI: Platform customization: "windows"
2016-10-28 12:54:18 GUI: PaymentServer::LoadRootCAs: Loaded  42  root certificates
2016-10-28 12:54:19 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63152, peer=1
2016-10-28 12:54:20 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63153, peer=2
2016-10-28 12:54:20 ERROR: ConnectBlock(): tried to overwrite transaction
2016-10-28 12:54:20 Misbehaving: 107.3.73.178:8333 (0 -> 100) BAN THRESHOLD EXCEEDED
2016-10-28 12:54:20 InvalidChainFound: invalid block=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048  height=1  log2_work=33.000022  date=2009-01-09 02:54:25
2016-10-28 12:54:20 InvalidChainFound:  current best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f  height=0  log2_work=32.000022  date=2009-01-03 18:15:05
2016-10-28 12:54:20 ERROR: ConnectTip(): ConnectBlock 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 failed
2016-10-28 12:54:20 InvalidChainFound: invalid block=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048  height=1  log2_work=33.000022  date=2009-01-09 02:54:25
2016-10-28 12:54:20 InvalidChainFound:  current best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f  height=0  log2_work=32.000022  date=2009-01-03 18:15:05
2016-10-28 12:54:21 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63155, peer=3
2016-10-28 12:54:21 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63156, peer=4
2016-10-28 12:54:22 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63157, peer=5
2016-10-28 12:54:23 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63160, peer=7
2016-10-28 12:54:24 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63162, peer=9
2016-10-28 12:54:24 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63161, peer=8
2016-10-28 12:54:25 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63163, peer=10
2016-10-28 12:54:25 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63164, peer=11
2016-10-28 12:54:27 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63166, peer=12
2016-10-28 12:54:27 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63167, peer=13
2016-10-28 12:54:29 P2P peers available. Skipped DNS seeding.
2016-10-28 12:54:29 dnsseed thread exit
2016-10-28 12:54:37 receive version message: /Satoshi:0.13.1/: version 70014, blocks=436291, us=92.221.115.30:63171, peer=14

db fil:
 wallet.1477655813.bak: DB_VERIFY_BAD: Database verification failed
Database handles still open at environment close
Open database handle: wallet.dat/main
wallet.1477657024.bak: DB_VERIFY_BAD: Database verification failed
Database handles still open at environment close
Open database handle: wallet.dat/main
Database handles still open at environment close
Open database handle: wallet.dat/main

This was recently added. Just ignore the testnet shortcut, you probably won't need it.

You have a corrupt block. The easiest solution is to delete the entire "blocks" folder inside of the Bitcoin Core data directory and then let Bitcoin Core resync the whole blockchain.

I had to reinstall my windows, and no am I trying to install my Bitcoin Core. First, I wonder why there is 2 shortcut, Bitcoin Core and Bitcoin Core (testnet)?

I have problem to start up my wallet. Got this error:

:30 Misbehaving: 54.186.37.39:8333 (66113000 -> 66113100)

2016-10-28 10:41:31 ERROR: ConnectBlock: Consensus::CheckBlock: bad-txnmrklroot, hashMerkleRoot mismatch (code 16)
2016-10-28 10:41:31 ERROR: ConnectTip(): ConnectBlock 00000000000003f0c8eb69f33b0899e96d87065c0c3c674f5af8ec8c0b48d541 failed
2016-10-28 10:41:31 ERROR: ConnectBlock: Consensus::CheckBlock: bad-txnmrklroot, hashMerkleRoot mismatch (code 16)
2016-10-28 10:41:31 ERROR: ConnectTip(): ConnectBlock 00000000000003f0c8eb69f33b0899e96d87065c0c3c674f5af8ec8c0b48d541 failed

This is after I used my wallet back up.

Anyone know what to do to fix it?