Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
/offtopic: hey Hal, your attitude is beyond annoying. take a dose of your own medicine as you're being equally unhelpful by cluttering the thread with attacks against everyone who isn't having problems.

i have been having these freezing issues really badly for a while. my i7 17-inch 500 gb started getting worse and worse so i took it in. the crappy repair tech replaced the HD because tests showed it running slightly slow. naturally, this did NOT fix the problem and the crashes continued.

i had noticed many of the display crashes were due to an NVIDIA channel exception which led me to this and another thread. as instructed i downloaded gfxCardStatus and set the display to intel-only. since then i have had NO crashes. for me and probably for many others, the display crash is undoubtedly related to apple's crap compatibility with NVIDIA.

i have NOT tested forcing to NVIDIA-only, mostly because another thread showed that this results in less battery life and higher running temperatures.

for anyone who knows that their issue is NOT hard-drive related i would suggest trying this.
 
According to one poster on the Apple boards, Apple engineering is aware of the problem and looking into a solution.

If this is true, it would be great if Apple would acknowledge the problem. I want to buy a new laptop, but there is no way I am going to until I know this problem is solved.
 
jpodtbc thanks for your valuable input. I'll try Intel-only with gfxCardStatus starting today. Thanks of course to the dude here who wrote the app too!

Anyway I don't get why a MacRumors poster can write software to switch MBPs to Intel-only but Apple can't figure this crap out. Especially since it's been oh I don't know MONTHS since Apple's known about this. They're over 50 pages on the Apple discussions on this issue. I really assumed 10.6.4 would both fix this issue AND put an option into the System Prefs to do Intel-only graphics. I hope 10.6.5 adds this.
 
Been reading this thread because I was thinking about buying a 17'' mbp and wanted to be aware of any issues...

Right now I have been using a 2010 13'' base model mbp for 30 days(I borrowed it from my roommate to test out). I have it plugged into a 24'' monitor and have been running windows 7 via bootcamp exclusively. I think i booted into mac os once in 3 weeks.

Up till today, it was running flawlessly, more stable than any pc I have used running windows. But today, the cursor suddenly froze and the keyboard stopped responding. I mashed buttons and nothing happened. I was on the phone so I just left it alone, and then suddenly after 2-3 minutes, it was working fine again and the mouse was moving.

This sounds like some of the same "freezeing" that people are talking about in this thread right?
 
I'm sending my MacBook Pro back:(
I'm using my DULL XPS 16 in the meantime
I have talked to Apple care on 4 separeate occasions and they said to swap the mechiene out.
Is there anything I need to know? I have been reading that it could be the Hard Drive or the Logic board no one is sure what it is!:(
Sry for the sad faces I'm just sad for having put myself into nearly $2800 in extra loans for a lemon. Is there anything I can do or is it in Apple court??
Thanks
A frustrated and sad college student
 
/offtopic: hey Hal, your attitude is beyond annoying. take a dose of your own medicine as you're being equally unhelpful by cluttering the thread with attacks against everyone who isn't having problems.
Maybe.

Or maybe there were 2,658 people all set to post "hey no problem here" —until they read my comments that is. ;)
 
Been reading this thread because I was thinking about buying a 17'' mbp and wanted to be aware of any issues...

Right now I have been using a 2010 13'' base model mbp for 30 days(I borrowed it from my roommate to test out). I have it plugged into a 24'' monitor and have been running windows 7 via bootcamp exclusively. I think i booted into mac os once in 3 weeks.

Up till today, it was running flawlessly, more stable than any pc I have used running windows. But today, the cursor suddenly froze and the keyboard stopped responding. I mashed buttons and nothing happened. I was on the phone so I just left it alone, and then suddenly after 2-3 minutes, it was working fine again and the mouse was moving.

This sounds like some of the same "freezeing" that people are talking about in this thread right?

I had the same thing happen to my 2010 MBP 13" using Win 7. Occasionaly, the system would hang (cursor frozen, no inputs registering, etc.) and then jump back into action 10-15 seconds later.

I found it would happen more frequently when watching videos, using Flash, etc.

Ending up sending it back.
 
I was planning on pulling to trigger on a new MBP 15"..should I wait until this is resolved? :confused:

I am waiting, and I recommend you wait... though be advised that this problem might never be solved until next revision (aka perhaps end of this year or next one...).
People have said that Apple engineering has acknowledged the problem but it doesn't imply they will be able to solve it (if it's hardware related and an internal revision can't be done then... next revision, and if it's software related the same applies). As an example... the screen flickering of late 2008 mbp... I don't know if it was acknowledged or not, but many suffered it... and there are still people "enjoying" this feature; according to some post on Apple's discussions... it is now a known problem and it can't be solved (the approach was changing the logic board but it doesn't seem to solve it as it is back after some time...)

