Armory Crashing and raw data does not match expected block hash?

[yoon]

Hello could someone please help me? I am trying to sync my armory wallet to verify my balance currently using bitcoin core along with armory for some reason I can't seem to get armory to function properly without crashing... I went ahead and included the log file from today if someone could be so kind as to help me with this as I am not a very technical person especially when it comes to this, would be greatly appreciated!!

Log file opened at 1501727566: C:\Users\Nightghost\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1501727566: (..\main.cpp:23) Running on 8 threads
-INFO  - 1501727566: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1501727566: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\Nightghost\AppData\Roaming\Armory\databases\blocks
-INFO  - 1501727566: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\Nightghost\AppData\Roaming\Armory\databases
-INFO  - 1501727566: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1501727567: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1501727568: (..\BDM_Server.cpp:996) registered bdv: 1b9dde153bcc8ce9639a
-INFO  - 1501727569: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1501727569: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN  - 1501727569: (..\lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO  - 1501727569: (..\DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO  - 1501727569: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1501727569: (..\DatabaseBuilder.cpp:268) parsed block file #0
-DEBUG - 1501727569: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1501727569: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.033s
-INFO  - 1501727569: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO  - 1501727569: (..\BDM_supportClasses.cpp:366) Starting address registration process
-INFO  - 1501727569: (..\BlockchainScanner.cpp:650) scanned from height #0 to #0
-INFO  - 1501727569: (..\BlockchainScanner.cpp:650) scanned from height #0 to #0
-WARN  - 1501727577: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1501727577: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1501727600: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1501727600: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1501727761: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1501727761: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-INFO  - 1501727934: (..\BDM_Server.cpp:1025) unregistered bdv: 1b9dde153bcc8ce9639a
-INFO  - 1501727934: (..\BDM_Server.cpp:936) proceeding to shutdown
-ERROR - 1501727934: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO  - 1501727934: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO  - 1501727934: (..\nodeRPC.cpp:59) RPC connection established
-ERROR - 1501727934: (..\BDM_mainthread.cpp:286) caught exception in main thread: terminate


Log file opened at 1501727980: C:\Users\Nightghost\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1501727980: (..\main.cpp:23) Running on 8 threads
-INFO  - 1501727980: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1501727980: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\Nightghost\AppData\Roaming\Armory\databases\blocks
-INFO  - 1501727980: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\Nightghost\AppData\Roaming\Armory\databases
-INFO  - 1501727980: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1501727981: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1501727982: (..\BDM_Server.cpp:996) registered bdv: b76099d066475e2b729a
-WARN  - 1501727983: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-INFO  - 1501727983: (..\BlockUtils.cpp:1120) Executing: doInitialSyncOnLoad_RescanBalance
-INFO  - 1501727983: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1501727983: (..\DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO  - 1501727983: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1501727986: (..\DatabaseBuilder.cpp:268) parsed block file #0
-DEBUG - 1501727986: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1501727988: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 5.001s
-INFO  - 1501727988: (..\DatabaseBuilder.cpp:106) scanning new blocks from #1 to #111164
--ERROR - 1501727988-ERROR - 1501727988-ERROR - 1501727988-ERROR - 1501727988-ERROR - 1501727988-ERROR - 1501727988-ERROR - 1501727988ERROR - 1501727988: (..\BlockchainScanner.cpp:271: (..\BlockchainScanner.cpp:271) raw data does not match expected block hash
: : (..\BlockchainScanner.cpp:271) raw data does not match expected block hash
: : : (..\BlockchainScanner.cpp:271(..\BlockchainScanner.cpp:271(..\BlockchainScanner.cpp:271: (..\BlockchainScanner.cpp:271) raw data does not match expected block hash
) (..\BlockchainScanner.cpp:271raw data does not match expected block hash
) ) raw data does not match expected block hash
raw data does not match expected block hash) raw data does not match expected block hash
)
raw data does not match expected block hash

[Mr.Vice]

Please use the code tags if you publish log files.

Is Bitcoin Core fully synced? Have you added server=1 to your bitcoin.conf file?
When you consider to restart Armory again after you let core fully sync, go to %APPDATA%/Armory in Windows and delete your database folder before.

[droark]

Which version of Armory are you running?

[padarjohn]

I'm having the same problem. I assume it's 0.96.1, since I downloaded it a couple of days ago. I can't tell for certain, because even though I have a core-i7 and 12GB of RAM starting Armory brings the system to its knees and it's completely unresponsive until it either finishes (24hrs or so if I try to rebuild the database) or crashes.

I was running an older version, and decided I should probably update after the recent split.

I've on my 3rd attempt to rebuild the database. If I just restart after Armory crashes it just eventually crashes again at a different place.

[yoon]

I was using version 96 and was synced completely with bitcoin core's block chain but I uninstalled and reinstalled to 96.1 armory version but I don't remember how to get Armory to search/sync with bitcoin core (last time the command prompt would pop up when I would run armory and start syncing with the block chain *installed bitcoin core on D drive so its not at the default location of C:\Users\xxx\AppData\Roaming not sure where to find it)

[taxmanmt5]

I don't know precisely what's happening, but is my serious suggestion at this time, and if possible leave that PC the alone for the moment. If you look at some of the successful messages the wallet is getting to the point where it is trying to read from the database, but it also looks to me like your wallet that has been replaced with fresh data and that is why you're getting no headers back from that.

[virasog]

It is very possible that for whatever reason probably the fork, the wallet is not getting proper information back from the internet but I'm pretty sure that no matter what the wallet is trying to pull information from a fresh wallet.dat. when a computer deletes data, what it is really doing is ignoring the pointers to where the data is that data still exists, but it will only continue to exist until some fresh data gets written to the same place on the hard drive.

[JohnBitCo]

It is very possible that for whatever reason probably the fork, the wallet is not getting proper information back from the internet but I'm pretty sure that no matter what the wallet is trying to pull information from a fresh wallet.dat. when a computer deletes data, what it is really doing is ignoring the pointers to where the data is that data still exists, but it will only continue to exist until some fresh data gets written to the same place on the hard drive.

so every second that computer is operating there is a greater and greater at the old data will be written over. I know that doesn't solve your problem, but I think it's a set of steps that you need to take to ensure that there is the greatest chance of you getting your data back.