Armoury 0.95 - "Building database" forever

[h7h]

I've updated to the armory 0.95. My current problem is described in the post #6




Hello. I am trying to get Arnory to work.
Bitcoin Core was synched and running ok.

When I run Armoury (after switching of bitcoin core and making sure that bitcoind is not active task), Armoury spends a little time syncing with the blockchain (usually downloading 1-3 blocks) and after that the dasboard is the usual "Armory is offline" because it "could not detect detect an internet connection". [Go online] button does nothing. Checking "skip online check on the startup" does nothing. Lower right corner of the screen says "Connected(0 blocks)" in green.

I tried to change settings and run bitcoind manually instead of letting Armury manage it. In that case Armory is unable to establish connection with bitcoind.

I looked in the logs and every time i try to launch Armory with it managing bitcoind the last line in the log is

Code:

TypeError: in method 'BlockDataManagerConfig_blkFileLocation_set', argument 2 of type 'string const &'

Logs (should include both attempts in letting armoury manage bitcoind and running it on it's own):
http://pastebin.com/uSF8yvNt
http://pastebin.com/qmY7kJUt
http://pastebin.com/iAKpzn1m

Edited to add: OS is Lubuntu 16.04

[1715589840]

1715589840

[1715589840]

1715589840

[1715589840]

1715589840

[achow101]

(after switching of bitcoin core and making sure that bitcoind is not active task),

Why are you turning off Bitcoin Core? Armory need Bitcoin Core/bitcoind in order to function properly. It will not think it is online unless Bitcoin Core is running and it can connect to it.

[h7h]

When Armory is set to be running bitcoind it starts it itself("Since version 0.88 armoury runs bitcoind in the background"), in fact if you will start Armory while bitcoind is active task it says "Please close Bitcoin Core".

In any case I have mentioned in the first post that I tried to switch off auto-management in armory and run bitcoin in background  manually. Result is the same - green "Connected(0 blocks)" in the lower right corner and "Armory is offlin" in the center of the ashboard. "Go online" button does nothing.

[achow101]

Try upgrading to 0.95 and see if that fixes the problem.

[goatpig]

When Armory is set to be running bitcoind it starts it itself("Since version 0.88 armoury runs bitcoind in the background"), in fact if you will start Armory while bitcoind is active task it says "Please close Bitcoin Core".

In any case I have mentioned in the first post that I tried to switch off auto-management in armory and run bitcoin in background  manually. Result is the same - green "Connected(0 blocks)" in the lower right corner and "Armory is offlin" in the center of the ashboard. "Go online" button does nothing.

Your issue is that Armory is failing to auto detect your Bitcoin folder. You need to enforce it manually through the --satoshi-datadir command line argument.

[h7h]

I've updated to the 0.95 and my problem has changed. Now when I star Armory the first progressbar on the dashboard ("Initializing bitcoin engine") fills instantly, however second progressbar ("Building databases") do not move at all even after 12 hours. Changing between bitcoind managed by Armory and manual mode do not change anything.

About --satoshi-datadir: When I done this properly there was no difference - which is exactly as it should be because from the beginning I pointed Armory to the folder with bitchain in the settings of Armory, so it is only logical that pointing in the settings do the same as pointing via command line argument.

However when I accidentally made a typo in the path in the --satoshi-datadir argument, the dashboard of Armory was telling me that it could not detect bitcoin engine. Which is different error from those that I had in 0.94.1 and is different from the current error.

New logs after update to the 0.95
http://pastebin.com/rpFn5c7v
http://pastebin.com/xbEypRTC
http://pastebin.com/0NH1KP0z

[M4rt1n]

For me it looks like this forever: https://i.imgur.com/hvjDUtX.png

Even after 1 and a half day completly online nothing happend

[h7h]

Yes, exactly as in M4rt1n's case. I did not think  to append screenshots and now they are somewhat redundant.

[goatpig]

run ArmoryDB manually with your command line args, see what it has to say.

[h7h]

Running from terminal i get this:

Code:

-INFO  - 1477229196: (main.cpp:22) Running on 1 threads
-INFO  - 1477229196: (main.cpp:23) Ram usage level: 4
-INFO  - 1477229196: (BlockUtils.cpp:1325) blkfile dir: /media/sdd/Bitchain/Bitcoin/blocks
-INFO  - 1477229196: (BlockUtils.cpp:1326) lmdb dir: /home/sdd/.armory/databases
-INFO  - 1477229196: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1477229196: (BlockUtils.cpp:1508) Executing: doInitialSyncOnLoad
-INFO  - 1477229196: (DatabaseBuilder.cpp:162) Reading headers from db
-ERROR - 1477229196: (StoredBlockObj.cpp:538) buffer is too small: 0 bytes. expected: 106
-ERROR - 1477229196: (BDM_mainthread.cpp:255) BDM thread failed: buffer is too small: 0 bytes. expected: 106

[goatpig]

Point it to another DB folder (--dbdir) or empty the default one. You can see the default db paths here:

https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockUtils.cpp#L704
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockUtils.cpp#L724

[h7h]

I cleared the entire .armory folder and run ArmoryDB for some time. How long should I do it and when I should start the entire Armory client?

In any case here are logs so far
http://pastebin.com/Nz80CGfy

[goatpig]

I cleared the entire .armory folder and run ArmoryDB for some time. How long should I do it and when I should start the entire Armory client?

In any case here are logs so far
http://pastebin.com/Nz80CGfy

It's ready now, start ArmoryQt.

[PeZ]

Point it to another DB folder (--dbdir) or empty the default one. You can see the default db paths here:

https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockUtils.cpp#L704
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockUtils.cpp#L724

Is --dbdir a new command? I upgraded from a working 0.93.3 to 0.95 and get the same problems as the other people in this thread. I tried clearing out the Armory database folder.

When I run "E:\Program Files (x86)\Armory\ArmoryQt.exe" --datadir="E:\ArmoryData" --dbdir="E:\ArmoryData\databases" --satoshi-datadir="E:\BitcoinData", nothing gets written to the databases folder.

I checked to make sure nothing is getting written into C:\Users\[Username]\AppData\Roaming.

Debug mode is showing this...

(INFO) ArmoryQt.py:2307 - Setting netmode: 0
(DEBUG) SDM.pyc:751 - Creating proxy
(INFO) SDM.pyc:755 - Creating proxy in SDM: host=127.0.0.1, port=8332
(INFO) ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
(DEBUG) SDM.pyc:798 - generic socket error
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception

[goatpig]

Is --dbdir a new command? I upgraded from a working 0.93.3 to 0.95 and get the same problems as the other people in this thread. I tried clearing out the Armory database folder.

Has been there since Armory has had a db. You don't need to specify the dbdir if you are just appending /databases to the datadir, it does that on its own to begin with.

nothing gets written to the databases folder.

Db isn't starting at all then. I suggest you run ArmoryDB.exe on its own in the command prompt with the same cli args. You'll get a terminal output that will help you figure out what's wrong.

[PeZ]

With ArmoryDB running, the database folder is now being written to. It will probably take awhile.

Prior to this, I ran Armory in debug mode and then end of the log was...

(INFO) ArmoryQt.py:2307 - Setting netmode: 0
(DEBUG) SDM.pyc:751 - Creating proxy
(INFO) SDM.pyc:755 - Creating proxy in SDM: host=127.0.0.1, port=8332
(INFO) ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
(DEBUG) SDM.pyc:798 - generic socket error
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception

[goatpig]

Your client is set to auto manage bitcoind, and apparently it's failing there, so it never got as far as starting the db.

[PeZ]

ArmoryDB wrote 797MB and the log ended with...

-DEBUG - 1477260767: (..\Blockchain.cpp:232) Organizing chain
-INFO  - 1477260780: (..\DatabaseBuilder.cpp:49) updated HEADERS db in 1127.35s
-INFO  - 1477260780: (..\BlockUtils.cpp:1619) Enabling zero-conf tracking

Started Armory and ArmoryQt.exe.log shows...

(ERROR) SDM.pyc:376 - Could not find guardian script: .\guardian.exe
(ERROR) ArmoryQt.py:2247 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 2243, in startBitcoindIfNecessary
  File "SDM.pyc", line 468, in startBitcoind
  File "SDM.pyc", line 577, in launchBitcoindAndGuardian
  File "SDM.pyc", line 377, in getGuardianPath
FileExistsError

[PeZ]

I uninstalled 0.95 and went back to 0.93.3, since I am not having any problems with the old version.

[M4rt1n]

This is what it showed me:

-INFO  - 1477270102: (..\main.cpp:22) Running on 8 threads
-INFO  - 1477270102: (..\main.cpp:23) Ram usage level: 4
-INFO  - 1477270102: (..\BlockUtils.cpp:1325) blkfile dir: C:\Users\***\AppData\Roaming/Bitcoin/blocks
-INFO  - 1477270102: (..\BlockUtils.cpp:1326) lmdb dir: C:\Users\***\AppData\Roaming/Armory/databases
-INFO  - 1477270102: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1477270103: (..\BlockUtils.cpp:1508) Executing: doInitialSyncOnLoad
-INFO  - 1477270103: (..\DatabaseBuilder.cpp:162) Reading headers from db
-WARN  - 1477270103: (..\lmdb_wrapper.cpp:1159) No headers in DB yet!
-INFO  - 1477270103: (..\DatabaseBuilder.cpp:201) Found 1 headers in db
-INFO  - 1477270103: (..\DatabaseBuilder.cpp:44) updating HEADERS db
-INFO  - 1477270105: (..\DatabaseBuilder.cpp:260) parsed block file #1
.
.
.
-INFO  - 1477270158: (..\DatabaseBuilder.cpp:260) parsed block file #125
-INFO  - 1477270159: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO  - 1477270161: (..\DatabaseBuilder.cpp:260) parsed block file #126
.
.
.
-INFO  - 1477270443: (..\DatabaseBuilder.cpp:260) parsed block file #658
-DEBUG - 1477270452: (..\Blockchain.cpp:232) Organizing chain
-INFO  - 1477270460: (..\DatabaseBuilder.cpp:49) updated HEADERS db in 357.254s
-INFO  - 1477270460: (..\BlockUtils.cpp:1619) Enabling zero-conf tracking
-INFO  - 1477270476: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1477270493: (..\BlockchainScanner.cpp:52) no history to scan

I had to run ArmoryDB.exe as Admin and first garant network access. (without admin it stuck at #96)
BTW: ArmoryQT.exe.log shows me:

(ERROR) SDM.pyc:376 - Could not find guardian script: .\guardian.exe
(ERROR) ArmoryQt.py:2247 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 2243, in startBitcoindIfNecessary
  File "SDM.pyc", line 468, in startBitcoind
  File "SDM.pyc", line 577, in launchBitcoindAndGuardian
  File "SDM.pyc", line 377, in getGuardianPath
FileExistsError

But in the end nothing changed and it's still not working
For me it looks like you forgot to add Guardian to the 0.95-Bundle of Windows

[M4rt1n]

For all Windowsuser getting the same error like me and getting this error in ArmoryQT.exe.log:

(ERROR) SDM.pyc:376 - Could not find guardian script: .\guardian.exe
(ERROR) ArmoryQt.py:2247 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 2243, in startBitcoindIfNecessary
  File "SDM.pyc", line 468, in startBitcoind
  File "SDM.pyc", line 577, in launchBitcoindAndGuardian
  File "SDM.pyc", line 377, in getGuardianPath
FileExistsError

Download this File (guardian.exe 109 KB) :

Zippyshare
Mega.nz
G-Drive

if you dont trust me (this files) download 0.94.1 and install it to another directory. Then continue with your own guardian.exe

place this file in the installationdirectory (standard is C:\Program Files (x86)\Armory)

If you now got this error by running ArmoryDB.exe:

-INFO  - 1477273626: (..\main.cpp:22) Running on 8 threads
-INFO  - 1477273626: (..\main.cpp:23) Ram usage level: 4
-INFO  - 1477273626: (..\BlockUtils.cpp:1325) blkfile dir: C:\Users\***\AppData\Roaming/Bitcoin/blocks
-INFO  - 1477273626: (..\BlockUtils.cpp:1326) lmdb dir: C:\Users\***\AppData\Roaming/Armory/databases
-INFO  - 1477273626: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1477273627: (..\BlockUtils.cpp:1508) Executing: doInitialSyncOnLoad
-INFO  - 1477273628: (..\DatabaseBuilder.cpp:162) Reading headers from db
-ERROR - 1477273629: (..\StoredBlockObj.cpp:538) buffer is too small: 80 bytes. expected: 106
-ERROR - 1477273629: (..\BDM_mainthread.cpp:255) BDM thread failed: buffer is too small: 80 bytes. expected: 106

Close and exit Armory (even in the tray)
Go to %appdata%\Armory\ and delete the folder called databases then start ArmoryDB.exe again.
After it finished start ArmoryQT.exe and wait (on HDD maybe about 5min) now ArmoryDB.exe starts itself and does everything what is necessary.

Have fun.


Proof of work -->

https://i.imgur.com/p1Ghh0H.png
https://i.imgur.com/atQBm62.png


I guess there will be a 0.95.0.1 with including guardian.exe

@goatpig: on Windows I have to wait about 1 min when I start ArmoryQT (like this) untill it starts ArmoryDB itself. Could you pls watch out what makes it taking so long?
Thanks!

[PeZ]

Well this just partly works, now I got this by starting ArmoryDB manually:

-INFO  - 1477273626: (..\main.cpp:22) Running on 8 threads
-INFO  - 1477273626: (..\main.cpp:23) Ram usage level: 4
-INFO  - 1477273626: (..\BlockUtils.cpp:1325) blkfile dir: C:\Users\***\AppData\Roaming/Bitcoin/blocks
-INFO  - 1477273626: (..\BlockUtils.cpp:1326) lmdb dir: C:\Users\***\AppData\Roaming/Armory/databases
-INFO  - 1477273626: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1477273627: (..\BlockUtils.cpp:1508) Executing: doInitialSyncOnLoad
-INFO  - 1477273628: (..\DatabaseBuilder.cpp:162) Reading headers from db
-ERROR - 1477273629: (..\StoredBlockObj.cpp:538) buffer is too small: 80 bytes. expected: 106
-ERROR - 1477273629: (..\BDM_mainthread.cpp:255) BDM thread failed: buffer is too small: 80 bytes. expected: 106

That was the error I got before I emptied the Armory data directory. When you empty the directory, ArmoryDB.exe will work without error, but that doesn't mean ArmoryQT will work.

[EDIT]
Looks like you got it to work with guardian.

[M4rt1n]

Well this just partly works, now I got this by starting ArmoryDB manually:

That was the error I got before I emptied the Armory data directory. When you empty the directory, ArmoryDB.exe will work without error, but that doesn't mean ArmoryQT will work.

I know, this happens because guardian.exe is missing in the 0.95 Windows installationfile.
Pls just watch the post above you

[PeZ]

Did you try skipping ArmoryDB and run ArmoryQT without it?

It's an annoyance to regenerate 59GB's worth of files.

[M4rt1n]

Did you try skipping ArmoryDB and run ArmoryQT without it?

It's an annoyance to regenerate 59GB's worth of files.

This will result in the same thing becasue ArmoryQT is starting ArmoryDB itself. At this 0.95 version there is a bug and it starts in visible (normaly it starts it in the Background) but it starts it anyway.
Btw you dont have to regenerate 59GB, it just creates 700MB DB;) (Building DB and scanning takes for me 10 min on SSD)

[PeZ]

I tried it again. ArmoryDB went fine, but when I run ArmoryQT I still get...

(DEBUG) SDM.pyc:794 - generic jsonrpc exception

Eventually ArmoryDB pops up on its own, but it uses the default path which doesn't exist.

Maybe it's because I am using Windows 10? Bitcoind does run in the background with ArmoryQT. Back to 0.93.3.

[M4rt1n]

I tried it again. ArmoryDB went fine, but when I run ArmoryQT I still get...

(DEBUG) SDM.pyc:794 - generic jsonrpc exception

Eventually ArmoryDB pops up on its own, but it uses the default path which doesn't exist.

Maybe it's because I am using Windows 10? Bitcoind does run in the background with ArmoryQT. Back to 0.93.3.

I'm running 0.95 on Windows 10 x64 so it's not related to Windows 10.
If you have TeamViewer I may could help you

BTW which BitCoin Version are you running? Pls update to v0.13 (as it is the minimum requirement --> https://btcarmory.com/0.95.0-release/ )

Back to 0.93.3

Why Back? You can just simply have both installed with different Installationdirectorys And why 0.93.3 and not 0.94.1?

[goatpig]

1) I forgot guardian.exe on the Windows package, my bad. You can still run Armory if you turn off auto bitcoind management and run BitcoinQt yourself. I'll fix the release sometimes this week.

2)

