Q: MacBook Pro (2010) Freeze

A small miracle?! You have to be kidding. When is the last time you used a PC? Maybe back in the Windows 98 days, twice a month was a blessing. PCs are much more stable than that now.

As for Kevin's expectations of Apple, I think freezing twice a month is worth complaining about. I know that there are many that unfairly expect perfection, but twice a month is not only far from perfection, it's far from adequate. My last MBP froze maybe twice a year, if that.

Seriously GoTVols, you make it sound as if we have some responsibility to Apple for being able to use their products. No, they have a responsibility to us to deliver products that work. Twice-a-month freezing is not a product that works. Have more self-respect than that; it's your money, you deserve better. Kevin, please complain all you like and return the machine until you get one that works.

I am not the most knowledgeable person about computers. I have been thinking about getting a 13" MPB, but with all the problems I am hesitating.
Why doesn't the Mac Mini have these problems, it has a lot of the same hardware. I just seems strange.
Please correct me if I am wrong.

what does this mean, vylain?:


"The freezing issue was also experienced on 10.6.3.
That is why it is believe that it comes from the hardware, not the software.

I guess you still have to lose some Windows habits..."


my macbook pro 13 is working perfectly so far, what can i say?

I just meant that on MAC OS X you should not be so much worried about OS updates.
I also use Windows (XP) and I can't really say the same from my own experience...

Anyway, it's just a joke and has nothing to do with the topic.

Is an AlienWare top of the line 17" laptop running the latest operating system and hardware available recent enough for you??

Sure, but if you are having two freezes a month on that machine then you should be angry. If it's hardware, they should fix it; if it's software, then they should fix the drivers or whatever the problem is.

I'm not trying to make this a windows vs mac argument; I hate windows myself. But I do know that there are plenty of PCs that do not suffer two crashes a month.

Your argument boiled down to "stop complaining because your computer is still better than the really sucky competition." The argument should be "is the computer reaching satisfactory performance or are you simply expecting too much?" Having fewer than two crashes per month is not an unreasonable expectation. People have the right to complain about this problem, and do everything that is reasonable to get a computer that has acceptable performance.

Hey All, I was a victem of this freezing as well, so i thought i put in what i did solve my owm problem incase someone else has the same problem.

