Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
There you go, NEVER buy first gen of any new Apple products!

On top of that, the i7 is known to heat up and I am personally not comfortable with electronic heats up (even they are within designed spec).

I had an HP DV6 i7-740, that heats up and the motherboard fried. I don't doubt this won't happen to a Macbook Pro.

Hardly 1st gen...more like 3rd (or possibly 4th)
 
bet there is so much thermal paste on the GPU/CPU its acting as an insulator rather than as a conductor of heat on most of these, that and apples priss poor quality control and testing of new products under load (im sure they get the 1st build units, install OSX and go "yup that works, ship it tommorow")

I love my early 2008 MBP (Nvidia issue aside) but i would never buy a 1st gen apple product without apple care and plenty of backup space, this includes speedbump major changes like the new MBPs, to many untested things to go wrong.

However, its what we buy applecare for isnt it, a failsafe against apples form over function method of manufacturing. Applecares existance is, in and off itself, proof apples knows its products are likely to fail due to manufacturing problems and a way of sidestepping lawsuits.

now Hurry up new iMacs, i need a Desktop at the end of April dagnammit !
 
Sorry -- no intention to leave anyone in suspenders (sic).

The point was to say that the system froze almost immediately. At that point the whole screen updating stopped and the system was interactively non-responsive, but I could still SSH into it from another machine. Up until the machine froze (all of about 30 seconds), top showed what I expected -- 5 processes each consuming 100% of the CPU, PhotoBooth consuming about 30% and all the usual other stuff.

From research and reading all the posts (500+ now) in the main Apple Discussion thread on this it appears that:


Anyway, if anyone were looking for a recommendation to buy a new machine right now, my advice would be to wait for this to be resolved. This is the first time in FOREVER I have violated my inviolable principle of NEVER buying the first batch of anything Apple, and I have been properly rewarded for my impatience :)

Best of luck to all struggling with this issue...

Scott

Wow, a very comprehensive report Scott! Many thanks for summarizing the key issues to date regarding all of this. Hopefully a fix for this turns up soon as I was hoping to pick up one of these new "ThunderBooks" within the next month or so.
 
My 2006 Intel powered MBP gets as hot as a Forman Grill and I use it graphic intensively for hours on end with no problem ever. Love this thing!
 
The amount of people try to 'recreate' this issue is pretty funny, if it hasn't happened to you in every day use then chances are it never will, hence it's a non-issue.
 
The amount of people try to 'recreate' this issue is pretty funny, if it hasn't happened to you in every day use then chances are it never will, hence it's a non-issue.

I might be wrong, but the circumstances under which this occurs are not at all outside of the everyday tasks of a mbp.

To me this a real issue, but I also believe that it will be fixed with an update.
 
I might be wrong, but the circumstances under which this occurs are not at all outside of the everyday tasks of a mbp.

To me this a real issue, but I also believe that it will be fixed with an update.

My comment was aimed at all the people that have never had the issue occur naturally yet are trying to make it happen.
 
My comment was aimed at all the people that have never had the issue occur naturally yet are trying to make it happen.
If it takes a hardware fix (rather than a firmware update or such) I'd rather know early rather than wait for my warranty to run out, and the fix to cost me $1000.
 
I have not had this problem on mine thankfully but I will have to do some load testing tomorrow. Hopefully for those affected, this can be fixed with some sort of software update.

Nonsense. If you have a 2011 Macintosh that crashes when used heavily, you bring it to the store and have it fixed or replaced with a new one under warranty. That is what warranty is for. If the problem can be fixed somehow, then Apple can do that at their own cost and sell your Macintosh as refurbished when it is fixed.

Is there a limit on how many times you can get warranty work done? JW

Until the problem is fixed. There will be some point depending on your local laws where you have a legal right to return a faulty device and get your money back.

If it takes a hardware fix (rather than a firmware update or such) I'd rather know early rather than wait for my warranty to run out, and the fix to cost me $1000.

In the UK, if it needs a hardware fix then you would have a problem that was already present when you bought the device, and such problems have to be fixed for up to six years. (Note: A low quality component that works fine on a brand new computer but stops working after 13 months would not fall under this law; it would have to be something that is already broken when you buy the computer. )
 
Last edited:
If it takes a hardware fix (rather than a firmware update or such) I'd rather know early rather than wait for my warranty to run out, and the fix to cost me $1000.

Relax - newest gen mbps' warranty lasts at least 11+ months more, I think we can remain confident everybody will have the chance to get this fixed before it expires :rolleyes:
 
i have done all kinds of tests, i cant get it to hang.

i do photoshop alday long, not hat cpu intensive... i have played game for like 50 min, no hang... i run win7, backtrack in vm fusion, no issues at all..

shall try the yes written to dev/null when i come home
 
My Late 2008 MBP locks up randomly, regardless of load. Be happy that you at least know why yours locks up! This is part of buying an Apple product, they look great and have great features, but their heat dissipation and the quality of the chips are extremely bad. Take the example of the bad nVidia bumps, or any other nVidia problem that almost all MBPs with nVidia chips had. It's just a matter of putting the wrong kind of metal in the soldering, and it fails. You'd think people how make chips know what material to use!
 
Obviously, you still haven't turned on the PC then.
Immature crap like this is exactly what give Apple users a bad reputation.
I had no trouble whatsoever with my previous computer running Windows XP (nor running Linux or FreeBSD). Apple/OS X isn't the only stable combination out there.
 
