A
A
artem782017-04-30 00:59:52
RAM
artem78, 2017-04-30 00:59:52

Prohibition of access to a broken memory cell, is it possible?

I found that when unpacking a large archive, a CRC error occurs every time in a different place. I ran Memtest, which found an error at one address. Rearranging the bar to another slot and cleaning the contacts does not help. Interested in the question, is it possible at the OS level (Windows / Linux) to prohibit access to a broken memory cell? It seems like I heard about such a possibility for Linux, but I can not find the information.
PS It is clear that you need to buy a new bar, but for now a temporary solution will do.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
1
15432, 2017-04-30
@15432

I know about the ability to "reflash" the bar by manually specifying the number of memory jars. This can theoretically "cut off" the broken half of the memory. In case of incorrect parameters, you will need a working memory bar for recovery and stick it hot. In short, all this is dangerous. Yes, and it’s not good if the beaten area is in the younger half

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question