My Computer is Sick

About four months ago my computer started to really freak out. I'm not sure how else to describe it, but "freak" seems to be the appropriate term here. What was it doing? Well, Safari would quit unexpectedly, Mail would quit unexpectedly, iChat would quit unexpectedly, Firefox would quit unex... are you getting the picture?

In addition to all of my programs crashing all the time, I would also get something called Kernel Panics – which is almost the equivalent to the Windows Blue Screen of Death.

All in all, not good.

So, I took my troubles to the Apple Discussion Forums. Nothing worked. Then I took my computer to the Apple Store here in KC for the Geniuses to look at. They couldn't find the problem and had even more trouble recreating the errors. Finally they re-seated the RAM and that seemed to fix it.

That is, until it started to crash again and give me more Kernel Panics.

Yesterday I took it in to the Apple Store again, and this time they think it's a faulty hard drive. They're sending it back to Apple today to get some new parts... hopefully it's all better when it gets back.

Time to catch up on TV, reading and fixing my new place up. Ugh, it'll be just like High School.

+ original post date: February 21, 2005 08:56 AM
+ categories: Computers


(comments rss feed)

crappy! just get a new one. they're pretty cheap i think.

+ author: Crasymaker
+ posted: June 25, 2005 09:25 AM

Ohhhhh... I'm hoping that they find something crazy-wrong with it so they would say, "it's unfixable, here's a new one." But, I doubt that'll happen.

+ author: Seth
+ posted: June 25, 2005 09:25 AM

Macs suck.

+ author: Wendy
+ posted: June 25, 2005 09:26 AM

I'm 97 percent sure that it's not a hardware problem. I've seen similar things a few times and the culprit is one of three things.

1) Some running process is causing a memory leak that shorts out all other running processes. Saft, an add-on for Safari, is notorious for this.

2) At least one critical System file is corrupt, again leading to the aforementioned memory leak. The usually have a name like com.apple.something.

3) Some System file(s) have permission issues. In this case, starting up from another drive and running First Aid should suffice, but you've probably already done that.

The best way to solve these issues? Back up all your non-OS files, wipe the drive and re-install. I know that's a very Windows sort of solution, but it's the best way to make sure you really, truly solve the issue.

That's just my two cents.

+ author: Sean Tevis
+ posted: June 25, 2005 09:26 AM

That's the funny thing Sean (thanks for the comments, btw)... Since last year, my system has been wiped twice with OS X re-installed each time. The last time it was in the Genius' hands, it was wiped and re-installed - when the problems persisted that's when they thought it was more hardware-ish than the OS. We'll see what happens. Thanks again.

+ author: Seth
+ posted: June 25, 2005 09:27 AM

post a comment



 Remember Me?

* (you may use HTML tags for style)

* Denotes required field