Glad I have a 2010 MBP. Only thing annoying me is stupid shiny keys! My old 2007 model looks brand new :(

You need to get the ClearSkin keyboard protector sold by 'KB Covers' (http://bit.ly/3K8jk2). It's amazing and you barely even realise it's there. No shiny keys for me! Sold my 2009 MBP after receiving the 2011 model. I could not tell the difference between the two (externally, of course). =)
 
Obviously, you still haven't turned on the PC then.

Oh its even more funny when you repeat/steal another users comment.

I would say that "Obviously" you are incompetent with computers and fall into the Mac User category of Ex-Windows users who fell for every fishing scam and Virus trick out there. You most likely had no concept of computer maintenance.

I've been using Windows, Mac, and Linux for over 25 years and almost never had a problem.

There are incompetent USERS ....Not Computers

I agree with excape
 
Last edited:
I can't reproduce the problem using the yes > /dev/null test in the wiki link on my new 15" base model MBP. Don't have time to try the others now, but I might later.

So it's certainly not all affected, and I'm glad I don't seem to be among them. But I definitely hope Apple releases some kind of fix soon for those who are experiencing this!

I am having the iTunes bug, though, so I hope that gets fixed, soon, too.

Which iTunes bugs??



For everyone 'Apple horror story' you have, I can point to a heck of a lot more from the PC world - and that isn't even getting the operating system involved. The operating system in the PC world is but a small component when compared to the larger clusterf-ck that is the PC's race to the bottom and cutting costs when ever and where ever possible.

Everybody does same thing including Apple they try to cut there cost but they keep high prices. PC world as well keep low cost but they also keep lower prices because of competition. You have one Apple manufacturor and you have 1000 PC makers. For Apple you can go only on one place for PC you can go on every corner, if Apple have competition for similar product they would dump there prices as well.


Glad I resisted the urge to sell my 2010 MBP to upgrade...

Me to i bought recently iMac and decide to wait for at list half year before i even consider buying new MBP...glad that i did follow my instinct.
 
I built my own PC 3 months ago (I do not do laptops for I get them for my job). It has not crashed or frozen even once. Obviously - no viruses (it's Windows 7)

I built my own PC soon two years ago and I've been running both Mac OS X 10.5 and 10.6 on it. Once I got everything in place things has been super stable. In fact I'm surprised at how stable it is considering the hacking needed. Sleep an wake from sleep is super stable, and I even have an external FireWire sound card and Apple's old iSight attached plus some other things via USB.

Windows 7 on the machine is stable too, but I have issues getting it to sleep (it logs out instead) and also the clock seems to forgets it's settings between restarts (it's one hour wrong) even if I set it to sync via Internet (time server).

A bit funny that Mac OS X can work better than Windows 7 on a custom-built PC. :)
 
My comment was aimed at all the people that have never had the issue occur naturally yet are trying to make it happen.

Well, in some senses, this is important. For me, the problem occurred simply as part of the normal transfer of data from my old machine to the new one. An occasional "glitch" is expected, particularly with new product. But after four hangs in several hours, each requiring a hard reset, one begins to wonder if there's a problem. That's what led to the various diagnostic tests to see if the problem could be reliably demonstrated.

I'd LOVE for the vast majority to be saying, "There's no problem at all -- these are isolated cases." That would give me confidence that I simply got a bad machine. But when I read about people getting two and three replacements from different locations, and still being able to reproduce the freezes, it begins to look much more like a systemic problem. Remember, we're not talking at all about over-taxing machines here... true, the dev/null test and the major compilation tests DO tax the machines, but the vast majority of freezes I (and others) have experienced happened randomly, when the machine was essentially sitting idle -- no exceptional heat, no out-of-the-ordinary activities -- just switching between windows, running a screen saver, waking from sleep, or just sitting around with the 8 threads contemplating a restful snooze on the beach (ok, so it's a silicon beach!) :)

Apart from a few people who HAVE chimed in and said "I don't have a problem", many, many others have been able to reproduce the issue when they've tried one or other of the methods to recreate the issue. So, maybe it's truly the case that there are a few, isolated issues, and these are the ones getting the press -- but every day we see more and more people highlighting this, thinking that "they were the only one seeing this"...

For me, this isn't an academic question. I cannot trust a machine that is going to die randomly during my work day. I know from personal experience that this will end up corrupting a disk, losing valuable data or wasting a whole lot of time for people counting on the results of what I do. I've had Macs for almost 20 years and apart from failures which ultimately could fully be explained as either hardware failure (and then replacement parts have solved the issue) or software problems (which have gone away when the offending software has been removed), I've never seen an out-of-the-box/vanilla-installation-of-Mac-OS-anything fail with such regularity as this new machine...

So, thanks to all who are helping to identify whether a bunch of us simply have a "bad lot" (in which case replacements under warranty will fix everything just fine), or whether there really is a systemic issue that suggests it will be better to wait until "Rev. B"...

Cheers,
S
 
Never had mine under load yet, but not going to bother trying it otherwise i'll end up OCD about it.

Also, its funny seeing all the 2010 owners constantly looking for excuses not to upgrade. Just **** and enjoy your mac ffs, you probably dont use half the power the dual core i's give, never mind the SB quads.
 
Temperatures hitting 90C? That's a thermal trip, not normal operation.

I've done 2-day Minecraft map renders, as well as 4-hour HandBrake encodes (man this thing is fast!), and my CPU and GPU temperatures never exceed 65C. Granted, I've set my fans to be a bit more aggressive with Fan Control.

This sounds like poor thermal paste application ala the iFixit teardown, than just drivers. Drivers may be a part of it, but drivers aren't going to result in 25C higher temps than what should be seen.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.