I'm not sure. I'm at block 235487 with no errors right now. I could try to zip up my copy of the blockchain for you, if anyone knows whether that will work? Another option is you could try starting from an old snapshot again with a limited peer list of nodes you know have the good blockchain...
If you could upload a blockchain snapshot that would be awesome (I have already used snapshots, it works, needed files are, if I remember right, addr.dat, blk0001.dat, blkindex.dat and the database folder). Obviously even better would be if we manage to really solve the issue.
I have already tried going back to block 205xxx (the last snapshot I have) and start slimcoin connecting only to the block explorer with -listen=0. Will try out BitcoinFX's new node now. What I don't have done still is revising the peer list in slimcoin.conf for bad nodes, will do this too and then tell you if I had success.
I'm not sure the cause of this, but if it's a problem with handling orphan blocks then that's not good. Can't have users getting stuck on random points of the blockchain...
Agree, the client is WAY more stable now that some months ago, but this bug is really annoying.