Re: Segfaults and Memory Test Failures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Both memory sticks from Kingston failed. I tested them one at a time. I 
did drop the CRIMM a few inches from my hand to the table. And I've been 
very busy fooling with hard drives and drive cables and playing with 2 
different, really cheap network cards. It's possible the Samsung memory 
is bad, I suppose. But I tend to wonder if I fried something on the 
motherboard with static or was otherwise klutzy. I'll try a few other 
memory test suites to see what they say.

Bob

Gerry Tool wrote:

> Robert L. Cochran wrote:
>
>> I tried the memtest86 suite from http://www.memtest86.com/ and my 
>> Kingston RIMM4200 memory failed it. This would seem to explain the X 
>> and kernel compile segfaults I have been getting with 8.0. This is 
>> PC1066 memory running on a 533 Mhz frontside bus. The motherboard is 
>> the Asus P4T533.
>>
>> Since Asus indicates that only 2 brands of memory are acceptable for 
>> my motherboard (Samsung and Elpida), I ordered a 256 Mb stick of 
>> Samsung memory which arrived today. I plugged that into the 
>> motherboard along with a CRIMM in the other slot. The machine failed 
>> memtest86 again.
>>
>> I also changed the memory frequency setting in BIOS based on advice I 
>> had previously seen on the Kingston web site for RIMM4200. When I 
>> used the 'x4' frequency setting, the memory flunked memtest86 
>> starting in the middle of test #4. When I used 'AUTO' for the memory 
>> frequency, it failed memtest86 starting in test #1. The options are 
>> either 'AUTO', 'x3', or 'x4'. I'm presently using the 'AUTO' setting. 
>> Maybe I should go back to 'x4'?
>>
>> That leaves me wondering if I messed up some other part of the 
>> hardware such as the motherboard. What other things can cause 
>> apparently 'bad memory' or the symptoms of segfaults, X server 
>> crashes, and segfaults during kernel compiles? Is there some part of 
>> the hardware that I'm overlooking and could have zapped without 
>> realizing it?
>>
>
> Have you identified which memory module is failing the test?
> Have you tested the memory with just one module installed at a time?
> New memory is no guarantee of good memory - your new units may need to 
> be replaced by the vendor.
>



-- 
Psyche-list mailing list
Psyche-list@redhat.com
https://listman.redhat.com/mailman/listinfo/psyche-list

[Index of Archives]     [Fedora General Discussion]     [Red Hat General Discussion]     [Centos]     [Kernel]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat 9]     [Gimp]     [Yosemite News]

  Powered by Linux