Tried uninstalling, removing data dir, and installing a freshly downloaded client.
Fatal error after a few minutes downloading
2015-07-04 01:34:26 UpdateTip: new best=000000000000099724b15ebd8556d0205d5589d860243bd9f48726c460f51658 height=127867 log2_work=63.229977 tx=593966 date=2011-06-01 00:12:33 progress=0.003462 cache=171137
2015-07-04 01:34:26 UpdateTip: new best=0000000000000e4e34b44d6e1fc7fb7bcd8ded69fa5f48dc628c9dde8216b8c3 height=127868 log2_work=63.230226 tx=594011 date=2011-06-01 00:15:53 progress=0.003462 cache=171177
2015-07-04 01:34:26 UpdateTip: new best=00000000000022e426c24cd660316c1259616f55b7239e9b1748408788c44fcc height=127869 log2_work=63.230476 tx=594039 date=2011-06-01 00:27:29 progress=0.003462 cache=171190
2015-07-04 01:34:26 UpdateTip: new best=00000000000025e74442e8711e727429cb6f9c3f0abf11a4e4b22d96fc56b229 height=127870 log2_work=63.230725 tx=594050 date=2011-06-01 00:33:19 progress=0.003462 cache=171194
2015-07-04 01:34:26 UpdateTip: new best=0000000000000dc000ce518d45ebecf26ebdfb40a4ade2c43e33361fd41ec777 height=127871 log2_work=63.230973 tx=594056 date=2011-06-01 00:34:13 progress=0.003462 cache=171196
2015-07-04 01:34:26 UpdateTip: new best=0000000000000e312b15bd1be69622ab20dcc87ddd468307ab8ad411becb242d height=127872 log2_work=63.231222 tx=594089 date=2011-06-01 00:43:10 progress=0.003462 cache=171208
2015-07-04 01:34:26 UpdateTip: new best=00000000000014c8ede8c55c720aceb0c2346f145e817df24b228f23ad445bfe height=127873 log2_work=63.231471 tx=594122 date=2011-06-01 01:05:06 progress=0.003462 cache=171214
2015-07-04 01:34:36 Corruption: block checksum mismatch
2015-07-04 01:34:36 *** System error while flushing: Database corrupted
2015-07-04 01:54:27 socket sending timeout: 1201s
2015-07-04 01:54:27 socket sending timeout: 1201s
2015-07-04 01:54:27 socket sending timeout: 1201s
2015-07-04 01:54:27 socket sending timeout: 1201s
2015-07-04 01:54:27 socket sending timeout: 1201s
2015-07-04 01:54:27 socket sending timeout: 1201s
2015-07-04 01:54:27 socket sending timeout: 1201s
2015-07-04 01:54:27 socket sending timeout: 1201s
2015-07-04 06:45:40 ERROR: ProcessNewBlock : ActivateBestChain failed
2015-07-04 06:45:40 socket send error An operation was attempted on something that is not a socket. (10038)
2015-07-04 06:45:41 dumpaddr thread stop
2015-07-04 06:45:41 opencon thread interrupt
2015-07-04 06:45:41 msghand thread interrupt
2015-07-04 06:45:41 addcon thread interrupt
2015-07-04 06:45:41 net thread interrupt
2015-07-04 06:45:41 Shutdown: In progress...
2015-07-04 06:45:41 StopNode()
2015-07-04 06:45:41 Corruption: block checksum mismatch
2015-07-04 06:45:41 *** System error while flushing: Database corrupted
2015-07-04 06:45:42 Shutdown: done
Anyway, I'm wondering how this corruption happened.
You have bad hardware: either SSD, SATA controller or DRAM memory.
Go get a Bittorrent client and download a bunch of multi-gigabyte files, maybe even the Bitcoin torrent. After download force the recheck of downloaded files multiple times in your Bittorrent client.
If you are moderately knowledgeable Windows user download some big files from Microsoft (e.g. Windows evaluation disk images) and multiple times verify SHA1 checksums that Microsoft supplies.
I'm betting on bad SSD, Bitcoin-Core uses write-ahead-logging databases that are pessimal case for SSD usage: lots of very short writes and no reads of the written logging data, which causes humongous write amplification.
Is any other database engine working correctly on your machine, e.g. MS-SQL or Oracle?
I'm not running the client on an SSD, I'm not crazy
No databases installed on this computer.
HD has healthy smart parameters, and an hdtune error check didn't find any problem on the disk surface.
I'll check for cpu and ram issue, but the system has been pretty rock solid since months, except for this.