I will not give any euro to Apple until this problem is solved. It seems not everybody is suffering from this, but I'm sure there are many who don't even know they have a problem and think it is their problem.
I advise you to wait unless you absolutely need it; and in that case... be prepared for the worst ;)
 
I need one within a week since my previous 1st Gen MBP is fried from coffee being spilled on it and I start summer school in 1 week..this is very unfortunate :mad:

I am waiting, and I recommend you wait... though be advised that this problem might never be solved until next revision (aka perhaps end of this year or next one...).
People have said that Apple engineering has acknowledged the problem but it doesn't imply they will be able to solve it (if it's hardware related and an internal revision can't be done then... next revision, and if it's software related the same applies). As an example... the screen flickering of late 2008 mbp... I don't know if it was acknowledged or not, but many suffered it... and there are still people "enjoying" this feature; according to some post on Apple's discussions... it is now a known problem and it can't be solved (the approach was changing the logic board but it doesn't seem to solve it as it is back after some time...)

I will not give any euro to Apple until this problem is solved. It seems not everybody is suffering from this, but I'm sure there are many who don't even know they have a problem and think it is their problem.
I advise you to wait unless you absolutely need it; and in that case... be prepared for the worst ;)
 
I wouldn't wait.

I had a couple of freezes since owning my MBP but since upgrading to 10.6.4 I haven't had one. Not sure if that's the reason or it's just a coincidence.
 

Yes. Was getting random freezes in Win 7 64 bit. (Infrequently, but still very annoying. Maybe 4-5 times during a week.)


I have a 15" i7.

So far, so good while running that fix under windows 7 for dev work.

(Have had fix in place for a few weeks now without issues.)

Am VERY interested to find out if anyone else has tried this fix and what their results are.
 
I've had my MBP 17" i7 AG for 2 weeks and am having these freezing issues.

This is my first Mac and I wasn't expecting these freezing issues. I've re-imaged 4 times. In addition to regular Mac applications having very slow performance, the performance of my VM (Fusion) on top of the OS/X problems are magnified! What's odd is that I open up the Activity Monitor (by the way, even opening this application up takes 20-30 seconds) the activity monitor shows no aberrations.

Thoughts on what I should do? I cannot afford to be without this laptop for business reasons.
 
I had the same thing happen to my 2010 MBP 13" using Win 7. Occasionaly, the system would hang (cursor frozen, no inputs registering, etc.) and then jump back into action 10-15 seconds later.

I found it would happen more frequently when watching videos, using Flash, etc.

Ending up sending it back.

Ok, this happened again today. This time it didn't come back though so I had to restart. Both times it happened right after I was away from the computer for a while. I start to move the mouse, then everything freezes right when I go to double click on something on my desktop, so I'm thinking it might be a problem with it not going to sleep or waking up from sleep properly. But That's 2 days in a row now after no problems for 30 days. So that doesn't really make sense that it's something wrong with it going to sleep/waking up from sleep, because I have been doing that 3x a day for 4 weeks w/ no problems. I feel better knowing I'm not the only one with these issues, but that means, I will have to wait a bit before I decide to by my own mbp. Soon I have to give this 13'' mbp back to my roommate who i swapped laptops with, but for now I will just keep monitoring the issues and see what happens. It's not that big of a deal right now, but since it's a new machine and already having problems, I figure it's likely to only get worse, not better.
 
My 13" just froze with the mouse being unresponsive as well. I've had this issue on a 2009 13" macbook pro with the nvidia 9400m and I remember when looking at the console log it had something to do with vmware fusion.

I cant believe that this issue is still around with the newer 13". I remember installing windows via bootcamp and then running vmware fusion via bootcamp corrected this freezing issue.

4746385183_b2c21e4c77_b.jpg


This is what my console looked like.
 
This is so weird because before the newest update I used to freeze twice a day and since I updated I never froze again.
 
My 13" just froze with the mouse being unresponsive as well. I've had this issue on a 2009 13" macbook pro with the nvidia 9400m and I remember when looking at the console log it had something to do with vmware fusion.

I cant believe that this issue is still around with the newer 13". I remember installing windows via bootcamp and then running vmware fusion via bootcamp corrected this freezing issue.

4746385183_b2c21e4c77_b.jpg


This is what my console looked like.

It happened to me again today on the 2010 13'' mbp I am using. This time the cursor only froze for about 20 sec. That's 3 days in a row now. I am starting to think that it must somehow be a display driver/video card problem, because today when it happened, it was right after i turned the monitor back on after not using it for a while. It was not sleeping or anything, but I have the monitor set to turn off after xx minutes, so the screen was off, and it happened within 15 sec after I moved the mouse and the screen turned back on.
 