My model is: MacBookPro5,4 (15", 4GB, 2.53Ghz)
Problem occured after system update and replacing stock hdd (Hitachi 250GB 5400rpm) with new Seagate Momentum 250GB 7200rpm

I only come accross it after doing a system update, which included the unsuspecting EFI 1.7-8 patch. It was 1.6 previous.
I replaced the stock HDD which had bad sectors - i took this as a chance to upgrade to a 7200rpm Seagate Momentum drive. This hdd was the perfect choice as it only uses 0.05% more power than a 5400rpm drive so my battery life wouldnt be affected. **** broke out after installing it however. My OS would freeze everytime i put the hdd under load (copying large files) for upto 20 seconds at a time. I was getting so frustrated and finaly came to this forum and others a like.

The EFI 1.7 patch indroduces Sata2 Specifications (3gb/s max) onto my sata controllers firmware, however they dont follow standards - which is why its freezing. Sloppy Apple Pie.

My solution was to look up the jumper settings to my new drive and force it to operate at Sata1 spec mode (1.5gb/s max). These platter drives wont get to that theoretical max anyways, so this jumper fix is perfect for me. No more freezing and finally i get the snapper performace boost from the upgraded 7200hdd.

I agree that two freezes a month is two too many, Fake Brain, but someone suffering this sort of level of problem is unlikely to have a hardware problem. When it comes to software such things generally involve either a problem with code in commonly used third party software of one kind or another , rather than a problem with the OS itself. If you are going to get "angry" in such circumstances then you need to work out who to be angry with!

As I've said before in this thread, many, many different things can cause "freezes" and even a cursoring reading of this thread indicates that many very different kinds of problems are actually being discussed in it. A few will involve hardware problems. A few may even involve a genuine "bug" in the OS. A few more probably involve issues with particular HD firmware and interfaces. Most, though, will be the result of things like directory corruption or problems with third party software, corrupted or out of date fonts, third party peripherals, etc etc etc.

In your own case (and a few, but not many, of the other problems discussed here) , after looking at your earlier images of the problem, I'd be wondering about an issue with the mini-port adaptors or cabling in use, or just maybe an issue with drivers for particular types of monitor configuration. What happens, by the way, if you simply power cycle the monitor in your own situation, or simply disconnect it? ( I ask this partly because I have several external monitors, and have found that they can behave quite differently with respect to such things. One that I have, for example, often simply turns into a mass of coloured pixels when connected through an Apple MDP to DVI adaptor to my 2009 13" MBP after the computer has been sleeping, but returns to "normal" if I simply press the monitor on / off switch or physically disconnect and reconnect it to the computer. Others exhibit no such problems, even when connected using exactly the same adaptor, so clearly the interaction with other parts of the video "chain" can be important here.)

But, again, I would suggest that people create their own threads if they want help with these sorts of issues, rather than relying on this humungous beast of a thread which involves many different types of problems necessitating many different types of real answers.

Cheers

Rod

hi,I AM mac user,and I am really love mac,but when I check this.....
very easy,Am I get MBP Anti glare 17inch i7,right now?cause I wanna use lap top for my school....but it's about 50pages,say about that Freeze issues.... what I am suppose to do.....
please help.

ok,the big deal is,it's not cheap computer,so I don't wanna get a little crap!!

thank you

Message was edited by: Liam sebastian

Message was edited by: Liam sebastian

A final update on my situation (the same issue as the OP). Mine was serviced and they replaced the logic board. That was last week and I've had zero issues since. It also seems to have resolved the constant ethernet messages (discussed here in another thread).

This thread seems to have degraded into a lot of bickering about what's acceptable, etc. I would suggest to those that don't find these types of issues to be acceptable that you contact Applecare and get your machine in to be checked. I highly suspect there was a bad batch of machines and Apple is not being very forthcoming about it.

If you happen to be within the first 14 days (or 30 days in some cases) push for a replacement, if not, contact Applecare.

Good luck all!

I have tested this problem under a number of different conditions, with different monitors, different miniport-to-dvi cables, different dvi cables, I reinstalled the OS from scratch, suffice to say that I've tested it. After it happens, if I replug-in or cycle the monitor power, I get colored snow on the external monitor. Nothing fixes the problem so far except a hard reset.

Your solution may work for a 2009 MBP, but the majority of issues being discussed here are for the 2010 MBPs, and the problem seems to be unique to it. Unfortunately, as you noted, many people are posting unrelated problems to this beast b/c it has grown so large; it's probably receiving many search hits.

Initially, my thought was that it is a software/driver issue, especially because it was so random. If it's software, then it should only affect the percentage of MBP owners that share similar configs. If it's driver, then it should affect nearly all 2010 MBPs. But look at the problems written on this thread, it happens under a variety of conditions and configurations, even when people are using Windows. And, there are a number of 2010 MBP owners that are reporting no problems; I know some of them. The clues at the moment point toward a hardware defect in a select set of MBPs. Some posters have even been posting partial serial numbers to look for a pattern.

Anyway, this is a diversion from the original argument. GoTVols basically told Kevin to stop complaining and be happy that his computer isn't worse than it is. True, Kevin will be wasting his time, if he keeps sending back his machine and it turns out to be a driver issue and not a hardware defect. We both agree that Kevin has a right to demand a laptop that works. We don't know what Kevin's computer literacy is. If he is highly literate, then he has probably tested his own machine and tried to diagnose it himself, and perhaps came to the conclusion that the problem is most likely hardware. Then his most logical choice is to keep returning computers till he gets one that is satisfactory. If he isn't computer literate, then he has to rely on apple to provide answers, and unless Apple says otherwise, it's just as fair for him to assume that the problem is hardware. It's their responsibility to figure out what keeps failing in these machines and find a solution. They haven't even acknowledged a problem yet, even though there a substantial number of reports. With the bad press stemming from the iPhone4, my guess is that Apple is reluctant to acknowledge any more issues. It's up to us, the consumers, to create enough noise to force them to acknowledge it.

Mine has the Seagate 7200RPM drive - 500GB. Really starting to wonder if this might be the culprit for me.

Another note: I turned on rlogin on my machine and used it till it "crashed." I could still ssh into my machine and use it from a terminal on another computer. Again, my problem only happens when I'm attached to an external monitor, but in many other ways is similar to issues reported in this thread. Can anyone else confirm the ability to remotely login?

I've been using my MBP for about a week since it had its logic board replaced. And it seems like I can now state that my problem has been solved, the machine now just flies. Unfortunately, seems to be a hardware-related issue.

Got my first crash WITHOUT an external monitor tonight. The symptoms were slightly different. Instead of getting random colored pixels over my current screen, a few spots on the screen turned black. No heavy load on the system, just web surfing. The mouse still moved, and eventually became a spinning beach ball. Nothing worked but a hard reset. Nothing in the console and no bug report after reboot. Interesting entries in the kernel log right before the crash, but I have no idea how to interpret them:

Jul 12 23:16:15 athens kernel[0]: NVRM-RC: 0 4e565f504649464f5f494e54525f303a307831323030
Jul 12 23:16:15 athens kernel[0]: NVRM-RC: 0 4e565f504649464f5f4341434845315f444d415f53544154453a307863303030
Jul 12 23:16:15 athens kernel[0]: NVRM-RC: 1 383330340a
Jul 12 23:16:15 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307838303230
Jul 12 23:16:15 athens kernel[0]: NVRM-RC: 1 35
Jul 12 23:16:15 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307839
Jul 12 23:16:15 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
Jul 12 23:16:15 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307865303830
Jul 12 23:16:15 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a307832323164
Jul 12 23:16:15 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a30783130300a
Jul 12 23:16:15 athens kernel[0]: NVDA(CopyEngine): Channel exception! exception type = 0x6 = Fifo: Parse Error
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f494e54523a3078323030303030
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f455843455054494f4e3a307832
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f5052495f4d454d464d545f4857575f4553523a307838
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 1 30303030303034
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f5052495f4d454d464d545f4857575f4553525f4c494d
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 1 4954565f5245513a30783334303134310a
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307835303330
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 1 333030
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307833
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307830
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a307832343534
Jul 12 23:16:19 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a3078300a
Jul 12 23:16:19 athens kernel[0]: NVDA(OpenGL): Channel exception! exception type = 0xd = GR: SW Notify Error
Jul 12 23:16:19 athens kernel[0]: 00000069
Jul 12 23:16:19 athens kernel[0]: 0000006e
Jul 12 23:16:19 athens kernel[0]: 00200000 00005039 00000474 00000002
Jul 12 23:16:19 athens kernel[0]: 0000047c 00000100 00000000 00000003
Jul 12 23:16:19 athens kernel[0]: 00000000 00000000 00000043
Jul 12 23:16:19 athens kernel[0]: 00000002 00000000
Jul 12 23:16:19 athens kernel[0]: NVDA(CopyEngine): Channel exception! exception type = 0x1 = Fifo: Fifo Method Error
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f494e54523a3078323030303030
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f455843455054494f4e3a307831
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f5052495f46455f4857575f4553523a30783830303030
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 1 3030310a
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307831303330
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 1 663030
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307837
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 1 65
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307830
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a307830
Jul 12 23:16:23 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a3078300a
Jul 12 23:16:23 athens kernel[0]: 00000069
Jul 12 23:16:23 athens kernel[0]: 0000006e
Jul 12 23:16:23 athens kernel[0]: 00200000 0000502d 00000468 00000001
Jul 12 23:16:23 athens kernel[0]: 0000046a 00000100 00000000 0000007e
Jul 12 23:16:23 athens kernel[0]: 00000000 00000000 00000000
Jul 12 23:16:23 athens kernel[0]: 00000001 00000000
Jul 12 23:16:31 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f494e54523a3078323030303030
Jul 12 23:16:31 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f455843455054494f4e3a30783830
Jul 12 23:16:31 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f5052495f545043315f534d435f4857575f4553523a30
Jul 12 23:16:31 athens kernel[0]: NVRM-RC: 1 7838303032303030300a
Jul 12 23:16:31 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f5052495f545043315f534d435f534d5f4354585f353a
Jul 12 23:16:31 athens kernel[0]: NVRM-RC: 1 534d313a307838310a
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f494e54523a3078323030303030
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f455843455054494f4e3a307832
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f5052495f4d454d464d545f4857575f4553523a307838
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 1 30303030303032
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 0 4e565f5047524150485f5052495f4d454d464d545f4857575f4553525f4c494d
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 1 4954565f5245513a30783332303235310a
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307834303330
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 1 333030
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307833
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307862343830
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a307832343562
Jul 12 23:16:37 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a30783130300a
Jul 12 23:16:37 athens kernel[0]: NVDA(OpenGL): Channel exception! exception type = 0xd = GR: SW Notify Error
Jul 12 23:16:37 athens kernel[0]: 0000006e
Jul 12 23:16:37 athens kernel[0]: 00200000 0000502d 00000468 00000080
Jul 12 23:16:37 athens kernel[0]: 0000046a 00000100 00000000 0000007e
Jul 12 23:16:37 athens kernel[0]: 00000000 00000000 00000000
Jul 12 23:16:37 athens kernel[0]: 00000080 00000000
Jul 12 23:16:37 athens kernel[0]: 0000006e
Jul 12 23:16:37 athens kernel[0]: 00200000 00005039 00000474 00000002
Jul 12 23:16:37 athens kernel[0]: 0000047c 00000100 00000000 00000003
Jul 12 23:16:37 athens kernel[0]: 00000000 00000000 00000043
Jul 12 23:16:37 athens kernel[0]: 00000002 00000000
Jul 12 23:16:46 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502830293a307831303430
Jul 12 23:16:46 athens kernel[0]: NVRM-RC: 1 333036
Jul 12 23:16:46 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502863686964293a307866
Jul 12 23:16:46 athens kernel[0]: NVRM-RC: 1 666339
Jul 12 23:16:46 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502832293a307830
Jul 12 23:16:46 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502833293a307863343063
Jul 12 23:16:46 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502834293a30783238
Jul 12 23:16:46 athens kernel[0]: NVRM-RC: 0 4e565f5046425f4d4d555f4c494d4954565f545241502835293a3078340a
Jul 12 23:17:20 athens kernel[0]: NVDA(OpenGL): Channel timeout!
Jul 12 23:18:09 athens kernel[0]: NVDA(OpenGL): Channel timeout!
Jul 12 23:18:49: --- last message repeated 1 time ---
Jul 12 23:18:49 athens kernel[0]: NVDA(OpenGL): Channel timeout!