Q: MacBook Pro (2010) Freeze

No, it's not a replacement.. it's the original that I ordered CTO a day after the release and received a week later. Below is the info on the chipsets. It appears that there really isn't one combination of ROM and gMux that's free of the issue? At this point, I'm hesitant to push for a replacement since barring this issue, the machine has been fine. And from past experience, I know that new Apple machines can have issues (anyone remember the iBook logic board recall around 2003? - it took Apple more than 1.5yrs to acknowledge the problem and issue a recall) so I don't want to risk switching machines to be rewarded with another problem..

Oh, and 3 freezes so far, one 2 weeks ago, and 2 this week.

Chipset Model: Intel HD Graphics
Type: GPU
Bus: Built-In
VRAM (Total): 288 MB
Vendor: Intel (0x8086)
Device ID: 0x0046
Revision ID: 0x0012
gMux Version: 1.9.21

Chipset Model: NVIDIA GeForce GT 330M
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0a29
Revision ID: 0x00a2
ROM Revision: 3532
gMux Version: 1.9.21

Message was edited by: baseliner

I read these forums, and many others across the internet, and I can add to the list by saying that I am having this exact same lockup issue.

Question: Has anyone reported this as a bug?

https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/wa/signIn

Login with your Apple ID and then report the problem, be sure to mention this thread in this forum.

I ask this of you to do it now before you forget.

I called Apple on this problem, told the escalation engineer of this problem and this forum thread, and he told me:

1. Tech Support NEVER reads these forums.

2. I should report this as a bug at the link I provided above, if I wanted an actual programmer to look into the issue.

3. Worldwide problems with Apple products are considered secret until a fix is available, and so he had no information on this problem.

4. That even senior Apple tech support do not have any knowledge of any beta patches, etc.

5. That this Core i7 lockup problem was NOT in his database because not enough people had reported it.

That means, please report this issue to the bug reporting tool link in my message so Apple programmer actually find out about this bug and fix it!!!!

Thanks...

I hesitated as well to have a replacement and I believe that it is too late for me: my fear was to have a replacement machine having much more problems than current.
Maybe it is a s/w problem accentuated by some faulty hw, on the edge?
We have not to forget that 10.6.3 has provided a lots of issues on previous mb and mbp too.
Wait and see.

blogthis wrote:
Question: Has anyone reported this as a bug?

Yes, I logged a bug on 5/24 - the bug ID is 8023327 if it helps. I listed it as a "Crash/Hang/Data Loss" bug so I'm hoping it will get looked at soon. They've been pretty responsive on several other bugs I've reported in the past so I'm hopeful...

Tried reporting it.... going to try a U.S. proxy since they seem to block anything outside the U.S.

You do not have access to the Apple Bug Reporter (aka RadarWeb).

<Edited by Host>

I cannot leave this alone:)

The macbook 15" MBP i had that was having many issues was manufactured in Shanghai China
The serial starts with S and then the factory code W8.

The 17" MBP i have now starts with SC0, also china but i do not know what factory.
No issue's on that one so far, even after heavy load.

The Shanghai factory has a bad reputation since many of the previous macbooks with problems also appeared to come from that factory.

-> http://forums.macrumors.com/showthread.php?t=422299

Mine starts with W80 and I'm not really having problems, just a few which should be fixed with 10.6.4. I still don't know where to download the beta that people are talking about.

Mine starts with W8 and I've had the freeze 3 times so far.

Forgot to mention again that I have a 2.4 i5.

I will add my 2010 15" i7 Hirez mat CTO in to the mix I had two lockups. Called tech support what a waste of time. Their solution was to reinstall os x and see if that happens again, if I would tell a customer that they have to reinstall the operating system on DB server or Exchange server because a freeze i would be fired so fast. Anyway heres my specs and I will be installing the 10.6.4 beta and see what I can see.

Chipset Model: NVIDIA GeForce GT 330M
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0a29
Revision ID: 0x00a2
ROM Revision: 3532
gMux Version: 1.9.21
Displays:
Display Connector:
Status: No Display Connected
Display Connector:
Status: No Display Connected

Just to update, I checked the spec of the good one and found no difference.....

Sorry to hear about your occasional lock-up - keep us updated if your recent software changes solved any of your issues and thanks for posting.

Any ideas when 10.6.4 will be released officially? I wonder if they will delay it working on the very issue in this thread.

joelyen, are the machines produced in factory w8 by any chance?
(serial starts with SW8?, or is it different?)

Thanks

My machine, which seems to have the issue from time to time:
Serial Number (system): W80182XXXXX

My friend's machine, which seems ok to him, has the same first part of the serial number too.