It happened to me again today on the 2010 13'' mbp I am using. This time the cursor only froze for about 20 sec. That's 3 days in a row now. I am starting to think that it must somehow be a display driver/video card problem, because today when it happened, it was right after i turned the monitor back on after not using it for a while. It was not sleeping or anything, but I have the monitor set to turn off after xx minutes, so the screen was off, and it happened within 15 sec after I moved the mouse and the screen turned back on.

For me it was when just browsing on the website (on a forum typing something) and it just froze. For me it seems to be the vmware fusion because so far it has froze twice (once a couple days ago too) and under console both times are showing the vmwarefusion.icn not found.
 
I'm full of battery.
Just read the Apple Support discussions, and you will see. Some started to say it's releated with the graphics card "on-the-fly" changing.
Apple it's investigatting it.

Look, from Apple Support forums, from source on OP:

Just to let you guys know, I have been contacted by a liaison from Apple's engineering dept.

They are aware of the reports of this issue, and are investigating the reports.

So, Apple's not ignoring it :)

(I would say more but they preferred that I keep any post here concise and nondescript. I expect some of you in this thread will also receive phone calls!)


They started to change HDDs, from Seagate to Hitachi to all the people that is out of the 14 magical days.

I repeat again: it's not a matter of "my machine yes" and "my machine not"... It's a matter of ALL THE MACHINES. It will happen in any moment, or at last, this is what seems to be. It's a pitty.


I have been searching for a way to fix my dying Macbook Pro for several days now and I came across this thread. I have an older model (2007, Intel Core 2 Duo), but it sounds like exactly what happened to me.

I had one of those defective NVIDIA card that Apple extended the warranty on, so they replaced it for no charge. When I got it back, I noticed an issue with freezing, so I performed Repair Permissions ... unfortunately, while this task was being processed, the magnetic power cord became detached and the machine froze. (Battery had not yet run out.) I reconnected the power and waiting several hours before deciding it was not going to unfreeze itself and was forced to hold the power button down ... very not good while repairing.

Now I'm stuck with starting in Single User mode, can't verify or repair the disk, getting invalid node structure, can't repair tree, large usage of RAM by kernel task. Essentially, I've just been so happy that I can even start up to have a chance to back everything up!

Has anyone heard anymore about what Apple is doing about this?
 
Good luck, hope this gets resolved.

Nice handle, dae ham min guk :cool:

For me it was when just browsing on the website (on a forum typing something) and it just froze. For me it seems to be the vmware fusion because so far it has froze twice (once a couple days ago too) and under console both times are showing the vmwarefusion.icn not found.
 
I registered just to share my experience.

First owned a late 2009 MacBook Pro 13". Worked fine at first, then after a bit it would randomly freeze upon one of three events:

  • Waking the computer from sleep by opening the lid (This was rare)
  • Connecting a VGA DisplayPort adapter while the computer was in sleep, then waking the computer
  • Disconnecting the VGA DisplayPort adpater at any time (This was rare)

It got to the point I was nervous to even use the adapter. The problem seemed to miraculously fix itself after a time, and I never had the problem again. Other activities, no issues: Running multiple VMs, iTunes, video/audio encoding, etc...no issues at all. Ran like a champ, served me well - to the point I was running a VM, a Keynote presentation, a Flash presentation, and some digital signage at a recent Padres show we sponsored, for 7 hours straight, without a hitch.

I recently sold it to a co-worker and bought a 15" i5, and haven't had any issues with it except for one self inflicted one where, on boot, the gray screen takes a LONG time to go away. Again though I think that was my fault.

To those who say "Give it time, it will happen!!" You might be right. Then again, you might not. The earliest of adopters might have gotten bad eggs. The reality is we just don't know at this point, and anything else is sheer speculation.



For reference, I also have the 7200RPM Hitachi hard drive, and for what it's worth, the issues in the 13" stopped when I bought that drive and installed it (did it to improve VM performance, then swapped it into the 15"). Those who have the OEM drive and the SSD, have you ever stopped to consider that it might be something with the drives Apple has selected?
 
How widespread is this problem? In particular for the base 15 inch model? :confused:

Very.

In all seriousness if you need a computer for work or other mission-critical applications you can not risk having a HARD CRASH while working in:

DO NOT BUY a MacBook Pro.

I haven't heard as many things about the MacBooks. If you want Apple laptop, get a MacBook. And they have much better WiFi signal reception.

To people saying "well I don't have the problem so is not be universal"...It's impossible to say whether it is or is not universal. But it sure feels like if you haven't seen this yet you're lucky. It's likely a driver issue (thus essentially universal).

I love Apple but their quality has taken a nose-dive. Macs shouldn't have these problems. It's been months, no official word from Apple.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.