contrapunctus, by Christopher League
 

Let the memory live again

I find the default configurations of most computers to be too low on memory. So one of the first things I did after ordering my PowerBook last year was to order a 1G SDRAM module from NewEgg. (The PB came with 2×256M, and Apple’s RAM is way overpriced.)

Unfortunately, last week I started having trouble with it. I had noticed that my laptop was reporting 768M rather than 1.2G as it did when I first installed the module. This was strange; can just half the memory be working? I removed and re-seated the module, with no improvement.

So then I tried swapping my module with the identical one in Art’s iBook. His computer reported the full amount (1.2G) and now so did mine. A strange situation, but I thought the problem was solved.

But then the next day my PB experienced a kernel panic. If you’ve never seen this on Darwin/OS X, the screen dims slightly, and a message comes up in about 5 languages that “you need to restart your computer,” with little additional explanation. Like a stable Linux, this kernel really does not panic lightly, and it is often indicative of a hardware defect.

At first, I’m not sure I blamed the panic on the recently swapped memory module. But then the computer was up just about 10 minutes before it crashed again. The next time, I only got about 8 minutes. This was becoming serious. As a stop-gap, I swapped the 1G module with the original 256M one, and the crashes ceased.

But this is strange: both 1G modules seem to work in Art’s iBook, neither works fully in my PB—although they exhibit very different symptoms—but the 256M module works fine. I don’t know whether to blame my laptop, the memory, or some crazy conspiracy between them. It’s far simpler to order a new 1G module than to phone AppleCare and complain about my laptop’s behavior with 3rd-party RAM. For now, I’m just surviving on 2×256M.

One response

You may leave a response below, or a trackback from your own site. You can follow responses to this post using this RSS feed.

1
19 May 2006 @16:45

Very bizarre. The timing of the module and/or the SPD must be degraded to just out of spec on the memory. I’ve had it happen once — the memory supplier blamed it on heat (shortening the life of the transistors) — not sure I agreed, but hey, I got a new stick out of them. Did you try booting into diagostics mode and seeing if/when it errors out? (Not that it would help much but it might provide some insight). I’ve had good luck (and cheap prices) with MemoryToGo or Crucial . Both offer lifetime warranties. At Hopkins the department bought Crucial on several occasions.

You could also take it as a sign that you need a MacBook Pro :) The switch from a Mac Mini as my primary machine to a MacBook Pro has been fantastic! Plus, with Parallel’s Desktop for OS X I can run the occasional program that doesn’t have an OS X equivalent (like Visio — yes, OmniGraffle can do the work but the whole input/output issue of Visio formats is still a problem — most people don’t save their Visio in Visio 2002 XML — they still use the binary VSD format)

Your response