Re: Kernel Panic during startup on iMac
Re: Kernel Panic during startup on iMac
- Subject: Re: Kernel Panic during startup on iMac
- From: Al Ciplickas <email@hidden>
- Date: Wed, 8 Aug 2007 08:36:12 -0700
Thanks, Mike. That's a good idea. I did it this morning and the
system still works fine, so it does point to the memory module. I
suppose I could put the suspect one back in and verify that the
system goes back to panic mode. It's the first time that I had a
memory module go out including 3rd party memory. Just lucky I guess...
-Al-
ps- just tried the bad module and it causes the same panic, so it IS
bad.
On Aug 8, 2007, at 5:06 AM, Michael Cashwell wrote:
On Aug 8, 2007, at 12:39 AM, Al Ciplickas wrote:
-- next, I removed the memory from the front slot (#0?) and now it
appears that system and other programs are running well (though a
bit slower in response, as expected).
-- conclusion so far: I have a bad memory module. It apparently
was not found by the startup tests.
Good catch, but it could be a bad memory socket instead.
Before declaring the module that's out as bad (and buying a
replacement) you need to verify that the socket it came out of are
OK. The easiest way to do that is to move the module that works to
that socket (leaving the back socket empty) and exercising the system.
If that module works in both places, then indeed the one you've
taken out is bad. If not then you likely have two good memory
modules and a bad front socket on the motherboard. (Just to be
clear, I don't mean here that the physical socket is necessarily
bad. I mean the whole of the socket and the circuitry dedicated to
driving it.)
A friend had the user-accessible memory socket in a Powerbook up
and fail. He didn't do these steps and was really frustrated when a
new module wouldn't work and had to be returned.
Good luck!
-Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden