This article provides information on what memory issues can be seen and how to troubleshoot them on a Dell Desktop PC.
This guide deals with memory issues in desktop systems and how to troubleshoot and resolve memory issues. Memory troubleshooting typically breaks down into three sections:
The common types of memory issues you will see during use are:
(Fig.1.1 Quad LEDs)
(Fig.1.2 Coloured Power State LEDs)
(Fig.2 BSOD NMI parity error)
(Fig.3.1 Application error)
(Fig.3.2 Internal error)
(Fig.3.3 Applet error)
The vast majority of this troubleshooting will normally be 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 you would normally see.
These articles take you through the diagnostics LEDs and codes for the various models.
The first thing to do is to check if the Pre-Boot System Assessment (PSA) Diagnostics run. Tap rapidly on the F12 key as the system starts up and select diagnostics from the boot once menu that appears.
The system will run through about 15-20 mins worth of hardware self checks. When these complete it will ask if you want to run the further memory tests which can take another 30 mins+. If the PSA's pass then run the further memory tests.
If all tests pass then you will want to skip to the software troubleshooting.
If they fail take a note of the error code and go to the next step.
If you have an error code then you will want to check the guide below to see if you can run the newer advanced diagnostics on your system as these diagnostics will identify the fault to a memory DIMM or slot on your system.
If the diagnostics are possible and you've updated to them on your system, then contact your support with the results of the diagnostics to take this further.
If the diagnostics are not possible for your system or you are unable to update to them, then you will want to go to the hardware troubleshooting.
The concept behind hardware troubleshooting memory is very simple. It comes down to part substitution and access to known good working parts.
All Desktops will have access to the memory from an access panel or Lid. You will find the specific method for your system in your user guide.
If you are experiencing a No POST situation, the first step is to remove the memory altogether from the system. does the fault change?
Yes, then please 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, proceed to the next step.
Most Desktop systems currently ship with 1 or 2 memory modules. Most typically it's 2, 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 1 DIMM and test it in every memory socket/slot. The majority of our Desktops will have 4 memory socket/slots split into pairs 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's was installed in the system. Does the issue change depending on which DIMM or which socket are 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 you can run the machine with reduced memory until you've got in touch with your support to report the fault.
No. If the fault is the same regardless of which DIMM or which slot the memory is fitted to, then either the fault isn't 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 at this point to take this further.
Software troubleshooting for memory issues are pretty brief and mostly deal 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 already run in the PSA diagnostics. Especially as the PSA's incorporate the Memtest diagnostics in it's own tests. If you get an error from third party diagnostics then we would need to check they are compatible and that the key to the error codes is available. you would be better to skip this and move to the next step.
To rule out a virtual memory fault, I'd recommend checking a couple of quick things on your PC. The first is to confirm that windows is handling your virtual memory? Go to control panel and performance in the hardware window and check your settings. Reset it if needed. Confirm which partition the virtual memory is being allocated from? The Computer assigns space on your Hard Drive to swap memory from your physical memory. The information will be located at the same place you confirm the PC is handling the memory. Check that partition and ensure at least 6-10 GB is free on that partition. Most paging files are only 2-4GB, but if the PC is handling this it can change the size as needed. Once you set this test the system 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 computer has, the faster your programs will generally run. If a lack of RAM is slowing your computer, you might be tempted to increase virtual memory to compensate. However, your computer can read data from RAM much more quickly than from a hard disk, so adding RAM is a better solution.
If your computer lacks the random access memory (RAM) needed 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 you memory usage high? If you can get into the windows environment to monitor these, then it cuts down on the number of issues you need to check. I've included a link below to a jump page with how to guides on these methods for each of the different OS's.
If Task Manager shows high memory usage, then you may simply need more memory installed to do all the work you want to do on your system. Normally this would mean replacing the original memory with larger sized DIMMs that you've purchased.
If Task manager shows the issue is with the OS, a program or with a process, then you may want to run a free third party malware checker such as Malwarebytes and if the problem continues restore or reinstall your version of the OS to resolve the issue.
You can contact our Online support on Chat, Twitter and Email or you can call your local support number. If you go to our support site and ensure the site is set to your country then you can click on the "Contact US" link for the latest information on getting in touch.
Article ID: SLN284238
Last Date Modified: 05/14/2019 11:54 AM
Thank you for your feedback.