|Go here and supply the info for your system or mboard model to determine which G.Skil module part numbers are listed as compatible with your system or mboard:|
If your system model or mboard model is not listed, or if it is listed but they don't list the module part number(s) you have, there is no way of knowing whether the ram will work properly in your mboard !!.
A common thing that can happen with ram, even ram that worked fine previously, is the ram has, or has developed, a poor connection in it's slot(s).
This usually happens a long time after the ram was installed, but it can happen with new ram, or after moving the computer case from one place to another, and I've had even new modules that needed to have their contacts cleaned.
See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:
If your ram passes a ram test, it's working fine, even if you can't determine whether it's listed for your mboard or system model anywhere
If you do a ram test, do that AFTER having tried cleaning the contacts and making sure the ram is seated properly - otherwise any errors found may be FALSE.
If the ram is incompatible with the chipset, or on more recent computers, incompatible with the memory controller built into the cpu, it will likely FAIL a ram test - that is NOT a true indication of the ram being faulty - there is probably nothing wrong with it, and it will pass the test if installed in a mboard it is compatible with.
NOTE: Sometimes incompatible modules (or matched pairs) won't work properly when more than one is installed, but will pass when by itself.
If you want to try a memory diagnostic utility that takes a lot less time to run a full pass than memtest86 does, this one is pretty good - Microsoft's
Windows Memory Diagnostic:
It can be toggled (press T) to do a standard or a more comprehensive set of tests - use the default 6 test one first - if it passes one pass of that, use the latter one. A few of the tests in the latter set are intentionally slower.
If you don't have a floppy drive, see the Quick Start Information at that Microsoft link for how to make a bootable CD of the Windows Memory Diagnostic (you need Windiag.iso - you don't necessarily need to use the program they mention to add it to the CD).
If the part numbers of the ram modules you have ARE listed for you model, and/or in any case. if you STILL get ram errors.....
Some ram manufacturer's modules do not strictly adhere to the JEDEC standards that most mboards bioses use to determine ram settings.
In that case, the ram settings in the bios Setup that the bios has automatically chosen may not be correct.
Check the ram settings in your bios - the ram voltage, and the ram timing numbers - those should be the same as for the specs for the modules themselves. Often the ram voltage and timing numbers are printed on the label on the modules.
If the voltage setting or timings settings in the bios are different from the specs for the ram, change them in the bios. The timing numbers must be as close as you can get to the same, or slower timings (higher numbers = slower) - you won't notice the difference the slower settings make.
If you have a mix of different modules
- don't mix ram that different voltages arespecified for - the bios will force the ram to use the lowest voltage, if "by spd" or similar is used (default settings) - ram that a higher voltage is specified for is more likely to not work properly in that situation.
- the bios settings must be those for the slowest timing settings of all the modules, or slower (higher numbers = slower).
G.Skil is one of the "also ran" ram module manufacturers.
According to The Muskin web site, some "also ran" ram module manufacturers test their ram modules when they're by themselves in a mboard, to get the best (fastest) timing ratings. When you install more than one of their modules, the timing may not work properly with more than one module installed, but if you change the timings in the bios Setup so that the timings are slower (higher numbers) , the ram will work fine.
I have seen several examples of people who posted on this site having to do that with G.Skil ram.