This guide deals with memory issues in desktop computers and how to troubleshoot and resolve memory issues. Memory troubleshooting typically breaks down into three sections:
The common types of memory issues you see are:
Most of this troubleshooting is done as part of a specific troubleshooting guide for a particular fault. This article is a General Overview that can go into a bit more detail than is usual.
These articles take you through the diagnostics light emitting diodes (LED) and codes for the various models.
The first thing to do is to check if the enhanced Pre-Boot System Assessment (ePSA) Diagnostics can run.
With the desktop turned off, hold down the Fn key and the power button simultaneously. Alternatively, tap rapidly at the F12 key as the desktop boots and select Diagnostics from the menu that appears. A Diagnostic Boot Selected message should appear in the upper right corner of the screen.
To run a specific test, perform the following steps.
Either:
The computer runs through about 15 to 20 minutes' worth of hardware self-checks. When these complete it asks if you want to run the further memory tests which can take over 30 minutes. If the ePSAs pass, then run the further memory tests:
If all tests pass, then you want to browse the software troubleshooting.
If they fail, then take a note of the error code and go to the next step.
When you have an error code, check the guide to see if you can run the newer advanced diagnostics on your desktop. The newer diagnostics identify the fault to a dual inline memory module (DIMM) or slot on your device:
If the diagnostics are possible and available on your desktop, then contact support with the results of the diagnostics to take this further.
If the diagnostics are not possible for your desktop or you are unable to update to them, then you want to go to the hard troubleshooting.
The concept behind troubleshooting hardware memory is simple. It comes down to part substitution and access to known good working parts.
All Desktops have access to the memory from an access panel or Lid. You find the specific method for your computer in your user guide.
If you are experiencing a No POST situation, the first step is to remove the memory altogether from the computer. Does the fault change?
If yes, then go to step 2.
If it does not, then you want to follow the No POST Guide below.
Yes, then swap the known good memory with the memory from this unit and see where the fault goes. Contact your support and take this further with them.
No, go to the next step.
Most Desktop computers currently ship with one or two memory modules, but they have the slots to fit more. Most typically it is two because most memory is designed to work better in matched pairs. Regardless of how many modules you have, the next step is the same. Take one DIMM and test it in every memory slot. Most of our Desktops have four memory slots split into pairs that are called banks. Note the results and do the same thing with the second DIMM if you have one. Repeat this step for every DIMM that is installed in the device. Does the issue change depending on which DIMM or which slot is in use?
Yes, if the fault follows a DIMM or stays with a particular slot on the motherboard, then you have identified the fault. The good news is that you can run the machine with reduced memory until you have got in touch with your support to report the fault.
No. The fault is the same regardless of which DIMM or which slot the memory is fitted to. The fault is either not with the memory, or both the memory and the slots are faulty. This is why we suggest carrying out step 2. I would recommend contacting your support to take this further.
Software troubleshooting for memory issues is brief and mostly deals with virtual memory instead of physical memory.
You can run further memory diagnostics in windows. There are several well-known tests to pick from such as Memtest. However, we would most likely go on the results that are already run in the ePSA diagnostics. Especially as the ePSAs incorporate the Memtest diagnostics in its tests. If you get an error from third-party diagnostics, then we must check they are compatible with our hardware and they explain what the error code means. You would be better to skip this and move to the next step.
To rule out a virtual memory fault, we recommend checking a couple of quick things on your computer. The first is to confirm that windows are handling your virtual memory. Go to the control panel and performance in the hardware window and check your settings. Reset it if needed. Confirm which partition that the virtual memory is being allocated from? The computer assigns space on your Hard Drive to swap memory from your physical memory. The information is at the same place that you confirm that the device is handling the memory. Check that partition and ensure at least 6 GB to 10 GB is free on that partition. Most paging files are only 2 GB to 4 GB, but if the desktop is handling this it can change the size as needed. Once you set this, test the computer to see if the fault returns. If it does go to the next step.
Virtual memory combines your physical RAM with temporary space on your hard disk. When RAM runs low, virtual memory moves data from RAM to a space called a paging file. Moving data to and from the paging file frees up RAM to complete its work.
The more RAM your desktop has, typically the faster your programs and applications run. If a lack of RAM is slowing your computer, you might be tempted to increase virtual memory to compensate. However, your desktop can read data from RAM more quickly than from a hard disk, so adding RAM is a better solution.
If your desktop lacks the random-access memory (RAM) required to run a program or operation, Windows uses virtual memory to compensate.
You can monitor the memory usage through Task Manager and event log exceptions. This would let you track if there was a particular program, process, or device that coincided with the errors. Alternatively, is your memory usage high? If you can get into the windows environment to monitor these, then it cuts down on the number of issues you must check. I have included a link below to a jump page with how-to guides on these methods for each of the different operating systems.
Task Manager shows high memory usage. You may need more memory than is installed to do all the work that you want to do on your computer. This would mean replacing the original memory with a larger sized DIMM that you have purchased.
Task manager shows that the issue is with the operating system, a program or with a process. You may want to run a free third-party malware checker. If the problem continues, then restore or reinstall your version of the operating system to resolve the issue.
You can contact our Online support on Chat, Twitter, and email or you can call your local support number. Ensure that the site is set to your location if you go to our support site. You can click the "Contact US" link for the latest information about getting in touch.
Here are some recommended articles related to this topic that might be of interest to you.