Unable to sync blockchain on laptop: ERROR: ReadBlockFromDisk: Deserialize or I/O error #29255

issue Xaspr opened this issue on January 16, 2024
  1. Xaspr commented at 6:41 PM on January 16, 2024: none

    Is there an existing issue for this?

    • I have searched the existing issues

    Current behaviour

    After installing Bitcoin Core 26.0 in Windows Pro 11 and starting IBD, Core crashes.

    I know Windows might not be exactly ideal, but I like to run a pruned node on my work laptop as well. I didn't set pruning yet by the way, I started Core just with the standard settings.

    Bitcoin Core crashes and the following error pops up in debug.log:

    ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at FlatFilePos(nFile=327, nPos=8)

    Expected behaviour

    I expect to get to the tip of the chain, but unfortunately the chain gets corrupted every time.

    Steps to reproduce

    There are no settings, no bitcoin.conf file.

    The problem persists after reindexing. It also persists after removing Core and removing the Bitcoin folder in %appdata% and trying a fresh start.

    The disk is an NVMe Samsung 970 Evo Plus 2 TB. I read that the problem should be due to disk corruption. I tried the Samsung Magician program, which did a full scan for a whopping 18 hours, but didn't find any issues. Also tried Minitool Partition Wizard, which found no issues either.

    I thought the problem could be the laptop going into sleep mode. However, after disabling sleep mode, and trying to sync again, I found out this doesn't cause the issue either.

    Relevant log output

    First attempt for which I have debug.log file:

    2024-01-16T11:39:33Z UpdateTip: new best=00000000000000001240f87e370943617c128a8d098b3cad6bd06e4c0927c3fe height=372076 version=0x00000003 log2_work=83.275584 tx=81612997 date='2015-08-29T14:53:41Z' progress=0.085632 cache=115.5MiB(1048378txo)
2024-01-16T11:39:33Z UpdateTip: new best=00000000000000000f8136ee9499e2920b99510bbc0bef7a2dfd95e49a911b99 height=372077 version=0x00000003 log2_work=83.275613 tx=81613437 date='2015-08-29T14:58:17Z' progress=0.085632 cache=115.5MiB(1048327txo)
2024-01-16T11:39:33Z ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at FlatFilePos(nFile=327, nPos=8)
2024-01-16T11:39:33Z *** Failed to read block
2024-01-16T11:39:33Z Error: A fatal internal error occurred, see debug.log for details
2024-01-16T13:01:41Z ERROR: ProcessNewBlock: ActivateBestChain failed (Failed to read block)
2024-01-16T13:01:42Z New outbound-full-relay v1 peer connected: version: 70016, blocks=826027, peer=37
2024-01-16T13:01:42Z Synchronizing blockheaders, height: 826027 (~100.00%)
2024-01-16T13:01:42Z tor: Thread interrupt
2024-01-16T13:01:42Z torcontrol thread exit
2024-01-16T13:01:42Z addcon thread exit
2024-01-16T13:01:42Z opencon thread exit
2024-01-16T13:01:42Z Shutdown: In progress...
2024-01-16T13:01:42Z net thread exit
2024-01-16T13:01:43Z ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at FlatFilePos(nFile=327, nPos=8)
2024-01-16T13:01:43Z *** Failed to read block
2024-01-16T13:01:43Z Error: A fatal internal error occurred, see debug.log for details
2024-01-16T13:01:43Z ERROR: ProcessNewBlock: ActivateBestChain failed (Failed to read block)
2024-01-16T13:01:43Z msghand thread exit
2024-01-16T13:01:43Z DumpAnchors: Flush 0 outbound block-relay-only peer addresses to anchors.dat started
2024-01-16T13:01:43Z DumpAnchors: Flush 0 outbound block-relay-only peer addresses to anchors.dat completed (0.01s)
2024-01-16T13:01:44Z scheduler thread exit
2024-01-16T13:01:44Z Writing 0 unbroadcast transactions to disk.
2024-01-16T13:01:44Z Dumped mempool: 2.8e-05s to copy, 0.01356s to dump
2024-01-16T13:01:44Z Flushed fee estimates to fee_estimates.dat.

    Another attempt from scratch:

    2024-01-16T17:48:48Z UpdateTip: new best=0000000000000000002cf0d7bfe0db7ae76733bd0cfb72ae44db3043d60ef8fc height=385247 version=0x00000003 log2_work=83.646829 tx=94144065 date='2015-11-25T07:28:22Z' progress=0.098767 cache=138.9MiB(1283001txo) 2024-01-16T17:48:48Z ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at FlatFilePos(nFile=380, nPos=8136310) 2024-01-16T17:48:48Z *** Failed to read block 2024-01-16T17:48:48Z Error: A fatal internal error occurred, see debug.log for details

    How did you obtain Bitcoin Core

    Pre-built binaries

    What version of Bitcoin Core are you using?

    v26.0.0

    Operating system and version

    Windows 11 Pro

    Machine specifications

    Asus ExpertBook B5 B5602CBA-MB0220X Intel Core i7-1260P 16 GB DDR5 RAM Added: NVMe Samsung SSD 970 EVO Plus 2TB.

  2. fanquake added the label Windows on Jan 16, 2024
  3. hebasto commented at 7:37 PM on January 16, 2024: member

    Does it happen with the previous versions: 25.1, 24.2?

    Does it happen, when antivirus tools/software are disabled (or the datadir is added to the excluded folders)?

  4. Xaspr commented at 9:36 PM on January 16, 2024: none

    I removed 26.0, installed 24.2 and kept the documents folder. It works well up to now, for about 2 hours already.

    I'll post an update if this goes up to the tip. If it crashes again, I'll try 26.0 with antivirus software disabled.

  5. maflcko added the label Data corruption on Jan 17, 2024
  6. maflcko commented at 8:59 AM on January 17, 2024: member

    Which filesystem is the blocks directory on?

    Otherwise, this may be due to overheating, which will only happen under CPU load, and not if a mere filesystem check tool is run.

  7. Xaspr commented at 9:27 AM on January 17, 2024: none

    The whole SSD is just 1 partition in NTFS. There are no other drives.

    I'll look into overheating as well.

    By the way, v24.2 crashed after about 4 hours. Now looking into trying v26.0.0 with antivirus software disabled.

  8. Xaspr commented at 3:03 PM on January 18, 2024: none

    I had to stop the sync for a while due to traveling and now starting it up again. I'm now at block height 720.000 without issues.

    The CPU temperature is pretty high, with one core going up to a peak of 95 degrees Celsius. Most cores go to max 80 Celsius. screenshot

    What I've tried to get it working up to now:

    • Reinstalled v26.0.0.
    • Deleted antivirus software Bitdefender.
    • Enabled Microsoft Defender, with an exclusion for the %appdata%/Bitcoin folder.
    • Excluded bitcoin-qt for exploit mitigation in HitmanPro.Alert.
    • Added the following lines in bitcoin.conf:
    connect=<<other node on LAN>>
assumevalid=0
dbcache=24000
disablewallet=1

    I'm not sure yet, but I think HitmanPro.Alert caused the issue. In an earlier try, I removed Bitdefender and Core still crashed.

  9. DocBrown101 commented at 6:23 PM on January 18, 2024: none

    I have the same problem on a raspberry pi 64 ...

    ERROR: ReadBlockFromDisk: Deserialize or I/O error - AutoFile::read: fread failed: iostream error at FlatFilePos(nFile=34   ││   80, nPos=63332608)
  10. Xaspr commented at 9:30 AM on January 19, 2024: none

    Core just fully synced with the changes mentioned earlier:

    Reinstalled v26.0.0. Deleted antivirus software Bitdefender. Enabled Microsoft Defender, with an exclusion for the %appdata%/Bitcoin folder. Excluded bitcoin-qt for exploit mitigation in HitmanPro.Alert. Added the following lines in bitcoin.conf: connect=<<other node on LAN>> assumevalid=0 dbcache=24000 disablewallet=1

    The issue wasn't caused by hardware, but must have been caused by antivirus software, most likely HitmanPro.Alert.

  11. Xaspr closed this on Jan 19, 2024
  12. Xaspr commented at 11:13 AM on February 1, 2024: none

    Not sure if related, but I'm still running into issues. I've tried a lot by now, from changing antivirus program, disabling antivirus and anti-malware, checking CPU temperature, checking SSD integrity, updating firmware, updating BIOS, trying older versions of Bitcoin Core and more.

    This specific data corruption error hasn't come up the last few attempts to get to IBD. But often after stopping Core and starting it up again, I get the message that I should reindex. This seems to be a problem with LevelDB not being able to remove files.

    In some cases, after a while, I try to start up Core again, and it just starts without issues.

    But then, the last log of the fail:

    2024-02-01T10:53:21Z Bitcoin Core version v26.0.0 (release build)
