Heart of the Home Dining

Caling all Bloggers

Some Ways To Fix “Memory Could Not Be Read” Error…

After some research, I have found some great ways to fix memory could not be read error in Windows:

Method 1 – Update drivers and install latest patches

Depending on your hardware, you may be getting the error because you computer is not using the most up to date drivers.

The main thing to update here are video, hard drive, chipset and network drivers. Those are usually the main culprits for this type of error. It’s also a good idea to update the BIOS to the latest version.

Also, be sure to install all the latest Windows patches and service packs. There have been several times when the referenced memory errors were being caused by Windows and not anything else. Update Windows, Office, and any other program on your computer.

Method 2 – Perform a System Restore

Hopefully, if you’ve gotten this error just recently, you might be able to restore your computer to a previous state. You can get this error sometimes if your registry has become corrupted.

The registry can become corrupted by a buggy program (like mentioned above),  but sometimes even after it is uninstalled, you’ll still get the error because the registry is still corrupted somewhere.

You can try to perform a system restore and hopefully get to a state before the program was installed. You can also try to download and install a registry cleaner and see if that fixes the issue.

Method 3 – Run System File Checker

Another possible solution is to run the built-in system file checker program that comes with Windows. You can run it by going to Start, Run and typing in CMD. At the prompt, type the following command:

sfc /scannow

Then press Enter. It will scan all the Windows system files and replace any corrupted or deleted ones. You can read my previous post on how to navigate the DOS command prompt if you’re new to it.

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay
Comments are off for this post

Comments are closed.