Skip to main content

3.7.1 Troubleshooting Memory

Learn how to troubleshoot memory issues on PC systems, including installation and configuration problems.

Symptoms

Memory issues tend to be intermittent, making them difficult to troubleshoot. Common symptoms include, but are not limited to:

  • system lockup
  • blank screen after POST
  • OS refuses completely boot
  • BSOD

Causes

Memory issues can be caused by both hardware and software issues.

  • One example is when a poorly written software program tries to access data stored on a memory address that has already been allocated to be used by another program. When the OS (in this case Windows) detects this, it halts the entire system to prevent further data corruption. In this case, this is when you'd get a Blue Screen of Death.
  • Another example is when a memory module is faulty, making some memory addresses inaccessible to the OS. If a program would try to access these memory addresses or write data to them, then the system would crash.
  • Damage caused by a spike in power provided from the PC.
  • ESD damage caused by improper handling.

Use Windows BSOD Errors

When older Windows systems crash we're talking Windows 7 and before and a BSOD is displayed, it may provide important information regarding the cause/source of the error, like a memory address. If the same memory address shows up multiple times when the system is crashing, it's likely that an entire memory module is faulty. If not, then you can assume it's a poorly written software application this is what happens when you put programmers in front of hardware.

However, in all systems Windows 8 and after, only minimal information is given on a BSOD boo.

Manually Test RAM Sticks

i already hate this One way to manually test memory modules is by removing them from the system, one at a time, until the error goes away. Then you'll know which memory module was causing the error and can replace it with a known good spare. However, this method is slow, and it can take a relatively long time to isolate the issue, especially if the error only happens intermittently.

Use a Memory Tester

Use a pair of hardware and software called a memory tester to check every module connected to the PC for errors. A memory tester has slots where you plug in your modules. It runs a check on all the memory locations each module has, then reports back on whether or not the module is good for use.

The software memory testing utility e.g. Memtest @ https://memtest86.com requires the use of a USB drive. The reason for this is that sometimes you might get a memory related issue that prevents the OS from booting up. So what Memtest does is it puts a mini-OS on the USB that you can boot from. From there, you can use the utility to scan the modules for errors. This process takes longer the more capacity the memory modules have.

Raw Lesson Content

Memory problems usually fall into one of the following categories:

  • Either more memory is installed than the system supports or the CMOS settings are incorrect.
  • Incompatible or broken modules.
  • Improperly installed modules or dirty or defective sockets.
Error Description
The system boot fails and sounds a beep code Either no memory is installed or the memory was not detected.
The system boots, but the display remains blank Either a card or memory module is not seated, or the system includes unsupported memory. Non-parity RAM is incompatible with ECC memory; SDRAM is incompatible with EDO memory.
The system boots, but the memory count is incorrect The POST failed to recognize all the memory. This can happen with incompatible memory installation. Remember to avoid combining dual-bank with single-bank memory. If you detect a problem during system boot, check the BIOS settings.

The system checks only for memory installed in memory slots on the motherboard. Memory on expansion cards or installed on other devices is not counted and tested.
Error messages Memory error usually indicates a failing module or discrepancies between new and old memory. Avoid the latter problem by not mixing new and old memory. Ensure that the memory is functioning properly and is compatible with the system.

If the memory is good and fully compatible, error messages could mean that the motherboard has a problem. The following are common error messages:

- Memory mismatch error
- Memory parity interrupt at x
- Memory address error at x
- Memory failure at x , read y , expecting z
- Memory verify error at x
Software-generated memory problems Software errors include:

- Registry error—Parts of the registry are written to faulty sections of RAM.
- Exception error—A software bug can cause this type of error.
- General-protection fault—A software bug can cause this type of error.
- Page fault—A software bug can cause this type of error.

For software errors, check to see if the memory address indicated in the error is consistently the same. If so, check the memory. Otherwise, reboot the system or update the software.
Intermittent problems One of the tougher detection challenges is the intermittent occurrence of error messages, crashes, or sudden reboots. The trouble in diagnosing this situation is the number of potential problems, including timing, heat, corrosion, fluctuating power, loose connections, EMI, or a combination of these problems.

You should be familiar with the following list of critical times when memory problems manifest themselves and the likely causes.

  • First boot of a new computer—Memory is not properly seated, missing, or the motherboard is defective.
  • After a memory upgrade—Memory is not compatible or was not properly installed and configured.
  • After software installation—New software requires more memory or is causing problems.
  • After hardware installation or removal—Incomplete hardware installation or improperly installed hardware can cause errors that appear to be memory related. #III

#Aplus

No comments to display

Back to top