0.13.1 sync problems, nearly finished, but stopped up several times

[Hanslo]

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?

[1714935509]

1714935509

[1714935509]

1714935509

[1714935509]

1714935509

[1714935509]

1714935509

[1714935509]

1714935509

[achow101]

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)?

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

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?

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.

[Hanslo]

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)?

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

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?

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 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

[achow101]

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

[Hanslo]

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

[Hanslo]

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

[Hanslo]

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

[cr1776]

Curious, but what version of Windows? Memory?

[Hanslo]

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

[cr1776]

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

That looks fine.

[Hanslo]

Can my Norton virus protection do some problems?

[OgNasty]

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?

[achow101]

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.

[Hanslo]

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.

[Hanslo]

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

[Hanslo]

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.

[btchris]

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.

[Hanslo]

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.

[Hanslo]

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?

[Lauda]

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).

[OgNasty]

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?

I'm assuming this has to do with how you installed the data on a separate drive.  If you believe the application is the reason why you are having these issues and not your hardware, you could alternatively try downloading the blockchain over the torrent network.

[achow101]

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).

[Hanslo]

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

[Hanslo]

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.

[Hanslo]

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.

[achow101]

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?

[shorena]

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.

[Lauda]

The logfile so long that it was not possible to post it here.

You could upload it somewhere, or make a copy and cut out the unimportant stuff (e.g. clean block processing).

Can I send my wallet.dat to you? It's only a few satoshi. I have another wallet to send to.

You can, either shorena or me (I'm usually online longer, in case that you miss them). Make sure that you keep in mind the concerns raised by them.

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.

Could be a cable/port problem in that case. USB 3.0 is really flaky, and I've had this happen 2-3 times myself (the port on the laptop was not as stable as the one in my USB Hub which I've used afterwards). Fixing this required several reindexing attempts (during diagnostic time).

[Hanslo]

The windows reporting Runtime Error! is "Microsoft Visual C++ Runtime Library

[achow101]

The windows reporting Runtime Error! is "Microsoft Visual C++ Runtime Library

That tells us absolutely nothing. Again, have you run diagnostics on your hardware? Have you tried using another drive (perhaps an internal one) for storing the blockchain?

[Hanslo]

The windows reporting Runtime Error! is "Microsoft Visual C++ Runtime Library

That tells us absolutely nothing. Again, have you run diagnostics on your hardware? Have you tried using another drive (perhaps an internal one) for storing the blockchain?

Yes, I have:

https://bitcointalk.org/index.php?topic=1664323.msg16736510#msg16736510

[Hanslo]

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.

[shorena]

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.

[Hanslo]

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.

[Hanslo]

After replaced wallet.dat with my bacup wallet the sync stopped up. No program error, but a huge debug list, around 600 000 bytes.

[Lauda]

After replaced wallet.dat with my bacup wallet the sync stopped up. No program error, but a huge debug list, around 600 000 bytes.

What exactly did you do? Hopefully you did not attempt to alter any files during the synchronization itself? Check the debug log and post the latest (or most relevant) part of it.

[Hanslo]

After replaced wallet.dat with my bacup wallet the sync stopped up. No program error, but a huge debug list, around 600 000 bytes.

What exactly did you do? Hopefully you did not attempt to alter any files during the synchronization itself? Check the debug log and post the latest (or most relevant) part of it.

I exite wallet first before rename wallet.dat to wallet.dat_original, then copied my backup, lommebok.dat, to BitCoinDat folder and renamed it to wallet.dat.
Debug.log was so huge that it was not possible to open it.
Right now sync my Bitcoin Core 0.13.1 with the network, but without my wallet backup.

[Lauda]

I exite wallet first before rename wallet.dat to wallet.dat_original, then copied my backup, lommebok.dat, to BitCoinDat folder and renamed it to wallet.dat.

You're trying to say that you can't sync up with the backup wallet, but with the original wallet it works?

Debug.log was so huge that it was not possible to open it.

You can open it, you just need better software to do so.

Right now sync my Bitcoin Core 0.13.1 with the network, but without my wallet backup.

Good. As mentioned earlier, someone could extract your money from the backup one if needed.

[Hanslo]

I exite wallet first before rename wallet.dat to wallet.dat_original, then copied my backup, lommebok.dat, to BitCoinDat folder and renamed it to wallet.dat.

You're trying to say that you can't sync up with the backup wallet, but with the original wallet it works?

With my oldest backup wallet it stopped up, yes.

Debug.log was so huge that it was not possible to open it.

You can open it, you just need better software to do so.

To late, debug.log was gone after I startet over again.

Right now sync my Bitcoin Core 0.13.1 with the network, but without my wallet backup.

Good. As mentioned earlier, someone could extract your money from the backup one if needed.

I'm 1 year and 46 weeks behind now. Nearest I come during my other attempt was around 39 weeks behind. I was also making a backup wallet that time, so I have 5 backups now

One of the forum members here warned me to send backup file to other.

[Lauda]

I'm 1 year and 46 weeks behind now. Nearest I come during my other attempt was around 42 weeks behind. I was also making a backup wallet that time, so I have 5 backups now

Well, you haven't really provided us with adequate information to come up with concrete ways to help you in addition to this being quite a specific problem. Your Bitcoin folder is not on an external disk, right?

One of the forum members here warned me to send backup file to other.

Correct. Do not send the wallet.dat unless you plan on never using those addresses again.

[Hanslo]

I'm 1 year and 46 weeks behind now. Nearest I come during my other attempt was around 42 weeks behind. I was also making a backup wallet that time, so I have 5 backups now

Well, you haven't really provided us with adequate information to come up with concrete ways to help you in addition to this being quite a specific problem. Your Bitcoin folder is not on an external disk, right?

One of the forum members here warned me to send backup file to other.

Correct. Do not send the wallet.dat unless you plan on never using those addresses again.

It is a Seagate Expansion Drive SSD 2 TB. External. Program is on my c drive. I was first using my internal 1 TB hardisk.

[Hanslo]

This is from old topic when I had problem with my e: harddisk

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

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 39 weeks left. Bitcoin Core asked me to start again and I answered yes, so it's on processing blocks again.

[shorena]

-snip-

Code:

2016-10-31 07:23:55 Misbehaving: 93.115.86.246:8333 (100 -> 200)

-snip-

Looks like you have nodes misbehaving, but that should be no issue.

[Hanslo]

Error opening block database. Want to restore block database now?

This is the last lines in debug.log:

2016-11-02 16:57:19 Opening LevelDB in I:\BitCoinData\chainstate
2016-11-02 16:57:26 Opened LevelDB successfully
2016-11-02 16:57:26 Using obfuscation key for I:\BitCoinData\chainstate: 0b2ecafd5c12fdff
2016-11-02 16:58:24 LoadBlockIndexDB: last block file = 275
2016-11-02 16:58:24 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=190, size=90703135, heights=358531...358766, time=2015-05-29...2015-05-31)
2016-11-02 16:58:24 Checking all blk files are present...
2016-11-02 16:58:35 LoadBlockIndexDB: transaction index disabled
2016-11-02 16:58:36 LoadBlockIndexDB: hashBestChain=000000000000000012612a2949ed88a757a2e7e9b54a5901ac74e76f0d207f17 height=358695 date=2015-05-30 18:28:52 progress=0.567726
2016-11-02 16:58:36 init message: Rewinding blocks...
2016-11-02 16:58:37 init message: Verifiserer blokker...
2016-11-02 16:58:37 Verifying last 6 blocks at level 3
2016-11-02 16:58:37 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...LevelDB read failure: Corruption: block checksum mismatch
2016-11-02 16:58:39 Corruption: block checksum mismatch

The hole log is to big to post here.

[shorena]

Error opening block database. Want to restore block database now?

Code:

This is the last lines in debug.log:
-snip-
2016-11-02 16:58:37 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...LevelDB read failure: Corruption: block checksum mismatch
2016-11-02 16:58:39 Corruption: block checksum mismatch

The hole log is to big to post here.

Since this keeps happening, it might still be a hardware problem (e.g. disk [you switch it IIRC], RAM or CPU) or a problem with some software that is interfering with the data (e.g. anti virus or similar).

[Hanslo]

Error opening block database. Want to restore block database now?

Code:

This is the last lines in debug.log:
-snip-
2016-11-02 16:58:37 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...LevelDB read failure: Corruption: block checksum mismatch
2016-11-02 16:58:39 Corruption: block checksum mismatch

The hole log is to big to post here.

Since this keeps happening, it might still be a hardware problem (e.g. disk [you switch it IIRC], RAM or CPU) or a problem with some software that is interfering with the data (e.g. anti virus or similar).

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 is a Seagate Expansion Drive SSD 2 TB. External. Program is on my c drive. I was first using my internal 1 TB hardisk.

Using Windows Defender with exeption. Else it's Norton.

[shorena]

Error opening block database. Want to restore block database now?

Code:

This is the last lines in debug.log:
-snip-
2016-11-02 16:58:37 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...LevelDB read failure: Corruption: block checksum mismatch
2016-11-02 16:58:39 Corruption: block checksum mismatch

The hole log is to big to post here.

Since this keeps happening, it might still be a hardware problem (e.g. disk [you switch it IIRC], RAM or CPU) or a problem with some software that is interfering with the data (e.g. anti virus or similar).

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 is a Seagate Expansion Drive SSD 2 TB. External. Program is on my c drive. I was first using my internal 1 TB hardisk.

Using Windows Defender with exeption. Else it's Norton.

Just going off the specs here... might as well be Win10 mucking about with the files for some reason.
12 GB is kinda odd, are you using old RAM maybe? Like 4+4 new and 2+2 old or something like that.

[Hanslo]

Error opening block database. Want to restore block database now?

Code:

This is the last lines in debug.log:
-snip-
2016-11-02 16:58:37 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...LevelDB read failure: Corruption: block checksum mismatch
2016-11-02 16:58:39 Corruption: block checksum mismatch

The hole log is to big to post here.

Since this keeps happening, it might still be a hardware problem (e.g. disk [you switch it IIRC], RAM or CPU) or a problem with some software that is interfering with the data (e.g. anti virus or similar).

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 is a Seagate Expansion Drive SSD 2 TB. External. Program is on my c drive. I was first using my internal 1 TB hardisk.

Using Windows Defender with exeption. Else it's Norton.

Just going off the specs here... might as well be Win10 mucking about with the files for some reason.
12 GB is kinda odd, are you using old RAM maybe? Like 4+4 new and 2+2 old or something like that.

Checked the memory and it was ok. Maybe Win10, yes. When I used my wallet very often my operativsystem was Win7.

[Hanslo]

2016-11-03 17:29:00 UpdateTip: new best=000000000000000001a4f543e574f6e9d6e6e7c4ea2b84a5c1d5193a0a295995 height=369485 version=0x00000003 log2_work=83.200456 tx=79613520 date='2015-08-11 22:44:49' progress=0.651173 cache=271.0MiB(105427tx)
2016-11-03 17:29:01 UpdateTip: new best=00000000000000000b171e323b3b22249bf387710174951fc028a90b13a6ba71 height=369486 version=0x00000003 log2_work=83.200486 tx=79614560 date='2015-08-11 22:49:23' progress=0.651180 cache=272.1MiB(106503tx)
2016-11-03 17:29:01 UpdateTip: new best=00000000000000000a46e4c6e7ccdcd267212ba28409c8f8652e3cbe09cfbc66 height=369487 version=0x00000003 log2_work=83.200515 tx=79615168 date='2015-08-11 22:59:53' progress=0.651186 cache=272.4MiB(107072tx)
2016-11-03 17:29:02 UpdateTip: new best=0000000000000000012dd40bbc4ec394f9a7a3cef8bb116e424233b6c57c51f5 height=369488 version=0x00000003 log2_work=83.200544 tx=79616449 date='2015-08-11 23:12:08' progress=0.651196 cache=274.9MiB(108360tx)
2016-11-03 17:29:02 UpdateTip: new best=00000000000000000614bbd45fd5fc16fc0c6ef9345f295e7c14b1ca53546084 height=369489 version=0x00000003 log2_work=83.200574 tx=79617255 date='2015-08-11 23:24:33' progress=0.651204 cache=276.4MiB(109206tx)
2016-11-03 17:29:03 UpdateTip: new best=00000000000000000e62faff5e379064fc5c4dfa6b760b7a74b04cd6551a8abc height=369490 version=0x00000003 log2_work=83.200603 tx=79619372 date='2015-08-12 00:00:47' progress=0.651226 cache=283.0MiB(111596tx)
2016-11-03 17:29:03 UpdateTip: new best=0000000000000000145edd92076d5b0680c1733af43ca326d75ca82ebf1b6a36 height=369491 version=0x00000003 log2_work=83.200633 tx=79619588 date='2015-08-12 00:02:17' progress=0.651228 cache=283.2MiB(111804tx)
2016-11-03 17:29:04 UpdateTip: new best=000000000000000009ea174667794d7f33d905d98d188c0cb97caa570cfcccbb height=369492 version=0x00000003 log2_work=83.200662 tx=79620593 date='2015-08-12 00:15:47' progress=0.651237 cache=284.5MiB(112790tx)
2016-11-03 17:29:04 Pre-allocating up to position 0x200000 in rev00318.dat
2016-11-03 17:29:04 UpdateTip: new best=00000000000000000a5a04a0db8e6c8d5ce77a57eb429c423187c369877e7f21 height=369493 version=0x00000003 log2_work=83.200691 tx=79621517 date='2015-08-12 00:28:21' progress=0.651246 cache=285.5MiB(113795tx)
2016-11-03 17:29:05 UpdateTip: new best=000000000000000001daa7e4139da51309bac6c78e851b19e32657428d094abf height=369494 version=0x00000003 log2_work=83.200721 tx=79622115 date='2015-08-12 00:40:03' progress=0.651253 cache=285.7MiB(114366tx)
2016-11-03 17:29:05 UpdateTip: new best=00000000000000000e21d6ae3944a058138a900e29813b97c0c8b78a241f34dd height=369495 version=0x00000003 log2_work=83.20075 tx=79622659 date='2015-08-12 00:49:27' progress=0.651258 cache=286.1MiB(114902tx)
2016-11-03 17:29:05 UpdateTip: new best=00000000000000000204a252c092267eea1cb005e8a3c9266f3699321aedd718 height=369496 version=0x00000003 log2_work=83.200779 tx=79623351 date='2015-08-12 00:57:51' progress=0.651264 cache=288.8MiB(115762tx)
2016-11-03 17:29:06 UpdateTip: new best=0000000000000000115f3e1d1b717f3bbfd6801786fab957a1a5b2058d61c2f2 height=369497 version=0x00000003 log2_work=83.200809 tx=79624909 date='2015-08-12 01:24:50' progress=0.651281 cache=289.4MiB(117378tx)
2016-11-03 17:29:10 Corruption: block checksum mismatch
2016-11-03 17:29:10 *** System error while flushing: Database corrupted
2016-11-03 17:29:24 ERROR: ProcessNewBlock: ActivateBestChain failed
2016-11-03 17:29:24 tor: Thread interrupt
2016-11-03 17:29:24 opencon thread interrupt
2016-11-03 17:29:24 torcontrol thread exit
2016-11-03 17:29:24 scheduler thread interrupt
2016-11-03 17:29:24 addcon thread interrupt
2016-11-03 17:29:24 msghand thread interrupt
2016-11-03 17:29:24 net thread interrupt
2016-11-03 17:29:24 Shutdown: In progress...
2016-11-03 17:29:24 StopNode()
2016-11-03 17:29:25 Corruption: block checksum mismatch
2016-11-03 17:29:25 *** System error while flushing: Database corrupted
2016-11-03 17:43:37 Shutdown: done

