|" the setup of these 4 memories has ran fine for 3 years, suddenly i started getting bluescreens a couple of days ago."|
Blue screens are NOT necessarily caused by ram problems !
What do you see on the blue screens ?
STOP: 0x000000xx (we usually don't need the stuff in brackets beside that)
A problem file may be named at the end of the text.
There may a link to "More info" or similar - if so. click on the link - if it names a problem file, tell us the name of it.
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 are specified 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).
Not all ram that might think should work in your mboard is 100% compatible with using it in your mboard.
See response 5 in this for some info about ram compatibilty, and some places where you can find out what will work in your mboard for sure:
Correction to that:
Once you know which module ID strings (part numbers) work in your mboard, you can get them from anywhere you like that has ram with those ID strings.
If you have brand name ram, it is usually easy to look up whether it's ID string (part number) is in a list of compatible modules found by using your mboard or brand name system model number.
If the ram is generic, that may be difficult or impossible.
Incompatible ram can sometimes test fine for each module individually, but may NOT test fine when more than one ram module is installed.
Did you ever test the same modules when they were all installed before this ? If not, and if you're only getting a relatively small number of ram errors, then the problem may have been there all along. Some people don't find out they have a problem until they try to run Windows Setup - it "freaks out" and produces all sorts of errors (can't find a file on the CD, etc., over and over again) if you have a small number of ram errors.
If you DID test the ram with memtest86 before when all modules you have now were installed and they passed, if you are only getting a relatively small number of errors, your problem is most likely caused by a poor connection of the ram in it's slots. Wipe the ram module's contacts off, make sure they are seated properly, and try testing the ram again. I've even had a few cases where I also had to blow out the ram slots, or wipe the contacts in them with alcohol, in order to get rid of a relatively small number of errors.
Any one ram testing program may have bugs that produce false errors in certain circumstances. E.g. - the memtest86 site says memtest86 v 3.5 has bugs that prevents more than 4gb of ram from testing properly - you're supposed to use v 3.4 or lower for more than 4gb of ram installed. Memtest86 in general produces false errors in certain tests when you mboard has certain Athlon cpus or AMD compatible chipsets - e.g. test 5 may be the only test to find a few or many errors , and another test may find infinite errors, in v 3.4.
Try more than one ram test.
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:
Windows Memory Diagnostic is limited to testing only the first 4 gigabytes (GB) of RAM.
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).