[error] A fatal internal error occurred, see debug.log for details: System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: C:\Bitcoin Core\chainstate/1131523.ldb

josephgal007 commented at 2:44 pm on March 18, 2026: none

Is there an existing issue for this?

I have searched the existing issues

Current behaviour

debug.log

This error is occurring frequently now.

Expected behaviour

no errors like this.

Steps to reproduce

error occurs again after restarting bitcoin core

Relevant log output

No response

How did you obtain Bitcoin Core

Pre-built binaries

What version of Bitcoin Core are you using?

Bitcoin Core version v30.2.0

Operating system and version

Windows 11

Machine specifications

maflcko commented at 2:49 pm on March 18, 2026: member

Bitcoin Core makes heavy use of CPU, RAM and storage IO. Hardware defects might only become visible when running Bitcoin Core. You might want to check your hardware for defects.

Use software such as memtest86 to check your RAM.
Use software such as linpack, or Prime95 to check the CPU behaviour under load.
Use software such as smartctl, fsck, badblocks, or CrystalDiskInfo to test your storage device use.

Source: https://bitcoin.stackexchange.com/a/12206

maflcko added the label Data corruption on Mar 18, 2026

maflcko added the label Questions and Help on Mar 18, 2026

josephgal007 commented at 8:14 pm on March 18, 2026: none

I did a power down and restart which resolved the issue. Thanks for your reply.

Thanks,

Joseph Gal

On Wed, Mar 18, 2026 at 10:51 AM maflcko @.***> wrote:

maflcko left a comment (bitcoin/bitcoin#34851) https://github.com/bitcoin/bitcoin/issues/34851#issuecomment-4083144387

Bitcoin Core makes heavy use of CPU, RAM and storage IO. Hardware defects might only become visible when running Bitcoin Core. You might want to check your hardware for defects.

Use software such as memtest86 to check your RAM.

Use software such as linpack, or Prime95 to check the CPU behaviour under load.

Use software such as smartctl, fsck, badblocks, or CrystalDiskInfo to test your storage device use.

Source: https://bitcoin.stackexchange.com/a/12206

— Reply to this email directly, view it on GitHub https://github.com/bitcoin/bitcoin/issues/34851#issuecomment-4083144387, or unsubscribe https://github.com/notifications/unsubscribe-auth/CAGA3WBWFBPKBSNUBG5SHLT4RKZXNAVCNFSM6AAAAACWWRPZF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBTGE2DIMZYG4 . You are receiving this because you authored the thread.Message ID: @.***>

l0rinc commented at 8:28 pm on March 18, 2026: contributor

I don’t think a restart can fix the failure - you had a local chainstate LevelDB corruption during flushing https://github.com/bitcoin/bitcoin/blob/20a6babfa9a66f5432ef19c6c433b4357560f853/src/leveldb/table/format.cc#L92

This will likely happen again if the source of the problem is indeed faulty hardware - which we assume is the case here.

josephgal007 commented at 8:42 pm on March 18, 2026: none

Ok, I’ll run those hardware checks you suggested.

Thanks,

Joseph Gal

On Wed, Mar 18, 2026 at 4:28 PM l0rinc @.***> wrote:

l0rinc left a comment (bitcoin/bitcoin#34851) https://github.com/bitcoin/bitcoin/issues/34851#issuecomment-4085383763

I don’t think a restart can fix the failure - you had a local chainstate LevelDB corruption during flushing https://github.com/bitcoin/bitcoin/blob/20a6babfa9a66f5432ef19c6c433b4357560f853/src/leveldb/table/format.cc#L92

This will likely happen again if the source of the problem is indeed faulty hardware - which we assume is the case here.

— Reply to this email directly, view it on GitHub https://github.com/bitcoin/bitcoin/issues/34851#issuecomment-4085383763, or unsubscribe https://github.com/notifications/unsubscribe-auth/CAGA3WCFSUYA2KK2RSRGXTT4RMBHZAVCNFSM6AAAAACWWRPZF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBVGM4DGNZWGM . You are receiving this because you authored the thread.Message ID: @.***>

maflcko commented at 5:21 am on March 19, 2026: member

Ok, I’ll run those hardware checks you suggested.

Sounds good. A few other things to check:

Is the machine self-built? What is the power supply?
Are any components external? External storage device?

In any case, I’ll close this issue for now. Discussion can still continue normally, but there is no need to keep it open.

maflcko closed this on Mar 19, 2026

josephgal007 commented at 3:28 pm on March 19, 2026: none

Purchased on a amazon.com. Its a Beelink Mini S13 Mini PC,13th Intel Twin Lake-N150 (up to 3.6GHz, Upgraded N100), 16GB DDR4 500GB M.2 SSD, Mini Desktop Computer Support 4K Dual Display/USB 3.2/WiFi 6/BT 5.2.
No external devices are connected, and it is currently running only as a pruned node.

Thanks,

Joseph Gal

On Thu, Mar 19, 2026 at 1:21 AM maflcko @.***> wrote:

maflcko left a comment (bitcoin/bitcoin#34851) https://github.com/bitcoin/bitcoin/issues/34851#issuecomment-4087888618

Ok, I’ll run those hardware checks you suggested.

Sounds good. A few other things to check:

Is the machine self-built? What is the power supply?

Are any components external? External storage device?

In any case, I’ll close this issue for now. Discussion can still continue normally, but there is no need to keep it open.

— Reply to this email directly, view it on GitHub https://github.com/bitcoin/bitcoin/issues/34851#issuecomment-4087888618, or unsubscribe https://github.com/notifications/unsubscribe-auth/CAGA3WFOZHI4HSKAFLRUCFD4RN7W5AVCNFSM6AAAAACWWRPZF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBXHA4DQNRRHA . You are receiving this because you authored the thread.Message ID: @.***>

[error] A fatal internal error occurred, see debug.log for details: System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: C:\Bitcoin Core\chainstate/1131523.ldb #34851

Is there an existing issue for this?

Current behaviour

Expected behaviour

Steps to reproduce

Relevant log output

How did you obtain Bitcoin Core

What version of Bitcoin Core are you using?

Operating system and version

Machine specifications