ERROR: ConnectBlock: Consensus::CheckBlock: bad-txnmrklroot, hashMerkleRoot mism

[joondez]

So my Bitcoin Core (v0.15.1 64-bit) is definitely stuck. Screenshot below. Anybody know what I can do? This is what shows in the debug.log:

2017-12-20 15:27:06 ERROR: ConnectTip(): ConnectBlock 00000000000000cb0ec2cbadfb9ce1b7e5909725b959ec3df2cfcaaf1dbe93f6 failed
2017-12-20 15:27:06 ERROR: ConnectBlock: Consensus::CheckBlock: bad-txnmrklroot, hashMerkleRoot mismatch (code 16)
2017-12-20 15:27:06 ERROR: ConnectTip(): ConnectBlock 00000000000000cb0ec2cbadfb9ce1b7e5909725b959ec3df2cfcaaf1dbe93f6 failed
2017-12-20 15:27:06 ERROR: ConnectBlock: Consensus::CheckBlock: bad-txnmrklroot, hashMerkleRoot mismatch (code 16)
2017-12-20 15:27:06 ERROR: ConnectTip(): ConnectBlock 00000000000000cb0ec2cbadfb9ce1b7e5909725b959ec3df2cfcaaf1dbe93f6 failed
2017-12-20 15:27:06 ERROR: ConnectBlock: Consensus::CheckBlock: bad-txnmrklroot, hashMerkleRoot mismatch (code 16)

https://i.imgur.com/qfneoYA.png

I'm running this on a Windows 10 Machine, i5-3570K 3.40 GHz, 16GB RAM, 75 MBps internet

[1715022939]

1715022939

[1715022939]

1715022939

[1715022939]

1715022939

[1715022939]

1715022939

[1715022939]

1715022939

[achow101]

The easiest thing to do would be to completely redownload the entire blockchain (considering that you aren't synced very far, this would not delay you that much). Stop Bitcoin Core and go to the Bitcoin Core data directory and delete the blocks and chainstate folders. Then start Bitcoin Core again.

[joondez]

Aw man. Okay thanks

[joondez]

unfortunately it happened again, this time at 5%

[achow101]

unfortunately it happened again, this time at 5%

Since this is continually happening, this may be a sign of hardware failure. You should run diagnostics on your RAM and hard drive to make sure that there are no errors.

[joondez]

What standard diagnostics tool is regularly used by this forum?

Not sure I have a hardware problem. I've been using this external hard drive to torrent and run other tasks, and have no problems. I can also play video games and utilize my RAM with no issues as well.

[joondez]

I give up. This is impossible. Client doesn't work, can't sync to the blockchain at all.

[AB de Royse777]

Maybe just export private keys and import them another wallet like Electrum?

[achow101]

What standard diagnostics tool is regularly used by this forum?

memtest86

Not sure I have a hardware problem. I've been using this external hard drive to torrent and run other tasks, and have no problems. I can also play video games and utilize my RAM with no issues as well.

Using an external hard drive is not recommended, both for performance reasons and data corruption reasons. USB is generally slower than the internal connection to a hard drive, so the sync will be much slower. Furthermore, we have found that people have had a hard time with syncing to external hard drives as Bitcoin Core will need continuous connection to the drive and any sort of interruption will result in data corruption. Have you tried not using the external drive?

[goddog]

Same problem here, using Bitcoin Core Daemon version v0.16.1rc2
CentOS Linux release 7.4.1708 (Core)
in a virtualbox environment.
(internal hdd no USB)

I will need weeks, or months, to resynchronize from the beginning :-(

Bitcoin Core will need continuous connection to the drive and any sort of interruption will result in data corruption.

this is very bad. something have to be done to prevent a total corruption, I know the best way to have it done is to work on it myself.... I will try, but C my coding skills are not the best.
A workaround can be to backup the blockchain daily... I will try to implement this first.