Corruption: block checksum mismatch ? Tried numerous fixes

[PeaMine]

Edit: Fixed, had to restart OS every 30GB or so for some reason, as the block chain eventually gets hung on updating.  Full fresh blockchain download was forced as well.

I had a BSOD on 13.1, Windows 10 64bit Bitcoin Core, display driver issue, not the first time it has happened.
When I tried to run it again, it syncs almost to about a few hours (back when it started) and then would say this error:
https://github.com/bitcoin/bitcoin/issues/6528
I tried a total reindex, dumped my wallet.dat and tried a fresh 14.1 install, but still getting this error in code.
Very odd.
Plenty of free space, no memory errors, modern updated Windows 10 64bit computer.

Code:

2017-06-06 04:32:08 Pre-allocating up to position 0x400000 in rev00253.dat
2017-06-06 04:32:08 UpdateTip: new best=00000000000000000fa971b5ffb1356cda3df57b58d24e148b309c3dbb42806c height=351176 version=0x00000002 log2_work=82.580196 tx=64812943 date='2015-04-07 22:41:08' progress=0.285647 cache=307.2MiB(152765tx)
2017-06-06 04:32:08 UpdateTip: new best=00000000000000000c802f81019bc47dceabe4cbc44595d23f69be34b14b5062 height=351177 version=0x00000003 log2_work=82.580238 tx=64814506 date='2015-04-07 22:59:48' progress=0.285654 cache=307.8MiB(154140tx)
2017-06-06 04:32:08 UpdateTip: new best=000000000000000008768a17383eb782f3cf20201dabe52632fb4a076fd7f117 height=351178 version=0x00000003 log2_work=82.580281 tx=64815111 date='2015-04-07 23:06:45' progress=0.285656 cache=308.0MiB(154526tx)
2017-06-06 04:32:08 UpdateTip: new best=000000000000000003942b65396a674ad467e9db6abd0c86301c00734f6cad3c height=351179 version=0x00000002 log2_work=82.580323 tx=64815840 date='2015-04-07 23:13:24' progress=0.285659 cache=308.8MiB(155062tx)
2017-06-06 04:32:08 UpdateTip: new best=00000000000000000ed0ac62cb58ba42e4275a158500615acf4bd92c888fc04f height=351180 version=0x00000002 log2_work=82.580365 tx=64817405 date='2015-04-07 23:37:07' progress=0.285666 cache=309.1MiB(156342tx)
2017-06-06 04:32:08 UpdateTip: new best=00000000000000000f9e71e350952890e95c9a3e285d127bc5925c757f077c3f height=351181 version=0x00000003 log2_work=82.580408 tx=64817407 date='2015-04-07 23:37:29' progress=0.285666 cache=309.1MiB(156345tx)
2017-06-06 04:32:08 UpdateTip: new best=0000000000000000004eb2ffd61c79d84837804cb6280e6a165f148019764ef3 height=351182 version=0x00000002 log2_work=82.58045 tx=64818449 date='2015-04-07 23:44:36' progress=0.285671 cache=309.5MiB(157207tx)
2017-06-06 04:32:08 UpdateTip: new best=000000000000000000910d55c5ded478ca02159b14691930243bd832b7740e01 height=351183 version=0x00000002 log2_work=82.580493 tx=64819196 date='2015-04-07 23:54:03' progress=0.285674 cache=310.0MiB(157791tx)
2017-06-06 04:32:08 UpdateTip: new best=00000000000000000843ce944e348501709c593c64be9adc41a869294cc1f8e9 height=351184 version=0x00000002 log2_work=82.580535 tx=64819412 date='2015-04-07 23:55:37' progress=0.285675 cache=310.2MiB(157892tx)
2017-06-06 04:32:08 UpdateTip: new best=00000000000000000a8ee45288116badf993fc2629323508c5de18d7dcb130df height=351185 version=0x00000002 log2_work=82.580577 tx=64820092 date='2015-04-08 00:03:53' progress=0.285678 cache=311.2MiB(159070tx)
2017-06-06 04:32:09 UpdateTip: new best=00000000000000000c39cf845bff6cf3e88d1cdf5a731939a331ec85dd27da50 height=351186 version=0x00000002 log2_work=82.58062 tx=64822107 date='2015-04-08 00:34:43' progress=0.285687 cache=314.8MiB(160562tx)
2017-06-06 04:32:09 UpdateTip: new best=0000000000000000142c1e2b3abce5e92bb5f5ce168d11c48ef429772e736485 height=351187 version=0x00000002 log2_work=82.580662 tx=64824267 date='2015-04-08 01:21:20' progress=0.285697 cache=317.1MiB(162732tx)
2017-06-06 04:32:10 Corruption: block checksum mismatch
2017-06-06 04:32:10 *** System error while flushing: Database corrupted
2017-06-06 04:32:24 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-06-06 04:32:25 tor: Thread interrupt
2017-06-06 04:32:25 torcontrol thread exit
2017-06-06 04:32:25 scheduler thread interrupt
2017-06-06 04:32:25 net thread exit
2017-06-06 04:32:25 opencon thread exit
2017-06-06 04:32:25 addcon thread exit
2017-06-06 04:32:25 Shutdown: In progress...
2017-06-06 04:32:25 msghand thread exit
2017-06-06 04:32:25 Dumped mempool: 0s to copy, 0.010048s to dump
2017-06-06 04:32:25 Corruption: block checksum mismatch
2017-06-06 04:32:25 *** System error while flushing: Database corrupted
2017-06-06 04:32:26 Shutdown: done

