<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1141" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=Arial size=2>Craig</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Have tried many varied combinations of three slots
for RAM.</FONT></DIV>
<DIV><FONT face=Arial size=2>Last config I tried was 128 in Bank 0 and 256 in
Bank 2, these numbers</FONT></DIV>
<DIV><FONT face=Arial size=2>are those seen in BIOS.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Error:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>CPU 0: Machine Check Exception:
0000000000000004</FONT></DIV>
<DIV><FONT face=Arial size=2>Bank 2: f60020000000017a at
000000000be5f000</FONT></DIV>
<DIV><FONT face=Arial size=2>Kernel panic: CPU context corrupt</FONT></DIV>
<DIV><FONT face=Arial size=2>Mar 5 21:15:47 Coven kernel: CPU 0: Machine Check
Exception: 0000000000000004</FONT></DIV>
<DIV><FONT face=Arial size=2>Mar 5 21:15:47 Coven kernel: Bank 2:
f60020000000017a at 000000000be5f000</FONT></DIV>
<DIV><FONT face=Arial size=2>Mar 5 21:15:47 Coven kernel: Kernel panic: CPU
context corrupt</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>As far as I can tell this Bank 2 refers to Bank 1
in BIOS and there was no RAM there.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Have also tried with I stick moved each time to
different Bank but error eventually comes.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Is it possible that mother board could be catcus
but RAM is ok?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Craig</FONT></DIV>
<DIV><FONT face=Arial size=2>----- Original Message ----- </FONT>
<DIV><FONT face=Arial size=2>From: "Craig Foster" <</FONT><A
href="mailto:fostware@iinet.net.au"><FONT face=Arial
size=2>fostware@iinet.net.au</FONT></A><FONT face=Arial size=2>></FONT></DIV>
<DIV><FONT face=Arial size=2>To: <</FONT><A
href="mailto:plug@plug.linux.org.au"><FONT face=Arial
size=2>plug@plug.linux.org.au</FONT></A><FONT face=Arial
size=2>></FONT></DIV>
<DIV><FONT face=Arial size=2>Sent: Monday, March 03, 2003 3:38 AM</FONT></DIV>
<DIV><FONT face=Arial size=2>Subject: RE: [plug] Memory
testing</FONT></DIV></DIV>
<DIV><FONT face=Arial><BR><FONT size=2></FONT></FONT></DIV><FONT face=Arial
size=2>> It look like under load, you have either a bad RAM buffer or a
faulty<BR>> Address line (read - dead stick). Notice how the faulty addresses
look<BR>> *really* similar :)<BR>> <BR>> If you have at least two
memory sticks (which you should have if you<BR>> have Bank 2), swap the
memory sitcks and see whether the failures<BR>> address stays high or whether
they are closer to half of what they are<BR>> now. From the looks of it, the
error is in the second stick (Bank 0,1 =<BR>> 1 stick; Bank 2,3 = 2nd stick,
etc) Programs like aida32<BR>> (</FONT><A href="http://www.aida32.hu"><FONT
face=Arial size=2>http://www.aida32.hu</FONT></A><FONT face=Arial size=2>) can
usually tell you who actually made the stick<BR>> too.<BR>> <BR>> Most
(decent) memory has lifetime warranties now, so why not just send<BR>> it
back to the distributors with this output, and get them to replace<BR>> the
stick.<BR>> Other than the big boys (Like SIMMS Int'l) most memory disties
don't<BR>> test memory other than putting it in another machine and run
memtest,<BR>> whatmem, or TuffTest Pro. (Trust me, this was a side job I used
to do<BR>> for a local memory distributor and one of their Eastern
States<BR>> competitors)<BR>> <BR>> Regards,<BR>> <BR>> Craig
Foster<BR>> </FONT><A href="mailto:fostware@iinet.net.au"><FONT face=Arial
size=2>fostware@iinet.net.au</FONT></A><FONT face=Arial size=2> (with SMIME)
<BR>> <BR>> > -----Original Message-----<BR>> > From: Craig Dyke
[mailto:grail@enterprize.net.au] <BR>> > Sent: Sunday, March 02, 2003
10:02 PM<BR>> > To: </FONT><A href="mailto:plug@plug.linux.org.au"><FONT
face=Arial size=2>plug@plug.linux.org.au</FONT></A><BR><FONT face=Arial
size=2>> > Cc: </FONT><A href="mailto:bernard@blackham.com.au"><FONT
face=Arial size=2>bernard@blackham.com.au</FONT></A><BR><FONT face=Arial
size=2>> > Subject: Re: [plug] Memory testing<BR>> > <BR>> >
<BR>> > Error:<BR>> > <BR>> > MCE: The hardware reports a non
fatal, correctable incident <BR>> > occured on CPU 0. Bank 2:
d40040000000017a Feb 22 08:34:11 <BR>> > Coven kernel: MCE: The hardware
reports a non fatal, <BR>> > correctable incident occured on CPU 0. Feb 22
08:34:11 Coven <BR>> > kernel: Bank 2: d40040000000017a<BR>> > MCE:
The hardware reports a non fatal, correctable incident <BR>> > occured on
CPU 0. Bank 2: 940040000000017a Feb 22 08:34:26 <BR>> > Coven kernel: MCE:
The hardware reports a non fatal, <BR>> > correctable incident occured on
CPU 0. Feb 22 08:34:26 Coven <BR>> > kernel: Bank 2:
940040000000017a<BR>> > MCE: The hardware reports a non fatal, correctable
incident <BR>> > occured on CPU 0. Bank 2: d40040000000017a Feb 22
08:34:41 <BR>> > Coven kernel: MCE: The hardware reports a non fatal,
<BR>> > correctable incident occured on CPU 0. Feb 22 08:34:41 Coven
<BR>> > kernel: Bank 2: d40040000000017a CPU 0: Machine Check <BR>>
> Exception: 0000000000000004 Bank 2: b60020000000017a at <BR>> >
000000000ad31280 Kernel panic: CPU context corrupt Feb 22 <BR>> > 08:34:45
Coven kernel: CPU 0: Machine Check Exception: <BR>> > 0000000000000004 Feb
22 08:34:45 Coven kernel: Bank 2: <BR>> > b60020000000017a at
000000000ad31280 Feb 22 08:34:45 Coven <BR>> > kernel: Kernel panic: CPU
context corrupt<BR>> > <BR>> > The above are the errors I keep
getting while trying to <BR>> > compile stuff. If I turn MCE off I
eventually get the last 4 <BR>> > line anyway. It seems to be unpicky
about what I compile, I <BR>> > just eventually get a runaway executable
(eg. ld, gcc even <BR>> > rm) which I cannot kill.<BR>> > <BR>>
> Craig<BR>> </FONT></BODY></HTML>