Failed to read block, and no, "-checklevel=2" doesn't help..

[kerubi]

Updated to latest 0.8.4 client, get that "failed to read block error" no matter what. Tried going back 0.8.3,0.8.1 even.

Adding -checklevel=2 in the shortcut or bitcoin.conf doesn't help. My SSD HDD is working fine.

So what gives?

[favdesu]

could you post a screenshot of you modified shortcut settings? I did it and it works just fine

edit: does it look like this?

[Dare]

Isn't it supposed to be "--checklevel=2", with 2 dashes? I'm not sure if it matters though, and the config file doesn't need dashes, so that's probably not your problem (but is worth a try).

Also, the transaction causing that bug is now far enough down that it doesn't trigger the error anymore even without that command, though forcing a rescan might still do it.

[kerubi]

Yes, my shortcut is exactly like that, tried both --checklevel=2 and -checklevel=2.

And in my C:\Users\<username>\AppData\Roaming\Bitcoin\bitcoin.conf I have these lines:
checklevel=2
dbcache=3000

Still now "failed to read data" right after starting, syncs perhaps two weeks of data. Tried deleting db, antivirus off, etc.

[Dare]

Have you tried backing up your wallet and reinstalling 0.8.4?

[kerubi]

Well, now it is syncing.. after multiple restarts and database deletions, the only thing I could pin this on was quite a strange thing.. If I clicked the client window active, it would fail to read block. If I would not touch it, it very slowly synced. So I let it run all night and it slowly made progress. Now it seems to work even if I click the window. Strange, all I can say