Author

Topic: Bitcoin Core 0.10.2.0 x64 on Win 8.1 crashing (Read 1889 times)

member
Activity: 67
Merit: 10
Stop trying to steal my account, thanks.
Well, probably nobody cares, but I'll update this thread anyway Smiley
After a few days of testing, I came up with the conclusion that the mainboard is faulty.
This was hardware from 2009, so not a great loss, but I really didn't need a new PC.
Anyway, I bought a new motherboard + cpu + memory, and after formatting, updating
and downloading the whole blockchain, everything is working properly.

Thanks to anyone who contributed to this post.
Se you on the moon! Smiley
member
Activity: 67
Merit: 10
Stop trying to steal my account, thanks.
New update: things get complicated...
So, i tested the processor with OCCT for a few hours, no problems and good temps.
Then i proceeded testing the memory with memtest86+... With all 4x2gb dimms the software crashed...
Testing 1 dimm at time works flawlessly. Testing again all of them together crashes again.
Ok, there's something more. Let's boot into windows again...
No way! BSOD, reboot. KERNEL_DATA_INPAGE ERROR.
Systems loads but... all the usb ports are not working. Leds on keyboard are frozen, and the mouse doesn't light up.
What the hell is going on? Let's reboot again... systems loads, no usb.
Let's check in the bios... Keyboard working. Ok, i guess it's a software problem.
Ok, let's try a ps2 keyboard... Frozen, too. Working in bios.
I left the computer turned off for a few hours, went out with friends and came back at home at 2am.
Powered it on... ps2 keyboard working. Why not try usb? Usb working again.
Can't find a significant error in the windows log.
I'm afraid there's something serious going on with the motherboard.
I'll dig the internet for the bsod error, i guess.
member
Activity: 67
Merit: 10
Stop trying to steal my account, thanks.
I'll first try testing cpu and memory.
Then I'll wipe clean the hard drive and do a write test on it.
Thanks everyone for the help. This may take a while, I'll update later.
Cheers!
member
Activity: 67
Merit: 10
Stop trying to steal my account, thanks.
Tried uninstalling, removing data dir, and installing a freshly downloaded client.
Fatal error after a few minutes downloading
Code:
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 Smiley
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.
member
Activity: 67
Merit: 10
Stop trying to steal my account, thanks.
Seriously, this is getting frustrating.
I renamed the old data directory, created a new empty one, and started the client.
It started downloading without problems.
After a few minutes tho...
Code:
2015-07-04 00:27:57 UpdateTip: new best=00000000000004549ccbc2ccd021b21f882835813420d3932b8f610a05983fbd  height=139845  log2_work=65.956962  tx=1222272  date=2011-08-06 12:13:15 progress=0.007124  cache=49910
2015-07-04 00:27:57 UpdateTip: new best=00000000000008245307c26b31ffc1546197e7755684dabcb33da2b1d9b80169  height=139846  log2_work=65.957126  tx=1222343  date=2011-08-06 12:18:10 progress=0.007124  cache=49975
2015-07-04 00:27:57 UpdateTip: new best=00000000000001c6de90647d5f03cd3070991ec93b5bda6c3d235a3dd79e3844  height=139847  log2_work=65.957289  tx=1222410  date=2011-08-06 12:46:39 progress=0.007125  cache=50036
2015-07-04 00:27:57 UpdateTip: new best=0000000000000038501bff79db124e941a8959c5efdb39c2d2041f3c4bd172b3  height=139848  log2_work=65.957452  tx=1222490  date=2011-08-06 13:17:00 progress=0.007125  cache=50124
2015-07-04 00:27:57 LevelDB read failure: Corruption: block checksum mismatch
2015-07-04 00:27:57 Corruption: block checksum mismatch
2015-07-04 00:28:03 Error reading from database: Database corrupted

Anyone?
I'm running out of ideas..
member
Activity: 67
Merit: 10
Stop trying to steal my account, thanks.
Thank you, kind sir Smiley
Guess it's time to start downloading...
legendary
Activity: 2128
Merit: 1068
I'm not running the client on an SSD, I'm not crazy Smiley
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.
I think hdtune only does read test, not the read-modify-write tests.

For CPU & RAM testing the best is "Torture test" in the Mersenne primes search program prime95.exe.

I also forgot the standard Windows database killers: online antivirus needs to be disabled.

Bitcoin-Core during initial synchronization is quite well optimized and really stresses the machine more than 95% of programs we've tested. So your "rock solid" doesn't mean much unless you've run something in the upper 5% of optimization & efficiency.
 
legendary
Activity: 2128
Merit: 1068
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?
staff
Activity: 3374
Merit: 6530
Just writing some code
I'm also running out of ideas. Try reinstalling. Besides that, the only thing I can think of is that your hard drive is failing.
staff
Activity: 3374
Merit: 6530
Just writing some code
Sigh, it's gonna take ages Sad
Care to suggest me a good light client for the windows platform?
I'll move my bitcoins to it once I get back in control of them.

edit: Should I copy over my wallet.dat before or after synchronizing the blockchain data?
I would recommend MultiBit or electrum. I have used multibit before and it is pretty good. I haven't used electrum, but from what I have heard, it is a very nice client.

It doesn't matter when you copy the wallet.dat back, as long as it is there and replaces the one that Bitcoin Core generates.
staff
Activity: 3374
Merit: 6530
Just writing some code
Yeah. Delete the whole directory and redownload the blockchain. It seems like the files containing the raw blocks was corrupted.
staff
Activity: 3374
Merit: 6530
Just writing some code
Your database is corrupted again, so you need to reindex the whole thing. Anytime Bitcoin Core crashes or you terminate it without letting it shutdown properly, you will need to reindex the database. That should fix your problems.
member
Activity: 67
Merit: 10
Stop trying to steal my account, thanks.
...
Jump to: