0.12.0 always crashes.

[Jhanzo]

core 0.12.0 crashes on me every time I start. sometimes I get through the opening but when I exit the program it crashed again. anyone can help?

here's the debug.log

Code:

2016-03-04 21:43:26 Bitcoin version v0.12.0 (2016-02-17 09:40:03 +0100)
2016-03-04 21:43:26 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2016-03-04 21:43:26 GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed
2016-03-04 21:43:27 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2016-03-04 21:43:27 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-03-04 21:43:27 Default data directory C:\Documents and Settings\Admin\Application Data\Bitcoin
2016-03-04 21:43:27 Using data directory K:\Important files\Bitcoin
2016-03-04 21:43:27 Using config file K:\Important files\Bitcoin\bitcoin.conf
2016-03-04 21:43:27 Using at most 125 connections (2048 file descriptors available)
2016-03-04 21:43:27 Using 2 threads for script verification
2016-03-04 21:43:27 Using wallet wallet.dat
2016-03-04 21:43:27 init message: Verifying wallet...
2016-03-04 21:43:27 CDBEnv::Open: LogDir=K:\Important files\Bitcoin\database ErrorFile=K:\Important files\Bitcoin\db.log
2016-03-04 21:43:27 Error: Couldn't open socket for incoming connections (socket returned error An address incompatible with the requested protocol was used.  (10047))
2016-03-04 21:43:27 Bound to 0.0.0.0:8333
2016-03-04 21:43:27 Cache configuration:
2016-03-04 21:43:27 * Using 2.0MiB for block index database
2016-03-04 21:43:27 * Using 32.5MiB for chain state database
2016-03-04 21:43:27 * Using 65.5MiB for in-memory UTXO set
2016-03-04 21:43:27 init message: Loading block index...
2016-03-04 21:43:27 Wiping LevelDB in K:\Important files\Bitcoin\blocks\index
2016-03-04 21:43:27 Opening LevelDB in K:\Important files\Bitcoin\blocks\index
2016-03-04 21:43:27 Opened LevelDB successfully
2016-03-04 21:43:27 Using obfuscation key for K:\Important files\Bitcoin\blocks\index: 0000000000000000
2016-03-04 21:43:27 Wiping LevelDB in K:\Important files\Bitcoin\chainstate
2016-03-04 21:43:27 Opening LevelDB in K:\Important files\Bitcoin\chainstate
2016-03-04 21:43:27 Opened LevelDB successfully
2016-03-04 21:43:27 Wrote new obfuscate key for K:\Important files\Bitcoin\chainstate: 10fbc306f36d757c
2016-03-04 21:43:27 Using obfuscation key for K:\Important files\Bitcoin\chainstate: 10fbc306f36d757c
2016-03-04 21:43:27 Initializing databases...
2016-03-04 21:43:27 init message: Verifying blocks...
2016-03-04 21:43:27  block index              78ms
2016-03-04 21:43:27 init message: Loading wallet...
2016-03-04 21:43:27 nFileVersion = 120000
2016-03-04 21:43:27 Keys: 105 plaintext, 0 encrypted, 105 w/ metadata, 105 total
2016-03-04 21:43:27  wallet                   93ms
2016-03-04 21:43:27 init message: Activating best chain...
2016-03-04 21:43:27 Waiting for genesis block to be imported...
2016-03-04 21:43:27 Reindexing block file blk00000.dat...
2016-03-04 21:43:27 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f  height=0  log2_work=32.000022  tx=1  date=2009-01-03 18:15:05 progress=0.000000  cache=0.0MiB(0tx)
2016-03-04 21:43:27 Pre-allocating up to position 0x100000 in rev00000.dat
2016-03-04 21:43:27 UpdateTip: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048  height=1  log2_work=33.000022  tx=2  date=2009-01-09 02:54:25 progress=0.000000  cache=0.0MiB(1tx)
2016-03-04 21:43:27 UpdateTip: new best=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd  height=2  log2_work=33.584985  tx=3  date=2009-01-09 02:55:44 progress=0.000000  cache=0.0MiB(2tx)
2016-03-04 21:43:27 UpdateTip: new best=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449  height=3  log2_work=34.000022  tx=4  date=2009-01-09 03:02:53 progress=0.000000  cache=0.0MiB(3tx)
2016-03-04 21:43:27 UpdateTip: new best=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485  height=4  log2_work=34.32195  tx=5  date=2009-01-09 03:16:28 progress=0.000000  cache=0.0MiB(4tx)
2016-03-04 21:43:27 UpdateTip: new best=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc  height=5  log2_work=34.584985  tx=6  date=2009-01-09 03:23:48 progress=0.000000  cache=0.0MiB(5tx)
2016-03-04 21:43:27 mapBlockIndex.size() = 7
2016-03-04 21:43:27 nBestHeight = 6
2016-03-04 21:43:27 setKeyPool.size() = 100
2016-03-04 21:43:27 mapWallet.size() = 4
2016-03-04 21:43:27 mapAddressBook.size() = 5
2016-03-04 21:43:27 init message: Loading addresses...
2016-03-04 21:43:27 torcontrol thread start
2016-03-04 21:43:27 ERROR: Read: Failed to open file K:\Important files\Bitcoin\banlist.dat
2016-03-04 21:43:27 Invalid or missing banlist.dat; recreating
2016-03-04 21:43:27 Loaded 879 addresses from peers.dat  31ms