Download this File (guardian.exe 109 KB) :

Zippyshare
Mega.nz
G-Drive

if you dont trust me (this files) download 0.94.1 and install it to another directory. Then continue with your own guardian.exe

place this file in the installationdirectory (standard is C:\Program Files (x86)\Armory)

Ugh, don't post unsigned 100Kb executables online, that's a poor idea. Guardian.exe is the same accross all versions, ever since it was introduced. If you can't wait for a fix, grab the file from older packages.

3)

-ERROR - 1477273629: (..\StoredBlockObj.cpp:538) buffer is too small: 80 bytes. expected: 106
-ERROR - 1477273629: (..\BDM_mainthread.cpp:255) BDM thread failed: buffer is too small: 80 bytes. expected: 106

DB is failing to detect older versions and still reads ahead, which results in this error. I'll fix that along with guardian. The end result is the same, you need to provide the DB with another a fresh dbdir or wipe your existing one.

BTW which BitCoin Version are you running? Pls update to v0.13

This is not accurate. 0.95 is compatible with SegWit chains that Core 0.13 enabled on the testnet and 0.13.1 will eventually enable on the mainnet. The requirement is for Armory to be updated to 0.95 to run against a SegWit chain. 0.95 can run against any older version of the blockchain.

I guess there will be a 0.95.0.1 with including guardian.exe

@goatpig: on Windows I have to wait about 1 min when I start ArmoryQT (like this) untill it starts ArmoryDB itself. Could you pls watch out what makes it taking so long?
Thanks!

It will be 0.95.1. No point disturbing the versioning pattern. The slow startup I believe is related to starting bitcoind first. The client waits on bitcoind to get ready before processing any further. Test this assumption by turning off auto bitcoind, starting BitcoinQt yourself, then starting Armory. The DB should spawn right away.

This issue will go away in the next subrelease (0.95.2 now), once I'll have all the bitcoind management moved to the DB.

At this 0.95 version there is a bug and it starts in visible (normaly it starts it in the Background) but it starts it anyway.

There is no "normally" per se yet. 0.95 just introduced the DB as its own binary. It used to run within the client's virtual address space as a shared library before.

I've left the DB command line dialog visible in Windows on purpose, as I explained in the release post. This is to make debugging easier and make users aware of the architectural shift. I'll hide it in 0.95.2

[PeZ]

Why Back? You can just simply have both installed with different Installationdirectorys And why 0.93.3 and not 0.94.1?

I just tried 0.94.1 and it appears to be working.

[M4rt1n]

Why Back? You can just simply have both installed with different Installationdirectorys And why 0.93.3 and not 0.94.1?

