Armory will make me crazy! Help to fix 2 problems (Mac)

[iCan]

Hi I really like Armory and don't wanted to change it. I deal with first problem for a year but now armory crash right after "Reading new block Headers".
First of all when I load up Armory it say's me:

Important Wallet Consistency Issues Detected!
Armory now detects certain kinds of hardware errors, and one or more of your wallets was flagged. The consistency logs need to be analyzed by the Armory team to determine if any further action is required.
This warning will pop up every time you start Armory until the wallet is fixed

I try to fix it with "Fix damage wallet tool" few times and I open 2 tickets on official support and nothing, but it is not a big deal, I can work with this problem, but it will be nice to know if it can be fixed.

The MAIN problem is that Armory crash right after "Reading new block Headers". 

I have OS X 10.11.3. Bitcoin Core v0.11.2. Armory 0.93.3-beta-2a6fc5355b.
All libraries (BC and Armory) store on second hard drive, armory load by command "open -a Armory --args --satoshi-datadir=/Volumes/......"

Error log      (if needed I can post full error log )

Process:               Python [3543]
Path:                  /Applications/Armory.app/Contents/MacOS/Python
Identifier:            com.armory.armory
Version:               
Code Type:             X86-64 (Native)
Parent Process:        [1]
Responsible:           Python [3543]
User ID:               501

Date/Time:             2016-02-04 11:57:16.189 +0300
OS Version:            Mac OS X 10.11.3 (15D21)
Report Version:        11
Anonymous UUID:        7201E72A-9682-8E4A-B734-52CA7A098153

Sleep/Wake UUID:       CA107355-322B-4251-9EF8-816D814B6422

Time Awake Since Boot: 150000 seconds
Time Since Wake:       4100 seconds

System Integrity Protection: enabled

Crashed Thread:        5

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       0x000000000000000a, 0x0000000dd22df001
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0xdd22df001:
    Memory Tag 251         00000001700b8000-00000001700bc000 [   16K] rw-/rwx SM=COW 
--> mapped file            00000001700bc000-0000000dd379d000 [ 49.6G] r--/rwx SM=PRV 
    STACK GUARD            0000700000000000-0000700000001000 [    4K] ---/rwx SM=NUL  stack guard for thread 1

[1714863800]

1714863800

[1714863800]

1714863800

[droark]

The SIGBUS error usually means faulty RAM. If you're seeing consistent crashes and weirdness, that's probably the problem. I had no problems like these when I ran 0.93.

[iCan]

The SIGBUS error usually means faulty RAM. If you're seeing consistent crashes and weirdness, that's probably the problem. I had no problems like these when I ran 0.93.

Nope it's not RAM I got 16 GB and only 10 in use, and it crash right after "Reading new block Headers". Always at this step! Can some one look what Armory do after "Reading new block Headers"?

[gangtraet]

Important Wallet Consistency Issues Detected!

I would be very worried by this.  I would probably back up the old wallet file, print out a paper backup, delete the wallet file and restore the paper wallet.  That way you lose all your notes etc, but you have a clean wallet.  A corrupt wallet could potentially generate addresses that you cannot later spend.

The SIGBUS error usually means faulty RAM. If you're seeing consistent crashes and weirdness, that's probably the problem. I had no problems like these when I ran 0.93.

Nope it's not RAM I got 16 GB and only 10 in use

He was not talking about the amount of RAM you have.  The error could mean that one of the RAM chips is defective.  It is not very likely, but you may be able to test it by downloading and Ubuntu install disk and use the memory test program included on it.

[iCan]

Ok, I delete every thing on my mac that related to Armory and start it as new one! With paper backup. Hope it will fix everything, because I truly believe that it is not RAM chips defective. Hope it will help. Thx for help!

[goatpig]

I would be very worried by this.  I would probably back up the old wallet file, print out a paper backup, delete the wallet file and restore the paper wallet.  That way you lose all your notes etc, but you have a clean wallet.  A corrupt wallet could potentially generate addresses that you cannot later spend.

Do NOT delete the wallet file if it was flagged for corruption. You should let me see the log file. Usually I will then recommend you to:

1) Sync the wallet
2) Create a new wallet and back it up. Verify the back up.
3) Move the funds from the old wallet to the new one.

Then you can get rid of the old wallet.

[iCan]

I would be very worried by this.  I would probably back up the old wallet file, print out a paper backup, delete the wallet file and restore the paper wallet.  That way you lose all your notes etc, but you have a clean wallet.  A corrupt wallet could potentially generate addresses that you cannot later spend.

Do NOT delete the wallet file if it was flagged for corruption. You should let me see the log file. Usually I will then recommend you to:

1) Sync the wallet
2) Create a new wallet and back it up. Verify the back up.
3) Move the funds from the old wallet to the new one.

Then you can get rid of the old wallet.

Too late, I already delete everything. Now is running process of restoring my wallet, hope it will work.  But I send log file to your support 2 times(10-oct-2015 and 2 days ago with critical priority), and no answer.

UPD. All works great, after deleting Wallet and all Armory files. Thx gangtraet for idea!