site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Aug 8, 2007, at 12:39 AM, Al Ciplickas wrote: Good catch, but it could be a bad memory socket instead. Good luck! -Mike _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... -- 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. 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. This email sent to site_archiver@lists.apple.com