Title: Corrupted wallet.dat file Post by: mraudio106 on March 11, 2018, 06:10:55 PM hopefully this channel is still alive....
I need help with a QT ver. 4.8.5 wallet.dat that is corrupt somehow. #1 trying to replace the wallet.bat file into the same dir but keeps failing and just hang at "Loading block index" then no more. #2 if I hover mouse over the wallet it just shows the spinning timer forever. #3 remove all files except all the dll's and the config file and restart, starts fine but all frome day 1. (sync and no Bal) #4 if wallet.dat just copied over wallet fails with "Fatal error occored" or exception ST13runtime error" #5 replace wallet.dat while wallet running... a program error pops up and locksup the wallet completely. #6 after running several hours with brand new install, stop mid sync and try to restart, no go just hangs... #7 repeat step #1 Title: Re: Corrupted wallet.dat file Post by: achow101 on March 12, 2018, 04:47:23 AM First of all, do not necropost (posting in topics that have not had a post in a long time), especially with your own issue, not an attempt to help the OP. I've moved your post into its own thread.
I need help with a QT ver. 4.8.5 wallet.dat that is corrupt somehow. Bitcoin Core is not called Qt, and the Qt version is completely irrelevant. What is the version of Bitcoin Core (which is not Qt).#1 trying to replace the wallet.bat file into the same dir but keeps failing and just hang How do you know that it is hanging? Sometimes Bitcoin Core can take a long time to start up, but that does not mean that it is hanging.at "Loading block index" then no more. #3 remove all files except all the dll's and the config file Of course there won't be a balance, the blockchain isn't synced yet.and restart, starts fine but all frome day 1. (sync and no Bal) #5 replace wallet.dat while wallet running... a program error pops up Don't do that, you'll end up corrupting things further. You cannot just remove and replace files while they are still in use by the software.and locksup the wallet completely. Please post the contents of your debug.log file. |