syncing stopped. coinbase pays too much #7301

I run the latest bitcoin core (v0.11.2 64 bit) on my debian and syncing stopped at height 389844. I tried to do what GMaxwell suggested in #6840 : I ran reconsiderblock with that and the follow up block according to some block explorer:

reconsiderblock 0000000000000000068234693e41decd5bfc1b8c5d62cc0aee8a78b398d39cb8 reconsiderblock 00000000000000000842286faa1f37fd609e1374ada25c0aa9c60155cc32425e

and in the debug console it gave me no feedback but in the log I find how these are being considered and rejected with coinbase pays too much (actual=2526435001 vs limit=2526435000)

How do I recover? How can I help you prevent this from happening generally?

2016-01-05 19:10:23 ERROR: ConnectTip(): ConnectBlock 00000000000000000842286faa1f37fd609e1374ada25c0aa9c60155cc32425e failed
2016-01-05 19:10:23 InvalidChainFound: invalid block=00000000000000000842286faa1f37fd609e1374ada25c0aa9c60155cc32425e  height=389845  log2_work=83.788191  date=2015-12-23 16:43:10
2016-01-05 19:10:23 InvalidChainFound:  current best=0000000000000000068234693e41decd5bfc1b8c5d62cc0aee8a78b398d39cb8  height=389844  log2_work=83.788156  date=2015-12-23 16:37:12
2016-01-05 19:11:01 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-01-05 19:11:46 ERROR: ConnectBlock(): **coinbase pays too much** (actual=2526435001 vs limit=2526435000)
2016-01-05 19:11:51 InvalidChainFound: invalid block=00000000000000000842286faa1f37fd609e1374ada25c0aa9c60155cc32425e  height=389845  log2_work=83.788191  date=2015-12-23 16:43:10
2016-01-05 19:11:51 InvalidChainFound:  current best=0000000000000000068234693e41decd5bfc1b8c5d62cc0aee8a78b398d39cb8  height=389844  log2_work=83.788156  date=2015-12-23 16:37:12
2016-01-05 19:11:51 ERROR: ConnectTip(): ConnectBlock 00000000000000000842286faa1f37fd609e1374ada25c0aa9c60155cc32425e failed
2016-01-05 19:11:51 InvalidChainFound: invalid block=00000000000000000842286faa1f37fd609e1374ada25c0aa9c60155cc32425e  height=389845  log2_work=83.788191  date=2015-12-23 16:43:10
2016-01-05 19:11:51 InvalidChainFound:  current best=0000000000000000068234693e41decd5bfc1b8c5d62cc0aee8a78b398d39cb8  height=389844  

That likely means that your UTXO set database is corrupt.

Typically that's the result of a hardware failure with your hard drive.

You will need to run with the -reindex flag set.

@pstratem thank you for your lightning fast reply. Interesting. Will check the disk, too.

The machine is totally not up to the task and on several occasions went into emergency shutdown due to overheating. Which of course also increases chances for disc failure a bit but for now I'll just check things out and assume this was it. So the UTXO set has no integrity check yet? There's talks of putting the UTXO-set hash into the block header, right?

Can you show us the rawblock 00000000000000000842286faa1f37fd609e1374ada25c0aa9c60155cc32425e? E.g.

$ bitcoin-cli getblock 00000000000000000842286faa1f37fd609e1374ada25c0aa9c60155cc32425e false | md5sum 
20a87cbae0f381ebd1adab3de7607191  -

:/ sorry, it's already re-indexing. Gives me an error: "Block not found" in the debug console and with bitcoin-cli "couldn't connect to server".

badblocks and touch /forcefsck did not yield any indications of a bad disk. The ram check found one bad bit in the 8GB in one of 8 runs. Also restarting bitcoin gave me a bad merkel root or so. Three lines of error, 60 times per second, preventing a normal shut down of bitcoin. Only kill -9 did the trick.

The ram check found one bad bit in the 8GB in one of 8 runs.

During initial block synchronization your computer is being pushed to it's limits.

If you found memory errors under zero load then there's going to be LOTS of errors under thermal load.