[Hanslo]

2016-11-04 04:30:52 UpdateTip: new best=00000000000000000d69fa2d55c58c82f754d64f75ec938044d21f6612998aa5 height=375787 version=0x00000003 log2_work=83.383111 tx=85073513 date='2015-09-23 14:24:10' progress=0.695425 cache=274.8MiB(116456tx)
2016-11-04 04:30:53 UpdateTip: new best=000000000000000004c68cd5660e0b94dffcb81c5b51cca535a7aac28f0c18e6 height=375788 version=0x00000003 log2_work=83.38314 tx=85075087 date='2015-09-23 14:40:00' progress=0.695436 cache=276.2MiB(118247tx)
2016-11-04 04:30:53 UpdateTip: new best=00000000000000000c2d37f8008b397fa78e2f82c982521c8292ebd14f1f7c80 height=375789 version=0x00000003 log2_work=83.383169 tx=85075088 date='2015-09-23 15:00:35' progress=0.695444 cache=276.2MiB(118248tx)
2016-11-04 04:30:56 Corruption: block checksum mismatch
2016-11-04 04:30:56 *** System error while flushing: Database corrupted
2016-11-04 04:49:51 ping timeout: 1200.022713s
2016-11-04 04:50:27 ping timeout: 1200.008012s
2016-11-04 04:50:43 ping timeout: 1200.004705s
2016-11-04 04:50:47 socket sending timeout: 1201s
2016-11-04 04:50:47 socket sending timeout: 1201s
2016-11-04 04:50:47 socket sending timeout: 1201s
2016-11-04 04:50:47 socket sending timeout: 1201s
2016-11-04 04:50:47 socket sending timeout: 1201s
2016-11-04 05:15:57 ERROR: ProcessNewBlock: ActivateBestChain failed
2016-11-04 05:15:57 tor: Thread interrupt
2016-11-04 05:15:57 addcon thread interrupt
2016-11-04 05:15:57 torcontrol thread exit
2016-11-04 05:15:57 opencon thread interrupt
2016-11-04 05:15:57 scheduler thread interrupt
2016-11-04 05:15:57 msghand thread interrupt
2016-11-04 05:15:57 net thread interrupt
2016-11-04 05:15:57 Shutdown: In progress...
2016-11-04 05:15:57 StopNode()
2016-11-04 05:15:57 Corruption: block checksum mismatch
2016-11-04 05:15:57 *** System error while flushing: Database corrupted
2016-11-04 05:16:06 Shutdown: done

[shorena]

Re: Bitcoin Core 0.13.1 Released
Today at 02:52:52 AM
Reply with quote  #35
I upgraded my client to ver 0.13.1 today but I encountered some problem with my antivirus - Avast.
After an upgrade when I wanted to start my wallet Avast stopped the process did a deep scan and quarantined the bitcoin-qt.exe.
Apparently bitcoin-qt.exe is infected with Dyna:BitCoinMiner-CR[PUP] - but I am pretty sure it is a false positive.

Well, kinda. AFAIK bitcoin core can still be used for mining, even though it only makes sense on Testnets.

[Hanslo]

4 weeks left. an then, again:

2016-11-05 07:56:35 Pre-allocating up to position 0x900000 in rev00641.dat
2016-11-05 07:56:35 UpdateTip: new best=0000000000000000029e7fab3a30a667bcde41dd4815a30aff85a6c74427f5d7 height=432888 version=0x20000000 log2_work=85.363322 tx=160683190 date='2016-10-04 23:39:13' progress=0.985894 cache=78.5MiB(43928tx)
2016-11-05 07:56:36 UpdateTip: new best=0000000000000000046e5681c834b21b9994636ac904c9408afa4891209ea695 height=432889 version=0x20000000 log2_work=85.363352 tx=160684129 date='2016-10-04 23:40:27' progress=0.985895 cache=79.6MiB(45950tx)
2016-11-05 07:56:37 UpdateTip: new best=000000000000000001b4e19a9dc637567bcd4aa8b565e4f1b59567aaf0039775 height=432890 version=0x20000000 log2_work=85.363382 tx=160685993 date='2016-10-04 23:52:27' progress=0.985898 cache=82.0MiB(49409tx)
2016-11-05 07:56:38 UpdateTip: new best=0000000000000000043df1cfa8167937117f32b54582ca5644a2b08cbf77c2b8 height=432891 version=0x20000000 log2_work=85.363412 tx=160688621 date='2016-10-05 00:11:55' progress=0.985905 cache=84.8MiB(53358tx)
2016-11-05 07:56:40 UpdateTip: new best=00000000000000000390a3b38f4bfdf15cb3528c6050c4c6cd68052f38fe25be height=432892 version=0x20000000 log2_work=85.363442 tx=160689837 date='2016-10-05 00:15:36' progress=0.985906 cache=87.7MiB(56838tx)
2016-11-05 07:56:40 LevelDB read failure: Corruption: block checksum mismatch
2016-11-05 07:56:40 Corruption: block checksum mismatch
2016-11-05 08:04:01 Error reading from database: Database corrupted

Again:

