Topic: Bitcoin Core crashes when I try to import my encrypted wallet file. Help please! (Read 2436 times)

Got them. Thank you a thousand, Lauda!
/H

Hereby I confirm that I have successfully moved the funds from OP's wallet to my own address as agreed with them via PM. Now I'll wait for you to provide your own address for relocation of remaining funds (3.88xx - 1). Provide me with one (either by posting here or via PM) and I'll finalize this as soon as possible. Please also make a backup or two of the wallet that will be used here.

---

Update: You're very welcome.

If you do send someone your wallet and password, be sure that that person is very trustworthy.

If you would like me to do this, please pm me.

Hello!
It has been a while. I have also tried to take help from a friend, but we are just not so good at this.
So I offer 1 BTC reward if you get my ca 4 coins out. I have a wallet file and I know the password but when I am asked to write my password in BitCoin Core, I get a "MinGW Runtime Assertion". Please see picture and information below.
I will send you the wallet file and password, and then I will just have to hold my thumbs for mankind and hope that someone honest wants to help me here.
All the best, Henric

A legacy version is an old version of the software. However using an older version isn't going to help at all.

Hi. Sorry for late reply. I was traveling.
Maybe a stupid question, but what is the "legacy version"?
BR Henric

Have you used Bitcoin Core for more than 100 TX? If no, you can probably use another computer and install the legacy version of Bitcoin Core to access your coins.

Hello.
Knightdk, you where right.

"2016-03-25 15:13:07 The wallet is probably corrupted: Some keys decrypt but not all"

So I have an encrypted backup wallet file I took 2015-12-20. I know the password. But can not retrieve my coins because I updated the program. Anyone that could help me?

All the best, Henric

Log:

2016-03-25 15:09:28
2016-03-25 15:09:28 Bitcoin version v0.12.0 (2016-02-17 09:40:03 +0100)
2016-03-25 15:09:28 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2016-03-25 15:09:28 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2016-03-25 15:09:30 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2016-03-25 15:09:30 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-03-25 15:09:30 Default data directory C:\Users\Henric\AppData\Roaming\Bitcoin
2016-03-25 15:09:30 Using data directory D:\Program Files\Bitcoin\DB
2016-03-25 15:09:30 Using config file D:\Program Files\Bitcoin\DB\bitcoin.conf
2016-03-25 15:09:30 Using at most 125 connections (2048 file descriptors available)
2016-03-25 15:09:30 Using 4 threads for script verification
2016-03-25 15:09:30 Using wallet wallet.dat
2016-03-25 15:09:30 scheduler thread start
2016-03-25 15:09:30 init message: Verifierar plånboken...
2016-03-25 15:09:30 CDBEnv::Open: LogDir=D:\Program Files\Bitcoin\DB\database ErrorFile=D:\Program Files\Bitcoin\DB\db.log
2016-03-25 15:09:30 Bound to [::]:8333
2016-03-25 15:09:30 Bound to 0.0.0.0:8333
2016-03-25 15:09:30 Cache configuration:
2016-03-25 15:09:30 * Using 2.0MiB for block index database
2016-03-25 15:09:30 * Using 32.5MiB for chain state database
2016-03-25 15:09:30 * Using 65.5MiB for in-memory UTXO set
2016-03-25 15:09:30 init message: Laddar blockindex...
2016-03-25 15:09:30 Opening LevelDB in D:\Program Files\Bitcoin\DB\blocks\index
2016-03-25 15:09:30 Opened LevelDB successfully
2016-03-25 15:09:30 Using obfuscation key for D:\Program Files\Bitcoin\DB\blocks\index: 0000000000000000
2016-03-25 15:09:30 Opening LevelDB in D:\Program Files\Bitcoin\DB\chainstate
2016-03-25 15:09:31 Opened LevelDB successfully
2016-03-25 15:09:31 Using obfuscation key for D:\Program Files\Bitcoin\DB\chainstate: 6431fae68c6f7f2d
2016-03-25 15:09:34 LoadBlockIndexDB: last block file = 476
2016-03-25 15:09:34 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=4, size=3985947, heights=404223...404227, time=2016-03-25...2016-03-25)
2016-03-25 15:09:34 Checking all blk files are present...
2016-03-25 15:09:34 LoadBlockIndexDB: transaction index disabled
2016-03-25 15:09:34 LoadBlockIndexDB: hashBestChain=000000000000000001edea1a2cfb9a1f8da41622620a6768fc153890186c5c29 height=404227 date=2016-03-25 15:00:05 progress=0.999996
2016-03-25 15:09:34 init message: Verifierar block...
2016-03-25 15:09:34 Verifying last 288 blocks at level 3
2016-03-25 15:09:42 No coin database inconsistencies in last 3 blocks (4726 transactions)
2016-03-25 15:09:42  block index           12156ms
2016-03-25 15:09:42 init message: Laddar plånbok...
2016-03-25 15:09:42 nFileVersion = 120000
2016-03-25 15:09:42 Keys: 0 plaintext, 210 encrypted, 0 w/ metadata, 210 total
2016-03-25 15:09:42 Performing wallet upgrade to 60000
2016-03-25 15:09:42  wallet                  593ms
2016-03-25 15:09:42 init message: Aktiverar bästa kedjan...
2016-03-25 15:09:42 mapBlockIndex.size() = 404229
2016-03-25 15:09:42 nBestHeight = 404227
2016-03-25 15:09:42 setKeyPool.size() = 0
2016-03-25 15:09:42 mapWallet.size() = 10
2016-03-25 15:09:42 mapAddressBook.size() = 0
2016-03-25 15:09:42 init message: Laddar adresser...
2016-03-25 15:09:42 torcontrol thread start
2016-03-25 15:09:43 ERROR: Read: Failed to open file D:\Program Files\Bitcoin\DB\banlist.dat
2016-03-25 15:09:43 Invalid or missing banlist.dat; recreating
2016-03-25 15:09:43 Loaded 62701 addresses from peers.dat  263ms
2016-03-25 15:09:43 upnp thread start
2016-03-25 15:09:43 dnsseed thread start
2016-03-25 15:09:43 addcon thread start
2016-03-25 15:09:43 init message: Klar med laddning
2016-03-25 15:09:43 net thread start
2016-03-25 15:09:43 msghand thread start
2016-03-25 15:09:43 opencon thread start
2016-03-25 15:09:43 GUI: Platform customization: "windows"
2016-03-25 15:09:43 GUI: PaymentServer::LoadRootCAs: Loaded  51  root certificates
2016-03-25 15:09:45 UPnP: ExternalIPAddress = 217.72.51.58
2016-03-25 15:09:45 AddLocal(217.72.51.58:8333,3)
2016-03-25 15:09:45 UPnP Port Mapping successful.
2016-03-25 15:09:49 ProcessMessages: advertizing address 217.72.51.58:8333
2016-03-25 15:09:49 receive version message: /Satoshi:0.11.2/: version 70002, blocks=404228, us=217.72.51.58:54248, peer=1
2016-03-25 15:09:49 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:09:50 ProcessMessages: advertizing address 217.72.51.58:8333
2016-03-25 15:09:50 receive version message: /Satoshi:0.11.2/: version 70002, blocks=404228, us=217.72.51.58:54250, peer=3
2016-03-25 15:09:50 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:09:52 ProcessMessages: advertizing address 217.72.51.58:8333
2016-03-25 15:09:52 receive version message: /Satoshi:0.12.0/: version 70012, blocks=404228, us=217.72.51.58:54249, peer=2
2016-03-25 15:09:52 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:09:53 ProcessMessages: advertizing address 217.72.51.58:8333
2016-03-25 15:09:53 receive version message: /Satoshi:0.12.0/: version 70012, blocks=404228, us=217.72.51.58:54252, peer=4
2016-03-25 15:09:53 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:09:54 P2P peers available. Skipped DNS seeding.
2016-03-25 15:09:54 dnsseed thread exit
2016-03-25 15:10:18 UpdateTip: new best=0000000000000000030438a88a7ce0d21ae83e7ef48f2ffdc23772ed4f73c3c8  height=404228  log2_work=84.363977  tx=118330145  date=2016-03-25 15:06:35 progress=0.999998  cache=32.1MiB(5688tx)
2016-03-25 15:10:18 UpdateTip: 4 of last 100 blocks above version 4
2016-03-25 15:10:18 ProcessMessages: advertizing address 217.72.51.58:8333
2016-03-25 15:10:18 receive version message: /Satoshi:0.12.99/: version 70012, blocks=404228, us=217.72.51.58:54255, peer=5
2016-03-25 15:10:18 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:10:19 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=217.72.51.58:8333, peer=6
2016-03-25 15:10:19 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:10:19 socket recv error En befintlig anslutning tvingades att st�nga av fj�rrv�rddatorn.  (10054)
2016-03-25 15:10:30 ProcessMessages: advertizing address 217.72.51.58:8333
2016-03-25 15:10:30 receive version message: /Satoshi:0.12.0/: version 70012, blocks=404228, us=217.72.51.58:54262, peer=7
2016-03-25 15:10:30 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:10:33 ProcessMessages: advertizing address 217.72.51.58:8333
2016-03-25 15:10:33 receive version message: /Bitcoin XT:0.11.0/: version 70010, blocks=404228, us=217.72.51.58:54264, peer=9
2016-03-25 15:10:33 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:10:44 ProcessMessages: advertizing address 217.72.51.58:8333
2016-03-25 15:10:44 receive version message: /Satoshi:0.9.3/: version 70002, blocks=404228, us=217.72.51.58:54268, peer=10
2016-03-25 15:10:44 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:10:53 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:13:07 The wallet is probably corrupted: Some keys decrypt but not all.
2016-03-25 15:13:12 receive version message: /bitnodes.21.co:0.1/: version 70002, blocks=404228, us=217.72.51.58:8333, peer=11
2016-03-25 15:13:12 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:13:49 UpdateTip: new best=000000000000000005cfd4085a15e750591b0e80aded3d6c8d4f383419a21322  height=404229  log2_work=84.364019  tx=118331224  date=2016-03-25 15:12:53 progress=1.000000  cache=41.3MiB(19566tx)
2016-03-25 15:13:49 UpdateTip: 4 of last 100 blocks above version 4
2016-03-25 15:15:24 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=217.72.51.58:8333, peer=12
2016-03-25 15:15:24 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:15:26 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=217.72.51.58:8333, peer=13
2016-03-25 15:15:26 AdvertizeLocal: advertizing address 217.72.51.58:8333
2016-03-25 15:15:26 socket recv error En befintlig anslutning tvingades att st�nga av fj�rrv�rddatorn.  (10054)
2016-03-25 15:15:56 receive version message: /Satoshi:0.11.2/: version 70002, blocks=404228, us=217.72.51.58:8333, peer=14
2016-03-25 15:15:56 AdvertizeLocal: advertizing address 217.72.51.58:8333

Synchronizing still. Will get back with the log when it is done.

is this has been resolved?
if Core has an auto backup,this may not be a lot happening.

Well first of all, after you run salvagwallet once, it should fix the wallet and save it so you shouldn't need to do it again or have it run every single time.

Secondly, you should post the debug.log so that we can examine it and see what the error is. Based upon your screenshot though, I think we are going to find this message:

I am back... unfortunately.
Today I wanted to use some of the coins.
When sending the coins I was asked to write my password in BitCoin Core and so I did. This renders a "MinGW Runtime Assertion". Please see picture here:

http://henric.nu/wp-content/uploads/2016/03/assertion.jpg

So I am now in a situation where I can recover my old encrypted wallet using -salvagewallet in combination with -wallet=old_wallet.dat, and see my coin balance in BitCoin Core. But I can not spend it or change password due to this assertion. First I thought I had the wrong password and tried some others, but these just renders the normal "password was wrong"-error. It is only when I enter the correct password that I get this
MinGW Runtime Assertion. I have tried uninstalling BitCoin Core, and reinstalling, but it did not help.

Much appreciative of any kind of pointers how to retrieve these 4 BTC.

Best Regards, Henric

I managed to solve it using -salvagewallet in combination with -wallet=old_wallet.dat.
Thank you still!
/H

Can you provide the Debug.log file for us to look at?

Hello.
I am quite new to this and have pulled my hair to solve this problem.
I made a back up of my encrypted wallet a few days ago. Installed the latest Bitcoin core on my slightly refreshed computer and now I get a crash. I have tried to replaced wallet.dat with my encrypted wallet, but just after the verification of block chain at startup, it crashes.

http://henric.nu/wp-content/uploads/2015/12/Bitcoin_core_crash.jpg

I know I should not have to start with the -rescan option, but tried that as well, just to rule it out.
I am on Windows 7 and use V0.11.2.

Any help is most appreciated. The encrypted wallet contains 4 BTC so a little bit too much to just waste.

Thank you.
Henric