OK, I took a look at your debug.log and it looks like your are on a forked chain, that is why your wallet is not sync'ing.
receive version message: version 61402, blocks=604736, us=64.71.178.234:57021, them=99.253.130.167:61510, peer=99.253.130.167:61510
SetBestChain: new best=9d1d16864b0f18bad2587a79acbfd77296b106ee3811ba043b6ee45b387f3ac7 height=604644 trust=84358606602758990281 blocktrust=1002471594 date=07/02/16 05:35:21
ProcessBlock: ACCEPTED
ResendWalletTransactions()
SetBestChain: new best=c020678abb286a76f6dd0294ba6a0e177d2ccd64f48cb8c0249d01d0836e3a52 height=604645 trust=84358667993271812045 blocktrust=61390512821764 date=07/02/16 05:35:28
ProcessBlock: ACCEPTED
SetBestChain: new best=c8df45b9a928bff59f81d8c1160fa1bdc746fc8c321f44ef0dd33dd248642377 height=604646 trust=84358667994094737231 blocktrust=822925186 date=07/02/16 05:35:59
ProcessBlock: ACCEPTED
Checking the block explorer the hashes do not match for blocks 604644, 604645, 604646 ...
Then later, you restarted your wallet and it connected to one of the seed nodes and when checking the last 500 blocks that is when the exceptions started happening. your hash chain did not match with the seed node blockchain and therefore could not sync.
Opened LevelDB successfully
LoadBlockIndex(): hashBestChain=c8df45b9a928bff59f81d8c1160fa1bdc746fc8c321f44ef0dd33dd248642377 height=604646 trust=84358667994094737231 date=07/02/16 05:35:59
LoadBlockIndex(): synchronized checkpoint 00005e5044b1a81bef73dd7fc302fe157a3537ed5188401622f17e04efb16f20
Verifying last 500 blocks at level 1
block index 9530ms
init message: Loading wallet...
nFileVersion = 2040000
Keys: 101 plaintext, 0 encrypted, 101 w/ metadata, 101 total
wallet 330ms
init message: Loading addresses...
Loaded 39 addresses from peers.dat 0ms
Secure messaging starting.
Loaded 1 addresses.
Message store directory does not exist.
smsg thread start
fLiteMode 0
nInstantXDepth 5
Darksend rounds 2
smsg-pow thread start
Anonymize AmsterdamCoin Amount 1000
mapBlockIndex.size() = 626880
nBestHeight = 604646
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
AddLocal([2405:8a00:4001:228:2d49:a36a:6810:c56f]:61510,1)
AddLocal([2405:8a00:4001:228:48e2:3928:f08:f2ad]:61510,1)
DNS seeding disabled
upnp thread start
net thread start
addcon thread start
msghand thread start
opencon thread start
init message: Done loading
dumpaddr thread start
GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64)
GUI: QObject::connect: (receiver name: 'SendCoinsDialog')
GUI: QObject::connect: No such slot BitcoinGUI::error(QString,QString,bool)
GUI: QObject::connect: (receiver name: 'amsterdamcoin')
receive version message: version 61402, blocks=660473, us=64.71.178.234:57111, them=68.71.58.226:61510, peer=68.71.58.226:61510
Added time data, samples 2, offset +9 (+0 minutes)
No valid UPnP IGDs found
upnp thread exit
Postponing 15 reconnects
REORGANIZE
REORGANIZE: Disconnect 548 blocks; 3ed050b41f6680c88fe1ba410171230ffb7ad0f23ad3047ebf55375d0d2de079..c8df45b9a928bff59f81d8c1160fa1bdc746fc8c321f44ef0dd33dd248642377
REORGANIZE: Connect 197 blocks; 3ed050b41f6680c88fe1ba410171230ffb7ad0f23ad3047ebf55375d0d2de079..fd58496069b7baa84c79055fa98c7be81c352f26da129d5fc9e6d5d1c6757cb4
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
C:\Users\Jane\Desktop\amsterdamcoin-qt.exe in ProcessMessages()
ProcessMessage(block, 436 bytes) FAILED
ResendWalletTransactions()
Successfully synced, asking for Masternode list and payment list
Postponing 16 reconnects
REORGANIZE
REORGANIZE: Disconnect 548 blocks; 3ed050b41f6680c88fe1ba410171230ffb7ad0f23ad3047ebf55375d0d2de079..c8df45b9a928bff59f81d8c1160fa1bdc746fc8c321f44ef0dd33dd248642377
REORGANIZE: Connect 197 blocks; 3ed050b41f6680c88fe1ba410171230ffb7ad0f23ad3047ebf55375d0d2de079..fd58496069b7baa84c79055fa98c7be81c352f26da129d5fc9e6d5d1c6757cb4
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
C:\Users\Jane\Desktop\amsterdamcoin-qt.exe in ProcessMessages()
ProcessMessage(block, 480 bytes) FAILED
receive version message: version 61402, blocks=660498, us=64.71.178.234:57295, them=68.71.58.226:61510, peer=68.71.58.226:61510
ProcessBlock: ORPHAN BLOCK 0, prev=a920784f06aa1a82ef57eff93a599b1b6f579d2a910d03ab1640989837c9ad35
ProcessBlock: ORPHAN BLOCK 1, prev=8d9477b54b031d196e3d82a704994a654460c196b5c2c40211020ec390c72e42
Postponing 17 reconnects
REORGANIZE
REORGANIZE: Disconnect 548 blocks; 3ed050b41f6680c88fe1ba410171230ffb7ad0f23ad3047ebf55375d0d2de079..c8df45b9a928bff59f81d8c1160fa1bdc746fc8c321f44ef0dd33dd248642377
REORGANIZE: Connect 197 blocks; 3ed050b41f6680c88fe1ba410171230ffb7ad0f23ad3047ebf55375d0d2de079..fd58496069b7baa84c79055fa98c7be81c352f26da129d5fc9e6d5d1c6757cb4
I will post a link to a fresh
bootstrap.dat in the morning, so that you can download and put in your
%appdata%/AmsterdamCoin directory (Windows) to bring your node up-to-date on the right blockchain.
There are a few nodes out on the net that are persistently on the wrong chain, not sure if it is malicious or not, but I have got caught on the wrong chain twice in the past.
The more wallets that are running the more stable the blockchain and the coin becomes, and will eventually negate the rogue wallets on the forked chain.
NOTE: @gothikghk - I reviewed your debug.log, you can edit your post and remove the link to the debug file to be on the safe side. No need to keep the file or the link up for any length of time.
