Error 'Memory can not be read'

In Windows operating systems, the error "Memory can not be read" is perhaps one of the most common. Various gurus on the Internet provide recommendations on how to fix and restore the normal functioning of the system. Not surprisingly, everyone is of the opinion "I'm right, but the rest is not." That's only the advice given is not always effective. However, there is no deception: the message "Memory can not be read" can appear due to several reasons, so there are several ways to solve the problem.

First a bit of theory. One of the advantages of the latest versions of operating systems from Microsoft is a redesigned and improved memory manager. If in Windows 9x various failures and reboots were a common occurrence, and even a long work in the normal mode could lead to problems, then in the line based on the Win NT kernel, this moment was paid the closest attention. As a result, the memory error message almost ceased to appear, because the work mechanism was radically redesigned. By the way, that's why users-beginners, who started acquaintance with the world of digital technologies through Win 7, may not even know what the "blue screen of death" (BSOD) is. It is worth to pay tribute to Microsoft - the reliability of the system has increased at times. Whence in this case on forums users' questions about an error "Memory can not be read" are taken?

The mechanism of work is the following: at start of any program the system manager allocates to it a certain isolated area of free memory. This solution allows you to optimally implement the work of applications in a multitask system. If the running program tries to access memory outside the allocated space, the message "Memory can not be read" is issued and the application is closed. Thanks to this, it is possible to ensure the stability of the operating system. It is quite clear that the problem is most often hidden in improperly working third-party applications, and expect help from Microsoft is not worth it. Well, the theory is over, and you can move to practical recommendations.

One of the most common causes is a hardware memory error that occurs in one of the installed modules. Immediately note that I happened to encounter this several times, so the recommendations are not unfounded. Although modern memory chips are quite reliable, and if problems arise, then infrequently, when reporting errors, you need to check the modules. Before performing a software test, you need to open the case and remove the memory modules. Of course, provided that the case is not sealed with a warranty sticker. The comb of the copper contacts of the modules must be thoroughly cleaned with a clerical eraser: sometimes the oxides appear to degrade the electrical conductivity, and the eraser eliminates them, polishing the copper to a shine. After that, carefully insert the memory back into the connectors, not forgetting about the side latches. From now on, you should observe whether the error has not disappeared.

If everything repeats, then you will have to resort to specialized programs. One of the most effective, giving almost 100% detection result, is Memtest86 + (not to be confused with TestMem). The peculiarity is that the test is designed to run in DOS, therefore it is necessary to download an image from the developer's site intended for writing to a disk (flash drive) and prepare the media in accordance with the instruction. You will have to boot from this media and test all memory. If errors are found, you should check each module separately.

By the way, sometimes the cause of errors lies in the overestimated timing or overclocking of components. Therefore, it is mandatory to remove the overclocking (if available) and check the real and actual values of the timings (you can find out in the CPU-Z program).

A little tip: if the problem is observed only with a certain application, then it needs to be updated or not used at all, trying to replace it with an analog. And, of course, you should use the original operating systems, not their assemblies.