Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bitcoin-qt.exe fatal error - NSt8ios_base7faillureE - ReadCompactSize() #1513

Closed
nanpanman opened this issue Jun 24, 2012 · 6 comments
Closed
Labels

Comments

@nanpanman
Copy link

When running the windows client 0.62 I get the following error shortly after the ''Loading Block Index...' screen:

A fatal error occured. Bitcoin can no longer continue safely and will quit.

EXCEPTION: NSt8ios_base7faillureE
ReadCompactSize(): size too large

Problem signature:
Problem Event Name: APPCRASH
Application Name: bitcoin-qt.exe
Application Version: 0.0.0.0
Application Timestamp: 4d44aa00
Fault Module Name: bitcoin-qt.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4d44aa00
Exception Code: 40000015
Exception Offset: 00ef4e1a
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 6153
Additional Information 1: c4bb
Additional Information 2: c4bb9ef13a8851680a056abd266bba35
Additional Information 3: 1095
Additional Information 4: 109595c20661a244f0b8c7c7a7fb1aa5

Running 0.62 on Win7, can send debug.log over if needed.

@gavinandresen
Copy link
Contributor

Your blk0001.dat or blkindex.dat file got corrupted somehow (did you run out of disk space perhaps?). To recover, backup your wallet.dat file, remove everything except for wallet.dat from the bitcoin data directory, and re-run.

Keeping this bug open, because it would be good to at least report a helpful error message in cases like this, and even better if bitcoin could recover itself. Pieter and Mike have both been working on complete re-writes of the block database, though, so spending time working on the current way we're doing things might be a waste of time.

@nanpanman
Copy link
Author

Thanks Gavin.

This error has been happening to me every couple of months going back to maybe September 2011. I've always upgraded to the latest version hoping the bug would be gone (including clean re-installs) but for some reason I always comes back. It is a pain since the only way to recover is to delete all the block-chain files and re-download. My wallet was never affected though.

I don't think I ran out of space (although space is tight - I'm running on a 64GB SSD). Perhaps it has to do with the fact that I always send my laptop into 'sleep' mode while running the bitcoin client in the background?

Good to hear a rewrite of the block db is on the way. Sounds like that might fix the issue.

@nanpanman
Copy link
Author

Speaking of the devil - the bitcoin client just unexpectedly crashed on me again. I have 5.54GB Free space on my SSD.

Debug.log:

http://dl.dropbox.com/u/1007482/debug.log

Error:

Problem signature:
Problem Event Name: APPCRASH
Application Name: bitcoin-qt.exe
Application Version: 0.0.0.0
Application Timestamp: 4d44aa00
Fault Module Name: bitcoin-qt.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4d44aa00
Exception Code: 40000015
Exception Offset: 00efd58a
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 6153
Additional Information 1: e403
Additional Information 2: e403e395f61488c484a049fbfa26e55d
Additional Information 3: fdd5
Additional Information 4: fdd5fe2be60a02ae15c676188e0d931d

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I am able to restart the client without errors this time though, so it could be unrelated/different bug.

@burger2
Copy link
Contributor

burger2 commented Mar 29, 2013

@nanpanman still got the problem?

@nanpanman
Copy link
Author

No. I moved to a new computer no issues since. The previous one had an SSD
that got progressively more corrupted so that might have been the culprit.
On Mar 29, 2013 3:53 PM, "Birger Hedman" notifications@github.com wrote:

@nanpanman https://github.com/nanpanman still got the problem?


Reply to this email directly or view it on GitHubhttps://github.com//issues/1513#issuecomment-15664454
.

@laanwj laanwj closed this as completed Nov 4, 2013
@Ambrose94
Copy link

@nanpanman hello, today I also have the same problem, when I try to transfer the bitcoin, the software was crashed and reminded the "A fatal error occured. Bitcoin can no longer continue safely and will quit.",I have the wallet.dat file, could you tell me how did you solve the problem?thanks much

suprnurd pushed a commit to chaincoin-legacy/chaincoin that referenced this issue Dec 5, 2017
* add masternodelist info call

* safe version conversion function

* change default sentinel version value

* fix issues
lateminer pushed a commit to lateminer/bitcoin that referenced this issue Jan 22, 2019
…ckDependencyOrdering (bitcoin#1513)

* Add more log info to "missing or spent" error condition in ConnectBlockDependencyOrdering

Add block hash, txid and input index to "missing or spent" error condition
ConnectBlockDependencyOrdering. It is already the case for ConnectBlockCanonicalOrdering
so this change is going to gave the same amount of useful info for both cases
(CTOR and TTOR).

* Reword "missing or spent" error log message.

* Add block hash to error log messages in ConnectBlock{Dependency,Canonical}Ordering

* Remove dead code from ConnectBlock{Dependency,Canonical}Ordering()

* Miss using __func__ in one ConnectBlockDependencyOrder() log statement
lateminer pushed a commit to lateminer/bitcoin that referenced this issue May 6, 2020
8af3ceb [Trivial] Remove CMasternode::SliceHash (random-zebra)

Pull request description:

  Removes un-used function  `SliceHash` (which is also buggy and overflowing,
  trying to copy 64 bytes to a destination buffer having only 8 bytes).

ACKs for top commit:
  Fuzzbawls:
    ACK 8af3ceb
  furszy:
    ACK 8af3ceb

Tree-SHA512: 70b194196bdc8ac216fc363ba347c77c75492ca2e432458bfa8f0aeeda09f90d401781771da5dec33c44a19a07921ea160787bfbb8b02d5c7193e0c50e64060f
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants