Error: A fatal internal error ocurred, see debug.log Core v. 0.12 WinX64

[induktor]

Hello
I am having these errors are driving me crazy and i got a lot of bitcoins on this wallet.

the error says:

A Fatal internal error ocurred, see debug.log for details

I can use it but very little time, less than 5 minutes, and i got that message sometimes takes 5 minutes sometimes 1 hour.

The wallet is version 0.12.0 64 bit windows, i am running windows 7 (samsung 840 pro SSD) so far no other problems with the machine, I don't have virus or anything like that, the last section of the log says:

Code:

2016-04-06 01:39:18 tor: Thread interrupt
2016-04-06 01:39:18 opencon thread interrupt
2016-04-06 01:39:18 addcon thread interrupt
2016-04-06 01:39:18 torcontrol thread exit
2016-04-06 01:39:18 scheduler thread interrupt
2016-04-06 01:39:18 msghand thread interrupt
2016-04-06 01:39:18 net thread interrupt
2016-04-06 01:39:18 Shutdown: In progress...
2016-04-06 01:39:18 StopNode()
2016-04-06 01:39:18 Corruption: block checksum mismatch
2016-04-06 01:39:18 *** System error while flushing: Database corrupted
2016-04-06 01:40:02 Shutdown: done

it seems to be something wrong with my copy of the blockchain right? or is it the indexing?
(i hope it is not the wallet, or i will be in trouble!)
how can i fix it? (if it is fixable   )

On top of that i have 1.9 BTC that i was sending when the wallet hanged, and now the wallet says that i send them but the TX is not on the blockchain, wtf!!, is there is any way to push the tx again? or recover the coins?
thanks!
Indkt.

[achow101]

It looks like you have corrupt blocks on the disk. The only way to fix this is to do a full resync, meaning you will be redownloading the entire blockchain. To do this, shutdown Bitcoin Core and go to the bitcoin data directory and delete the "blocks" folder. Then start Bitcoin Core back up and it will do a full resync, which can take several hours.

[induktor]

HUH so it is not a reindexing problem it is a corrupted data block then?

jeez with my ISP it would take a week to download 70 GB !, can i copy the blockchain from another core wallet?
will that work?

do I need to do a --reindex if i do that or it is not necessary?
thank you!

[achow101]

HUH so it is not a reindexing problem it is a corrupted data block then?

jeez with my ISP it would take a week to download 70 GB !, can i copy the blockchain from another core wallet?
will that work?

do I need to do a --reindex if i do that or it is not necessary?
thank you!

Yes, you can copy it from another instance of Bitcoin Core. It won't require a reindex. You will need to copy the blocks, chainstate, and database folders.

[induktor]

Thank you!
doing it right now.

now, what happens with the 1.9 BTC that are not anywhere, they are not in my wallet because the wallet says that it send it, and the tx is not on the blockchain   can I resend the TX manually? or i just have to wait and the wallet will resend it? (if so, how long should i leave the wallet online for that to happen?

thanks!
Indkt.

[achow101]

Thank you!
doing it right now.

now, what happens with the 1.9 BTC that are not anywhere, they are not in my wallet because the wallet says that it send it, and the tx is not on the blockchain   can I resend the TX manually? or i just have to wait and the wallet will resend it? (if so, how long should i leave the wallet online for that to happen?

thanks!
Indkt.

It should periodically rebroadcast the transaction. However, you can just get the raw hex of the transaction and send it yourself. You can right click the transaction in the transactions list and select "Copy Raw Transaction" and then go to Help > Debug window > Console and type into the box

Code:

sendrawtransaction <pasted raw tx>

where <pasted raw tx> is just pasting what you copied there. Then hit enter and it will send.

[induktor]

Genius knightdk!

i used that command to push the tx again and it went through! awesome!

Thank you for taking the time to help a stranger, i really appreciate it!

let me buy you a beer

TxID: 3d64cade3eeaba18ba99bd000c71b48325abfe7aa91ac991f0956e359ff292b8

indkt.