Fatal error when installing bitcoin core !

[gabrielPPC]

Hi,
I have have tried to install bitcoin core a few times over the last few days.

Every time I start the process I get through the sync part, which does not show as progress.

When the progress begins to be displayed, usually around the 5% progress I get the following from the debug log;

2024-03-16T01:47:08Z *** Corrupt block found indicating potential hardware failure; shutting down
2024-03-16T01:47:08Z Error: A fatal internal error occurred, see debug.log for details
2024-03-16T01:48:50Z ERROR: ConnectTip: ConnectBlock 000000000000000003f7db5e0b08cf5aa220078f8734d7fbe4041e420ee82832 failed, bad-txnmrklroot, hashMerkleRoot mismatch
2024-03-16T01:48:50Z *** Failed to connect best block (bad-txnmrklroot, hashMerkleRoot mismatch)
2024-03-16T01:48:50Z Error: A fatal internal error occurred, see debug.log for details
2024-03-16T01:48:51Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2024-03-16T01:48:51Z initload thread exit
2024-03-16T01:48:51Z tor: Thread interrupt
2024-03-16T01:48:51Z Shutdown: In progress...
2024-03-16T01:48:51Z torcontrol thread exit
2024-03-16T01:48:51Z opencon thread exit
2024-03-16T01:48:51Z addcon thread exit
2024-03-16T01:48:51Z net thread exit
2024-03-16T01:48:51Z msghand thread exit
2024-03-16T01:48:52Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started
2024-03-16T01:48:52Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.00s)
2024-03-16T01:48:52Z scheduler thread exit
2024-03-16T01:48:52Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T01:48:56Z Shutdown: done





