<p>It is possible that you are running out of RAM or HDD space.  Check <a href="https://github.com/bitcoin/bitcoin/issues/6196" rel="nofollow">this</a> github report from a user with a similar issue.  If this is not the case then I would run a memtest and see if you don't have an issue with your RAM.</p>

CC BY-SA 3.0
2016-03-16T23:59:44.797Z
Hi Mark, thanks for the quick reply! I have 90Gb of free space on HDD and will try a RAM memtest next. Will update this post when thats complete
Ragnarok
CC BY-SA 3.0
2016-03-23T03:16:51.853Z
Hello again, I tried to use a RAM test software and mounted its image onto a USB stick. I followed their instructions it and after I went to enter set up, i could see it there under BOOT section but could not activate it when it was highlighted. I pressed enter when it was high lighted and nothing happened. If anyone can recommend another course of action to correct the problem as seen in the JPEG above, please give us your take on this.
Ragnarok
CC BY-SA 3.0
2016-03-16T19:01:48.557Z
2016-03-16T19:01:48.557Z
Mark S.
<p>I am experiencing a recurring problem with my BitCoin Core wallet. The main issue here is that I get an error message every so often as the program is updating the transaction blocks. <a href="https://i.sstatic.net/PQFlE.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/PQFlE.jpg" alt="Assertion failed error"></a></p>

<p>Please see the jpeg in the link above, this is the exact error message I get when the client is updating.</p>

<p>Details:</p>

<ol>
<li><p>I am using BitCoin Core V 12.0</p></li>
<li><p>I have tried reindexing using : c:\Program Files\Bitcoin\bitcoin-qt.exe -reindex</p></li>
<li><p>I have tried to reinstall the client, then restart my computer, then open and let it update.</p></li>
<li><p>I haven't yet tried a RAM test to see if my RAM could be the source of corrupted data</p></li>
<li><p>I'm running Windows 7 OS 64-bit, 8Gb DDR3 RAM</p></li>
</ol>

<p>I feel its something that can be fixed with a patch, but I could be wrong. If anyone has a solution that I can try myself, that would be most welcome. </p>

<wallet><bitcoin-core><block><synchronization>
BitCoin Core Error Message: "Assertion failed!"
Ragnarok
# BitCoin Core Error Message: "Assertion failed!"

(Asked by: username_0 on 2016-03-16)

I am experiencing a recurring problem with my BitCoin Core wallet. The main issue here is that I get an error message every so often as the program is updating the transaction blocks. [![Assertion failed error](https://i.sstatic.net/PQFlE.jpg)](https://i.sstatic.net/PQFlE.jpg)

Please see the jpeg in the link above, this is the exact error message I get when the client is updating.

Details:

1. I am using BitCoin Core V 12.0
2. I have tried reindexing using : c:\Program Files\Bitcoin\bitcoin-qt.exe -reindex
3. I have tried to reinstall the client, then restart my computer, then open and let it update.
4. I haven't yet tried a RAM test to see if my RAM could be the source of corrupted data
5. I'm running Windows 7 OS 64-bit, 8Gb DDR3 RAM

I feel its something that can be fixed with a patch, but I could be wrong. If anyone has a solution that I can try myself, that would be most welcome.

**Tags:** wallet, bitcoin-core, block, synchronization


---

## 1 answers

### Answer by username_1 on 2016-03-16. Score: 1

It is possible that you are running out of RAM or HDD space. Check [this](https://github.com/bitcoin/bitcoin/issues/6196) github report from a user with a similar issue. If this is not the case then I would run a memtest and see if you don't have an issue with your RAM.

> **Comments:**
> **username_0**: Hi Mark, thanks for the quick reply! I have 90Gb of free space on HDD and will try a RAM memtest next. Will update this post when thats complete  
> **username_0**: Hello again, I tried to use a RAM test software and mounted its image onto a USB stick. I followed their instructions it and after I went to enter set up, i could see it there under BOOT section but could not activate it when it was highlighted. I pressed enter when it was high lighted and nothing happened. If anyone can recommend another course of action to correct the problem as seen in the JPEG above, please give us your take on this.  

---

