<p>From your debug.log file, you can see these lines:</p>

<pre><code>018-03-28 18:05:07 LevelDB read failure: Corruption: block checksum mismatch
2018-03-28 18:05:07 Corruption: block checksum mismatch
</code></pre>

<p>Typically this error is caused by faulty hardware. There have been a number of reports on github of the same issue, for example <a href="https://github.com/bitcoin/bitcoin/issues/10897" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/issues/10897</a></p>

<p>So nothing wrong with the software, you just have poor quality hardware :)</p>

CC BY-SA 3.0
2018-03-28T21:02:02.443Z
2018-03-28T21:02:02.443Z
meshcollider
<p>Thanks, that was helpful. </p>

<p>Now, I have never had a problem with that computer. Can't remember it blue screening a single time. So the question was, why was Bitcoin Core synchronization causing hardware failures? </p>

<p>From experience, I know unexpected hardware problems are usually a result of a system stretched to the limit, but neither CPU usage nor hard disk access was operating around 100%. So I downloaded <a href="http://openhardwaremonitor.org/downloads/" rel="nofollow noreferrer" title="Open Hardware Monitor">Open Hardware Monitor</a> (No plug here. I have no stake in this application) and started snooping around. Among other things, it provides current temperature information about the CPU and some other components. I noticed even though CPU wasn't running anywhere close to 100% capacity its operating temperature was hovering around its limit with synchronization running. </p>

<p>I realized I needed to figure out a way to keep the temperature under control. I am running Bitcoin Core on an Intel NUC, which is tiny and I figured the internal cooling wasn't up to snuff. So I blasted away a table fan on the computer and let it rip. Sure enough, operating temperature started staying reasonably below the limit. I also shut off the Bitcoin Core for 3-4 minutes every few hours to let the CPU cool down (I don't think that was necessary, but I wasn't taking any chances). In the end, it took some extra effort and monitoring, but block synchronization is now completed. My Bitcoin Core Wallet is up-to-date.</p>

<p>Thanks for your help again MeshCollider. </p>

CC BY-SA 3.0
2018-04-01T23:04:20.673Z
2018-04-01T23:04:20.673Z
Rahul Deshmukh
<p>Trying to set up Bitcoin Core Wallet. </p>

<p>I've started blockchain synchronization 4 times and each time it has reached a certain percentage and then failed. I've followed instructions on the website, tried running it in pruned mode, tried running it with reindex. Is anyone else facing the same problem?</p>

<p>Worse still, it restarts downloading every block after it fails. Any ideas? Is there a way to force a restart at a location. This is very frustrating. And have to say this is poor quality software. Bitcoin has no future if just setting up a full wallet is so difficult.  </p>

<p><a href="https://1drv.ms/u/s!Arm8w0Wz3u8DvIFOYA59z3wveNOyOQ" rel="nofollow noreferrer">Debug.log</a> </p>

CC BY-SA 3.0
2018-03-28T19:24:23.727Z
Could you please upload your debug.log file so we can help diagnose the issue?
meshcollider
CC BY-SA 3.0
2018-03-28T20:56:25.053Z
Thanks. I've updated the question with a link to zipped log file
Rahul Deshmukh
<bitcoin-core><wallet><debugging>
Setting up Bitcoin Core Wallet
Rahul Deshmukh
# Setting up Bitcoin Core Wallet

(Asked by: username_0 on 2018-03-28)

Trying to set up Bitcoin Core Wallet.

I've started blockchain synchronization 4 times and each time it has reached a certain percentage and then failed. I've followed instructions on the website, tried running it in pruned mode, tried running it with reindex. Is anyone else facing the same problem?

Worse still, it restarts downloading every block after it fails. Any ideas? Is there a way to force a restart at a location. This is very frustrating. And have to say this is poor quality software. Bitcoin has no future if just setting up a full wallet is so difficult.

[Debug.log](https://1drv.ms/u/s!Arm8w0Wz3u8DvIFOYA59z3wveNOyOQ)

**Tags:** bitcoin-core, wallet, debugging

> **Comments:**
> **username_1**: Could you please upload your debug.log file so we can help diagnose the issue?  
> **username_0**: Thanks. I've updated the question with a link to zipped log file  

---

## 2 answers

### Answer by username_1 on 2018-03-28. Score: 2

From your debug.log file, you can see these lines:

```
018-03-28 18:05:07 LevelDB read failure: Corruption: block checksum mismatch
2018-03-28 18:05:07 Corruption: block checksum mismatch

```

Typically this error is caused by faulty hardware. There have been a number of reports on github of the same issue, for example <https://github.com/bitcoin/bitcoin/issues/10897>

So nothing wrong with the software, you just have poor quality hardware :)


---

### Answer by username_0 on 2018-04-01. Score: 1

Thanks, that was helpful.

Now, I have never had a problem with that computer. Can't remember it blue screening a single time. So the question was, why was Bitcoin Core synchronization causing hardware failures?

From experience, I know unexpected hardware problems are usually a result of a system stretched to the limit, but neither CPU usage nor hard disk access was operating around 100%. So I downloaded [Open Hardware Monitor](http://openhardwaremonitor.org/downloads/ "Open Hardware Monitor") (No plug here. I have no stake in this application) and started snooping around. Among other things, it provides current temperature information about the CPU and some other components. I noticed even though CPU wasn't running anywhere close to 100% capacity its operating temperature was hovering around its limit with synchronization running.

I realized I needed to figure out a way to keep the temperature under control. I am running Bitcoin Core on an Intel NUC, which is tiny and I figured the internal cooling wasn't up to snuff. So I blasted away a table fan on the computer and let it rip. Sure enough, operating temperature started staying reasonably below the limit. I also shut off the Bitcoin Core for 3-4 minutes every few hours to let the CPU cool down (I don't think that was necessary, but I wasn't taking any chances). In the end, it took some extra effort and monitoring, but block synchronization is now completed. My Bitcoin Core Wallet is up-to-date.

Thanks for your help again MeshCollider.


---