2024-03-16T01:59:24Z Bitcoin Core version v26.0.0 (release build)
2024-03-16T01:59:24Z Qt 5.15.10 (static), plugin=windows (static)
2024-03-16T01:59:24Z Static plugins:
2024-03-16T01:59:24Z  QWindowsIntegrationPlugin, version 331520
2024-03-16T01:59:24Z  QWindowsVistaStylePlugin, version 331520
2024-03-16T01:59:24Z Style: windowsvista / QWindowsVistaStyle
2024-03-16T01:59:24Z System: Windows 10 Version 2009, x86_64-little_endian-llp64
2024-03-16T01:59:24Z Screen: \\.\DISPLAY1 1920x1080, pixel ratio=1.0
2024-03-16T01:59:25Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2024-03-16T01:59:25Z Using RdRand as an additional entropy source
2024-03-16T01:59:25Z Default data directory C:\Users\gabri\AppData\Roaming\Bitcoin
2024-03-16T01:59:25Z Using data directory Z:\gabri
2024-03-16T01:59:25Z Config file: Z:\gabri\bitcoin.conf (not found, skipping)
2024-03-16T01:59:25Z Using at most 125 automatic connections (2048 file descriptors available)
2024-03-16T01:59:25Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core non si è ancora chiuso..."
2024-03-16T01:59:25Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2024-03-16T01:59:25Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2024-03-16T01:59:25Z Script verification uses 3 additional threads
2024-03-16T01:59:25Z scheduler thread start
2024-03-16T01:59:25Z Using wallet directory Z:\gabri
2024-03-16T01:59:25Z init message: Verificando il(i) portafoglio(portafogli)...
2024-03-16T01:59:25Z Using /16 prefix for IP bucketing
2024-03-16T01:59:25Z init message: Caricamento degli indirizzi P2P...
2024-03-16T01:59:25Z Loaded 28460 addresses from peers.dat  144ms
2024-03-16T01:59:25Z init message: Caricando la banlist...
2024-03-16T01:59:25Z SetNetworkActive: true
2024-03-16T01:59:25Z Cache configuration:
2024-03-16T01:59:25Z * Using 2.0 MiB for block index database
2024-03-16T01:59:25Z * Using 8.0 MiB for chain state database
2024-03-16T01:59:25Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2024-03-16T01:59:25Z init message: Caricando l'indice di blocco...
2024-03-16T01:59:25Z Assuming ancestors of block 00000000000000000001a0a448d6cf2546b06801389cc030b2b18c6491266815 have valid signatures.
2024-03-16T01:59:25Z Setting nMinimumChainWork=000000000000000000000000000000000000000052b2559353df4117b7348b64
2024-03-16T01:59:25Z Opening LevelDB in Z:\gabri\blocks\index
2024-03-16T01:59:25Z Opened LevelDB successfully
2024-03-16T01:59:25Z Using obfuscation key for Z:\gabri\blocks\index: 0000000000000000
2024-03-16T01:59:29Z LoadBlockIndexDB: last block file = 265
2024-03-16T01:59:29Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=268, size=102814801, heights=355103...355402, time=2015-05-05...2015-05-07)
2024-03-16T01:59:29Z Checking all blk files are present...
2024-03-16T01:59:30Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2024-03-16T01:59:30Z Opening LevelDB in Z:\gabri\chainstate
2024-03-16T01:59:30Z Opened LevelDB successfully
2024-03-16T01:59:30Z Using obfuscation key for Z:\gabri\chainstate: e8c83a0f50ae856d
2024-03-16T01:59:31Z Loaded best chain: hashBestChain=000000000000000001ac8327c5161e4239157e49252a7a5cb9262a3160085886 height=355204 date=2015-05-06T12:15:23Z progress=0.069102
2024-03-16T01:59:31Z Opening LevelDB in Z:\gabri\chainstate
2024-03-16T01:59:31Z Opened LevelDB successfully
2024-03-16T01:59:31Z Using obfuscation key for Z:\gabri\chainstate: e8c83a0f50ae856d
2024-03-16T01:59:31Z [Chainstate [ibd] @ height 355204 (000000000000000001ac8327c5161e4239157e49252a7a5cb9262a3160085886)] resized coinsdb cache to 8.0 MiB
2024-03-16T01:59:31Z [Chainstate [ibd] @ height 355204 (000000000000000001ac8327c5161e4239157e49252a7a5cb9262a3160085886)] resized coinstip cache to 440.0 MiB
2024-03-16T01:59:31Z init message: Verificando i blocchi...
2024-03-16T01:59:31Z Verifying last 6 blocks at level 3
2024-03-16T01:59:31Z Verification progress: 0%
2024-03-16T01:59:31Z Verification progress: 16%
2024-03-16T01:59:31Z Verification progress: 33%
2024-03-16T01:59:31Z Verification progress: 50%
2024-03-16T01:59:31Z Verification progress: 66%
2024-03-16T01:59:31Z Verification progress: 83%
2024-03-16T01:59:31Z Verification progress: 99%
2024-03-16T01:59:31Z Verification: No coin database inconsistencies in last 6 blocks (7922 transactions)
2024-03-16T01:59:31Z  block index            6352ms
2024-03-16T01:59:31Z Setting NODE_NETWORK on non-prune mode
2024-03-16T01:59:31Z block tree size = 834505
2024-03-16T01:59:31Z nBestHeight = 355204
2024-03-16T01:59:31Z initload thread start
2024-03-16T01:59:31Z torcontrol thread start
2024-03-16T01:59:31Z *** Corrupt block found indicating potential hardware failure; shutting down
2024-03-16T01:59:31Z Error: A fatal internal error occurred, see debug.log for details
2024-03-16T01:59:31Z Bound to 127.0.0.1:8334
2024-03-16T01:59:31Z Bound to [::]:8333
2024-03-16T01:59:31Z Bound to 0.0.0.0:8333
2024-03-16T01:59:31Z Loaded 2 addresses from "anchors.dat"
2024-03-16T01:59:31Z 2 block-relay-only anchors will be tried for connections.
2024-03-16T01:59:31Z init message: L'esecuzione delle threads della rete sta iniziando...
2024-03-16T01:59:31Z net thread start
2024-03-16T01:59:31Z dnsseed thread start
2024-03-16T01:59:31Z addcon thread start
2024-03-16T01:59:31Z Waiting 300 seconds before querying DNS seeds.
2024-03-16T01:59:31Z msghand thread start
2024-03-16T01:59:31Z opencon thread start
2024-03-16T02:04:32Z Loading addresses from DNS seed dnsseed.bluematt.me.
2024-03-16T02:04:32Z Loading addresses from DNS seed seed.bitcoin.sipa.be.
2024-03-16T02:04:32Z Loading addresses from DNS seed dnsseed.bitcoin.dashjr.org.
2024-03-16T02:04:32Z Waiting 300 seconds before querying DNS seeds.
2024-03-16T02:09:33Z Loading addresses from DNS seed seed.bitcoin.jonasschnelli.ch.
2024-03-16T02:09:33Z Loading addresses from DNS seed seed.bitcoin.sprovoost.nl.
2024-03-16T02:09:33Z Loading addresses from DNS seed seed.btc.petertodd.org.
2024-03-16T02:09:33Z Waiting 300 seconds before querying DNS seeds.
2024-03-16T02:14:34Z Loading addresses from DNS seed dnsseed.emzy.de.
2024-03-16T02:14:34Z Loading addresses from DNS seed seed.bitcoinstats.com.
2024-03-16T02:14:34Z Loading addresses from DNS seed seed.bitcoin.wiz.biz.
2024-03-16T02:14:34Z 209 addresses found from DNS seeds
2024-03-16T02:14:34Z dnsseed thread exit
2024-03-16T02:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T03:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T04:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T05:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T06:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T07:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T08:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T09:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T10:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T11:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T12:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T13:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T14:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T15:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T16:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T17:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T18:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T19:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T20:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T21:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T22:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-16T23:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T00:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T01:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T02:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T03:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T04:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T05:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T06:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T07:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T08:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T09:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T10:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T11:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T12:59:25Z Flushed fee estimates to fee_estimates.dat.
2024-03-17T13:59:25Z Flushed fee estimates to fee_estimates.dat.

Any help would be much appreciated.


Thanks
Gabriel

Bitcoin Client Software and Version Number: Bitcoin Core 26.0.0
Operating System: Microsoft Windows 10 Professional (x64) Build 19045.4170
System Hardware Specs: Intel Core i5-3470 with 16 GB RAM and 1958 GB free hard drive space in master boot record MBR.

[1714754351]

1714754351

[1714754351]

1714754351

[achow101]

As the debug.log states, a corrupt block was found on disk, which indicates a potential hardware failure. This could just be a fluke (e.g. a cosmic ray bit flip) and you could try to resolve it by deleting the blocks and chainstate directories so that it will resync from scratch. However, if you do that and continue to have block corruption errors, you probably want to run some diagnostics to check if your hardware is failing.

[promise444c5]

I encountered same error recently and it mostly occurs  when you forcefully shutdown your bitcoin core while it's  writing  the chainstate, that little dialogue box that comes up when you close your bitcoin core or if your sys unexpected shutsdown or a corrupt disk.
If the synchronisation process haven't gone far you should just restart the synchronising process from start just as it has been advised by @achow101, or you could perform re-index but I wouldn't  advise that .
You could just delete the directory  folder files entirely  and run bitcoin core again  if you have a wallet data you could save it to import it without having to create another one or you could just delete the chainstate and index file

[Edt]
You can check:
https://bitcointalk.org/index.php?topic=5484626.msg63643316#msg63643316

https://bitcointalk.org/index.php?topic=5484626.msg63644201#msg63644201

For reindex :
Check Reindex

[Forsyth Jones]

I saw that you are using Windows to run the bitcoin core node, I have suffered with this several times, but after I started using bitcoin core on Linux, I never had this problem again.

As @promise444c5 warned, this happens because you probably forcibly turned off your bitcoin core while it was running, this on Windows corrupts the block files forcing you to download or reindex the blocks from scratch.

The best option, if you continue using Windows, is before turning off the computer, close bitcoin core and wait for the dialog window to disappear, doing this drastically reduces the chances of your database being corrupted (don't worry, regardless of the database failing, your coins will always be safe).

Easiest solution: use bitcoin core on linux.