Fatal Internal Error when syncing headers (right after startup) #10572

Describe the issue

First Install on new PC. First start. After Syncing 2010 (sometimes it gets to 2011) headers the Message "Fehler: Ein schwerer interner Fehler ist aufgetreten, siehe debug.log für Details." occurs. (In english: "Error: A fatal internal error occured, see debug.log for details) Then the programm closes. The Error is occuring after some synced days again until it occures by startup without syncing. Sometimes it corrupts the database. -reindex doesnt work. It just starts from the beginning and crashes the same time. Any ideas?

Can you reliably reproduce the issue?

Yes.

If so, please list the steps to reproduce below:

1. Start it

Expected behaviour

Downloading Blockchain ?

Actual behaviour

Error, Application closes

Screenshots.

http://imgur.com/a/uWNYu

What version of bitcoin-core are you using?

v0.14.1

Machine specs:

• OS: Win 10 Pro
• CPU: Intel i7-6700
• RAM: 32GB
• Disk size: 2TB (300GB free when i tried it)
• Disk Type (HD/SDD): HDD

Any extra information that might be useful in the debugging process.

One Possible Log: (most likely without admin rights) 2017-06-11 19:37:13 Unable to open file D:\myPath\BitcoinCore\Bitcoin\Data\blocks\rev00000.dat 2017-06-11 19:37:13 ERROR: UndoWriteToDisk: OpenUndoFile failed 2017-06-11 19:37:13 *** Failed to write undo data 2017-06-11 19:42:29 ERROR: ConnectTip(): ConnectBlock 00000000000079d698b1bfc909042b63a1767157321d98edfb2027d9f1357537 failed 2017-06-11 19:42:29 ERROR: ProcessNewBlock: ActivateBestChain failed

Another Possible Log: (most likely with admin rights) 2017-06-11 19:47:30 mapBlockIndex.size() = 124156 2017-06-11 19:47:30 nBestHeight = 112193 2017-06-11 19:47:30 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large at CBlockDiskPos(nFile=0, nPos=91863112) 2017-06-11 19:47:30 *** Failed to read block 2017-06-11 19:47:30 torcontrol thread start 2017-06-11 19:47:30 AddLocal([2001:0:9d38:6abd:2c2e:18a3:a848:ce48]:8333,1) 2017-06-11 19:47:30 Discover: YRIA - 2001:0:9d38:6abd:2c2e:18a3:a848:ce48 2017-06-11 19:47:30 init message: Lade Adressen... 2017-06-11 19:47:30 Loaded 33538 addresses from peers.dat 146ms 2017-06-11 19:47:30 init message: Lade Sperrliste... 2017-06-11 19:47:30 init message: Netzwerk-Threads werden gestartet... 2017-06-11 19:47:30 net thread start 2017-06-11 19:47:30 dnsseed thread start 2017-06-11 19:47:30 init message: Laden abgeschlossen 2017-06-11 19:47:30 addcon thread start 2017-06-11 19:47:30 opencon thread start 2017-06-11 19:47:30 msghand thread start 2017-06-11 19:47:32 Failed to connect best blockImported mempool transactions from disk: 0 successes, 0 failed, 0 expired 2017-06-11 19:47:32 tor: Thread interrupt 2017-06-11 19:47:32 torcontrol thread exit

Looks like a corrupted block file:

2017-06-11 19:47:30 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large at CBlockDiskPos(nFile=0, nPos=91863112)

Simplest solution is probably to re-sync from the scratch.

Well, whatever it is, there is a "work around". Everytime an error occurs, i restart it. When the error occures and the gui does not become visible, i use "-reindex". Looks like this at least works. But 2 days for sync until 2015 is very slow. @fanquake : How would i re-sync from the scratch? Is that the "-reindex"? In case it does not help to resync, what should I backup before, so i can get back to the point im currently achieved with my "work arround".

You might want to check your hardware for defects: Cf. https://bitcoin.stackexchange.com/a/12206

HARDWARE has nothing to do with this, I have the EXACT same issue. It's a complete bullshit, and the application is bugged.