[achow101]

You have a corrupted block on disk. This means that you will need to resync the entire blockchain. Delete the blocks folder inside of the Bitcoin Core datadir and then start Bitcoin Core and let it sync.

[PeaMine]

You have a corrupted block on disk. This means that you will need to resync the entire blockchain. Delete the blocks folder inside of the Bitcoin Core datadir and then start Bitcoin Core and let it sync.

Thanks, tried 2 fresh installs, on 2 different SSD, and version 13 and 14.1 with new wallets.
For some reason it just stops around April 7th 2015.
Also tried -reindex as well which re-downloaded everything, same issue, total of 5 block chain downloads.

I posted in that one persons thread because it seems to be an issue with the blockchain download, as the wallet version and drive doesn't seem to matter.
Could of course be OS related, so I'm going over that now.

[PeaMine]

I just restarted my computer, then tried to resume it.
It hung for a few seconds on the block it normally crashes on, then made it past it!
It's still going, so perhaps every X blocks, I need to restart when doing a full download?
Not sure.
i7, 16GB of RAM, SSD.

[achow101]

Thanks, tried 2 fresh installs,

Did you delete the blockchain or just uninstall and reinstall? If you only uninstalled and reinstalled, that won't help at all because none of the data is removed from the disk.

on 2 different SSD, and version 13 and 14.1 with new wallets.
For some reason it just stops around April 7th 2015.

If you actually did a full resync where the blockchain actually redownloaded (and reindex does not do this, I'll get to that below), then this error is indicative of hardware failure. In that case, I suggest you run hardware diagnostics to find what is wrong.

Also tried -reindex as well which re-downloaded everything, same issue, total of 5 block chain downloads.

Reindex does not redownloaded anything. All it does is reindex what is already on disk and then it will do the normal catch-up process with whatever blocks that you don't have downloaded. Reindexing is the process of building the databases that have all of the indexes of where to find blocks and transactions. It absolutely does not redownload the blockchain even though it looks like it.

The only way to redownload the blockchain is to actually delete the blocks folder within the datadir and start Bitcoin Core. Nothing else will cause a resync; reindexing, rescanning, reinstalling, etc. will not cause a resync.

I posted in that one persons thread because it seems to be an issue with the blockchain download, as the wallet version and drive doesn't seem to matter.
Could of course be OS related, so I'm going over that now.

His issue was completely unrelated. You clearly did not read the thread.

[PeaMine]

Thanks, tried 2 fresh installs,

Did you delete the blockchain or just uninstall and reinstall? If you only uninstalled and reinstalled, that won't help at all because none of the data is removed from the disk.

on 2 different SSD, and version 13 and 14.1 with new wallets.
For some reason it just stops around April 7th 2015.

If you actually did a full resync where the blockchain actually redownloaded (and reindex does not do this, I'll get to that below), then this error is indicative of hardware failure. In that case, I suggest you run hardware diagnostics to find what is wrong.

Also tried -reindex as well which re-downloaded everything, same issue, total of 5 block chain downloads.

Reindex does not redownloaded anything. All it does is reindex what is already on disk and then it will do the normal catch-up process with whatever blocks that you don't have downloaded. Reindexing is the process of building the databases that have all of the indexes of where to find blocks and transactions. It absolutely does not redownload the blockchain even though it looks like it.

The only way to redownload the blockchain is to actually delete the blocks folder within the datadir and start Bitcoin Core. Nothing else will cause a resync; reindexing, rescanning, reinstalling, etc. will not cause a resync.

I posted in that one persons thread because it seems to be an issue with the blockchain download, as the wallet version and drive doesn't seem to matter.
Could of course be OS related, so I'm going over that now.

His issue was completely unrelated. You clearly did not read the thread.

I'm using the portable version with -datadir, all on a single SSD dedicated entirely to the blockchain, application, and all app data but nothing else.
All data, hidden, application, wallet, appdata, etc, all were fully empty before proceeding.
Manual backup of the wallet.dat and a dump as well.

When I used -reindex, it re-downloaded the entire blockchain, twice.
It prompted an error before re-downloading.

Only solution that fixed it stopping on that one single block, was an OS restart after a proper shutdown of bitcoind.
On my Windows 7 backup system, it never finished downloading the blockchain, same issue as the other person, but indeed, not related to this specific case.
Still, two systems that have worked without issue for Core for over 3 years, same wallet file etc, chances of both messing up at the same time is quite odd.

In regards to the other thread, I experienced the same issue they had on my Windows 7 machine:
No error, no progress, just stuck sometimes.
Other times it will error out with the debug code snip.
https://bitcointalk.org/index.php?topic=1951354.0

So I assumed that since 2 machines went stopped working with Core, on the same day after 3+ years, maybe it was related.
Obviously not though now, as a restart of the OS fixed everything it seems and resumed progress.