Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Week 30 MacBook Owners- Experience any problems?
- Thread starter myMac
- Start date
- Sort by reaction score
Mine's week 29. I had some blue discolouration, but that's because of some really low-quality bedsheets I recently bought... I've been turning everything blue. Towels, napkins, my Macbook, everything.
Came off with a Magic Eraser.
Anyway, no mooing or anything out of the ordinary.
Came off with a Magic Eraser.
Anyway, no mooing or anything out of the ordinary.
7on said:Really?!?! Random Shutdowns or randomly turning off? If it's just turning off, black, poof nothing. Then I'd probably sign into the Apple Discussions board and tell them about this. To my knowledge no books have showcased this problem so early - most have been 3-4 weeks new but repaired books coming back and working for about a week. We're all trying to find the lowest common denominator.
Sorry my earlier post was lacking information. I was in a hurry and frustrated - to clarify:
I purchased a 1.83 Macbook last week on Wednesday (8/9/06). The S/N indicated that it was a week 31 assembled in China. The machine was booted for the first time around 2:00. That evening around 9:00 it exhibited the random crashing/turning off behavior for the first time. We would be using it and then "poof" nothing - black screen. We rebooted the system and it ran fine the remainder of the evening. The next morning we tried to wake the system from sleep to find it had shutdown/crashed at some point during the evening. That morning the machine began to crash on a more regular basis. After the 11th crash in about 4 hours, we decided to return it.
An apple store employee said they knew about the problem and it stemmed from an OSX version that did not agree with the Macbook. If I would update my system it would fix the problem. I had not had a chance to update the new system yet b/c it was so new - so I was willing to give it a try. I asked if it would be ok to do it in store. I was about half way through the update and the system blacked out/crashed again. I showed it again to the store rep and w/out any more discussion, he promptly took the machine and exchanged it for a new one.
We've had the new machine since with no hiccups. Hope it stays that way. Either way, this experience illustrates to me that at least some Apple assembly plants are still putting out Macbooks that exhibit this problem. Im sure that at this point its a dwindling number and my story could be related to a completely unique problem specific to the unit I bought. This is my 4th Apple computer purchase and I remain a loyal and happy customer.
I have a week 30 macbook. Unfortunately it has both the moo and the whine, so I'll be sending it back this week for a full refund. My previous week 27 macbook had the whine and several dead pixels.
I'm dissapointed that Apple still hasn't fixed the moo issue. It's really annoying.
Not sure what to do next though, I guess I'll wait for rev. b...
I'm dissapointed that Apple still hasn't fixed the moo issue. It's really annoying.
Not sure what to do next though, I guess I'll wait for rev. b...
twoodcc said:
Oh that is good to know. I Have a black macbook, and I just sent it back via fed ex, and a new one is coming tomorrow. Apple promised overnight shipping on Friday when I got my new MB ordered and was supposed to come at the lastest on Monday, but Fed Ex says... Tuesday. Blah!!!!
Well I have problems...
My macbook's a week 30 and it's experiencing the random shutdown problems other macbook owners are having. I ordered mine on line on July 26th, recieved it August 1st. A newbie to Macs, I haven't added extra RAM, or parallel or bootcamp, or even any additional widgets. I installed Microsoft Office for Mac, but didn't even have any documents created before the problems started.
It went in for repairs a week ago today, but surprise, surprise, the Apple Genius "couldn't recreate the problem". Although when I checked the log after I got it home, it showed the log entry "Previous Shutdown cause: -82" during the time it was in Apple's custody.
This is the code other Mac users with random shutdown problems have reported seeing in their logs at the times they've eperienced problems. I've found it in mine every time my laptop has shutdown, when it's ACTUALLY STARTED!! Most of the time, mine shuts down before it can fully load the OS. In fact, it took a whopping 50 attempts before I could get the thing up and running to post this today.
And while I seem to be one of the few week 30 macbook owners with this problem, there have been over 600 responses to the "Randomly turns off thread" at Apple Discussions.
http://discussions.apple.com/thread.jspa?threadID=544012&tstart=0
BTW - there MIGHT have been more, but Apple locked the thread down. Last I heard, over 20,000 people had viewed the thread. So this could be a problem of a major scale. General concensus now seems to be settling around either the logic board, or the Intel duo processor. Whatever the cause, one guy who posted to the apple discussions board said his macbook has been replaced 5 times!!!
So I'm off to the Apple Store again today. Since I got mine back last Monday, it's had shutdown problems every day but yesterday - I was having a bad day anyway, so I just didn't feel like messing with my mac and I used my old Dell laptop instead. If this time doesn't fix it, I'm returning it (I have a 30 day window since I payed for it using Amex) and buying another Dell. At least they had the good grace to admit they were having problems, and issued a recall. And with the money leftover, I can afford to buy new software, or take a relaxing weekend away. After all the problems with my mac, I suspect I'll need it.
My macbook's a week 30 and it's experiencing the random shutdown problems other macbook owners are having. I ordered mine on line on July 26th, recieved it August 1st. A newbie to Macs, I haven't added extra RAM, or parallel or bootcamp, or even any additional widgets. I installed Microsoft Office for Mac, but didn't even have any documents created before the problems started.
It went in for repairs a week ago today, but surprise, surprise, the Apple Genius "couldn't recreate the problem". Although when I checked the log after I got it home, it showed the log entry "Previous Shutdown cause: -82" during the time it was in Apple's custody.
This is the code other Mac users with random shutdown problems have reported seeing in their logs at the times they've eperienced problems. I've found it in mine every time my laptop has shutdown, when it's ACTUALLY STARTED!! Most of the time, mine shuts down before it can fully load the OS. In fact, it took a whopping 50 attempts before I could get the thing up and running to post this today.
And while I seem to be one of the few week 30 macbook owners with this problem, there have been over 600 responses to the "Randomly turns off thread" at Apple Discussions.
http://discussions.apple.com/thread.jspa?threadID=544012&tstart=0
BTW - there MIGHT have been more, but Apple locked the thread down. Last I heard, over 20,000 people had viewed the thread. So this could be a problem of a major scale. General concensus now seems to be settling around either the logic board, or the Intel duo processor. Whatever the cause, one guy who posted to the apple discussions board said his macbook has been replaced 5 times!!!
So I'm off to the Apple Store again today. Since I got mine back last Monday, it's had shutdown problems every day but yesterday - I was having a bad day anyway, so I just didn't feel like messing with my mac and I used my old Dell laptop instead. If this time doesn't fix it, I'm returning it (I have a 30 day window since I payed for it using Amex) and buying another Dell. At least they had the good grace to admit they were having problems, and issued a recall. And with the money leftover, I can afford to buy new software, or take a relaxing weekend away. After all the problems with my mac, I suspect I'll need it.
I've had a week 24 and a week 26, both started turning pink within a week, now on a week 30 which is starting to turn yellow. I'm actually really embarrassed about going back to the local reseller to exchange it. This is my first experience with Apple, and it's a bit of a (bad) joke.
post shutdown HEAT!!
week 10.. this happened TWICE:
i shut down the computer normally. pack it up, put it in the carrying case, and then a few hours later when i open it up its BURNING HOT, like it was never shut off or working extremely hard. then it wouldn't even turn on, probably because it was overheating. the book would finally turn on after it cooled down but i could SMELL the heat! it was crazy! not too mention it was very stressful.. any explanations?? HELP.. i coulda fried an egg on it. just don't want it to happen again. thx
week 10.. this happened TWICE:
i shut down the computer normally. pack it up, put it in the carrying case, and then a few hours later when i open it up its BURNING HOT, like it was never shut off or working extremely hard. then it wouldn't even turn on, probably because it was overheating. the book would finally turn on after it cooled down but i could SMELL the heat! it was crazy! not too mention it was very stressful.. any explanations?? HELP.. i coulda fried an egg on it. just don't want it to happen again. thx
My build has 4 digits after the letter, x being the numbers and y being the letter, what would be it's week?
looks like this: XYXXXX
looks like this: XYXXXX
week 26
I'm week 26 and bought it like 4 weeks ago. last two weeks its acting up with random shutdowns. Ive been to apple store and they tell me its known issue and will replace heat sink...???
I'm week 26 and bought it like 4 weeks ago. last two weeks its acting up with random shutdowns. Ive been to apple store and they tell me its known issue and will replace heat sink...???
flowlikeh2o said:
You need to make sure that after clicking shutdown, the screen is totally off for a few seconds before closing it. This is a common Apple notebook issues, where you'll close it too early and it'll kinda hang and get very very hot after a while.
macbook won't turn on... sniffle..
this is my first mac (macbook arrived in august) and i've had some problems. all was fine, until the cd drive decided that it would stop accepting all cds... sent it in for a new drive. working fine, but now sometimes (more often than not) when i've shut it down, it will refuse to come back on. it makes noises but a gray screen comes up and nothing happens. only re-setting the pram will bring is back from the dead. anyone know what this is about? i love the little guy, but seriously.. this can't be the norm.
warning... i have the most basic of knowledge about computers (can turn them on... usually... sadly, i seem to be losing that skill now.).
this is my first mac (macbook arrived in august) and i've had some problems. all was fine, until the cd drive decided that it would stop accepting all cds... sent it in for a new drive. working fine, but now sometimes (more often than not) when i've shut it down, it will refuse to come back on. it makes noises but a gray screen comes up and nothing happens. only re-setting the pram will bring is back from the dead. anyone know what this is about? i love the little guy, but seriously.. this can't be the norm.
warning... i have the most basic of knowledge about computers (can turn them on... usually... sadly, i seem to be losing that skill now.).
Mine is a week 30 Macbook, and within two weeks of owning it I started to get daily RSDs. I haven't had time to take the book in for maintenance, but I'll have to bite the bullet eventually.
The interesting thing is that the RSDs typically happen within 5-10 minutes of powering up. If I don't get an RSD within that timeframe, the machine will stay on indefinitely under all sorts of load conditions.
But if I let it go to sleep, or if I shut it down, I'll get RSDs again when the book powers up.
The interesting thing is that the RSDs typically happen within 5-10 minutes of powering up. If I don't get an RSD within that timeframe, the machine will stay on indefinitely under all sorts of load conditions.
But if I let it go to sleep, or if I shut it down, I'll get RSDs again when the book powers up.