I just tried 0.94.1 and it appears to be working.

Now pls backup the guardian.exe File from C:\Program Files (x86)\Armory and install 0.95 then copy it back. Thats all

[PeZ]

Why Back? You can just simply have both installed with different Installationdirectorys And why 0.93.3 and not 0.94.1?

I just tried 0.94.1 and it appears to be working.

Now pls backup the guardian.exe File from C:\Program Files (x86)\Armory and install 0.95 then copy it back. Thats all

No such luck. I even tried reindexing my Bitcoin database and then ran ArmoryDB. ArmoryQT in debug mode spams out...

Code:

(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception

Armory 0.93.3 and 0.94.1 work fine, but not 0.95.0. Maybe it's because I'm using an old AMD 1090T processor?

[achow101]

No such luck. I even tried reindexing my Bitcoin database and then ran ArmoryDB. ArmoryQT in debug mode spams out...

Code:

(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception

Armory 0.93.3 and 0.94.1 work fine, but not 0.95.0

That error is due to it being unable to connect to Bitcoin Core's RPC server. What version of Bitcoin Core are you using? What is inside of the bitcoin.conf file?

[PeZ]

That error is due to it being unable to connect to Bitcoin Core's RPC server. What version of Bitcoin Core are you using? What is inside of the bitcoin.conf file?

Bitcoin Core (64-bit) 0.13.0

Code:

rpcuser=generated_by_armory

rpcpassword=[Removed Due to Public Posting]

[achow101]

Try commenting out (with a # in front of the lines) those lines in the bitcoin.conf and see if it will work then.

[PeZ]

Try commenting out (with a # in front of the lines) those lines in the bitcoin.conf and see if it will work then.

That caused an immediate crash. On the second attempt it started up with plenty of repeated errors...

Code:

(ERROR) SDM.pyc:790 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 764, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded

GUI still stuck at the same spot.

[M4rt1n]

Why Back? You can just simply have both installed with different Installationdirectorys And why 0.93.3 and not 0.94.1?

I just tried 0.94.1 and it appears to be working.

Now pls backup the guardian.exe File from C:\Program Files (x86)\Armory and install 0.95 then copy it back. Thats all

No such luck. I even tried reindexing my Bitcoin database and then ran ArmoryDB. ArmoryQT in debug mode spams out...

Code:

(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception
(DEBUG) SDM.pyc:794 - generic jsonrpc exception

Armory 0.93.3 and 0.94.1 work fine, but not 0.95.0. Maybe it's because I'm using an old AMD 1090T processor?

Now I'm confused if 0.94.1 works 0.95 should also work (after pasting guardian.exe in it) but I think it is now becasue of an processor.
Have you also deleted databases in %appdata%\Armory\? if yes and it still does not work pls try BitCoin Core 0.13.1 (27.10.2016)
May with the newest Bitcoin it works for you, for me it also works with 0.13.1

[PeZ]

Now I'm confused if 0.94.1 works 0.95 should also work

Isn't 0.95 when they separated ArmoryDB from ArmoryQT? When ArmoryDB is called by ArmoryQT, it doesn't pass the proper settings, so you have to run ArmoryDB on its own.