You need to be more specific. Go into details as of what is "not working". Are you online? What is your top block? Can you spend from within Armory? What versions of Core and Armory are you running?

Your online Armory is most likely off sync. What is your top block in the bottom right?

Use the wallet restoration feature from within Armory, it will guide you.

There is no sorting anymore in ledgers, since they are computed and paged in on the DB side. If the wallet side balance is fine, then this isn't a DB issue but a GUI one.

At this point you'll have to wait for 0.96, which has a lot of fixes on that front.

If you tally the transactions visible in the ledger, what total amount do you end up with? If you double click on the wallet, is the balance off as well?

Log doesn't show anything off. Look at the wallet history, are there transactions missing?

Do you have enough addresses computed on the wallet chain? What is your top block? Let's see dbLog.txt.

My clever plan to summon the droark worked.

Use pastebin.

Seeing you are a complete newcomer, you're in for a ride. Consider that Armory is an advanced wallet, and you know too little about Bitcoin to get a smooth first experience.

With that behind us, follow achow's instructions to get Armory online. Armory requires a fully synchronized Bitcoin node to operate (this is not a design limitation but part of the model). Bootstrapping a Bitcoin node can take days if your hardware/internet connection is not up to par. Be warned that this is a long and resource intensive process.

Once you have that part covered, the worst is behind you. You can keep on asking for help on this forum but remember to keep it civil.

Now, if you wish to verify your coins are on your wallet, open Armory (doesn't matter if its offline), double click your wallet, and find the address you sent the coins to. Copy that address (should start with "1" and be some 30+ characters long), and paste it in a block explorer (I use blockr.io). This will show you the balance on your address (your coins should be there).

Generally, you can just get offline Armory to spit out addresses to receive payment. You need to take Armory online to:

1) Verify your balance from within Armory
2) Create transactions, in order to pay others.

This is just gdb reporting threads starting and ending, nothing to see here. When the code crashes, you will see a SIGSEGV or SIGTERM at the bottom then prompt back at gdb> ready for your input.

Then post only the output for "bt" and wait on instructions.

I meant as in Windows/OSX/Linux

If the chance for the code to fail is not reduced, that's a way to go about it.

You can build with DEBUG=1 and run ArmoryDB in gdb. You can then post the backtrace after it hangs, although that will require some extra work to be really useful, as you would need to show me the bt for all relevant threads (seeing you run 100 ZC threads, it will be tedious to filter through).

- You need to tell Armory where to find your custom Bitcoin folder (--satoshi-datadir="mybitcoincorepath").

- You'll have to turn off auto bitcoind as well in Armory (File -> Settings -> 1st section)

- Sounds like either your laptop is unstable or your external HDD is partially damaged (Core wouldn't freeze your machine during IBD otherwise).

I'll have to reproduce the issue on my own. It sounds deterministic enough that I should be able to.

What OS are you using?

I know what you are using. My point is without logs, I can't do anything.

I would need to see the logs.

You would have to delete the log and reproduce in offline mode for the issue to be clearly isolated. Otherwise, I can't really tell.