Quote from: induktor on November 16, 2016, 11:14:11 AM

Quote from: Hanslo on November 16, 2016, 08:19:41 AM

I had a similar problem a couple of times. Now I'm using Norton Firewall after a consultant from Norton helped me to make exception, and 0.13.1 running ok.

But after Windows update I got crash like you. I shut down my computer and startet again. Startet bitcoin-qt wallet and after a couple of minuts it was up and go.

Hi
usually if bitcoin-qt hangup due to a block corruption, it will work again, as long as it does not attempt to access that block, once that detects the fucked up block it will hangup again, so the only solution is to do a --reindex, which takes a very long time, and my main complain is that why, if it detects a damaged block, it does not redownload it, instead, it forces you to do a full disk reindex which is crazy!.

at least with the hyper-mega tip achow101 give me of use the --dbcache=hughememoryusenumber lowered the processing time a lot, but it still takes a long time (and i know my computer is two - three year old machine, i should get at least a 6th gen intel i5 with pci-e M2 SSD, will do as soon as i can get the money for it

that kind of hw is very expensive here in my area

)

the other way is to restore from backup, which i can do, i backup the entire blockchain to a 7z file once a month and keep three copies, but i wanted to find another solution to prevent this or solve it quickly.

3weeks behind... almost done!!

Here is how it looks for me:

Code:

2016-11-11 20:34:20 UpdateTip: new best=000000000000000001542e46acf8bd8901baae7dfa47f44950c48b139c88371a height=438440 version=0x20000000 log2_work=85.529235 tx=169959484 date='2016-11-11 20:15:51' progress=0.999995 cache=126.1MiB(62820tx)
2016-11-11 20:34:21 tor: Thread interrupt
2016-11-11 20:34:21 torcontrol thread exit
2016-11-11 20:34:21 scheduler thread interrupt
2016-11-11 20:34:21 addcon thread interrupt
2016-11-11 20:34:21 net thread interrupt
2016-11-11 20:34:21 opencon thread interrupt
2016-11-11 20:34:21 ProcessMessages: advertising address [2001:0:5ef5:79fd:24ba:1f45:a322:8ce1]:8333
2016-11-11 20:34:21 receive version message: /Satoshi:0.13.1/: version 70014, blocks=438444, us=92.221.115.30:59592, peer=5
2016-11-11 20:34:21 msghand thread interrupt
2016-11-11 20:34:21 Shutdown: In progress...
2016-11-11 20:34:21 StopNode()
2016-11-11 20:34:23 Corruption: block checksum mismatch
2016-11-11 20:34:23 *** System error while flushing: Database corrupted
2016-11-11 20:34:41 Shutdown: done

It did'nt reindex.