Bitcoin Core froze at 99.96%

[Tricky Dicky]

All went good (sync) till 99.96% then it froze ..
I looked at the debug.log, and there are some problems.
Can you help to address them?

Here is the last section of the debug.log:

2021-04-21T12:20:38Z loadblk thread start
2021-04-21T12:20:38Z upnp thread start
2021-04-21T12:20:38Z Bound to [::]:8333
2021-04-21T12:20:38Z Bound to 0.0.0.0:8333
2021-04-21T12:20:38Z Bound to 127.0.0.1:8334
2021-04-21T12:20:38Z init message: Loading P2P addresses...
2021-04-21T12:20:38Z torcontrol thread start
2021-04-21T12:20:38Z Leaving InitialBlockDownload (latching to false)
2021-04-21T12:20:38Z Loaded 65711 addresses from peers.dat  328ms
2021-04-21T12:20:38Z ERROR: DeserializeFileDB: Failed to open file C:\Bitcoin\anchors.dat
2021-04-21T12:20:38Z 0 block-relay-only anchors will be tried for connections.
2021-04-21T12:20:38Z init message: Starting network threads...
2021-04-21T12:20:38Z net thread start
2021-04-21T12:20:38Z dnsseed thread start
2021-04-21T12:20:38Z Waiting 300 seconds before querying DNS seeds.
2021-04-21T12:20:38Z addcon thread start
2021-04-21T12:20:38Z opencon thread start
2021-04-21T12:20:38Z msghand thread start
2021-04-21T12:20:38Z init message: Done loading
2021-04-21T12:20:38Z GUI: Platform customization: "windows"
2021-04-21T12:20:38Z Imported mempool transactions from disk: 13 succeeded, 4711 failed, 4117 expired, 0 already there, 0 waiting for initial broadcast
2021-04-21T12:20:38Z loadblk thread exit
2021-04-21T12:20:40Z New outbound peer connected: version: 70015, blocks=680009, peer=0 (full-relay)
2021-04-21T12:20:40Z No valid UPnP IGDs found
2021-04-21T12:20:40Z upnp thread exit
2021-04-21T12:20:41Z New outbound peer connected: version: 70015, blocks=680010, peer=1 (full-relay)
2021-04-21T12:20:48Z New outbound peer connected: version: 70015, blocks=680010, peer=3 (full-relay)
2021-04-21T12:20:48Z New outbound peer connected: version: 70016, blocks=680010, peer=4 (full-relay)
2021-04-21T12:20:49Z P2P peers available. Skipped DNS seeding.
2021-04-21T12:20:49Z dnsseed thread exit
2021-04-21T12:20:55Z New outbound peer connected: version: 70015, blocks=680010, peer=5 (full-relay)
2021-04-21T12:20:56Z New outbound peer connected: version: 70016, blocks=680010, peer=6 (full-relay)
2021-04-21T12:20:56Z New outbound peer connected: version: 70015, blocks=680010, peer=7 (full-relay)
2021-04-21T12:20:58Z Pre-allocating up to position 0x6000000 in blk02545.dat
2021-04-21T12:21:00Z UpdateTip: new best=0000000000000000000606abd0f162b2810543e958e16e51011a7478121fe7ad height=679936 version=0x20400000 log2_work=92.822271 tx=635561064 date='2021-04-20T18:40:48Z' progress=0.999649 cache=1.4MiB(10411txo)
2021-04-21T12:21:00Z UpdateTip: new best=00000000000000000007b55ff74a0f08fb99eedff7bf94b12db84e196a5c0f9f height=679937 version=0x2fffe000 log2_work=92.822288 tx=635563426 date='2021-04-20T18:55:28Z' progress=0.999654 cache=3.7MiB(27145txo)
2021-04-21T12:21:00Z UpdateTip: new best=00000000000000000006198a87c0fb87fcbf1f9e6c4cbc0ea1e6211e510ded09 height=679938 version=0x2fffe000 log2_work=92.822304 tx=635566200 date='2021-04-20T18:58:45Z' progress=0.999655 cache=5.0MiB(37950txo)
2021-04-21T12:21:01Z LevelDB read failure: Corruption: block checksum mismatch: C:\Bitcoin\chainstate/398969.ldb
2021-04-21T12:21:01Z Fatal LevelDB error: Corruption: block checksum mismatch: C:\Bitcoin\chainstate/398969.ldb
2021-04-21T12:21:01Z You can use -debug=leveldb to get more complete diagnostic messages
2021-04-21T12:21:01Z Error: Error reading from database, shutting down.
2021-04-21T12:40:57Z socket sending timeout: 1201s

[ranochigo]

As the debug.log suggests, there is some corruption with your files.  How did you shut down Bitcoin Core previously? Was it unclean or did you wait until the dialog to disappear?

Unfortunately, you have to build the database again. Try running it with -reindex-chainstate. It would work if your chainstate is corrupted, and is strictly faster than a reindex. If it doesn't work, then you'll have to do a reindex.

[Tricky Dicky]

It was shut down normally, I did wait until the dialog box disappear.
How do you run this command?

bitcoin-qt.exe -reindex-chainstate?

[ranochigo]

How do you run this command?

bitcoin-qt.exe -reindex-chainstate?

Yes.

If you've never had a history of any unclean shutdown, there could also be a slight chance of some hardware failure. You can try checking your RAM (memtest86) and disk (crystaldiskmark) for any bad sectors. Bitcoin Core tends to magnify any insignificant hardware faults as well.