iBook RAM caused kernel panic
My wife’s iBook was consistently throwing a kernel panic. It started almost completely out of the blue, so I figured that a recent software update, or a specific application was at fault.
After many days, many different tries, and a few different solutions I had found on the Internet - I came across this list of solutions. One that I found the most interesting…
Defective or incompatible RAM are the most frequent causes of kernel panics. Despite being a highly-reliable product, RAM can fail. Modern operating systems, like Mac OS X, are sensitive to RAM. Purchase additional RAM from either Apple or third parties who guarantee their RAM is compatible with Mac OS X, offer a liberal exchange policy, and provide a lifetime warranty should the RAM become defective or a later version of Mac OS X introduce incompatibilities. — TheXLab
I did have third-party RAM in her iBook. Who buys Apple RAM? So I ripped it out and sure enough the iBook has yet to throw a kernel panic (going on a few days now). I called the store (read: website) that I bought the RAM from and it is covered under a lifetime warranty. They are going to replace the RAM for free.
If you are experiencing a kernel panic on your system, please be sure to try the RAM first, then the Airport card, then some of the other solutions on The X Lab’s site - before doing anything drastic.
Related sites
Recent features
Coheed and Cambria - The Velorium Camper II: Backend Of Forever
Leah Andreone - Break Your Fall
The Format - Give It Up
Song of the week
Sara Bareilles - Between the Lines
Sara Bareilles' "Between the Lines" is the Song of the Week for April 20 to 26.

I’ve been lucky over the years to have experienced relatively few kernel panics. Almost all of them were in the earliest days of OS X. I’m not sure I’ve had a single one with Tiger on several different machines. My parents had an iMac that used to get them due to a bad Apple mouse. This was before OS X gave you a nice clean screen telling you that you had a crash, and the text that printed onscreen had something about a mouse, and sure enough, it stopped happening after we swapped out the mouse.
Chris Coleman on August 21st, 2006 9:39 am
That is whack. The kernel would crash due to a mouse.
Colin D. Devroe on August 21st, 2006 9:41 am
I have had problems with non-apple ram before. All I can say is to make sure that you can return it if it doesn’t work. I was lucky enough to have mentioned I had an apple when ordering, so they replaced it with more expensive ram for the lower cost of the ram I purchased.
Nathan on August 21st, 2006 9:58 am
Bad RAM is one of the leading causes of system problems. If you see an OS-wide crash (kernel panic on OSX, blue screen on Windows), a bad stick of RAM is usually the culprit.
Bad memory can lead to corrupt files on a disk too. After replacing a bad stick of memory, it is usually a good idea to do a format/reinstall just to be safe.
Also, I should point out that you are LUCKY the bad memory appeared in such an obvious way. Some systems have bad memory that goes undetected for years. People don’t realize they have a problem until they start seeing file corruption.
In the PC world, there is the wonderful program called Memtest86 (http://www.memtest86.com). Maybe they’ll come out with a version that supports the new Intel Macs. If your system can’t survive 24 hours of Memtest86 without error, then you have something wrong.
The low end of the DRAM market is filled with a lot deceptive practices. Vendors will knowingly sell you defective memory. They re-label low speed DRAMs as high speed ones. I used to work for one of the largest “discount” DRAM vendors in the US, and I saw some really shady stuff happen.
The lesson is: You get what you pay for. Spend the extra $$$ for Crucial memory.
Myron A. Semack on August 22nd, 2006 10:16 am