operating systems Vindovs error "memory could not be read», perhaps, is one of the most common.Various gurus in the pages of the Internet allow for troubleshooting and restore the normal functioning of the system.No wonder that every opinion, "I am right, but not the others."Here are tips given are not always effective.However, there is no deception: the message "The memory could not be read» may occur due to several reasons why the workaround there are also a few.
First, a little theory.One advantage of the latest operating system from Microsoft - a redesigned and improved memory management.If Vindovs 9x various crashes and restart were commonplace, and even the length of time in the normal mode could lead to problems in the line, based on the core Win NT, this time it was given the highest priority.As a result of an error memory virtually ceased to appear, because the mechanism works has been radically altered.By the way, this is why novice users, to begin acquaintance with the world of digital technology through the Win 7, may not even know what a "blue screen of death» (BSOD).It is necessary to pay tribute to Microsoft - the reliability of the system has increased significantly.How, then, in the forums are taken questions from users receive a "The memory could not be read»?
mechanism works as follows: when you run any program system manager allocates her some isolated section of memory.This solution enables an optimal way to implement the applications in a multitasking system.If the running program tries to access memory outside the allocated space, a message "The memory could not be read» and the program closes.Because of this it is possible to ensure the stability of the operating system.It is quite clear that the problem often lies in the incorrect operation of third-party applications, and expect help from Microsoft is not worth it.Well, the theory is finished, and you can move on to practical recommendations.
One of the most common causes - a hardware memory error that occurs in one of the modules installed.Just note that this encounter happened a few times, so the recommendations are not unfounded.Although modern memory chips are fairly reliable, and if problems arise, rarely, if error messages need to check-ins.Before you spend checking software, you need to open the case and remove the memory modules.Of course, provided that the case is not sealed warranty sticker.Comb copper contacts modules need to be thoroughly cleaned stationery eraser sometimes appeared oxides deteriorate the electrical conductivity, and an eraser removes them, copper polishing to a shine.Then carefully insert the memory back to the connectors, do not forget about the side latches.From this point on should be observed, if the error persists.
If all repeats, you'll have to resort to specialized programs.One of the most effective, giving almost 100% detection result - is Memtest86 + (not to be confused with TestMem).Feature - that the test is designed to run in DOS, so you need to download from the developer image to be recorded to disk (USB flash drive) and prepare the media in accordance with the instructions.It will boot from the media and test all memory.If errors are found, check each module separately.
way, sometimes the cause of the error lies in the timings or excessive acceleration components.Therefore it is absolutely necessary to remove the acceleration (if available) and check the real and actual timings (can be found in the program CPU-Z).
A word of advice: they ate the problem occurs only with a specific application, it is necessary to update or not at all, try to replace analogue.And, of course, should use the original operating system, and not build them.
