How to fix the “Unable to read memory” error in Windows 10, 8, 8.1 and 7

Who I am
Catherine Le Nevez
@catherinelenevez
Author and references

In the immense world of Microsoft Windows and its impressive number of tools and services, as in many operating systems such as Linux and Mac, with which it also has some differences and similarities, there are many internal errors with different causes.

Today we have in mind the problem of another error, that relating to memory, 'you could not read the memory', but which also has a solution, like everything else. If you want to know more about this error and also learn how to fix it, read on.



What is the problem of "the memory could not be read" and what does it entail?

Perhaps in the midst of the use you normally give to your computer with the Microsoft Windows operating system, a window pops up saying 'the memory cannot be read'. This obviously gives the possibility to think it is a mistake of RAM, which is a bit iffy.

We need to clarify that this error isn't just about RAM - it can also mean a problem in the storage memory. This is a fairly common error, which has to do with the location of files in memory.

'The memory cannot be read' refers to the circumstance or time when a file is running as an administrator to be installed, and takes an address that leads it to one wrong memory space, a place where it cannot be. 

As a result, the cannot be executed and this implies a solution within the same Windows operating system, which we will explain, and which is necessary for the execution of said file.

It is a recurring problem in the work operating Windows, that is, in all existing versions of this Microsoft product.



How to fix the “Unable to read memory” error in Windows 10, 8, 8.1 and 7?

Like any problem or error that Windows presents, regardless of its versions, there is one or more causes behind it. For example, the “Desktop Window Manager has stopped working” problem has causes related to hard drive infections. And giving the solution is our duty.

The main causes of this error are related to memory, obviously, and it can be a malware (virus) problem inside it; insufficient amount of access to random memory; a hardware problem; or it can be related to the incorrect use of the logical resource of one application or multiple applications at the same time.

The first thing we need to do to resolve the error in question is to right-click on the "My Computer" icon to access "Properties". Once there, we locate where it says Performance and click on "Settings", then enter "Advanced Options".

In the window 'Virtual memory', click on 'Change'; then, select the custom size option and you will enter an amount that depends on your computer's RAM memory. In "Initial size" you must enter half of the RAM capacity and in "Maximum size" enter the total amount of this capacity.

Finally, you just have to accept and proceed to restart the device and wait for it to turn on again for check if the problem has been solved.

What to do if the "Unable to Read Memory" problem in Windows is not resolved?

Sometimes it happens that the situation does not resolve itself and the problem persist, the which is somewhat annoying and frustrating. If this is the case for you, try the following. 


You have to locate yourself in the path C: / Windows / System32At this point, you just have to open the config.nt file, with the 'Open with' option and click on Notes blog.


When it is open with the 'Notes blog' option you just have to write the following, right after the file: buffers = 3000. Finally you have to save the file and then close it.

The final step is the same as the previous process, you just have to restart your computer and after turning it on, checking that the problem is already solved is what we want in our windows computer. If the problem persists, you should go to Microsoft Technical Support and Customer Service, waiting for their response to be resolved.

Tagsfinestre
add a comment of How to fix the “Unable to read memory” error in Windows 10, 8, 8.1 and 7
Comment sent successfully! We will review it in the next few hours.