The database is getting corrupted. This usually indicates some sort of hardware error.
What OS are you using?
Topic: bitcoin-qt wallet crashes twice a month, database corrupted - page 2. (Read 2454 times)
Hello.
i've been having these issues for almost a year, but now it is far more frequent.
before version 0.13.0 happened maybe once every two months, now it's twice a month.
i use bitcoin to work, i need the wallet operational, every time it dies, it means that i cannot use it for nearly 30 hours until the --reindex, rescan finishes!, what is it, the same issue happened with 0.12.0, then 0.13.0 , now with 0.13.1.
here is the log section:
i don't understand why it gets corrupted, my computer works fantastically fine, i have zero problems, i am an IT, i don't use antivirus, i can detect a virus a mile away and remove it without any tool.
i do all kind of heavy work on this machine all the time and never have one single problem, except for the bitcoin wallet that gets corrupted all the time.
specs:
AMD APU A8-7600 on gigabyte F2A88X, 16GB DDR3 1866 kingston black, SSD (boot/bitcoin wallet) Samsung 840 Pro, win 7 64bit.
any idea of what can cause this?, it is not hardware, last crash i even left it overnight doing memory test to see if that was the issue but no, all fine.
i am lost with this issue.
if it is a block that get's corrupted, why do i need to rescan the entire blockchain, if it just can remove and update from the network the damaged block it will be done in minutes, not 30 hours (i can't even imagine how much longer would it take if i used a standard hard drive!).
thanks
sorry for the long post.
indkt.
i've been having these issues for almost a year, but now it is far more frequent.
before version 0.13.0 happened maybe once every two months, now it's twice a month.
i use bitcoin to work, i need the wallet operational, every time it dies, it means that i cannot use it for nearly 30 hours until the --reindex, rescan finishes!, what is it, the same issue happened with 0.12.0, then 0.13.0 , now with 0.13.1.
here is the log section:
Code:
2016-11-16 01:29:48 Corruption: block checksum mismatch
2016-11-16 01:29:48 *** System error while flushing: Database corrupted
2016-11-16 01:29:57 ERROR: ProcessNewBlock: ActivateBestChain failed
2016-11-16 01:29:57 tor: Thread interrupt
2016-11-16 01:29:57 torcontrol thread exit
2016-11-16 01:29:57 msghand thread interrupt
2016-11-16 01:29:57 addcon thread interrupt
2016-11-16 01:29:57 scheduler thread interrupt
2016-11-16 01:29:57 net thread interrupt
2016-11-16 01:29:59 opencon thread interrupt
2016-11-16 01:29:59 Shutdown: In progress...
2016-11-16 01:29:59 StopNode()
2016-11-16 01:29:59 Corruption: block checksum mismatch
2016-11-16 01:29:59 *** System error while flushing: Database corrupted
2016-11-16 01:30:01 Shutdown: done
2016-11-16 01:30:09
2016-11-16 01:29:48 *** System error while flushing: Database corrupted
2016-11-16 01:29:57 ERROR: ProcessNewBlock: ActivateBestChain failed
2016-11-16 01:29:57 tor: Thread interrupt
2016-11-16 01:29:57 torcontrol thread exit
2016-11-16 01:29:57 msghand thread interrupt
2016-11-16 01:29:57 addcon thread interrupt
2016-11-16 01:29:57 scheduler thread interrupt
2016-11-16 01:29:57 net thread interrupt
2016-11-16 01:29:59 opencon thread interrupt
2016-11-16 01:29:59 Shutdown: In progress...
2016-11-16 01:29:59 StopNode()
2016-11-16 01:29:59 Corruption: block checksum mismatch
2016-11-16 01:29:59 *** System error while flushing: Database corrupted
2016-11-16 01:30:01 Shutdown: done
2016-11-16 01:30:09
i don't understand why it gets corrupted, my computer works fantastically fine, i have zero problems, i am an IT, i don't use antivirus, i can detect a virus a mile away and remove it without any tool.
i do all kind of heavy work on this machine all the time and never have one single problem, except for the bitcoin wallet that gets corrupted all the time.
specs:
AMD APU A8-7600 on gigabyte F2A88X, 16GB DDR3 1866 kingston black, SSD (boot/bitcoin wallet) Samsung 840 Pro, win 7 64bit.
any idea of what can cause this?, it is not hardware, last crash i even left it overnight doing memory test to see if that was the issue but no, all fine.
i am lost with this issue.
if it is a block that get's corrupted, why do i need to rescan the entire blockchain, if it just can remove and update from the network the damaged block it will be done in minutes, not 30 hours (i can't even imagine how much longer would it take if i used a standard hard drive!).
thanks
sorry for the long post.
indkt.
Jump to: