Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
If memtest86 consistently gives the same failure locations after multiple testing cycles, then you probably have bad memory. Try retesting the modules one at a time (i.e., pull one out).
But other things can cause memtest86 failures at random memory locations that do not involve bad memory. Two that I have seen are excessive overclocking of either the CPU or the memory bus. Another would be an overheated CPU.
If you consistently get the same memory locations reported as failed from several full testing cycles of memtest86, as opposed to seeing errors that jump around the memory map, then you probably have bad memory.
My cpu is not overclocked, and it have a original fan and cooler. Its a p4, 3,2 ghz. The memtest86 fails at all the whatevers, there is no "passes". Could it be the motherboard, scince both the modules are bad?
Beyond things like memory bus speed, ECC/non-ECC and registered/non-registered mismatches, you can get a motherboard/memory combination that just doesn’t work well together. Look at the motherboard vendor’s recommendations for memory and see if your memory is on their “recommended” list. And not being on the list doesn’t mean it won’t work.
Also, it’s always possible that your source of memtest86 has a problem. Try a different download/distribution source. It seems to come on a lot of linux installation disks and on Live-CD disks like Knoppix.
Just to make sure we are on the same memtest86 wavelength, are you seeing a long list of failed locations being listed below the displayed counters?
The part numbers refer to the same memory modules. The “k2" at the end of the first number just means “kit, 2 pieces”, so kvr400x64c3ak2/1g = 2 x kvr400x64c3a/512. The two part numbers have the same specs and the specs look fairly standard for DDR400.
Did you try testing just one module with memtest86? If they both give failures when tested alone, it sounds like a true memory problem, but it would be nice to try them in a different system or to borrow someone else DDR400 to test in your system.
But, yes, it does seem odd to have two modules fail, unless the motherboard fried them with an overvoltage. If you can check/change your motherboard voltages through the BIOS, be sure to check that the memory is set at 2.6V and that the other voltages look reasonable.
i just mounted both ram-modules in their slots and fired up the computer. All parts are brand new. The motherboard user guide does not say that installing ram need any configuration. At boot, the computer counts 1024 mb ram.
Both modules fail when inserted separately
edit: The failing starts at "test #4 moving inv, 32bit pattern, cached"