2016-11-05 08:14:13 Bitcoin version v0.13.1
2016-11-05 08:14:13 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2016-11-05 08:14:14 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2016-11-05 08:14:14 Default data directory C:\Users\Pc\AppData\Roaming\Bitcoin
2016-11-05 08:14:14 Using data directory E:\BitCoinData
2016-11-05 08:14:14 Using config file E:\BitCoinData\bitcoin.conf
2016-11-05 08:14:14 Using at most 125 connections (2048 file descriptors available)
2016-11-05 08:14:14 Using 2 threads for script verification
2016-11-05 08:14:14 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-11-05 08:14:14 Using wallet wallet.dat
2016-11-05 08:14:14 scheduler thread start
2016-11-05 08:14:14 init message: Verifiserer lommebok...
2016-11-05 08:14:14 CDBEnv::Open: LogDir=E:\BitCoinData\database ErrorFile=E:\BitCoinData\db.log
2016-11-05 08:14:14 Bound to [::]:8333
2016-11-05 08:14:14 Bound to 0.0.0.0:8333
2016-11-05 08:14:14 Cache configuration:
2016-11-05 08:14:14 * Using 2.0MiB for block index database
2016-11-05 08:14:14 * Using 8.0MiB for chain state database
2016-11-05 08:14:14 * Using 290.0MiB for in-memory UTXO set
2016-11-05 08:14:14 init message: Laster blokkindeks...
2016-11-05 08:14:14 Opening LevelDB in E:\BitCoinData\blocks\index
2016-11-05 08:14:14 Opened LevelDB successfully
2016-11-05 08:14:14 Using obfuscation key for E:\BitCoinData\blocks\index: 0000000000000000
2016-11-05 08:14:14 Opening LevelDB in E:\BitCoinData\chainstate
2016-11-05 08:14:22 Opened LevelDB successfully
2016-11-05 08:14:22 Using obfuscation key for E:\BitCoinData\chainstate: e0c23e443b44f65d
2016-11-05 08:14:34 LoadBlockIndexDB: last block file = 641
2016-11-05 08:14:34 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=103, size=85176170, heights=432731...432948, time=2016-10-03...2016-10-05)
2016-11-05 08:14:34 Checking all blk files are present...
2016-11-05 08:14:47 LoadBlockIndexDB: transaction index disabled
2016-11-05 08:14:48 LoadBlockIndexDB: hashBestChain=0000000000000000013e73c780c7c322a0eda336f094f27b04591795953098d5 height=432877 date=2016-10-04 21:49:48 progress=0.985853
2016-11-05 08:14:48 init message: Rewinding blocks...
2016-11-05 08:14:50 init message: Verifiserer blokker...
2016-11-05 08:14:50 Verifying last 6 blocks at level 3
2016-11-05 08:14:50 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2016-11-05 08:14:57 No coin database inconsistencies in last 7 blocks (12014 transactions)
2016-11-05 08:14:57  block index           43374ms
2016-11-05 08:14:57 init message: Laster lommebok...
2016-11-05 08:14:58 nFileVersion = 130100
2016-11-05 08:14:58 Keys: 0 plaintext, 267 encrypted, 63 w/ metadata, 267 total
2016-11-05 08:14:58  wallet                  705ms
2016-11-05 08:14:58 mapBlockIndex.size() = 437429
2016-11-05 08:14:58 nBestHeight = 432877
2016-11-05 08:14:58 setKeyPool.size() = 100
2016-11-05 08:14:58 mapWallet.size() = 491
2016-11-05 08:14:58 mapAddressBook.size() = 12
2016-11-05 08:14:58 init message: Laster adresser...
2016-11-05 08:14:58 torcontrol thread start
2016-11-05 08:14:58 Loaded 12328 addresses from peers.dat  102ms
2016-11-05 08:14:58 init message: Loading banlist...
2016-11-05 08:14:58 init message: Starting network threads...
2016-11-05 08:14:58 AddLocal([2001:0:9d38:6ab8:2832:372f:a322:8ce1]:8333,1)
2016-11-05 08:14:58 Discover: DESKTOP-KKQMMP0 - 2001:0:9d38:6ab8:2832:372f:a322:8ce1
2016-11-05 08:14:58 dnsseed thread start
2016-11-05 08:14:58 net thread start
2016-11-05 08:14:58 addcon thread start
2016-11-05 08:14:58 opencon thread start
2016-11-05 08:14:58 msghand thread start
2016-11-05 08:14:58 init message: Ferdig med lasting
2016-11-05 08:14:58 GUI: Platform customization: "windows"
2016-11-05 08:14:58 GUI: PaymentServer::LoadRootCAs: Loaded  43  root certificates
2016-11-05 08:15:01 receive version message: /Satoshi:0.13.1/: version 70014, blocks=437431, us=92.221.115.30:62217, peer=1
2016-11-05 08:15:01 receive version message: /Satoshi:0.13.1/: version 70014, blocks=437431, us=92.221.115.30:62219, peer=2
2016-11-05 08:15:02 receive version message: /Satoshi:0.13.1/: version 70014, blocks=437431, us=92.221.115.30:62221, peer=4
2016-11-05 08:15:03 receive version message: /Satoshi:0.13.1/: version 70014, blocks=437431, us=92.221.115.30:62222, peer=5
2016-11-05 08:15:04 receive version message: /Satoshi:0.13.1/: version 70014, blocks=437431, us=92.221.115.30:62224, peer=6
2016-11-05 08:15:04 receive version message: /Satoshi:0.13.1/: version 70014, blocks=437431, us=92.221.115.30:62220, peer=3
2016-11-05 08:15:04 receive version message: /Satoshi:0.13.1/: version 70014, blocks=437431, us=92.221.115.30:62225, peer=7
2016-11-05 08:15:04 Pre-allocating up to position 0x7000000 in blk00641.dat
2016-11-05 08:15:05 receive version message: /Satoshi:0.13.1/: version 70014, blocks=437431, us=92.221.115.30:62226, peer=8
2016-11-05 08:15:06 Pre-allocating up to position 0x8000000 in blk00641.dat
2016-11-05 08:15:08 Leaving block file 641: CBlockFileInfo(blocks=166, size=134175325, heights=432731...433046, time=2016-10-03...2016-10-05)
2016-11-05 08:15:09 P2P peers available. Skipped DNS seeding.
2016-11-05 08:15:09 dnsseed thread exit
2016-11-05 08:15:09 Pre-allocating up to position 0x1000000 in blk00642.dat
2016-11-05 08:15:12 Pre-allocating up to position 0x100000 in rev00642.dat
2016-11-05 08:15:12 UpdateTip: new best=000000000000000000dd6160c3f55894ac03a97f8bc124386c8791f73b8979f0 height=432878 version=0x20000000 log2_work=85.363021 tx=160666615 date='2016-10-04 21:55:22' progress=0.985855 cache=6.1MiB(4688tx)
2016-11-05 08:15:14 Pre-allocating up to position 0x800000 in rev00641.dat
2016-11-05 08:15:14 UpdateTip: new best=00000000000000000451b0075829e3972d0c3221de56a6c2c5b8ed6e70357ce5 height=432879 version=0x20000000 log2_work=85.363051 tx=160667134 date='2016-10-04 21:57:25' progress=0.985855 cache=7.9MiB(8489tx)
2016-11-05 08:15:14 UpdateTip: new best=000000000000000001c39e53f7a20dcad570ce806b7dc29a5bc4469873c57948 height=432880 version=0x20000000 log2_work=85.363081 tx=160667335 date='2016-10-04 21:58:36' progress=0.985856 cache=22.6MiB(9512tx)
2016-11-05 08:15:15 UpdateTip: new best=0000000000000000042c68cfb3a48be38f9ea4273f0da692243e0839a5d93cf6 height=432881 version=0x20000000 log2_work=85.363111 tx=160669526 date='2016-10-04 22:11:32' progress=0.985860 cache=25.2MiB(14872tx)
2016-11-05 08:15:17 UpdateTip: new best=00000000000000000201eff0480024dadd2dd8d459a09d7ed8c856a65c46613e height=432882 version=0x20000000 log2_work=85.363142 tx=160670090 date='2016-10-04 22:13:56' progress=0.985861 cache=33.3MiB(19045tx)
2016-11-05 08:15:18 UpdateTip: new best=000000000000000002efdbec5eff8b787aa44f9ed0592a61a90cab140f21167d height=432883 version=0x20000000 log2_work=85.363172 tx=160671958 date='2016-10-04 22:24:04' progress=0.985864 cache=37.0MiB(22812tx)
2016-11-05 08:15:18 Pre-allocating up to position 0x2000000 in blk00642.dat
2016-11-05 08:15:20 Pre-allocating up to position 0x3000000 in blk00642.dat
2016-11-05 08:15:21 Pre-allocating up to position 0x4000000 in blk00642.dat
2016-11-05 08:15:22 Pre-allocating up to position 0x5000000 in blk00642.dat
2016-11-05 08:15:23 Pre-allocating up to position 0x6000000 in blk00642.dat
2016-11-05 08:15:24 Pre-allocating up to position 0x7000000 in blk00642.dat
2016-11-05 08:15:26 UpdateTip: new best=0000000000000000004f2541c6c4814190bbdf137115a1a5ff2d9d59fce490a4 height=432884 version=0x20000000 log2_work=85.363202 tx=160674857 date='2016-10-04 22:47:11' progress=0.985871 cache=45.3MiB(27837tx)
2016-11-05 08:15:27 UpdateTip: new best=000000000000000000a090c253993270fe976bc6342cbccddfafad53f35ed8b2 height=432885 version=0x20000000 log2_work=85.363232 tx=160677198 date='2016-10-04 22:59:05' progress=0.985875 cache=52.8MiB(32308tx)
2016-11-05 08:15:29 UpdateTip: new best=0000000000000000042704e992de1f01e4f57e3c6ac38b3a5533fad8ab95a7a2 height=432886 version=0x20000000 log2_work=85.363262 tx=160679256 date='2016-10-04 23:09:03' progress=0.985878 cache=61.0MiB(36325tx)
2016-11-05 08:15:30 UpdateTip: new best=0000000000000000028f77654acc17cd4ed522ff90d3371fb1332dc951ae7836 height=432887 version=0x20000000 log2_work=85.363292 tx=160680339 date='2016-10-04 23:14:43' progress=0.985880 cache=68.9MiB(39589tx)
2016-11-05 08:15:31 UpdateTip: new best=0000000000000000029e7fab3a30a667bcde41dd4815a30aff85a6c74427f5d7 height=432888 version=0x20000000 log2_work=85.363322 tx=160683190 date='2016-10-04 23:39:13' progress=0.985888 cache=71.0MiB(43928tx)
2016-11-05 08:15:31 UpdateTip: new best=0000000000000000046e5681c834b21b9994636ac904c9408afa4891209ea695 height=432889 version=0x20000000 log2_work=85.363352 tx=160684129 date='2016-10-04 23:40:27' progress=0.985889 cache=72.1MiB(45950tx)
2016-11-05 08:15:32 Pre-allocating up to position 0x900000 in rev00641.dat
2016-11-05 08:15:32 UpdateTip: new best=000000000000000001b4e19a9dc637567bcd4aa8b565e4f1b59567aaf0039775 height=432890 version=0x20000000 log2_work=85.363382 tx=160685993 date='2016-10-04 23:52:27' progress=0.985893 cache=74.5MiB(49409tx)
2016-11-05 08:15:33 UpdateTip: new best=0000000000000000043df1cfa8167937117f32b54582ca5644a2b08cbf77c2b8 height=432891 version=0x20000000 log2_work=85.363412 tx=160688621 date='2016-10-05 00:11:55' progress=0.985899 cache=77.3MiB(53358tx)
2016-11-05 08:15:35 UpdateTip: new best=00000000000000000390a3b38f4bfdf15cb3528c6050c4c6cd68052f38fe25be height=432892 version=0x20000000 log2_work=85.363442 tx=160689837 date='2016-10-05 00:15:36' progress=0.985900 cache=80.2MiB(56838tx)
2016-11-05 08:15:35 LevelDB read failure: Corruption: block checksum mismatch
2016-11-05 08:15:35 Corruption: block checksum mismatch
2016-11-05 08:15:48 Error reading from database: Database corrupted

