On December 2, 2005 19:01, Chris wrote: > On Friday 02 December 2005 6:41 pm, Chris wrote: > > Had this waiting for me when I got home from work today. > > > > Dec 2 17:01:00 cpollock kernel: CPU 0: Machine Check Exception: > > 0000000000000004 > > Dec 2 17:01:00 cpollock kernel: Bank 2: f60020000000017a at > > 0000000000148000 > > Dec 2 17:01:00 cpollock kernel: Kernel panic: CPU context corrupt > > > > The one below is a panic I had back in May, looks pretty much the same > > which turned out to be memory. Stupid question though, the Bank 2 that > > is referenced, its apparently not memory bank 2 since I left it empty and > > put modules in 1 and 3. So, just what does the "Bank 2" thats mentioned > > mean? > > > > 11:15:02 cpollock kernel: CPU 0: Machine Check Exception: > > 0000000000000004 May 26 11:15:02 cpollock kernel: Bank 2: > > f60020000000017a at > > 0000000000364000 > > May 26 11:15:02 cpollock kernel: Kernel panic: CPU context corrupt > > > > Looks like I'll be picking up more memory tomorrow. > > I'll reply to my own msg here, when memtest86 goes to run the "block move" > test, instant reboot. Looks like it is memory for sure.
Could be the motherboard too. I had that happen to me. I was getting a memory error identifying a specific memory bank. But the diagnostic guide I was looking at told me to swap the dimms around to confirm it was the dimm. If it is, the location of the error should change correspondingly. But whatever memory I put in that bank, the error location was the same. So the dimms were fine, it was the motherboard. Most likely a broken trace. -- Ron ronhd at users dot sourceforge dot net Opinions expressed here are all mine.
____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
