|
Here is a list of the most common ways the desktop informs you of a memory problem.
1. The desktop won't boot, merely beeps.
2. desktop boots but doesn't recognize all the installed memory.
3. The desktop boots but the screen is blank.
4. The desktop reports a memory error.
a. Memory mismatch error
b. Memory parity interrupt at xxxxx
c. Memory address error at xxxxx
d. Memory failure at xxxxx, read xxxxx, expecting xxxxx
e. Memory verify error at xxxxx
5. The desktop has other problems caused by memory.
a. The desktop intermittently reports errors, crashes frequently, or spontaneously reboots.
b. Registry Errors
c. General-protection faults, page faults, and exception errors
6. The server system manager reports a memory error.
The following translations help you understand what the desktop means when it gives you one of these signals.
- desktop won't boot, merely beeps.
Every time the computer starts, it takes inventory of hardware. Inventory consists of the desktop BIOS recognizing, acknowledging, and in some cases, assigning addresses to, the components in the desktop. If the desktop won't boot, the CPU is unable to communicate with hardware. The cause can be improper installation or failure of the BIOS to recognize hardware. Follow basic troubleshooting, paying special attention to whether the memory module is completely installed and that you have the latest version of the BIOS.
- desktop boots but doesn't recognize all the installed memory.
When the computer boots, a part of the process is counting memory. On some machines the count appears on the screen and on others is masked. If the count is masked, from the computer set-up menu see how much memory the desktop thinks it has. If the desktop counts to or lists a number less than the memory you installed, the desktop hasn't recognized all the memory.
Sometimes the computer will recognize only part of a module. This is almost always due to using the wrong kind of memory. For example, if your desktop accepts only single-banked memory and you have installed dual-banked, the desktop will read only half the memory on the module. Sometimes the desktop will accept only modules containing memory chips with specific organizations. For example, the VX chipset doesn't work well with 64 Mbit chips.
In many computers the maximum amount of memory the computer can recognize is lower than the maximum amount you can physically install. For example, your desktop may have three sockets, each of which can hold a 128MB module. If you filled every socket with 128MB, you would have 384MB of memory. However, your desktop may recognize a maximum of 256MB. In most cases you can avoid this problem by consulting your desktop manual or a memory configuration Web site before purchasing memory. Or visit the Kingston Web site.
- The desktop boots but the screen is blank.
The most common reason for a blank screen is a dislodged card, memory not fully seated, or memory the desktop doesn't Advice. Confirm that the memory is installed properly and that other components in the desktop were not accidentally disconnected or dislodged while you installed memory.
Double-check that you have the right part number for the desktop. If you have nonparity memory in a desktop that requires error-checking memory, or SDRAM memory in a desktop that supports only EDO, the screen may be blank at boot up.
- The desktop reports a memory error.
Memory mismatch error:
This is not actually an error. Some computers require you to tell them that it's OK to have a new amount of memory. Use the set-up menu to tell the desktop. Follow the prompts, enter the new amount, select Save, and exit.
desktop memory or address errors:
All of the following errors, and those similar to them, indicate that the desktop has a problem with memory:
o Memory parity interrupt at xxxxx
o Memory address error at xxxxx
o Memory failure at xxxxx, read xxxxx, expecting xxxxx
o Memory verification error at xxxxx
Typically the desktop will perform a simple memory test as it boots. The desktop will write information to memory and read it back. If the desktop doesn't get what it was expecting, then it will report an error and sometimes give the address where the error occurred.
Such errors normally indicate a problem with a memory module but can sometimes indicate a defective motherboard or incompatibility between old and new memory. To verify that the new memory is causing the problem, remove the new memory and see whether the problem goes away. Then remove the old memory and install only the new memory. If the error persists, phone the memory manufacturer and ask for a replacement.
5. The desktop has other problems caused by memory. The desktop Intermittently Reports Errors, Crashes Frequently, or Spontaneously Reboots: Because of the large number of causes, these problems are difficult to diagnose. Possible causes are ESD (Electro-static Discharge), overheating, corrosion, or a faulty power supply. If you suspect ESD damage, contact the memory manufacturer and ask for a replacement. Before you install new memory, see page 85 for information on how to prevent ESD. If you suspect corrosion, clean the memory contacts and the sockets as explained on page 96. If you suspect the power supply, you will have to do overall desktop troubleshooting with a focus on the power supply.
Registry Errors: Windows writes a large portion of the registry to RAM. Sometimes defective memory will cause registry errors. Windows reports a registry error and prompts you to restart and restore. If the prompts repeat, remove your newly installed memory and restart the desktop. If the errors disappear, ask the memory manufacturer for replacement modules.
General-Protection Faults, Page Faults, and Exception Errors: The most common cause is . For example, one application may not have released the memory after quitting or occupies the same memory addresses as another. In these cases, rebooting should solve the problem. If the desktop suddenly displays general-protection faults, exception errors, or page faults after you have installed new memory, remove the new memory and see whether the errors stop. If they occur only when the new memory is installed, contact the memory manufacturer for assistance.
- The server system manager reports a memory error.
Most servers ship with system managers that monitor component utilization and test for abnormalities. Some of these system managers count soft errors in memory. Soft errors have been corrected by ECC memory. If the rate of soft errors is higher than specifications, however, the system manager issues a pre-failure warning. This warning enables the network administrator to replace the memory and prevent system downtime.
If the system manager on your server issues a pre-failure warning or other memory error, ask your memory manufacturer for a replacement. If the system manager continues to issue errors after memory replacement, make sure you have the latest BIOS, service patches, and firmware. The chance of receiving two bad memory modules in a row is low. Contact the memory manufacturer for compatibility troubleshooting. Sometimes the server does not work well with certain types of memory chips or certain memory designs.
|
