Topic: Fatal Error in Bitcoin Core Windows x64 (Read 838 times)
Your blockchain is probably corrupted. Try resyncing the entire blockchain by renaming the blocks and chainstate folders in the Bitcoin datadir to something else (e.g. blocks -> blocks-bak and chainstate -> chainstate-bak). The renaming will make Bitcoin Core think those folders don't exist, but still keep them around in case you want to revert back to using them. If Bitcoin Core syncs, then you can delete those folders.
No errors reported on the memory test and none on the HD it is installed on. I tried replacing my wallet file with a backup wallet file I made and it also fataled while syncing. Any other ideas?
Considering you have so much RAM and CPUs, depending on how long it takes to do the reindex before the database fails, can you load the bitcoin core with the -debug command to get more detailon what the error is specifically and post the log here.
Also go to the computer management tool on windows 10 and see if there are any highly urgent recent data memory corruptions (If you shut your computer down, do you ever get an app called CHKDSK that runs and if so, how often)?
EDIT: any problems found in the diagnostics programmes running will also be in the computer management software (search for event logs). Could you suggest the diagnostic tool you're using for the hard drives and the other hardware)? Also, do you have the debug.log for the entire session in the OP, there may be something that can be picked up about if there is anything else that causes and issue that is ignored, such as a corrupted peers.dat file as I understand that bitcoin core would just make a new file and ignore that issue but it'd suggest a greater hard drive problem.
No errors reported on the memory test and none on the HD it is installed on. I tried replacing my wallet file with a backup wallet file I made and it also fataled while syncing. Any other ideas?
Do you really have that much RAM or is it some kind of a bug?
Are you running a supercomputer by any chance?
128 GB of RAM is some serious business.
Are you running a supercomputer by any chance?
128 GB of RAM is some serious business.
Yes, it does
Two sets of Dominator Platinum 64GB
Well, congrats! You can maybe store an entire blockchain in RAM.
It would be a fastest node I ever heard of.
Lol thanks. If I could get it to work maybe I'll make a RAM DISK and do it. For now I would love to get the thing to load and solve the corrupted database issue.
Do you really have that much RAM or is it some kind of a bug?
Are you running a supercomputer by any chance?
128 GB of RAM is some serious business.
Are you running a supercomputer by any chance?
128 GB of RAM is some serious business.
Yes, it does
Two sets of Dominator Platinum 64GB
Well, congrats! You can maybe store an entire blockchain in RAM.
It would be a fastest node I ever heard of.
Do you really have that much RAM or is it some kind of a bug?
Are you running a supercomputer by any chance?
128 GB of RAM is some serious business.
Are you running a supercomputer by any chance?
128 GB of RAM is some serious business.
Yes, it does
Two sets of Dominator Platinum 64GB
Do you really have that much RAM or is it some kind of a bug?
Are you running a supercomputer by any chance?
128 GB of RAM is some serious business.
Are you running a supercomputer by any chance?
128 GB of RAM is some serious business.
Memory: 131072MB RAM
Available OS Memory: 130906MB RAM
Page File: 8038MB used, 142324MB available
Wow, thats a lot of ram.Available OS Memory: 130906MB RAM
Page File: 8038MB used, 142324MB available
It might be a hardware failure of some sort. Can you run a memory diagnostic test on both your HDD and Ram? It might be a sign of hardware failure. Can you also ensure that you copy the wallet.dat to a safe place, and check that its there. Then, delete the whole data directory and synchronize again.
I am running a memory diagnostics today while I am at work to see if there is an issue there. I can then run a diagnostics on the PCie SSD drive, but it has an app that runs in windows and constantly runs diagnostics on it and it hasn't said anything.
Memory: 131072MB RAM
Available OS Memory: 130906MB RAM
Page File: 8038MB used, 142324MB available
Wow, thats a lot of ram.Available OS Memory: 130906MB RAM
Page File: 8038MB used, 142324MB available
It might be a hardware failure of some sort. Can you run a memory diagnostic test on both your HDD and Ram? It might be a sign of hardware failure. Can you also ensure that you copy the wallet.dat to a safe place, and check that its there. Then, delete the whole data directory and synchronize again.
Yesterday I started getting a Fatal Error in the BTC core. I have tried to delete the .lock file. I have tried running it as an administrator. I have tried setting permissions of the folders with my account as the owner and full none inherited permissions, and lastly, I tried running the client with the -reindex command.
Bitcoin Core 14.2 x64
Operating System: Windows 10 Pro 64-bit (10.0, Build 15063) (15063.rs2_release.170317-1834)
System Manufacturer: Gigabyte Technology Co., Ltd.
BIOS: F5f
Processor: Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz (16 CPUs), ~3.2GHz
Memory: 131072MB RAM
Available OS Memory: 130906MB RAM
Page File: 8038MB used, 142324MB available
Can't show transactions as it fatals out before I can get them.
Any help, please! I have a backup from 5-29-2017 and I have backup up the wallet before it has fataled out, but I don't know if that DAT file is also corrupt.
Thanks!
Overcon
Bitcoin Core 14.2 x64
Operating System: Windows 10 Pro 64-bit (10.0, Build 15063) (15063.rs2_release.170317-1834)
System Manufacturer: Gigabyte Technology Co., Ltd.
BIOS: F5f
Processor: Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz (16 CPUs), ~3.2GHz
Memory: 131072MB RAM
Available OS Memory: 130906MB RAM
Page File: 8038MB used, 142324MB available
Can't show transactions as it fatals out before I can get them.
Code:
2017-09-08 03:38:53 UpdateTip: new best=0000000000000000011ceaabea8329b4d1c070a84f468b825376c3f74bbe9377 height=484109 version=0x20000000 log2_work=87.065625 tx=252812213 date='2017-09-08 03:01:52' progress=0.999972 cache=304.7MiB(232927tx)
2017-09-08 03:38:53 receive version message: /Satoshi:0.14.2/: version 70015, blocks=484115, us=68.233.158.163:50187, peer=7
2017-09-08 03:38:54 Corruption: block checksum mismatch
2017-09-08 03:38:54 *** System error while flushing: Database corrupted
2017-09-08 03:39:05 tor: Thread interrupt
2017-09-08 03:39:05 torcontrol thread exit
2017-09-08 03:39:05 addcon thread exit
2017-09-08 03:39:05 opencon thread exit
2017-09-08 03:39:05 scheduler thread interrupt
2017-09-08 03:39:05 Shutdown: In progress...
2017-09-08 03:39:05 net thread exit
2017-09-08 03:39:05 msghand thread exit
2017-09-08 03:39:05 Corruption: block checksum mismatch
2017-09-08 03:39:05 *** System error while flushing: Database corrupted
2017-09-08 03:39:07 Shutdown: done
2017-09-08 03:45:13
2017-09-08 03:38:53 receive version message: /Satoshi:0.14.2/: version 70015, blocks=484115, us=68.233.158.163:50187, peer=7
2017-09-08 03:38:54 Corruption: block checksum mismatch
2017-09-08 03:38:54 *** System error while flushing: Database corrupted
2017-09-08 03:39:05 tor: Thread interrupt
2017-09-08 03:39:05 torcontrol thread exit
2017-09-08 03:39:05 addcon thread exit
2017-09-08 03:39:05 opencon thread exit
2017-09-08 03:39:05 scheduler thread interrupt
2017-09-08 03:39:05 Shutdown: In progress...
2017-09-08 03:39:05 net thread exit
2017-09-08 03:39:05 msghand thread exit
2017-09-08 03:39:05 Corruption: block checksum mismatch
2017-09-08 03:39:05 *** System error while flushing: Database corrupted
2017-09-08 03:39:07 Shutdown: done
2017-09-08 03:45:13
Any help, please! I have a backup from 5-29-2017 and I have backup up the wallet before it has fataled out, but I don't know if that DAT file is also corrupt.
Thanks!
Overcon
Jump to: