Need help with errors

[anon4250158]

I can't seem to get the Core client to work anymore.  I started having problems about 10 days ago with version 9.2.  It kept giving me an "assertion failed" error while executing GetBestBlock() and would shut down.  So I installed 0.9.3.  Same problem.  So I deleted everything and copied a backup from a few days earlier into the folder and tried to run.  Same problem.  So I said F it and redownloaded the entire blockchain for several days.  It is STILL having the problem, with additional ones like "Exception: st9bad_aloc" and "Assertion failed.  Expression: this -> GetLockedPageCount() == 0" and won't load the wallet.  

What is wrong here?  

Is there any way to fix this without downloading the blockchain again?  

If I delete a block .dat file, how can I get the client to load to that point and just update again?


I'm running Windows XP 32-bit in a VM with 2GB memory.

[1714625234]

1714625234

[1714625234]

1714625234

[1714625234]

1714625234

[1714625234]

1714625234

[1714625234]

1714625234

[2112]

Either hardware problem in the VM host or corruption in the VM guest.

Good stress test for the host hardware: http://www.mersenne.org/download/ . If the host passes the test reinstall fresh guest VM from the clean Windows media.

No point in futzing with Bitcoin, just make sure to have a good wallet backup.

Edit: PS: Move this thread to the "Technical Support" forum. "Move" is available to you on the bottom left of the page.

[cr1776]

bad_aloc sounds like a memory issue. Either VM or real memory - 32 bit, 2GB of memory XP, seems likely the culprit. Can you try it on a 64 bit system?

(And this should get moved as above.  :-).  )

[anon4250158]

I've got no memory issues on host, and I created a new VM and it still had the problem.  The issue is with the files somehow.  How can I keep most of the blocks but have Bitcoin Core just download the last few again without reindexing or redownloading the entire blockchain?  What files should I delete/change?

[2112]

I've got no memory issues on host, and I created a new VM and it still had the problem.  The issue is with the files somehow.  How can I keep most of the blocks but have Bitcoin Core just download the last few again without reindexing or redownloading the entire blockchain?  What files should I delete/change?

There is no "issue with the files somehow". There is an issue with your hardware or software. In my limited experience the most common problem with corrupted files on Windows, even with "fresh installs", is caused by the buggy antivirus or security packages. Edit: The second most common is that people who claim "fresh installs" actually don't do a fresh install but some sort of "OEM restore" that riddles the Windows with crapware, which although not malicious is frequently ultra buggy. The true "fresh install" is from non-writable original Microsoft disk or from a writable disk/image with SHA1 verified with MSDN/Technet/other official Microsoft channel source, not through an OEM. End of edit.

Bitcoin lets you be your own bank. Then just be your own bank and put your wallet on a backup computer (you do have a backup computer, right?). You'll quickly learn that you have problem with your primary computer.

[cr1776]

I've got no memory issues on host, and I created a new VM and it still had the problem.  The issue is with the files somehow.  How can I keep most of the blocks but have Bitcoin Core just download the last few again without reindexing or redownloading the entire blockchain?  What files should I delete/change?

Bad_alloc (or bad_aloc - assuming that is really the message, often it is "st9bad_alloc" or "bad_alloc" with two Ls) is a memory problem.  Bitcoin can not allocate memory when it needs it.  Saying "I've not go memory issues on host" just means that you are not understanding the meaning of the error message.  For some reason, it is running out of memory when it goes to allocate memory.   It could be something corrupted in your copy of the blockchain or it could just be running out of memory for some other reason (the junk of which 2112 was speaking).

As I asked before, can you run it on a 64 bit system and one with more memory?  Was the new VM the same as the old one?  I bet that if you created a new 64 bit VM with 4GB you wouldn't see the issue.

e.g.
http://lmgtfy.com/?q=st9bad_alloc