Hi, Personally, I just keep a check on the ambient temperature inside the case.. There are ram stick coolers available as well to help solve this problem. And of course, if the RAM is too hot touch when the machine has just powered down then something isnt right :) James On Thu, 2002-10-17 at 12:23, Robert L. Cochran wrote: > I'll check all these things, thank you. How do I know if the RAM is > overheating in the case, though? Is there a way of recognizing that? The > Kingston web site mentioned it too, but not how to identify when > overheating is happening. > > Bob > > James McArthur wrote: > > >Hi, > > > >Its a bit of a long-shot, but are all the cards in your PC seated > >properly? Is the CPU sitting in its socket okay? > > > >Are the ram slots clean and not showing signs of corrosion? > >Can you see if the RAM is overheating inside the case? > > > >James > > > >On Thu, 2002-10-17 at 11:42, 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? > >> > >>Thanks > >> > >>Bob Cochran > >>Greenbelt, Maryland, USA > >> > >> > >> > >> > >> > >>-- > >>Psyche-list mailing list > >>Psyche-list@redhat.com > >>https://listman.redhat.com/mailman/listinfo/psyche-list > >> > >> > > > > > > > > > > > > -- > Psyche-list mailing list > Psyche-list@redhat.com > https://listman.redhat.com/mailman/listinfo/psyche-list >
Attachment:
signature.asc
Description: This is a digitally signed message part