also this time I get this error. this happens sometimes but not always.

bitcoin-qt.exe - Application Error
The instruction at "0x77c33509" referenced memory at "0x00000000". The memory could not be "read".

[1714772007]

1714772007

[1714772007]

1714772007

[1714772007]

1714772007

[Melech]

Code:

2016-03-04 21:43:27 ERROR: Read: Failed to open file K:\Important files\Bitcoin\banlist.dat
2016-03-04 21:43:27 Invalid or missing banlist.dat; recreating

bitcoin-qt.exe - Application Error
The instruction at "0x77c33509" referenced memory at "0x00000000". The memory could not be "read".

Based on the last message in debug.log, I would guess that bitcoin is not able to create the file banlist.dat

Are you running linux?  Does bitcoin have permission to write to this folder? (K:\Important files\Bitcoin\)

[ViperMad]

The "Invalid or missing banlist.dat" is normal in .12.0. If you have never banned anyone, you have no banlist.dat, and regardless of the message, it will not be recreated.

If the message bothers you, just ban someone, then unban them. This will create a banlist.dat, then no more banlist messages.

[Jhanzo]

running XP SP3 (yeah). installed core in an external HD.
I don't think it's the banlist.dat or write permission issues. sometimes I get past the opening and it crashes when I exit or while it's reindexing the blockchain. I even did a complete uninstall using revo uninstaller but it still doesn't work.

[achow101]

also this time I get this error. this happens sometimes but not always.

bitcoin-qt.exe - Application Error
The instruction at "0x77c33509" referenced memory at "0x00000000". The memory could not be "read".

Based on this error I think that you may have a hardware problem with your memory. Maybe try doing a hardware diagnostic and see if it finds any problems

[cr1776]

running XP SP3 (yeah). installed core in an external HD.
I don't think it's the banlist.dat or write permission issues. sometimes I get past the opening and it crashes when I exit or while it's reindexing the blockchain. I even did a complete uninstall using revo uninstaller but it still doesn't work.
...
The instruction at "0x77c33509" referenced memory at "0x00000000". The memory could not be "read".

Following up from knightdk how much memory do you have on the system?  Is this Windows XP Professional or not? A guess is that you are running a 32 bit version of Windows XP and you may just be running out of memory.

[Jhanzo]

ok just finished running every diagnostic tool I can find on hiren boot CD (damn that took long). RAM and CPU are ok. found some error on disks but was quickly fixed. core still crashes.

Following up from knightdk how much memory do you have on the system?  Is this Windows XP Professional or not? A guess is that you are running a 32 bit version of Windows XP and you may just be running out of memory.

professional 32bit, yes. if by memory you mean RAM, my RAM is 2GB and I've tried terminating every unneeded processes before starting core.

I'll try installing older versions and see if they works.

======================================================
version 0.11.1 works. I'll just use this until I find a solution.

[cr1776]

ok just finished running every diagnostic tool I can find on hiren boot CD (damn that took long). RAM and CPU are ok. found some error on disks but was quickly fixed. core still crashes.

Following up from knightdk how much memory do you have on the system?  Is this Windows XP Professional or not? A guess is that you are running a 32 bit version of Windows XP and you may just be running out of memory.

professional 32bit, yes. if by memory you mean RAM, my RAM is 2GB and I've tried terminating every unneeded processes before starting core.

I'll try installing older versions and see if they works.

======================================================
version 0.11.1 works. I'll just use this until I find a solution.

My suspicion is that 2GB RAM (memory) is not nearly enough.  You will likely have better luck with 4GB (or even better, a 64 bit system with even more memory/swap).

Glad 0.11.1 is an interim solution.