I have yet to run a disk checker, I would be surprised if there was a problem physically with my disk, but I will soon.
I was out of town for a few days and core ran perfectly the whole time. Once I got home and started using my computer again I kept receiving "fatal errors" and the log shows db corruption, to the point where it wouldn't even finish loading the program/checking the blockchain/verify my wallet without erroring and freezing up. I uninstalled 0.10.1 this morning, deleted the blockchain, reinstalled, and am now re-indexing. Hopefully that clears it up.
Topic: Bitcoin Core: internal fatal error, help! (Read 3398 times)
It's been running flawlessly for days now, no indication of the error happening again. Might have been a one time, well two time, thing...
The Force was not strong with you on Star Wars Day, obviously!Try running a disk checker to verify your drive is good (to Soros Shorts' point).
'Have you tried turning it off and on again?'
:-)
:-)
It's been running flawlessly for days now, no indication of the error happening again. Might have been a one time, well two time, thing...
It says "database corrupted" when it crashed while verifying blocks. However, it loaded fine the second time. This could mean that your hard drive has marginally bad sectors (or you might have a poor quality SSD, but my experience with bad SSDs is that the entire drive usually goes offline).
That's strange, can't say I've seen the message before but as mentioned above perhaps close apps that might be a conflict? also try another version as a method of troubleshooting.
Been running fine since it started up again last night.
It's not antivirus, and I never close core without waiting.
Yes, it could be any number of things, but the error from the log are pretty specific and I'm hoping someone can extract from that what happened.
I do not know how to run in a VM, what would that accomplish?
I always back my wallets up.
It's not antivirus, and I never close core without waiting.
Yes, it could be any number of things, but the error from the log are pretty specific and I'm hoping someone can extract from that what happened.
I do not know how to run in a VM, what would that accomplish?
I always back my wallets up.
Well, if you ran it in VM (such as VirtualPC, VMware, etc) and it worked, then it would mean it's some program (antivirus or something) that is running on your main system.
I don't know anything about Bitcoin errors.
Maybe you should post it in technical discussion sub-forum.
Been running fine since it started up again last night.
It's not antivirus, and I never close core without waiting.
Yes, it could be any number of things, but the error from the log are pretty specific and I'm hoping someone can extract from that what happened.
I do not know how to run in a VM, what would that accomplish?
I always back my wallets up.
It's not antivirus, and I never close core without waiting.
Yes, it could be any number of things, but the error from the log are pretty specific and I'm hoping someone can extract from that what happened.
I do not know how to run in a VM, what would that accomplish?
I always back my wallets up.
Can you run it in VM?
Also, did you make a backup of your wallet.dat?
That is the most important thing to do BEFORE you try anything.
Also, did you make a backup of your wallet.dat?
That is the most important thing to do BEFORE you try anything.
it's not unstable, but sometime there are conflict with other programs maybe antivirus, or inside your roaming something is corrupted(you have closed core without waiting ecc...), it could be many things
I am using the release version, what is unstable about it?
You are using unstable release 0.11, so no wonder it crashed.
Good that you managed to mitigate problem
, but unstable releases should be only used as bug hunting.
Good that you managed to mitigate problem
, but unstable releases should be only used as bug hunting.
Core v0.10.1 crashed on me today, this time with an error window stating fatal internal error, see debug.log. Here is the offending entry, after which Core terminated:
An hour later I tried restarting Core and got the exact same error while it was starting up and verifying blocks. I am attempting to start it again. What is this error, what caused it, and how do I fix it?
Edit: This time it restarted and verified all blocks just fine. Still curious if there's any insight on the initial error(s).
Code:
2015-05-05 01:16:34 receive version message: /Satoshi:0.8.1/: version 70001, blocks=308691, us=66.215.192.104:8333, peer=1372
2015-05-05 01:16:34 Added time data, samples 200, offset -3532 (-58 minutes)
2015-05-05 01:16:34 msghand thread interrupt
2015-05-05 01:16:34 Shutdown: In progress...
2015-05-05 01:16:34 StopRPCThreads: Warning: The attempted operation is not supported for the type of object referenced when cancelling acceptorStopNode()
2015-05-05 01:16:34 Corruption: block checksum mismatch
2015-05-05 01:16:34 *** System error while flushing: Database corrupted
GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed
2015-05-05 01:18:26 Shutdown: In progress...
2015-05-05 01:18:26 StopNode()
2015-05-05 01:18:26 Shutdown: done
2015-05-05 01:19:37 Shutdown: done
2015-05-05 01:19:52 GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed
2015-05-05 01:19:52
2015-05-05 01:16:34 Added time data, samples 200, offset -3532 (-58 minutes)
2015-05-05 01:16:34 msghand thread interrupt
2015-05-05 01:16:34 Shutdown: In progress...
2015-05-05 01:16:34 StopRPCThreads: Warning: The attempted operation is not supported for the type of object referenced when cancelling acceptorStopNode()
2015-05-05 01:16:34 Corruption: block checksum mismatch
2015-05-05 01:16:34 *** System error while flushing: Database corrupted
GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed
2015-05-05 01:18:26 Shutdown: In progress...
2015-05-05 01:18:26 StopNode()
2015-05-05 01:18:26 Shutdown: done
2015-05-05 01:19:37 Shutdown: done
2015-05-05 01:19:52 GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed
2015-05-05 01:19:52
An hour later I tried restarting Core and got the exact same error while it was starting up and verifying blocks. I am attempting to start it again. What is this error, what caused it, and how do I fix it?
Edit: This time it restarted and verified all blocks just fine. Still curious if there's any insight on the initial error(s).
Jump to: