Q: MacBook Pro (2010) Freeze

Hi Guys,

I caught a LOG from the console right after my already repaired device froze up on me again. Reporting this issue to apple bug report I got the answer that this is "unit specific" and that I should again bring it to repair. For what? Getting the device back to freeze up on me again? I am really really dissapointed in Apple!

Anyways, here is the LOG, it seems that the kernel tries to regain control of the graphic card but can't for some reason.
At 24.09.10 07:17:51 I did a hard shutdown.

b.r.


24.09.10 07:16:51 kernel 6425f4d4d555f4c494d4954565f545241502863686964293a307831
24.09.10 07:16:51 kernel NVRM-RC: 1 66666339
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307832353430
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a30783131
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a3078340a
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307831303430
24.09.10 07:16:51 kernel NVRM-RC: 1 333036
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307831
24.09.10 07:16:51 kernel NVRM-RC: 1 66666339
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307832353438
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a30783131
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a3078340a
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307831303430
24.09.10 07:16:51 kernel NVRM-RC: 1 333036
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307831
24.09.10 07:16:51 kernel NVRM-RC: 1 66666339
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307832353530
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a30783131
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a3078340a
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307831303430
24.09.10 07:16:51 kernel NVRM-RC: 1 333036
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307831
24.09.10 07:16:51 kernel NVRM-RC: 1 66666339
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307832353538
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a30783131
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a3078340a
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307831303430
24.09.10 07:16:51 kernel NVRM-RC: 1 333036
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307831
24.09.10 07:16:51 kernel NVRM-RC: 1 66666339
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307832353630
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a30783131
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a3078340a
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307831303430
24.09.10 07:16:51 kernel NVRM-RC: 1 333036
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307831
24.09.10 07:16:51 kernel NVRM-RC: 1 66666339
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307832353638
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a30783131
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a3078340a
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f504649464f5f494e54525f303a307831303031
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f504649464f5f4341434845315f444d415f53544154453a307863303030
24.09.10 07:16:51 kernel NVRM-RC: 1 303030300a
24.09.10 07:16:51 kernel NVDA(CopyEngine): Channel exception! exception type = 0x6 = Fifo: Parse Error
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307831303430
24.09.10 07:16:51 kernel NVRM-RC: 1 333036
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307831
24.09.10 07:16:51 kernel NVRM-RC: 1 66666339
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307832303838
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a307830
24.09.10 07:16:51 kernel NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a3078340a
24.09.10 07:17:11 kernel NVDA(OpenGL): Channel timeout!
24.09.10 07:17:31 kernel NVDA(OpenGL): Channel timeout!
24.09.10 07:17:51 kernel NVDA(OpenGL): Channel timeout!
24.09.10 07:18:42 kernel npvhash=4095
24.09.10 07:18:42 kernel PAE enabled
24.09.10 07:18:42 kernel 64 bit mode enabled
24.09.10 07:18:42 kernel Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386

Beach ball, beach ball, beach ball, beach balls !
Omg, never seen so many beach balls in last 3 years.
@ work I changed my Macbook pro several times, and, on the core2duo age, I never had so many problems as now with the brand new i7 chipset.
Anyway there are still people with 13" MB that have same problem, so I do not think it's i7 chipset fault.
So I really don't know where the problem can be found.
The really bad sensation is that Apple ain't telling anything about this problem...

I've turned off Sudden Motion Sensor and since then I haven't got a single freeze. It's been 4 days since then.

Beach balls may simply be a memory problem. Safari is such a memory-gobbling monster that even on my 8GB i7 I occasionally run out of memory because of Safari. Just today it started eating memory so fast that my machine was completely unresponsive, but I managed to kill Safari from a unix shell - and my machine was fine again.

I've been having beachball issues from day 1 as well, EFI update didn't fix anything. I find that after a fresh boot the beachballing is a lot worse (I'm guessing nothing is cached in the RAM yet). I've done all the changes that have been suggested to keep the HD from idling and motion sensors but it haven't fixed the issue completely, it's definitely helped though.

I was close to buying a Hitachi or WD to replace it but I've read it's not guarantee to fix the issue…oh and Seagate *****!

Apple, where is the fix to this? The i7 feels much slower than it should, and the negotiated link speed is 1.5Gbps instead of 3.0Gbps.

First time poster. Posting in this thread for another case of Macbook Pro 13-inch freezing.

I bought this laptop from an apple store on the 29th May 2010.

In the first few months it would completely freeze every now and then. The only solution to hold in the power button and turn it off then on. I thought nothing of this as it only happened a couple of times in a few months. I was still annoyed however as I know it should not be doing this.

It's not September, and in the last couple of days it has been happening quite frequently. Sometimes 4 times in a row, each within 2 minutes of me turning the computer off and on.

I gave applecare a call. We did the verify disk and then repair disk. But the freeze still happens.

Right now I haven't opened iTunes and the laptop has not frozen yet. I believe the whole freezing thing could be an iTunes 10 problem. Maybe it is that that is freezing up the whole computer. (no idea why it would be doing this though).

Anyways just adding to this thread to present another case of the 2010 Macbook Pro 13-inch freezing. Hope apple an update to fix this. Not sure what else to do. I think I'm going to give applecare another call to say the problem is still ongoing. They'll probably just take me through the steps to reformat the hard drive though, which I really couldn't be bothered doing.

Meh, my first mac and this is a pretty frustrating thing to happen in the first 4 months of use.

Message was edited by: FTorres

Message was edited by: FTorres

So this time when I turned it off and on after it froze, I didn't open iTunes the whole time. After a while of using the laptop, it froze again. So I guess it's not an iTunes problem.

Want to give applecare a call again now but it's after 6pm on a Saturday so they're not available to call right now.

This freezing of the whole computer is very, very annoying and frustrating.

To all users..Dont waste more time in tests or repair disk..is very clear is a hardware failure..
Mine is since yesterday at apple service.....if any fail is discovered ,logic board will be replaced...thats what tecnician said me.

If you prefeer to repair them just ending warranty time,you will not have time to check the repair ,and its results..
Cheers.

Again.. someone here with issues.

A friend and me ordered 2 new MBP 2 weeks ago.. Got them yesterday. (Actually I got mine today because it was shipped to him)

His MBP, no issues... Mine.. it keeps freezing non-stop..

It looks like it's only when the disk get a lot of I/O... for example, it crashed when I was copying my VMWare machine onty my new MBP.

Earlier today I have reinstalled the MBP with a new partition. It crashed before and after doing all the Software Updates.

I tried to remove some ram.. Removed one of the 2 2GB chip.. it was still freezing.. did the same thing with the 2nd chip.. Just to make sure it's not the ram.. looks like the issue might be with the disk.

Here are my specs.

17" i7, 4GB Ram, 128GB SSD

My friend (No issues with his MBP)
17" i7, 8GB Ram, 256GB SSD

I'm really ******.. I think I'll have to go at the Apple Store tomorrow.. hope they can fix it on site

Finally a little update..

Found out that every times my MBP Freeze I get a lot of I/O Errors for the device disk0s2.. I tried erasing everything and zero-out all the disk.. re-partitionned and Mac OS X Install did not finish (Getting the message that OSX Can't be installed on my computer)..

Tomorrow I'm heading to my local Apple Store with the hope that they can change a SSD Hard Drive on site.

Hi - I switched off the graphics switching and the machine stopped freezing. Software update turned it back on, and my machine froze again. The machine was fine from July when I bought it until early September, then it just started freezing more and more frequently. restting pram and ram seemed to help, but not for long. This week turned off graphic switching in the energy settings and didn't freeze for three days, until software update ran.

I wonder if apple properly tested their 'new' graphics switching software with nvidia - who have a rival piece of software - which by all accounts works better.

Report to Apple: 9/25/2010; 9/26/2010

Since purchasing this MacBook Pro early in 2008, often -- perhaps 80% of the time, I must “Force Quite” in order to shut it down.

Recently, in the last two weeks, while in the middle of research or processing an important document, a dark veil comes over the screen, apparently named the “Screen of Death,” which informs me that I must physically power off and then restart my laptop. When I return to work on the computer, I am not returned to my last screen, but am forced to begin again.

What is happening? Why does it not shut down normally, and why is it suddenly needing to be shut down unnecessarily? This is happening too frequently, and I am loosing valuable information.

Within five minutes of my last report to Apple, the Death Screen has come down again.
For my profession, I am required to write and publish. A MacBook Pro is too expensive
for me to tolerate the valuable loss of time it has caused.

Ten minutes later: I now must force quit programs. My university uses nothing but MACs.
Previous to this more recent problem, I lived with the forced-quit shutdowns, but this added
problem is forcing me to express my displeasure.

I am seeing exactly this when there is 'congestion' on the harddrive. It's reproducible for me when downloading more that 800 or so pics from my canon camera.

My MBP went for over a week without freezing, until today... This freezing is so unbelievably irritating. You never know when it's gonna freeze. You might lose hours of work because of it or it might freeze while it's not being used. Something must be done to this problem. If I'm ****** off I can't even imagine how people with more expensive 15" and !7" models are feeling.

Well .
My MBP 13 MID 2010 has been 6 days in Apple service center...
Any issue with hardware,all test ok by diagnostic software.....Im very dissapointed with this,
I only spent 50 euros in shippng for nothing..and now im like the first day....
My laptop only has 3 months...
I will sell it right now for sure.I dont want a Apple machine..


BTW: im apple user 20 years ago...now i can install OS x in a PC!

Bye APPLE!!
My job have to trust in good machines.....