Author

Topic: [Resolved] Bitcoin Core assertion failed error? (Read 296 times)

copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
You got it right there Achow.

I couldn't work out the issue so I just had to delete the bitcoin folder and start again, I think it was something important as the obfuscation key didn't seem valid.
staff
Activity: 3458
Merit: 6793
Just writing some code
This error means that something in the database is missing a value that it should have. This is likely due to database corruption which can occur many different ways. Try reindexing the database and see if Bitcoin Core is able to rebuild the databases correctly.
legendary
Activity: 1624
Merit: 2481
You might have a corrupted HDD/SSD there is an old thread here that solve this issue by reinstalling the bitcoin core.

To quickly check that, download a tool which reads out the S.M.A.R.T. values of your hard drive.

For windows, you can use HDD Health or CrystalDiskInfo. Both are able to exactly show you what the problem with your HD is (if any at all).

Might be faster than reinstalling core, and you will know whether you have to backup your whole drive / buy a new one.
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
You might have a corrupted HDD/SSD there is an old thread here that solve this issue by reinstalling the bitcoin core.

And another thread by backing up the wallet.dat and transfer it to another PC with bitcoin core.

Check this thread here https://bitcointalksearch.org/topic/hard-drive-corrupted-but-have-walletdat-problem-importing-dat-on-2nd-computer-3090431
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Jump to solution

I'm getting an on the startup screen of an error that says there's an issue at line 102 of bitcoin-qt "pindexWalk->pprev" I just downloaded the latest version v0.18.0.

In the debug log, everything goes as normal and it gets to the point where it uses the obfuscation key, the key used is zero though which seems odd.

I'm on windows 7 sp1.
Jump to: