Performed a clean install and am currently re-syncing.
I also had to make a clean install after updating from the former version. There must be some sort of backwards incompatibility. 
Topic: Help, Bitcoin Core 0.10.0 crashes on start-up, no error pop-up (Read 2149 times)
I get MinGW Runtime Assertion errors while d/ling the block chain, please see this thread: https://bitcointalksearch.org/topic/mingw-runtime-assertion-error-while-syncing-bitcoin-core-972389
February 28, 2015, 04:08:16 PM
Performed a clean install and am currently re-syncing.
February 27, 2015, 01:49:13 PM
If you have your wallet.dat backed up, I'd completely uninstall Bitcoin Core, delete any associated folders and registry keys, then do a clean install of Bitcoin Core once again and let it index the blocks from block 1 all the way to today.
Do this closer to before you go to bed, so you can let it reindex the blockchain overnight.
Do this closer to before you go to bed, so you can let it reindex the blockchain overnight.
Do you have the private key where you could reinstall and import the key?
I do have my wallet backed up. I was hoping there would be a resolution that did not require me to d/l the entire block chain again. Could I keep the blockchain files and just copy them into the new directory after a clean install?
If you don't want to download the whole chain, believe you can just forego Bitcoin Core for Electrum wallet, which doesn't require the full Blockchain download instead, then import the wallet.dat there.
http://bitcoin.stackexchange.com/questions/25331/how-do-i-load-wallet-dat-on-new-pc-and-import-everything-into-electrum
https://electrum.org/tutorials.html#switching-to-electrum
I don't want to d/l the whole chain again; I want to run/enjoy running a full node, both to support the network and for solo mining.
February 27, 2015, 01:18:40 PM
If you have your wallet.dat backed up, I'd completely uninstall Bitcoin Core, delete any associated folders and registry keys, then do a clean install of Bitcoin Core once again and let it index the blocks from block 1 all the way to today.
Do this closer to before you go to bed, so you can let it reindex the blockchain overnight.
Do this closer to before you go to bed, so you can let it reindex the blockchain overnight.
Do you have the private key where you could reinstall and import the key?
I do have my wallet backed up. I was hoping there would be a resolution that did not require me to d/l the entire block chain again. Could I keep the blockchain files and just copy them into the new directory after a clean install?
If you don't want to download the whole chain, believe you can just forego Bitcoin Core for Electrum wallet, which doesn't require the full Blockchain download instead, then import the wallet.dat there.
http://bitcoin.stackexchange.com/questions/25331/how-do-i-load-wallet-dat-on-new-pc-and-import-everything-into-electrum
https://electrum.org/tutorials.html#switching-to-electrum
February 27, 2015, 01:10:12 PM
If you have your wallet.dat backed up, I'd completely uninstall Bitcoin Core, delete any associated folders and registry keys, then do a clean install of Bitcoin Core once again and let it index the blocks from block 1 all the way to today.
Do this closer to before you go to bed, so you can let it reindex the blockchain overnight.
Do this closer to before you go to bed, so you can let it reindex the blockchain overnight.
Do you have the private key where you could reinstall and import the key?
I do have my wallet backed up. I was hoping there would be a resolution that did not require me to d/l the entire block chain again. Could I keep the blockchain files and just copy them into the new directory after a clean install?
February 27, 2015, 12:50:33 PM
I do not have the ability to go back in time on my computer unfortunately, no back up system of that nature, so that wouldn't help me, but thanks.
Do you have the private key where you could reinstall and import the key?
February 27, 2015, 12:49:46 PM
If you have your wallet.dat backed up, I'd completely uninstall Bitcoin Core, delete any associated folders and registry keys, then do a clean install of Bitcoin Core once again and let it index the blocks from block 1 all the way to today.
Do this closer to before you go to bed, so you can let it reindex the blockchain overnight.
Do this closer to before you go to bed, so you can let it reindex the blockchain overnight.
February 27, 2015, 12:43:45 PM
I do not have the ability to go back in time on my computer unfortunately, no back up system of that nature, so that wouldn't help me, but thanks.
February 27, 2015, 12:26:41 PM
I had a similar problem once and I was only able to solve it by using the "going to previous state" thing, I dont remember the exact term, like going at an older backup from a week ago, then re-installed the client and worked.
February 27, 2015, 12:18:49 PM
I've been running Bitcoin Core 0.10.0 stable for several days, but this morning I woke up to an error window telling me to see debug.log. I've had errors before, and always just restart the program and no problem. Well this time I restarted it and the loading screen comes up and it went through the block verification so fast as if there was no blockchain on my computer, then the program crashed. I repeated the step and same thing, no error window either time. I reinstalled 0.10.0, reset the options, pointed it to my data directory, but it still crashes at the loading window with no error message. Here is a debug log from an attempted start of the program:
Any assistance would be appreciated, cross posting this in the Bitcoin core 0.10.0 release thread, too.
Code:
2015-02-27 14:55:26 Bitcoin version v0.10.0 (2015-02-13 09:55:11 +0100)
2015-02-27 14:55:26 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2015-02-27 14:55:26 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2015-02-27 14:55:26 Default data directory C:\Documents and Settings\Mn\Application Data\Bitcoin
2015-02-27 14:55:26 Using data directory D:\Documents and Settings\Mn\Application Data\Bitcoin
2015-02-27 14:55:26 Using config file D:\Documents and Settings\Mn\Application Data\Bitcoin\bitcoin.conf
2015-02-27 14:55:26 Using at most 125 connections (2048 file descriptors available)
2015-02-27 14:55:26 Using 2 threads for script verification
2015-02-27 14:55:26 Using wallet wallet.dat
2015-02-27 14:55:26 init message: Verifying wallet...
2015-02-27 14:55:26 CDBEnv::Open : LogDir=D:\Documents and Settings\Mn\Application Data\Bitcoin\database ErrorFile=D:\Documents and Settings\Mn\Application Data\Bitcoin\db.log
2015-02-27 14:55:26 Error: Couldn't open socket for incoming connections (socket returned error An address incompatible with the requested protocol was used. (10047))
2015-02-27 14:55:26 Bound to 0.0.0.0:8333
2015-02-27 14:55:26 init message: Loading block index...
2015-02-27 14:55:26 Opening LevelDB in D:\Documents and Settings\Mn\Application Data\Bitcoin\blocks\index
2015-02-27 14:55:26 Opened LevelDB successfully
2015-02-27 14:55:26 Opening LevelDB in D:\Documents and Settings\Mn\Application Data\Bitcoin\chainstate
2015-02-27 14:55:26 Opened LevelDB successfully
2015-02-27 14:55:26 LoadBlockIndexDB: last block file = 0
2015-02-27 14:55:26 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=125316, size=135455381, heights=0...119964, time=2009-01-03...2011-04-24)
2015-02-27 14:55:26 Checking all blk files are present...
2015-02-27 14:55:26 LoadBlockIndexDB(): transaction index disabled
2015-02-27 14:55:26 LoadBlockIndexDB(): hashBestChain=00000000660aaa727ebc610ed069e23abd28f516c614de894e1492994df78edc height=5350 date=2009-02-23 15:53:18 progress=0.000041
2015-02-27 14:55:26 init message: Verifying blocks...
2015-02-27 14:55:26 Verifying last 288 blocks at level 3
2015-02-27 14:55:26 No coin database inconsistencies in last 289 blocks (293 transactions)
2015-02-27 14:55:26 block index 406ms
2015-02-27 14:55:26 init message: Loading wallet...
2015-02-27 14:55:26 nFileVersion = 100000
2015-02-27 14:55:26 Keys: 0 plaintext, 201 encrypted, 201 w/ metadata, 201 total
2015-02-27 14:55:26 wallet 15ms
2015-02-27 14:55:26 Reindexing block file blk00000.dat...
2015-02-27 14:55:26 Block Import: already had block 00000000c937983704a73af28acdec37b049d214adbda81d7e2a3dd146f6ed09 at height 1000
2015-02-27 14:55:26 Block Import: already had block 00000000dfd5d65c9d8561b4b8f60a63018fe3933ecb131fb37f905f87da951a at height 2000
2015-02-27 14:55:26 Block Import: already had block 000000004a81b9aa469b11649996ecb0a452c16d1181e72f9f980850a1c5ecce at height 3000
2015-02-27 14:55:26 Block Import: already had block 00000000922e2aa9e84a474350a3555f49f06061fd49df50a9352f156692a842 at height 4000
2015-02-27 14:55:26 Block Import: already had block 000000004d78d2a8a93a1d20a24d721268690bebd2b51f7e80657d57e226eef9 at height 5000
2015-02-27 14:55:27 UpdateTip: new best=0000000083be2e513d76f87ebdf93310040ecb5ec14556bbe2b635bad65bdbdb height=5351 log2_work=44.385884 tx=5419 date=2009-02-23 15:56:37 progress=0.000041 cache=1
{several more of these entries, deleted to save space}
2015-02-27 14:55:28 UpdateTip: new best=00000000507fcfe6138eaf4ebbb1766337d78bbbda1f5e15fba2c822d77ec01c height=5762 log2_work=44.492626 tx=5830 date=2009-02-27 10:53:38 progress=0.000044 cache=411
2015-02-27 14:55:28 mapBlockIndex.size() = 5764
2015-02-27 14:55:28 nBestHeight = 5762
2015-02-27 14:55:26 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2015-02-27 14:55:26 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2015-02-27 14:55:26 Default data directory C:\Documents and Settings\Mn\Application Data\Bitcoin
2015-02-27 14:55:26 Using data directory D:\Documents and Settings\Mn\Application Data\Bitcoin
2015-02-27 14:55:26 Using config file D:\Documents and Settings\Mn\Application Data\Bitcoin\bitcoin.conf
2015-02-27 14:55:26 Using at most 125 connections (2048 file descriptors available)
2015-02-27 14:55:26 Using 2 threads for script verification
2015-02-27 14:55:26 Using wallet wallet.dat
2015-02-27 14:55:26 init message: Verifying wallet...
2015-02-27 14:55:26 CDBEnv::Open : LogDir=D:\Documents and Settings\Mn\Application Data\Bitcoin\database ErrorFile=D:\Documents and Settings\Mn\Application Data\Bitcoin\db.log
2015-02-27 14:55:26 Error: Couldn't open socket for incoming connections (socket returned error An address incompatible with the requested protocol was used. (10047))
2015-02-27 14:55:26 Bound to 0.0.0.0:8333
2015-02-27 14:55:26 init message: Loading block index...
2015-02-27 14:55:26 Opening LevelDB in D:\Documents and Settings\Mn\Application Data\Bitcoin\blocks\index
2015-02-27 14:55:26 Opened LevelDB successfully
2015-02-27 14:55:26 Opening LevelDB in D:\Documents and Settings\Mn\Application Data\Bitcoin\chainstate
2015-02-27 14:55:26 Opened LevelDB successfully
2015-02-27 14:55:26 LoadBlockIndexDB: last block file = 0
2015-02-27 14:55:26 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=125316, size=135455381, heights=0...119964, time=2009-01-03...2011-04-24)
2015-02-27 14:55:26 Checking all blk files are present...
2015-02-27 14:55:26 LoadBlockIndexDB(): transaction index disabled
2015-02-27 14:55:26 LoadBlockIndexDB(): hashBestChain=00000000660aaa727ebc610ed069e23abd28f516c614de894e1492994df78edc height=5350 date=2009-02-23 15:53:18 progress=0.000041
2015-02-27 14:55:26 init message: Verifying blocks...
2015-02-27 14:55:26 Verifying last 288 blocks at level 3
2015-02-27 14:55:26 No coin database inconsistencies in last 289 blocks (293 transactions)
2015-02-27 14:55:26 block index 406ms
2015-02-27 14:55:26 init message: Loading wallet...
2015-02-27 14:55:26 nFileVersion = 100000
2015-02-27 14:55:26 Keys: 0 plaintext, 201 encrypted, 201 w/ metadata, 201 total
2015-02-27 14:55:26 wallet 15ms
2015-02-27 14:55:26 Reindexing block file blk00000.dat...
2015-02-27 14:55:26 Block Import: already had block 00000000c937983704a73af28acdec37b049d214adbda81d7e2a3dd146f6ed09 at height 1000
2015-02-27 14:55:26 Block Import: already had block 00000000dfd5d65c9d8561b4b8f60a63018fe3933ecb131fb37f905f87da951a at height 2000
2015-02-27 14:55:26 Block Import: already had block 000000004a81b9aa469b11649996ecb0a452c16d1181e72f9f980850a1c5ecce at height 3000
2015-02-27 14:55:26 Block Import: already had block 00000000922e2aa9e84a474350a3555f49f06061fd49df50a9352f156692a842 at height 4000
2015-02-27 14:55:26 Block Import: already had block 000000004d78d2a8a93a1d20a24d721268690bebd2b51f7e80657d57e226eef9 at height 5000
2015-02-27 14:55:27 UpdateTip: new best=0000000083be2e513d76f87ebdf93310040ecb5ec14556bbe2b635bad65bdbdb height=5351 log2_work=44.385884 tx=5419 date=2009-02-23 15:56:37 progress=0.000041 cache=1
{several more of these entries, deleted to save space}
2015-02-27 14:55:28 UpdateTip: new best=00000000507fcfe6138eaf4ebbb1766337d78bbbda1f5e15fba2c822d77ec01c height=5762 log2_work=44.492626 tx=5830 date=2009-02-27 10:53:38 progress=0.000044 cache=411
2015-02-27 14:55:28 mapBlockIndex.size() = 5764
2015-02-27 14:55:28 nBestHeight = 5762
Any assistance would be appreciated, cross posting this in the Bitcoin core 0.10.0 release thread, too.
Jump to: