This issue has just popped up on my PC. I was running 0.15.1 without issue. Now at startup I get an error.
MinGW Runtime Assertion
Assertion failed!
Program: D:\Bitcoin Core (64-bit)\bitcoin-0.15.1\bin\bitcoin-qt.exe File: chain.cpp, Line 101
Expression: pindexWalk->pprev
Abort Retry Ignore
The program crashes after that. Removed and reinstalled with new download, same issue. Running on Windows 64-bit Pro v.1703, i7-6700 CPU, 32 GB ram
Can you share the debug.log (or at least the part from right before/after the restart)? I'm betting your chainstate somehow got corrupted.
2017-11-30 07:14:10
2017-11-30 07:14:10 Bitcoin version v0.15.1 2017-11-30 07:14:10 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2017-11-30 07:14:10 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures. 2017-11-30 07:14:10 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a 2017-11-30 07:14:10 Using the 'standard' SHA256 implementation 2017-11-30 07:14:10 Using RdRand as an additional entropy source 2017-11-30 07:14:10 Default data directory C:\Users\Ty\AppData\Roaming\Bitcoin 2017-11-30 07:14:10 Using data directory D:\Bitcoin Core (64-bit)\Bitcoin 2017-11-30 07:14:10 Using config file D:\Bitcoin Core (64-bit)\Bitcoin\bitcoin.conf 2017-11-30 07:14:10 Using at most 125 automatic connections (2048 file descriptors available) 2017-11-30 07:14:10 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 2017-11-30 07:14:10 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2017-11-30 07:14:10 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2017-11-30 07:14:10 Using 4 threads for script verification 2017-11-30 07:14:10 init message: Verifying wallet(s)... 2017-11-30 07:14:10 scheduler thread start 2017-11-30 07:14:10 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2017-11-30 07:14:10 Using wallet wallet.dat 2017-11-30 07:14:10 CDBEnv::Open: LogDir=D:\Bitcoin Core (64-bit)\Bitcoin\database ErrorFile=D:\Bitcoin Core (64-bit)\Bitcoin\db.log 2017-11-30 07:14:10 Cache configuration: 2017-11-30 07:14:10 * Using 2.0MiB for block index database 2017-11-30 07:14:10 * Using 8.0MiB for chain state database 2017-11-30 07:14:10 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2017-11-30 07:14:10 init message: Loading block index... 2017-11-30 07:14:10 Opening LevelDB in D:\Bitcoin Core (64-bit)\Bitcoin\blocks\index 2017-11-30 07:14:10 Opened LevelDB successfully 2017-11-30 07:14:10 Using obfuscation key for D:\Bitcoin Core (64-bit)\Bitcoin\blocks\index: 0000000000000000 2017-12-01 17:01:20
2017-12-01 17:01:20 Bitcoin version v0.15.1 2017-12-01 17:01:20 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2017-12-01 17:01:20 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures. 2017-12-01 17:01:20 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a 2017-12-01 17:01:20 Using the 'standard' SHA256 implementation 2017-12-01 17:01:20 Using RdRand as an additional entropy source 2017-12-01 17:01:20 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 2017-12-01 17:01:20 Default data directory C:\Users\Ty\AppData\Roaming\Bitcoin 2017-12-01 17:01:20 Using data directory D:\Bitcoin Core (64-bit)\Bitcoin 2017-12-01 17:01:20 Using config file D:\Bitcoin Core (64-bit)\Bitcoin\bitcoin.conf 2017-12-01 17:01:20 Using at most 125 automatic connections (2048 file descriptors available) 2017-12-01 17:01:20 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2017-12-01 17:01:20 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2017-12-01 17:01:20 Using 4 threads for script verification 2017-12-01 17:01:20 init message: Verifying wallet(s)... 2017-12-01 17:01:20 scheduler thread start 2017-12-01 17:01:20 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2017-12-01 17:01:20 Using wallet wallet.dat 2017-12-01 17:01:20 CDBEnv::Open: LogDir=D:\Bitcoin Core (64-bit)\Bitcoin\database ErrorFile=D:\Bitcoin Core (64-bit)\Bitcoin\db.log 2017-12-01 17:01:20 Cache configuration: 2017-12-01 17:01:20 * Using 2.0MiB for block index database 2017-12-01 17:01:20 * Using 8.0MiB for chain state database 2017-12-01 17:01:20 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2017-12-01 17:01:20 init message: Loading block index... 2017-12-01 17:01:20 Opening LevelDB in D:\Bitcoin Core (64-bit)\Bitcoin\blocks\index 2017-12-01 17:01:20 Opened LevelDB successfully 2017-12-01 17:01:20 Using obfuscation key for D:\Bitcoin Core (64-bit)\Bitcoin\blocks\index: 0000000000000000 2017-12-01 17:30:35
2017-12-01 17:30:35 Bitcoin version v0.15.1 2017-12-01 17:30:35 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2017-12-01 17:30:35 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures. 2017-12-01 17:30:35 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a 2017-12-01 17:30:35 Using the 'standard' SHA256 implementation 2017-12-01 17:30:35 Using RdRand as an additional entropy source 2017-12-01 17:30:35 Default data directory C:\Users\Ty\AppData\Roaming\Bitcoin 2017-12-01 17:30:35 Using data directory D:\Bitcoin Core (64-bit)\Bitcoin 2017-12-01 17:30:35 Using config file D:\Bitcoin Core (64-bit)\Bitcoin\bitcoin.conf 2017-12-01 17:30:35 Using at most 125 automatic connections (2048 file descriptors available) 2017-12-01 17:30:35 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 2017-12-01 17:30:35 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2017-12-01 17:30:35 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2017-12-01 17:30:35 Using 4 threads for script verification 2017-12-01 17:30:35 scheduler thread start 2017-12-01 17:30:35 init message: Verifying wallet(s)... 2017-12-01 17:30:35 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2017-12-01 17:30:35 Using wallet wallet.dat 2017-12-01 17:30:35 CDBEnv::Open: LogDir=D:\Bitcoin Core (64-bit)\Bitcoin\database ErrorFile=D:\Bitcoin Core (64-bit)\Bitcoin\db.log 2017-12-01 17:30:35 Cache configuration: 2017-12-01 17:30:35 * Using 2.0MiB for block index database 2017-12-01 17:30:35 * Using 8.0MiB for chain state database 2017-12-01 17:30:35 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2017-12-01 17:30:35 init message: Loading block index... 2017-12-01 17:30:35 Opening LevelDB in D:\Bitcoin Core (64-bit)\Bitcoin\blocks\index 2017-12-01 17:30:35 Opened LevelDB successfully 2017-12-01 17:30:35 Using obfuscation key for D:\Bitcoin Core (64-bit)\Bitcoin\blocks\index: 0000000000000000 2017-12-01 18:10:15
2017-12-01 18:10:15 Bitcoin version v0.15.1 2017-12-01 18:10:15 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2017-12-01 18:10:15 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures. 2017-12-01 18:10:15 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a 2017-12-01 18:10:15 Using the 'standard' SHA256 implementation 2017-12-01 18:10:15 Using RdRand as an additional entropy source 2017-12-01 18:10:15 Default data directory C:\Users\Ty\AppData\Roaming\Bitcoin 2017-12-01 18:10:15 Using data directory D:\Bitcoin Core (64-bit)\Bitcoin 2017-12-01 18:10:15 Using config file D:\Bitcoin Core (64-bit)\Bitcoin\bitcoin.conf 2017-12-01 18:10:15 Using at most 125 automatic connections (2048 file descriptors available) 2017-12-01 18:10:15 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 2017-12-01 18:10:15 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2017-12-01 18:10:15 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2017-12-01 18:10:15 Using 4 threads for script verification 2017-12-01 18:10:15 init message: Verifying wallet(s)... 2017-12-01 18:10:15 scheduler thread start 2017-12-01 18:10:15 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2017-12-01 18:10:15 Using wallet wallet.dat 2017-12-01 18:10:15 CDBEnv::Open: LogDir=D:\Bitcoin Core (64-bit)\Bitcoin\database ErrorFile=D:\Bitcoin Core (64-bit)\Bitcoin\db.log 2017-12-01 18:10:15 Cache configuration: 2017-12-01 18:10:15 * Using 2.0MiB for block index database 2017-12-01 18:10:15 * Using 8.0MiB for chain state database 2017-12-01 18:10:15 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2017-12-01 18:10:15 init message: Loading block index... 2017-12-01 18:10:15 Opening LevelDB in D:\Bitcoin Core (64-bit)\Bitcoin\blocks\index 2017-12-01 18:10:15 Opened LevelDB successfully 2017-12-01 18:10:15 Using obfuscation key for D:\Bitcoin Core (64-bit)\Bitcoin\blocks\index: 0000000000000000
If I delete the chainstate will the database need to be re-downloaded?
The easiest way is to run with -reindex, which will re-sync fully but without using the network to re-download blocks (unless you've pruned blocks, in which case it obviously has to).
so i would run it through cmd line then? Can you give me an example? Thanks for your help
Yes, bitcoin-qt.exe -reindex on the cmd prompt should do the trick.
Note to others: likely corruption appears to be that some block index didn't get added on disk. Thus, when LoadBlockIndexGuts insertBlockIndex'd the hashPrev element of its descendant block, a null CBlockIndex was left around in mapBlockIndex until the LoadBlockIndexDB loop eventually called BuildSkip() which blew up. Note that I have no idea why LoadBlockIndexDB seems to half-support having null pprevs after LoadBlockIndexGuts, that should never happen and we blow up anyway, so should probably remove that dead code and turn it into a more useful error message.
Yes, bitcoin-qt.exe -reindex on the cmd prompt should do the trick.
Note to others: likely corruption appears to be that some block index didn't get added on disk. Thus, when LoadBlockIndexGuts insertBlockIndex'd the hashPrev element of its descendant block, a null CBlockIndex was left around in mapBlockIndex until the LoadBlockIndexDB loop eventually called BuildSkip() which blew up. Note that I have no idea why LoadBlockIndexDB seems to half-support having null pprevs after LoadBlockIndexGuts, that should never happen and we blow up anyway, so should probably remove that dead code and turn it into a more useful error message.
I did that in command prompt and all i got was "'bitcoin-qt.exe' is not recognized as an internal or external command, operable program or batch file."
@Jxcwill Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base. Keep in mind that general bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange or the #bitcoin IRC channel on freenode.