[Hanslo]

At last.
After bitcoin-qt stoppet 2 last time, I did'nt start over again.
I restartet my computer I opened Bitcoin Core again (it was 4 weeks back) and it sync to finished.
When starting up with this attemps I closed my Norton Firewall and used instad Windows Defender.
Not sure this was the reason for success. I opened Norton and could find that Bitcoin-Qt.exe was
on exeption. In Windows Defender it was possible also to set the map with BitCoinCore data on exeption,
but I cannot find something similar in Norton Firewall.

Thank you all for trying help me.

[shorena]

At last.
After bitcoin-qt stoppet 2 last time, I did'nt start over again.
I restartet my computer I opened Bitcoin Core again (it was 4 weeks back) and it sync to finished.
When starting up with this attemps I closed my Norton Firewall and used instad Windows Defender.
Not sure this was the reason for success. I opened Norton and could find that Bitcoin-Qt.exe was
on exeption. In Windows Defender it was possible also to set the map with BitCoinCore data on exeption,
but I cannot find something similar in Norton Firewall.

Thank you all for trying help me.

Consider creating a backup copy of the folder once a month so you dont have to resync from scratch every time something like this happens (might very well been norton).

[Hanslo]

At last.
After bitcoin-qt stoppet 2 last time, I did'nt start over again.
I restartet my computer I opened Bitcoin Core again (it was 4 weeks back) and it sync to finished.
When starting up with this attemps I closed my Norton Firewall and used instad Windows Defender.
Not sure this was the reason for success. I opened Norton and could find that Bitcoin-Qt.exe was
on exeption. In Windows Defender it was possible also to set the map with BitCoinCore data on exeption,
but I cannot find something similar in Norton Firewall.

Thank you all for trying help me.

Consider creating a backup copy of the folder once a month so you dont have to resync from scratch every time something like this happens (might very well been norton).

Yes, my wallet.dat backup was 1 year old. But you mean I should creat a backup copy of the hole folder?

[shorena]

At last.
After bitcoin-qt stoppet 2 last time, I did'nt start over again.
I restartet my computer I opened Bitcoin Core again (it was 4 weeks back) and it sync to finished.
When starting up with this attemps I closed my Norton Firewall and used instad Windows Defender.
Not sure this was the reason for success. I opened Norton and could find that Bitcoin-Qt.exe was
on exeption. In Windows Defender it was possible also to set the map with BitCoinCore data on exeption,
but I cannot find something similar in Norton Firewall.

Thank you all for trying help me.

Consider creating a backup copy of the folder once a month so you dont have to resync from scratch every time something like this happens (might very well been norton).

Yes, my wallet.dat backup was 1 year old. But you mean I should creat a backup copy of the hole folder?

Yes, that way you dont have to resync if the database gets corrupted again. You can just restore from the (uncorrupted) copy and sync the rest of the way (e.g. the month).

[Hanslo]

At last.
After bitcoin-qt stoppet 2 last time, I did'nt start over again.
I restartet my computer I opened Bitcoin Core again (it was 4 weeks back) and it sync to finished.
When starting up with this attemps I closed my Norton Firewall and used instad Windows Defender.
Not sure this was the reason for success. I opened Norton and could find that Bitcoin-Qt.exe was
on exeption. In Windows Defender it was possible also to set the map with BitCoinCore data on exeption,
but I cannot find something similar in Norton Firewall.

Thank you all for trying help me.

Consider creating a backup copy of the folder once a month so you dont have to resync from scratch every time something like this happens (might very well been norton).

Yes, my wallet.dat backup was 1 year old. But you mean I should creat a backup copy of the hole folder?

Yes, that way you dont have to resync if the database gets corrupted again. You can just restore from the (uncorrupted) copy and sync the rest of the way (e.g. the month).

Takes some time to copy the folder, 97 GB

[shorena]

-snip-
Yes, that way you dont have to resync if the database gets corrupted again. You can just restore from the (uncorrupted) copy and sync the rest of the way (e.g. the month).

Takes some time to copy the folder, 97 GB

How long did it take you to resync under these conditions? Its 9 days since your first post. Just an idea. Im not doing it myself, but I also never had these problems.

[Hanslo]

-snip-
Yes, that way you dont have to resync if the database gets corrupted again. You can just restore from the (uncorrupted) copy and sync the rest of the way (e.g. the month).

Takes some time to copy the folder, 97 GB

How long did it take you to resync under these conditions? Its 9 days since your first post. Just an idea. Im not doing it myself, but I also never had these problems.

Yes, true, to copy it took only 55 minutts . And the hole shit startet with install of 0.13.1.