2024-02-01T10:53:21Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2024-02-01T10:53:21Z InitParameterInteraction: parameter interaction: -proxy set -> setting -natpmp=0
2024-02-01T10:53:21Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2024-02-01T10:53:21Z InitParameterInteraction: parameter interaction: -onlynet excludes IPv4 and IPv6 -> setting -dnsseed=0
2024-02-01T10:53:21Z Qt 5.15.10 (static), plugin=windows (static)
2024-02-01T10:53:21Z Static plugins:
2024-02-01T10:53:21Z  QWindowsIntegrationPlugin, version 331520
2024-02-01T10:53:21Z  QWindowsVistaStylePlugin, version 331520
2024-02-01T10:53:21Z Style: windowsvista / QWindowsVistaStyle
2024-02-01T10:53:21Z System: Windows 11 Version 2009, x86_64-little_endian-llp64
2024-02-01T10:53:21Z Screen: \\.\DISPLAY1 1280x720, pixel ratio=3.0
2024-02-01T10:53:22Z Using the 'x86_shani(1way,2way)' SHA256 implementation
2024-02-01T10:53:22Z Using RdSeed as an additional entropy source
2024-02-01T10:53:22Z Using RdRand as an additional entropy source
2024-02-01T10:53:22Z [qt] GUI: requestInitialize : Requesting initialize
2024-02-01T10:53:22Z [qt] GUI: Running initialization in thread
2024-02-01T10:53:22Z Default data directory C:\Users\xasp\AppData\Roaming\Bitcoin
2024-02-01T10:53:22Z Using data directory C:\Users\xasp\AppData\Roaming\Bitcoin
2024-02-01T10:53:22Z Config file: C:\Users\xasp\AppData\Roaming\Bitcoin\bitcoin.conf
2024-02-01T10:53:22Z Config file arg: debug="1"
2024-02-01T10:53:22Z Config file arg: listen="1"
2024-02-01T10:53:22Z Config file arg: listenonion="1"
2024-02-01T10:53:22Z Config file arg: onlynet="onion"
2024-02-01T10:53:22Z Config file arg: proxy="127.0.0.1:9050"
2024-02-01T10:53:22Z Config file arg: server="1"
2024-02-01T10:53:22Z Config file arg: torcontrol="127.0.0.1:9051"
2024-02-01T10:53:22Z Config file arg: txindex="1"
2024-02-01T10:53:22Z Setting file arg: lang = "en"
2024-02-01T10:53:22Z Using at most 125 automatic connections (2048 file descriptors available)
2024-02-01T10:53:22Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2024-02-01T10:53:22Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely…"
2024-02-01T10:53:22Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2024-02-01T10:53:22Z Script verification uses 15 additional threads
2024-02-01T10:53:22Z scheduler thread start
2024-02-01T10:53:22Z [http] Allowing HTTP connections from: 127.0.0.0/8 ::1/128 
2024-02-01T10:53:22Z Binding RPC on address ::1 port 8332
2024-02-01T10:53:22Z Binding RPC on address 127.0.0.1 port 8332
2024-02-01T10:53:22Z [http] Initialized HTTP server
2024-02-01T10:53:22Z [http] creating work queue of depth 16
2024-02-01T10:53:22Z [rpc] Starting RPC
2024-02-01T10:53:22Z [rpc] Starting HTTP RPC server
2024-02-01T10:53:22Z Using random cookie authentication.
2024-02-01T10:53:22Z Generated RPC authentication cookie C:\Users\xasp\AppData\Roaming\Bitcoin\.cookie
2024-02-01T10:53:22Z [http] Registering HTTP handler for / (exactmatch 1)
2024-02-01T10:53:22Z [http] Registering HTTP handler for /wallet/ (exactmatch 0)
2024-02-01T10:53:22Z [http] Starting HTTP server
2024-02-01T10:53:22Z [http] starting 4 worker threads
2024-02-01T10:53:22Z [http] Entering http event loop
2024-02-01T10:53:22Z Using wallet directory C:\Users\xasp\AppData\Roaming\Bitcoin
2024-02-01T10:53:22Z init message: Verifying wallet(s)…
2024-02-01T10:53:22Z Using /16 prefix for IP bucketing
2024-02-01T10:53:22Z init message: Loading P2P addresses…
2024-02-01T10:53:22Z [addrman] CheckAddrman: new 2174, tried 1, total 2175 started
2024-02-01T10:53:22Z [addrman] CheckAddrman: completed (1.36ms)
2024-02-01T10:53:22Z Loaded 2175 addresses from peers.dat  5ms
2024-02-01T10:53:22Z init message: Loading banlist…
2024-02-01T10:53:22Z [net] Loaded 0 banned node addresses/subnets  0ms
2024-02-01T10:53:22Z [net] setting try another outbound peer=false
2024-02-01T10:53:22Z SetNetworkActive: true
2024-02-01T10:53:22Z C:\Users\xasp\AppData\Roaming\Bitcoin\fee_estimates.dat is not found. Continue anyway.
2024-02-01T10:53:22Z Cache configuration:
2024-02-01T10:53:22Z * Using 2.0 MiB for block index database
2024-02-01T10:53:22Z * Using 56.0 MiB for transaction index database
2024-02-01T10:53:22Z * Using 8.0 MiB for chain state database
2024-02-01T10:53:22Z * Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2024-02-01T10:53:22Z init message: Loading block index…
2024-02-01T10:53:22Z Assuming ancestors of block 00000000000000000001a0a448d6cf2546b06801389cc030b2b18c6491266815 have valid signatures.
2024-02-01T10:53:22Z Setting nMinimumChainWork=000000000000000000000000000000000000000052b2559353df4117b7348b64
2024-02-01T10:53:22Z [leveldb] LevelDB using max_open_files=1000 (default=1000)
2024-02-01T10:53:22Z Opening LevelDB in C:\Users\xasp\AppData\Roaming\Bitcoin\blocks\index
2024-02-01T10:53:22Z [leveldb:debug] Recovering log [#224](/bitcoin-bitcoin/224/)
2024-02-01T10:53:22Z [leveldb:debug] Level-0 table [#232](/bitcoin-bitcoin/232/): started
2024-02-01T10:53:22Z [leveldb:debug] Level-0 table [#232](/bitcoin-bitcoin/232/): 1243 bytes OK
2024-02-01T10:53:22Z [leveldb:debug] Delete type=2 [#162](/bitcoin-bitcoin/162/)
2024-02-01T10:53:22Z [leveldb:debug] Delete type=2 [#163](/bitcoin-bitcoin/163/)
2024-02-01T10:53:22Z [leveldb:debug] Delete type=2 [#164](/bitcoin-bitcoin/164/)
2024-02-01T10:53:22Z [leveldb:debug] Delete type=2 [#165](/bitcoin-bitcoin/165/)
2024-02-01T10:53:22Z [leveldb:debug] Delete type=2 [#166](/bitcoin-bitcoin/166/)
2024-02-01T10:53:22Z [leveldb:debug] Delete type=2 [#167](/bitcoin-bitcoin/167/)
2024-02-01T10:53:22Z [leveldb:debug] Delete type=2 [#223](/bitcoin-bitcoin/223/)
2024-02-01T10:53:22Z [leveldb:debug] Delete type=0 [#224](/bitcoin-bitcoin/224/)
2024-02-01T10:53:22Z [leveldb:debug] Delete type=3 [#222](/bitcoin-bitcoin/222/)
2024-02-01T10:53:22Z Opened LevelDB successfully
2024-02-01T10:53:22Z Using obfuscation key for C:\Users\xasp\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2024-02-01T10:53:23Z [leveldb:debug] Compacting 1@0 + 5@1 files
2024-02-01T10:53:23Z [leveldb:debug] Generated table [#234](/bitcoin-bitcoin/234/)@0: 14791 keys, 2140622 bytes
2024-02-01T10:53:23Z [leveldb:debug] Generated table [#235](/bitcoin-bitcoin/235/)@0: 14790 keys, 2141209 bytes
2024-02-01T10:53:23Z [leveldb:debug] Generated table [#236](/bitcoin-bitcoin/236/)@0: 7758 keys, 1122796 bytes
2024-02-01T10:53:23Z [leveldb:debug] Generated table [#237](/bitcoin-bitcoin/237/)@0: 14790 keys, 2142962 bytes
2024-02-01T10:53:23Z [leveldb:debug] Generated table [#238](/bitcoin-bitcoin/238/)@0: 12050 keys, 1746933 bytes
2024-02-01T10:53:23Z [leveldb:debug] Generated table [#239](/bitcoin-bitcoin/239/)@0: 2 keys, 220 bytes
2024-02-01T10:53:23Z [leveldb:debug] Compacted 1@0 + 5@1 files => 9294742 bytes
2024-02-01T10:53:23Z [leveldb:debug] compacted to: files[ 0 6 24 54 0 0 0 ]
2024-02-01T10:53:23Z [leveldb:debug] Delete type=2 [#225](/bitcoin-bitcoin/225/)
2024-02-01T10:53:23Z [leveldb:debug] Delete type=2 [#226](/bitcoin-bitcoin/226/)
2024-02-01T10:53:23Z [leveldb:debug] Delete type=2 [#227](/bitcoin-bitcoin/227/)
2024-02-01T10:53:23Z [leveldb:debug] Delete type=2 [#228](/bitcoin-bitcoin/228/)
2024-02-01T10:53:23Z [leveldb:debug] Delete type=2 [#229](/bitcoin-bitcoin/229/)
2024-02-01T10:53:23Z [leveldb:debug] Delete type=2 [#232](/bitcoin-bitcoin/232/)
2024-02-01T10:53:24Z LoadBlockIndexDB: last block file = 4086
2024-02-01T10:53:24Z [leveldb:debug] Compacting 1@1 + 1@2 files
2024-02-01T10:53:24Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=31, size=53509967, heights=828340...828370, time=2024-02-01...2024-02-01)
2024-02-01T10:53:24Z Checking all blk files are present...
2024-02-01T10:53:24Z [leveldb:debug] Generated table [#240](/bitcoin-bitcoin/240/)@1: 2 keys, 220 bytes
2024-02-01T10:53:24Z [leveldb:debug] Compacted 1@1 + 1@2 files => 220 bytes
2024-02-01T10:53:24Z [leveldb:debug] compacted to: files[ 0 5 24 54 0 0 0 ]
2024-02-01T10:53:24Z [leveldb:debug] Delete type=2 [#230](/bitcoin-bitcoin/230/)
2024-02-01T10:53:24Z [leveldb:debug] Delete type=2 [#239](/bitcoin-bitcoin/239/)
2024-02-01T10:53:26Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2024-02-01T10:53:26Z [leveldb] LevelDB using max_open_files=1000 (default=1000)
2024-02-01T10:53:26Z Opening LevelDB in C:\Users\xasp\AppData\Roaming\Bitcoin\chainstate
2024-02-01T10:53:26Z [leveldb:debug] Recovering log [#107836](/bitcoin-bitcoin/107836/)
2024-02-01T10:53:26Z [leveldb:debug] Level-0 table [#108594](/bitcoin-bitcoin/108594/): started
2024-02-01T10:53:26Z [leveldb:debug] Level-0 table [#108594](/bitcoin-bitcoin/108594/): 4126913 bytes OK
2024-02-01T10:53:26Z [leveldb:debug] Recovering log [#108593](/bitcoin-bitcoin/108593/)
2024-02-01T10:53:26Z [leveldb:debug] Level-0 table [#108595](/bitcoin-bitcoin/108595/): started
2024-02-01T10:53:26Z [leveldb:debug] Level-0 table [#108595](/bitcoin-bitcoin/108595/): 308 bytes OK
2024-02-01T10:53:26Z Fatal LevelDB error: IO error: C:\Users\xasp\AppData\Roaming\Bitcoin\chainstate/108593.dbtmp: Kan het te vervangen bestand niet verwijderen.\x0d

2024-02-01T10:53:26Z You can use -debug=leveldb to get more complete diagnostic messages
2024-02-01T10:53:26Z Fatal LevelDB error: IO error: C:\Users\xasp\AppData\Roaming\Bitcoin\chainstate/108593.dbtmp: Kan het te vervangen bestand niet verwijderen.\x0d

2024-02-01T10:53:26Z : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2024-02-01T10:53:29Z Aborted block database rebuild. Exiting.
2024-02-01T10:53:29Z [qt] GUI: initializeResult : Initialization result:  false
2024-02-01T10:53:29Z [qt] GUI: requestShutdown : Requesting shutdown
2024-02-01T10:53:29Z [rpc] Interrupting RPC
2024-02-01T10:53:29Z [rpc] Stopping RPC
2024-02-01T10:53:29Z [rpc] RPC stopped.
2024-02-01T10:53:29Z [qt] GUI: Running Shutdown in thread
2024-02-01T10:53:29Z [http] Interrupting HTTP server
2024-02-01T10:53:29Z [rpc] Interrupting HTTP RPC server
2024-02-01T10:53:29Z Shutdown: In progress...
2024-02-01T10:53:29Z [rpc] Stopping HTTP RPC server
2024-02-01T10:53:29Z [http] Unregistering HTTP handler for / (exactmatch 1)
2024-02-01T10:53:29Z [http] Unregistering HTTP handler for /wallet/ (exactmatch 0)
2024-02-01T10:53:29Z [http] Stopping HTTP server
2024-02-01T10:53:29Z [http] Waiting for HTTP worker threads to exit
2024-02-01T10:53:29Z [http] Exited http event loop
2024-02-01T10:53:29Z [http] Waiting for HTTP event thread to exit
2024-02-01T10:53:29Z [http] Stopped HTTP server
2024-02-01T10:53:29Z scheduler thread exit
2024-02-01T10:53:29Z [estimatefee] Recorded 0 unconfirmed txs from mempool in 0s
2024-02-01T10:53:29Z Flushed fee estimates to fee_estimates.dat.
2024-02-01T10:53:29Z Shutdown: done
2024-02-01T10:53:29Z [qt] GUI: Shutdown finished
2024-02-01T10:53:29Z [qt] GUI: ~InitExecutor : Stopping thread
2024-02-01T10:53:29Z [qt] GUI: ~InitExecutor : Stopped thread

    Last log of the try a few minutes later. First it fails, then it succeeds to start :

    2024-02-01T10:54:01Z Bitcoin Core version v26.0.0 (release build)
2024-02-01T10:54:01Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2024-02-01T10:54:01Z InitParameterInteraction: parameter interaction: -proxy set -> setting -natpmp=0
2024-02-01T10:54:01Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2024-02-01T10:54:01Z InitParameterInteraction: parameter interaction: -onlynet excludes IPv4 and IPv6 -> setting -dnsseed=0
2024-02-01T10:54:01Z Qt 5.15.10 (static), plugin=windows (static)
2024-02-01T10:54:01Z Static plugins:
2024-02-01T10:54:01Z  QWindowsIntegrationPlugin, version 331520
2024-02-01T10:54:01Z  QWindowsVistaStylePlugin, version 331520
2024-02-01T10:54:01Z Style: windowsvista / QWindowsVistaStyle
2024-02-01T10:54:01Z System: Windows 11 Version 2009, x86_64-little_endian-llp64
2024-02-01T10:54:01Z Screen: \\.\DISPLAY1 1280x720, pixel ratio=3.0
2024-02-01T10:54:02Z Using the 'x86_shani(1way,2way)' SHA256 implementation
2024-02-01T10:54:02Z Using RdSeed as an additional entropy source
2024-02-01T10:54:02Z Using RdRand as an additional entropy source
2024-02-01T10:54:02Z [qt] GUI: requestInitialize : Requesting initialize
2024-02-01T10:54:02Z [qt] GUI: Running initialization in thread
2024-02-01T10:54:02Z Default data directory C:\Users\xasp\AppData\Roaming\Bitcoin
2024-02-01T10:54:02Z Using data directory C:\Users\xasp\AppData\Roaming\Bitcoin
2024-02-01T10:54:02Z Config file: C:\Users\xasp\AppData\Roaming\Bitcoin\bitcoin.conf
2024-02-01T10:54:02Z Config file arg: debug="1"
2024-02-01T10:54:02Z Config file arg: listen="1"
2024-02-01T10:54:02Z Config file arg: listenonion="1"
2024-02-01T10:54:02Z Config file arg: onlynet="onion"
2024-02-01T10:54:02Z Config file arg: proxy="127.0.0.1:9050"
2024-02-01T10:54:02Z Config file arg: server="1"
2024-02-01T10:54:02Z Config file arg: torcontrol="127.0.0.1:9051"
2024-02-01T10:54:02Z Config file arg: txindex="1"
2024-02-01T10:54:02Z Setting file arg: lang = "en"
2024-02-01T10:54:02Z Using at most 125 automatic connections (2048 file descriptors available)
2024-02-01T10:54:02Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2024-02-01T10:54:02Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely…"
2024-02-01T10:54:02Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2024-02-01T10:54:02Z Script verification uses 15 additional threads
2024-02-01T10:54:02Z scheduler thread start
2024-02-01T10:54:02Z [http] Allowing HTTP connections from: 127.0.0.0/8 ::1/128 
2024-02-01T10:54:02Z Binding RPC on address ::1 port 8332
2024-02-01T10:54:02Z Binding RPC on address 127.0.0.1 port 8332
2024-02-01T10:54:02Z [http] Initialized HTTP server
2024-02-01T10:54:02Z [http] creating work queue of depth 16
2024-02-01T10:54:02Z [rpc] Starting RPC
2024-02-01T10:54:02Z [rpc] Starting HTTP RPC server
2024-02-01T10:54:02Z Using random cookie authentication.
2024-02-01T10:54:02Z Generated RPC authentication cookie C:\Users\xasp\AppData\Roaming\Bitcoin\.cookie
2024-02-01T10:54:02Z [http] Registering HTTP handler for / (exactmatch 1)
2024-02-01T10:54:02Z [http] Registering HTTP handler for /wallet/ (exactmatch 0)
2024-02-01T10:54:02Z [http] Starting HTTP server
2024-02-01T10:54:02Z [http] starting 4 worker threads
2024-02-01T10:54:02Z [http] Entering http event loop
2024-02-01T10:54:02Z Using wallet directory C:\Users\xasp\AppData\Roaming\Bitcoin
2024-02-01T10:54:02Z init message: Verifying wallet(s)…
2024-02-01T10:54:02Z Using /16 prefix for IP bucketing
2024-02-01T10:54:02Z init message: Loading P2P addresses…
2024-02-01T10:54:02Z [addrman] CheckAddrman: new 2174, tried 1, total 2175 started
2024-02-01T10:54:02Z [addrman] CheckAddrman: completed (1.42ms)
2024-02-01T10:54:02Z Loaded 2175 addresses from peers.dat  5ms
2024-02-01T10:54:02Z init message: Loading banlist…
2024-02-01T10:54:02Z [net] Loaded 0 banned node addresses/subnets  0ms
2024-02-01T10:54:02Z [net] setting try another outbound peer=false
2024-02-01T10:54:02Z SetNetworkActive: true
2024-02-01T10:54:02Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 48 blocks
2024-02-01T10:54:02Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 12 blocks
2024-02-01T10:54:02Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 1008 blocks
2024-02-01T10:54:02Z Cache configuration:
2024-02-01T10:54:02Z * Using 2.0 MiB for block index database
2024-02-01T10:54:02Z * Using 56.0 MiB for transaction index database
2024-02-01T10:54:02Z * Using 8.0 MiB for chain state database
2024-02-01T10:54:02Z * Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2024-02-01T10:54:02Z init message: Loading block index…
2024-02-01T10:54:02Z Assuming ancestors of block 00000000000000000001a0a448d6cf2546b06801389cc030b2b18c6491266815 have valid signatures.
2024-02-01T10:54:02Z Setting nMinimumChainWork=000000000000000000000000000000000000000052b2559353df4117b7348b64
2024-02-01T10:54:02Z [leveldb] LevelDB using max_open_files=1000 (default=1000)
2024-02-01T10:54:02Z Opening LevelDB in C:\Users\xasp\AppData\Roaming\Bitcoin\blocks\index
2024-02-01T10:54:02Z [leveldb:debug] Recovering log [#233](/bitcoin-bitcoin/233/)
2024-02-01T10:54:02Z [leveldb:debug] Delete type=0 [#233](/bitcoin-bitcoin/233/)
2024-02-01T10:54:02Z [leveldb:debug] Delete type=3 [#231](/bitcoin-bitcoin/231/)
2024-02-01T10:54:02Z Opened LevelDB successfully
2024-02-01T10:54:02Z Using obfuscation key for C:\Users\xasp\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2024-02-01T10:54:04Z LoadBlockIndexDB: last block file = 4086
2024-02-01T10:54:04Z [leveldb:debug] Compacting 1@2 + 1@3 files
2024-02-01T10:54:04Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=31, size=53509967, heights=828340...828370, time=2024-02-01...2024-02-01)
2024-02-01T10:54:04Z Checking all blk files are present...
2024-02-01T10:54:04Z [leveldb:debug] Generated table [#243](/bitcoin-bitcoin/243/)@2: 6167 keys, 466856 bytes
2024-02-01T10:54:04Z [leveldb:debug] Compacted 1@2 + 1@3 files => 466856 bytes
2024-02-01T10:54:04Z [leveldb:debug] compacted to: files[ 0 5 23 54 0 0 0 ]
2024-02-01T10:54:04Z [leveldb:debug] Delete type=2 [#221](/bitcoin-bitcoin/221/)
2024-02-01T10:54:04Z [leveldb:debug] Delete type=2 [#240](/bitcoin-bitcoin/240/)
2024-02-01T10:54:05Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2024-02-01T10:54:05Z [leveldb] LevelDB using max_open_files=1000 (default=1000)
2024-02-01T10:54:05Z Opening LevelDB in C:\Users\xasp\AppData\Roaming\Bitcoin\chainstate
2024-02-01T10:54:05Z [leveldb:debug] Recovering log [#107836](/bitcoin-bitcoin/107836/)
2024-02-01T10:54:06Z [leveldb:debug] Level-0 table [#108594](/bitcoin-bitcoin/108594/): started
2024-02-01T10:54:06Z [leveldb:debug] Level-0 table [#108594](/bitcoin-bitcoin/108594/): 4126913 bytes OK
2024-02-01T10:54:06Z [leveldb:debug] Recovering log [#108593](/bitcoin-bitcoin/108593/)
2024-02-01T10:54:06Z [leveldb:debug] Level-0 table [#108595](/bitcoin-bitcoin/108595/): started
2024-02-01T10:54:06Z [leveldb:debug] Level-0 table [#108595](/bitcoin-bitcoin/108595/): 308 bytes OK
2024-02-01T10:54:06Z [leveldb:debug] Recovering log [#108596](/bitcoin-bitcoin/108596/)
2024-02-01T10:54:06Z Fatal LevelDB error: IO error: C:\Users\xasp\AppData\Roaming\Bitcoin\chainstate/108593.dbtmp: Kan het te vervangen bestand niet verwijderen.\x0d

2024-02-01T10:54:06Z You can use -debug=leveldb to get more complete diagnostic messages
2024-02-01T10:54:06Z Fatal LevelDB error: IO error: C:\Users\xasp\AppData\Roaming\Bitcoin\chainstate/108593.dbtmp: Kan het te vervangen bestand niet verwijderen.\x0d

2024-02-01T10:54:06Z : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2024-02-01T10:54:07Z Aborted block database rebuild. Exiting.
2024-02-01T10:54:07Z [qt] GUI: initializeResult : Initialization result:  false
2024-02-01T10:54:07Z [qt] GUI: requestShutdown : Requesting shutdown
2024-02-01T10:54:07Z [rpc] Interrupting RPC
2024-02-01T10:54:07Z [rpc] Stopping RPC
2024-02-01T10:54:07Z [rpc] RPC stopped.
2024-02-01T10:54:07Z [qt] GUI: Running Shutdown in thread
2024-02-01T10:54:07Z [http] Interrupting HTTP server
2024-02-01T10:54:07Z [rpc] Interrupting HTTP RPC server
2024-02-01T10:54:07Z Shutdown: In progress...
2024-02-01T10:54:07Z [rpc] Stopping HTTP RPC server
2024-02-01T10:54:07Z [http] Unregistering HTTP handler for / (exactmatch 1)
2024-02-01T10:54:07Z [http] Unregistering HTTP handler for /wallet/ (exactmatch 0)
2024-02-01T10:54:07Z [http] Stopping HTTP server
2024-02-01T10:54:07Z [http] Waiting for HTTP worker threads to exit
2024-02-01T10:54:07Z [http] Exited http event loop
2024-02-01T10:54:07Z [http] Waiting for HTTP event thread to exit
2024-02-01T10:54:07Z [http] Stopped HTTP server
2024-02-01T10:54:07Z scheduler thread exit
2024-02-01T10:54:07Z [estimatefee] Recorded 0 unconfirmed txs from mempool in 0s
2024-02-01T10:54:07Z Flushed fee estimates to fee_estimates.dat.
2024-02-01T10:54:07Z Shutdown: done
2024-02-01T10:54:07Z [qt] GUI: Shutdown finished
2024-02-01T10:54:07Z [qt] GUI: ~InitExecutor : Stopping thread
2024-02-01T10:54:07Z [qt] GUI: ~InitExecutor : Stopped thread





2024-02-01T10:59:30Z Bitcoin Core version v26.0.0 (release build)
2024-02-01T10:59:30Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2024-02-01T10:59:30Z InitParameterInteraction: parameter interaction: -proxy set -> setting -natpmp=0
2024-02-01T10:59:30Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2024-02-01T10:59:30Z InitParameterInteraction: parameter interaction: -onlynet excludes IPv4 and IPv6 -> setting -dnsseed=0
2024-02-01T10:59:30Z Qt 5.15.10 (static), plugin=windows (static)
2024-02-01T10:59:30Z Static plugins:
2024-02-01T10:59:30Z  QWindowsIntegrationPlugin, version 331520
2024-02-01T10:59:30Z  QWindowsVistaStylePlugin, version 331520
2024-02-01T10:59:30Z Style: windowsvista / QWindowsVistaStyle
2024-02-01T10:59:30Z System: Windows 11 Version 2009, x86_64-little_endian-llp64
2024-02-01T10:59:30Z Screen: \\.\DISPLAY1 1280x720, pixel ratio=3.0
2024-02-01T10:59:30Z Using the 'x86_shani(1way,2way)' SHA256 implementation
2024-02-01T10:59:30Z Using RdSeed as an additional entropy source
2024-02-01T10:59:30Z Using RdRand as an additional entropy source
2024-02-01T10:59:30Z [qt] GUI: requestInitialize : Requesting initialize
2024-02-01T10:59:30Z [qt] GUI: Running initialization in thread
2024-02-01T10:59:30Z Default data directory C:\Users\xasp\AppData\Roaming\Bitcoin
2024-02-01T10:59:30Z Using data directory C:\Users\xasp\AppData\Roaming\Bitcoin
2024-02-01T10:59:30Z Config file: C:\Users\xasp\AppData\Roaming\Bitcoin\bitcoin.conf
2024-02-01T10:59:30Z Config file arg: debug="1"
2024-02-01T10:59:30Z Config file arg: listen="1"
2024-02-01T10:59:30Z Config file arg: listenonion="1"
2024-02-01T10:59:30Z Config file arg: onlynet="onion"
2024-02-01T10:59:30Z Config file arg: proxy="127.0.0.1:9050"
2024-02-01T10:59:30Z Config file arg: server="1"
2024-02-01T10:59:30Z Config file arg: torcontrol="127.0.0.1:9051"
2024-02-01T10:59:30Z Config file arg: txindex="1"
2024-02-01T10:59:30Z Setting file arg: lang = "en"
2024-02-01T10:59:30Z Using at most 125 automatic connections (2048 file descriptors available)
2024-02-01T10:59:30Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2024-02-01T10:59:30Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely…"
2024-02-01T10:59:30Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2024-02-01T10:59:30Z Script verification uses 15 additional threads
2024-02-01T10:59:30Z scheduler thread start
2024-02-01T10:59:30Z [http] Allowing HTTP connections from: 127.0.0.0/8 ::1/128 
2024-02-01T10:59:30Z Binding RPC on address ::1 port 8332
2024-02-01T10:59:30Z Binding RPC on address 127.0.0.1 port 8332
2024-02-01T10:59:30Z [http] Initialized HTTP server
2024-02-01T10:59:30Z [http] creating work queue of depth 16
2024-02-01T10:59:30Z [rpc] Starting RPC
2024-02-01T10:59:30Z [rpc] Starting HTTP RPC server
2024-02-01T10:59:30Z Using random cookie authentication.
2024-02-01T10:59:30Z Generated RPC authentication cookie C:\Users\xasp\AppData\Roaming\Bitcoin\.cookie
2024-02-01T10:59:30Z [http] Registering HTTP handler for / (exactmatch 1)
2024-02-01T10:59:30Z [http] Registering HTTP handler for /wallet/ (exactmatch 0)
2024-02-01T10:59:30Z [http] Starting HTTP server
2024-02-01T10:59:30Z [http] starting 4 worker threads
2024-02-01T10:59:30Z [http] Entering http event loop
2024-02-01T10:59:30Z Using wallet directory C:\Users\xasp\AppData\Roaming\Bitcoin
2024-02-01T10:59:30Z init message: Verifying wallet(s)…
2024-02-01T10:59:30Z Using /16 prefix for IP bucketing
2024-02-01T10:59:30Z init message: Loading P2P addresses…
2024-02-01T10:59:30Z [addrman] CheckAddrman: new 2174, tried 1, total 2175 started
2024-02-01T10:59:30Z [addrman] CheckAddrman: completed (1.02ms)
2024-02-01T10:59:30Z Loaded 2175 addresses from peers.dat  4ms
2024-02-01T10:59:30Z init message: Loading banlist…
2024-02-01T10:59:30Z [net] Loaded 0 banned node addresses/subnets  0ms
2024-02-01T10:59:30Z [net] setting try another outbound peer=false
2024-02-01T10:59:30Z SetNetworkActive: true
2024-02-01T10:59:30Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 48 blocks
2024-02-01T10:59:30Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 12 blocks
2024-02-01T10:59:30Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 1008 blocks
2024-02-01T10:59:30Z Cache configuration:
2024-02-01T10:59:30Z * Using 2.0 MiB for block index database
2024-02-01T10:59:30Z * Using 56.0 MiB for transaction index database
2024-02-01T10:59:30Z * Using 8.0 MiB for chain state database
2024-02-01T10:59:30Z * Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2024-02-01T10:59:30Z init message: Loading block index…
2024-02-01T10:59:30Z Assuming ancestors of block 00000000000000000001a0a448d6cf2546b06801389cc030b2b18c6491266815 have valid signatures.
2024-02-01T10:59:30Z Setting nMinimumChainWork=000000000000000000000000000000000000000052b2559353df4117b7348b64
2024-02-01T10:59:30Z [leveldb] LevelDB using max_open_files=1000 (default=1000)
2024-02-01T10:59:30Z Opening LevelDB in C:\Users\xasp\AppData\Roaming\Bitcoin\blocks\index
2024-02-01T10:59:30Z [leveldb:debug] Recovering log [#242](/bitcoin-bitcoin/242/)
2024-02-01T10:59:30Z [leveldb:debug] Delete type=0 [#242](/bitcoin-bitcoin/242/)
2024-02-01T10:59:30Z [leveldb:debug] Delete type=3 [#241](/bitcoin-bitcoin/241/)
2024-02-01T10:59:30Z Opened LevelDB successfully
2024-02-01T10:59:30Z Using obfuscation key for C:\Users\xasp\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2024-02-01T10:59:33Z LoadBlockIndexDB: last block file = 4086
2024-02-01T10:59:33Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=31, size=53509967, heights=828340...828370, time=2024-02-01...2024-02-01)
2024-02-01T10:59:33Z Checking all blk files are present...
2024-02-01T10:59:34Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2024-02-01T10:59:34Z [leveldb] LevelDB using max_open_files=1000 (default=1000)
2024-02-01T10:59:34Z Opening LevelDB in C:\Users\xasp\AppData\Roaming\Bitcoin\chainstate
2024-02-01T10:59:34Z [leveldb:debug] Recovering log [#107836](/bitcoin-bitcoin/107836/)
2024-02-01T10:59:34Z [leveldb:debug] Level-0 table [#108594](/bitcoin-bitcoin/108594/): started
2024-02-01T10:59:34Z [leveldb:debug] Level-0 table [#108594](/bitcoin-bitcoin/108594/): 4126913 bytes OK
2024-02-01T10:59:34Z [leveldb:debug] Recovering log [#108593](/bitcoin-bitcoin/108593/)
2024-02-01T10:59:34Z [leveldb:debug] Level-0 table [#108595](/bitcoin-bitcoin/108595/): started
2024-02-01T10:59:34Z [leveldb:debug] Level-0 table [#108595](/bitcoin-bitcoin/108595/): 308 bytes OK
2024-02-01T10:59:34Z [leveldb:debug] Recovering log [#108596](/bitcoin-bitcoin/108596/)
2024-02-01T10:59:34Z [leveldb:debug] Recovering log [#108597](/bitcoin-bitcoin/108597/)
2024-02-01T10:59:34Z [leveldb:debug] Delete type=0 [#107836](/bitcoin-bitcoin/107836/)
2024-02-01T10:59:34Z [leveldb:debug] Delete type=0 [#108593](/bitcoin-bitcoin/108593/)
2024-02-01T10:59:34Z [leveldb:debug] Delete type=0 [#108596](/bitcoin-bitcoin/108596/)
2024-02-01T10:59:34Z [leveldb:debug] Delete type=0 [#108597](/bitcoin-bitcoin/108597/)
2024-02-01T10:59:34Z [leveldb:debug] Delete type=3 [#107835](/bitcoin-bitcoin/107835/)
2024-02-01T10:59:34Z Opened LevelDB successfully
2024-02-01T10:59:34Z Using obfuscation key for C:\Users\xasp\AppData\Roaming\Bitcoin\chainstate: 78478a1000ecbe10
2024-02-01T10:59:34Z Loaded best chain: hashBestChain=000000000000000000031d97d157fa92796482295ce82a8544a7f534664629b1 height=828370 date=2024-02-01T10:50:50Z progress=0.999997
2024-02-01T10:59:34Z [leveldb] LevelDB using max_open_files=1000 (default=1000)
2024-02-01T10:59:34Z Opening LevelDB in C:\Users\xasp\AppData\Roaming\Bitcoin\chainstate
2024-02-01T10:59:34Z [leveldb:debug] Recovering log [#108598](/bitcoin-bitcoin/108598/)
2024-02-01T10:59:34Z [leveldb:debug] Delete type=0 [#108598](/bitcoin-bitcoin/108598/)
2024-02-01T10:59:34Z [leveldb:debug] Delete type=3 [#108593](/bitcoin-bitcoin/108593/)
2024-02-01T10:59:34Z Opened LevelDB successfully

    It's may still be antivirus software that's persistent in interfering with Core.

  13. Xaspr reopened this on Feb 1, 2024
  14. maflcko commented at 11:20 AM on February 1, 2024: member

    It's may still be antivirus software that's persistent in interfering with Core.

    It would be good to check this. If you have a completely separate machine, you could try to install the "anti"-virus software there and see if the issue happens?

    Other than that, I believe this is a caused by overheating. It may be possible that the CPU itself happens to work under high heat as part of a benchmark or stress test. Also, other hardware components are fine by themselves as part of a benchmark or stress test, as long as they are not overheated. However, other hardware components may fail when the CPU's heat adds on to them during IBD sync?

  15. Xaspr commented at 2:04 PM on February 7, 2024: none

    It would be good to check this. If you have a completely separate machine, you could try to install the "anti"-virus software there and see if the issue happens?

    I don't have another windows machine, so unfortunately I'm not able to check this. I'm not sure if it would do much, because I've now gotten to IBD several times without issues, whereas before when antivirus was still active, the issues came up persistently around block height 350,000-450,000 or so.

    So I didn't get the previous error again (ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at .......). But there's still plenty of issues. Whenever I reboot or stop Core and start it again a few minutes later, a fatal LevelDB IO error pops up, saying it can't delete .dbtmp files.

  16. maflcko commented at 6:10 PM on February 8, 2024: member

    Bitcoin Core makes heavy use of CPU, RAM and disk IO. Hardware defects might only become visible when running Bitcoin Core. You might want to check your hardware for defects.

    • memtest86 to check your RAM
    • to check the CPU behaviour under load, use linpack or Prime95
    • to test your storage device use smartctl or CrystalDiskInfo

    Source: https://bitcoin.stackexchange.com/a/12206

  17. Xaspr commented at 2:38 PM on February 14, 2024: none

    Thank you.

    I did a memtest86 check (the mix option), and a Prime95 stress test for about 24 hours in total. I encountered no issues.

    CrystalDiskInfo has no critical warnings and gives Health Status as Good 99%.

  18. maflcko commented at 10:12 AM on October 8, 2024: member

    It would be good to check this. If you have a completely separate machine, you could try to install the "anti"-virus software there and see if the issue happens?

    I don't have another windows machine, so unfortunately I'm not able to check this. I'm not sure if it would do much, because I've now gotten to IBD several times without issues, whereas before when antivirus was still active, the issues came up persistently around block height 350,000-450,000 or so.

    Bitcoin Core 28.0 was just released with a new option to xor the block files. It would be interesting to check if this makes a difference. Though, the blocksdir must be completely empty on the first start for the xor pattern to be created. See https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-28.0.md#blockstorage

  19. Xaspr commented at 11:23 AM on October 9, 2024: none

    Thanks for the heads up. I'm now doing IBD with 28.0 on the same Windows installation. On earlier versions, the issue came up after a few days. I will check in again after a week if the issue is solved with blocksxor.

  20. Xaspr commented at 11:53 AM on October 9, 2024: none

    No luck I'm afraid. Version 28.0 also hangs after a few hours.

    2024-10-09T11:48:11Z UpdateTip: new best=0000000000000000fee087a31f2c9c00f8a26935bf133a63ae4659bcc671460c height=287693 version=0x00000002 log2_work=76.854021 tx=33605130 date='2014-02-25T05:33:06Z' progress=0.030781 cache=323.7MiB(2627196txo)
2024-10-09T11:48:11Z UpdateTip: new best=0000000000000000db9ac4e9bbd0335f94305fc1f6772f5b39bb7c188f610f3e height=287694 version=0x00000002 log2_work=76.854163 tx=33606248 date='2014-02-25T05:49:15Z' progress=0.030782 cache=323.9MiB(2627489txo)
2024-10-09T11:48:11Z UpdateTip: new best=000000000000000128e48a97041efac0c72a3846aaedaa6ef676aa4d93fb73f6 height=287695 version=0x00000002 log2_work=76.854305 tx=33606473 date='2014-02-25T05:45:55Z' progress=0.030782 cache=323.9MiB(2626805txo)
2024-10-09T11:48:14Z [error] ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at FlatFilePos(nFile=119, nPos=8)
2024-10-09T11:48:14Z [error] A fatal internal error occurred, see debug.log for details: Failed to read block.
2024-10-09T11:48:26Z [error] ProcessNewBlock: ActivateBestChain failed (Failed to read block.)
2024-10-09T11:48:26Z [error] ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at FlatFilePos(nFile=119, nPos=8)
2024-10-09T11:48:26Z [error] A fatal internal error occurred, see debug.log for details: Failed to read block.
  21. maflcko commented at 12:04 PM on October 9, 2024: member

    I presume this is semi-related to the "Anti"-virus software. It is possible that the software adds load on the system, which makes data corruption more likely, due to increased heat production. You could try to limit the power consumption for the machine, or limit the compute that Bitcoin Core consumes and see if it helps. However, I am not sure how to do that on Windows.

  22. Xaspr commented at 2:08 PM on October 9, 2024: none

    Ah yes, I'll look into whether the lower load does anything.

    Just to be complete on what happened. The IBD continued after restarting Core again, but after an eventual third shutdown and restart of Core to test what would happen, the block database was corrupted again.

    2024-10-09T13:52:42Z UpdateTip: new best=00000000000000000878cd8de3dccda91cdcf6ef0e6e8536120c65f487dd0197 height=390296 version=0x00000004 log2_work=83.803743 tx=100238753 date='2015-12-26T14:25:06Z' progress=0.091811 cache=84.2MiB(686486txo)
2024-10-09T13:52:45Z tor: Thread interrupt
2024-10-09T13:52:45Z addcon thread exit
2024-10-09T13:52:45Z Shutdown: In progress...
2024-10-09T13:52:45Z opencon thread exit
2024-10-09T13:52:45Z torcontrol thread exit
2024-10-09T13:52:45Z net thread exit
2024-10-09T13:52:45Z msghand thread exit
2024-10-09T13:52:45Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started
2024-10-09T13:52:45Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.00s)
2024-10-09T13:52:45Z scheduler thread exit
2024-10-09T13:52:45Z Writing 0 mempool transactions to file...
2024-10-09T13:52:45Z Writing 0 unbroadcast transactions to file.
2024-10-09T13:52:45Z Dumped mempool: 0.000s to copy, 0.004s to dump, 27 bytes dumped to file
2024-10-09T13:52:45Z Flushed fee estimates to fee_estimates.dat.
2024-10-09T13:52:46Z Shutdown: done





2024-10-09T13:52:50Z Bitcoin Core version v28.0.0 (release build)
2024-10-09T13:52:50Z Qt 5.15.14 (static), plugin=windows
2024-10-09T13:52:50Z Static plugins:
2024-10-09T13:52:50Z  QWindowsIntegrationPlugin, version 331520
2024-10-09T13:52:50Z  QWindowsVistaStylePlugin, version 331520
2024-10-09T13:52:50Z Style: windowsvista / QWindowsVistaStyle
2024-10-09T13:52:50Z System: Windows 11 Version 2009, x86_64-little_endian-llp64
2024-10-09T13:52:50Z Screen: \\.\DISPLAY1 1280x720, pixel ratio=3.0
2024-10-09T13:52:51Z Script verification uses 15 additional threads
2024-10-09T13:52:51Z Using the 'x86_shani(1way,2way)' SHA256 implementation
2024-10-09T13:52:56Z Using RdSeed as an additional entropy source
2024-10-09T13:52:56Z Using RdRand as an additional entropy source
2024-10-09T13:52:56Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core werd nog niet veilig afgesloten..."
2024-10-09T13:52:56Z Default data directory C:\Users\xxxxxxx\AppData\Local\Bitcoin
2024-10-09T13:52:56Z Using data directory C:\Users\xxxxxxx\AppData\Local\Bitcoin
2024-10-09T13:52:56Z Config file: C:\Users\xxxxxxx\AppData\Local\Bitcoin\bitcoin.conf (not found, skipping)
2024-10-09T13:52:56Z Using at most 125 automatic connections (2048 file descriptors available)
2024-10-09T13:52:56Z scheduler thread start
2024-10-09T13:52:56Z Using wallet directory C:\Users\xxxxxxx\AppData\Local\Bitcoin\wallets
2024-10-09T13:52:56Z init message: Wallet(s) controleren...
2024-10-09T13:52:56Z Using /16 prefix for IP bucketing
2024-10-09T13:52:56Z init message: P2P-adressen laden...
2024-10-09T13:52:56Z Loaded 25019 addresses from peers.dat  50ms
2024-10-09T13:52:56Z init message: Verbanningslijst laden...
2024-10-09T13:52:56Z SetNetworkActive: true
2024-10-09T13:52:56Z Script verification uses 15 additional threads
2024-10-09T13:52:56Z Cache configuration:
2024-10-09T13:52:56Z * Using 2.0 MiB for block index database
2024-10-09T13:52:56Z * Using 8.0 MiB for chain state database
2024-10-09T13:52:56Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2024-10-09T13:52:56Z Using obfuscation key for blocksdir *.dat files (C:\Users\xxxxxxx\AppData\Local\Bitcoin\blocks): '3627471231765da0'
2024-10-09T13:52:56Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2024-10-09T13:52:56Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2024-10-09T13:52:56Z init message: Blokindex laden...
2024-10-09T13:52:56Z Assuming ancestors of block 000000000000000000011c5890365bdbe5d25b97ce0057589acaef4f1a57263f have valid signatures.
2024-10-09T13:52:56Z Setting nMinimumChainWork=000000000000000000000000000000000000000088e186b70e0862c193ec44d6
2024-10-09T13:52:56Z Opening LevelDB in C:\Users\xxxxxxx\AppData\Local\Bitcoin\blocks\index
2024-10-09T13:52:56Z Opened LevelDB successfully
2024-10-09T13:52:56Z Using obfuscation key for C:\Users\xxxxxxx\AppData\Local\Bitcoin\blocks\index: 0000000000000000
2024-10-09T13:53:01Z LoadBlockIndexDB: last block file = 405
2024-10-09T13:53:01Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=196, size=120801576, heights=390028...390913, time=2015-12-25...2015-12-30)
2024-10-09T13:53:01Z Checking all blk files are present...
2024-10-09T13:53:04Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2024-10-09T13:53:04Z Opening LevelDB in C:\Users\xxxxxxx\AppData\Local\Bitcoin\chainstate
2024-10-09T13:53:04Z Opened LevelDB successfully
2024-10-09T13:53:04Z Using obfuscation key for C:\Users\xxxxxxx\AppData\Local\Bitcoin\chainstate: 29b031841c0fff1d
2024-10-09T13:53:05Z Loaded best chain: hashBestChain=00000000000000000878cd8de3dccda91cdcf6ef0e6e8536120c65f487dd0197 height=390296 date=2015-12-26T14:25:06Z progress=0.091811
2024-10-09T13:53:05Z Opening LevelDB in C:\Users\xxxxxxx\AppData\Local\Bitcoin\chainstate
2024-10-09T13:53:05Z Fatal LevelDB error: IO error: C:\Users\xxxxxxx\AppData\Local\Bitcoin\chainstate/019218.dbtmp: Kan het te vervangen bestand niet verwijderen.\x0d

2024-10-09T13:53:05Z You can use -debug=leveldb to get more complete diagnostic messages
2024-10-09T13:53:05Z [error] Fatal LevelDB error: IO error: C:\Users\xxxxxxx\AppData\Local\Bitcoin\chainstate/019218.dbtmp: Kan het te vervangen bestand niet verwijderen.\x0d

2024-10-09T13:53:05Z : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2024-10-09T13:53:11Z [error] Aborted block database rebuild. Exiting.
2024-10-09T13:53:11Z Shutdown: In progress...
2024-10-09T13:53:11Z scheduler thread exit
2024-10-09T13:53:11Z Flushed fee estimates to fee_estimates.dat.
  23. Xaspr commented at 8:50 AM on October 15, 2024: none

    Unfortunately limiting CPU and memory usage in Windows itself and in Project Lasso didn't work. Core still hangs while indexing after a few hours & the blocks are corrupted afterwards. It must be a hardware issue, as no one else experiences this issue.

  24. maflcko commented at 9:59 AM on October 15, 2024: member

    It must be a hardware issue, as no one else experiences this issue.

    Ok, closing for now, but please do provide a comment with more details, if you find anything.

  25. maflcko closed this on Oct 15, 2024
  26. bitcoin locked this on Oct 15, 2025
Contributors
XasprhebastomaflckoDocBrown101
Labels
WindowsData corruption
github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-17 03:13 UTC
This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me