Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
To add, my PS and Lightroom usage is pretty intensive and they are always running when I use AI.

I should add that I've since used AI on much larger projects than what reported on above, with no perf or reliability issues -- also, w/ LR and PS open. In fact, was starting to think all was OK until the Chrome issue from the last post of mine.

There's no rhyme or reason that I can observe for what triggers the bug, but there's definitely a reliability issue as I've seen similar on two separate systems, both with W7500X cards. I don't think the issue is specific to running Adobe software, but rather any application that leverages GPU hardware acceleration, and just a matter of time before hit it.
 
I should add that I've since used AI on much larger projects than what reported on above, with no perf or reliability issues -- also, w/ LR and PS open. In fact, was starting to think all was OK until the Chrome issue from the last post of mine.

There's no rhyme or reason that I can observe for what triggers the bug, but there's definitely a reliability issue as I've seen similar on two separate systems, both with W7500X cards. I don't think the issue is specific to running Adobe software, but rather any application that leverages GPU hardware acceleration, and just a matter of time before hit it.

I agree, I blame Metal/GPU drivers on Catalina. it's an unrefined mess. i don't know exactly what but even FCP at times suffers from it so it's not Adobe related. I am seriously hoping Big Sur makes it right....
 
I keep seeing W7500X in this thread title and think there is some new magic GPU from AMD available.
 
I keep seeing W7500X in this thread title and think there is some new magic GPU from AMD available.

Lol. I edited my post last night to say W7500X instead of W5700X thinking I got the numbers flipped I my head based on title.

I am seriously hoping Big Sur makes it right....

I actually updated to Big Sur to evaluate after another Chrome glitch earlier today -- same deal, mishmash of noise in browser window and fans spool up to max -- requiring cold boot to restore to normal. The alternative is to return machine and re-order w/ Vega II, so nothing to lose by trying Big Sur. So far so good, but it will take at least a couple days to know for sure. No more funky artifacts around login progress bar, so that's an encouraging sign. AI performance seems much better when loading same file I referred to in earlier post (where performance was terrible). So, that's another encouraging sign. Fingers crossed I don't need to return machine.
 
Odd thing happened tonight (exactly 1 week into new MacPro 7.1 system). I was doing some dev work for a web frontend and loading in Chrome, and then the top part of page started pixelating as shown in attachment (just top of page view area -- not entire screen).

At the same time the fans started spooling up -- a little at first and then progressively faster. I closed Chrome and all was back to normal, but when I opened same page again, same deal, except screen artifacts too over the entire page view this time. System fan was what I assume is maxed based on how loud.

I soft rebooted system, but issue persisted. I hard rebooted system and it booted into recover mode, with no keyboard or mouse function -- so needed to go dig out an old USB keyboard / touchpad combo from storage so I could exit recovery mode. (Rebooting system w/ button or pulling power just put me back into recovery again -- so I needed to reboot from the recovery UI to get system to load as normal again).

All seems OK now, but unsettling to say the least -- esp. for such an expensive system. I will call Apple Support tomorrow. Posting back to this thread because seems like a graphic card issue (the browser pixelation issue). As for rebooting into recovery, perhaps due to dirty shutdown? Haven't run into before on other macOS systems.
I’ve had something strange the past two days. Usually after the system has been sleep. Yesterday nothing was open. I noticed when I dragged my mouse it stopped half way. Clicking wasn’t doing anything. Then it would catchup and then the same. I struggled to hey to the start menu. Eventually hard rebooting which fixed it. Today same thing. Very odd, nothing new on the system. No updates. Super odd
 
FWIW, I'm throwing in the towel and returning the system for a Vega II configured system. I've had two W5700X equipped systems, a clean setup (i.e., not restored from backup), with only Apple updates and fresh install of a handful of mainstream apps (as-is, w/o plug-ins), and both systems experienced a similar crash pattern and frequency.

I installed Big Sur as last ditch effort to get a reliable machine and traded one problem for another. Fewer (but still present) graphics issue, but Big Sur itself is still Beta and has it's own set of reliability issues --as to be expected at this stage of development. The system crashed on me last night in response from dragging and dropping an icon file of all things. Also, feels borderline reckless to install a Beta OS on a new $$$$$$$$ workstation that I use as my main machine.

At this point, I can only assume that the W5700X -- being a newer GPU offering for 7.1 Pro -- hasn't had all the kinks worked out and needs more bake time. And, again, one of the support engineers I spoke to acknowledged there is known issue w/ the card. Frankly, I'm surprised more people aren't complaining given how unreliable the system is, as configured. I'm sure Apple will eventually get it sorted out, but anybody's guess how long that will take.

On paper, the W5700X was the right card for me so I'm not very happy about needing to spend more $$$ for a Vega II just to get a reliable system. I don't require the additional GPU compute power and I lose some 5700 nice-to-haves, such as the display stream compression. I was hoping Apple would let me swap out just the cards to avoid needing to send back the system, but after much discussion, the only option is to return it (or take it the an Apple Store, which I'm not doing in the middle of a pandemic).

After I get the Vega II system (another 7-10 days) I'll post back to inform if it results in a more reliable system. It won't take long to confirm -- just a day or two after receiving. Hanging on to my iMac Pro just in case, because if the 3rd system is not a charm, it's all going back for good (tower + display) and I'll just go back to using my iMac Pro, which has provided me with 2-1/2 years of reliable service. Except for the crashes, I otherwise love the new MacPro! But reliability trumps all else.
 
So I have a Vega II Duo system and am still waiting for a correction update for Photoshop for example. Version 21.2 still has a VRAM problem when using the path tool. Otherwise I always have the sleep mode off. But unfortunately I am not yet using the new MacPro so intensively that I have noticed further errors. I still depend on my old one.
 
Not sure if this is W5700X related, but my new Mac Pro keeps turning off when I perform certain clicks in Adobe apps?

I just posted this in another thread, but it "may" apply here as well?

Just shut down again. I am starting to suspect this is something in Adobe that is causing this. This time, I opened Illustrator CC2020, when to the application menu to choose another workspace and got the spinning beachball followed by shutdown. This is the message I got on restart:

panic(cpu 11 caller 0xffffff801c25fda9): "XCPM lock timeout, cpu: 11, lock: 0xffffff801cbf4580, lock value: 0xffff0001, deadline: 0x5d24ee9cdea, current: 0x5d24ee9cdf2, timeout: 0x188683ce, contender: 0xffff0001, sniffs: 0x53c2c1, CAScount: 0x0"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.121.2/osfmk/x86_64/xcpm/xcpm_internal.h:305
Backtrace (CPU 11), Frame : Return Address
0xffffff83c8a437b0 : 0xffffff801c11f5cd
0xffffff83c8a43800 : 0xffffff801c258b05
0xffffff83c8a43840 : 0xffffff801c24a68e
0xffffff83c8a43890 : 0xffffff801c0c5a40
0xffffff83c8a438b0 : 0xffffff801c11ec97
0xffffff83c8a439b0 : 0xffffff801c11f087
0xffffff83c8a43a00 : 0xffffff801c8c27cc
0xffffff83c8a43a70 : 0xffffff801c25fda9
0xffffff83c8a43ad0 : 0xffffff801c26022a
0xffffff83c8a43b80 : 0xffffff801c261bc0
0xffffff83c8a43bf0 : 0xffffff801c262dcd
0xffffff83c8a43cc0 : 0xffffff801c24cd7e
0xffffff83c8a43d10 : 0xffffff801c141deb
0xffffff83c8a43d70 : 0xffffff801c14170b
0xffffff83c8a43de0 : 0xffffff801c13fc2f
0xffffff83c8a43e30 : 0xffffff801c1010f6
0xffffff83c8a43e70 : 0xffffff801c112bfe
0xffffff83c8a43f00 : 0xffffff801c230d05
0xffffff83c8a43fa0 : 0xffffff801c0c6226

BSD process name corresponding to current thread: Adobe CEF Helper
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19F101

Kernel version:
Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64
Kernel UUID: 54F1A78D-6F41-32BD-BFED-4381F9F6E2EF
Kernel slide: 0x000000001be00000
Kernel text base: 0xffffff801c000000
__HIB text base: 0xffffff801bf00000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO

System uptime in nanoseconds: 31616923778546
last loaded kext at 67570091546: com.getdropbox.dropbox.kext 1.11.1 (addr 0xffffff7fa3271000, size 49152)
loaded kexts:
com.getdropbox.dropbox.kext 1.11.1
>!AUpstreamUserClient 3.6.8
>!AMCCSControl 1.14
>!ATopCaseHIDEventDriver 3430.1
@kext.AMDRadeonX6000 3.0.9
@kext.AMDRadeonServiceManager 3.0.9
>!AGraphicsDevicePolicy 5.2.4
@fileutil 20.036.15
@filesystems.autofs 3.0
@AGDCPluginDisplayMetrics 5.2.4
>!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.5f6
>AGPM 111.4.4
>!APlatformEnabler 2.7.0d0
>X86PlatformShim 1.0.0
>pmtelemetry 1
>AudioAUUC 1.70
@Dont_Steal_Mac_OS_X 7.0.0
>BridgeAudioCommunication 6.70.7
>ACPI_SMC_PlatformPlugin 1.0.0
>!AThunderboltIP 3.1.4
>!AFWOHCI 5.6.2
>!ABridgeAudio!C 6.70.7
>!A!IMCEReporter 115
>!AAVEBridge 6.1
>!A!IPCHPMC 2.0.1
>!AFIVRDriver 4.1.0
>!A!ISlowAdaptiveClocking 4.0.0
>!AGFXHDA 100.1.428
|SCSITaskUserClient 422.120.3
>usb.!UHostBillboardDevice 1.0
@!AEthernetAquantiaAqtionFirmware 1.0.36
>BCMWLANFirmware4355.Hashstore 1
>BCMWLANFirmware4364.Hashstore 1
>BCMWLANFirmware4377.Hashstore 1
>!ARAID 5.1.0
>!AFileSystemDriver 3.0.1
@filesystems.hfs.kext 522.100.5
@BootCache 40
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
>!AVirtIO 1.0
>!ABCMWLANBusInterfacePCIe 1
>!A!II210Ethernet 2.3.1
@filesystems.apfs 1412.120.2
@private.KextAudit 1.0
>!AAHCIPort 341.0.2
>!AACPIButtons 6.1
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
|EndpointSecurity 1
>!ASMBus!C 1.0.18d1
@kext.AMDRadeonX6700HWLibs 1.0
>!AMultitouchDriver 3440.1
>!AInputDeviceSupport 3440.8
>!AHS!BDriver 3430.1
>IO!BHIDDriver 7.0.5f6
|IOAccelerator!F2 438.5.4
@kext.AMDRadeonX6000HWServices 3.0.9
>!AGraphicsControl 5.2.4
@kext.triggers 1.0
|IOAVB!F 850.1
>!ASSE 1.0
|IO!BHost!CUARTTransport 7.0.5f6
|IO!BHost!CTransport 7.0.5f6
|IOFireWireIP 2.3.0
>IOPlatformPluginLegacy 1.0.0
@!AGPUWrangler 5.2.4
>!AHDA!C 283.15
|IOHDA!F 283.15
@kext.AMDRadeonX6000Framebuffer 3.0.9
>!AHIDKeyboard 209
>!UAudio 323.1
|IOFireWire!F 4.7.5
>usb.cdc.acm 5.0.0
>usb.serial 6.0.0
>!A16X50Serial 3.2
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
>!ASMBusPCI 1.0.14d1
@plugin.IOgPTPPlugin 840.3
|IOSlowAdaptiveClocking!F 1.0.0
|IONDRVSupport 576.1
@kext.AMDSupport 3.0.9
@!AGraphicsDeviceControl 5.2.4
|IOGraphics!F 576.1
>!AThunderboltEDMSink 4.2.3
>!UMergeNub 900.4.2
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc.ecm 5.0.0
>usb.cdc.ncm 5.0.0
>usb.!UHub 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>!AThunderboltDPOutAdapter 6.2.6
>!AThunderboltPCIUpAdapter 2.5.4
>!AThunderboltPCIDownAdapter 2.5.4
>!AHPM 3.4.4
>!A!ILpssI2C!C 3.0.60
>!A!ILpssDmac 3.0.60
>!AThunderboltDPInAdapter 6.2.6
>!AThunderboltDPAdapter!F 6.2.6
|IOSurface 269.11
@filesystems.hfs.encodings.kext 1
|IOAudio!F 300.2
@vecLib.kext 1.2.0
>!AEthernetAquantiaAqtion 1.0.64
>!ABCMWLANCore 1.0.0
>IOImageLoader 1.0.0
|IOSerial!F 11
|IO80211!FV2 1200.12.2b1
>corecapture 1.0.4
|IOSkywalk!F 1
>!AThunderboltNHI 5.8.6
|IOThunderbolt!F 7.6.1
|IOEthernetAVB!C 1.1.0
>mDNSOffloadUserClient 1.0.1b8
>!AXsanScheme 3
>usb.!UHostPacketFilter 1.0
|IOAHCIBlock!S 316.100.5
|IOUSB!F 900.4.2
>usb.!UVHCIBCE 1.2
>usb.!UVHCI 1.2
>usb.!UVHCICommonBCE 1.0
>usb.!UVHCICommon 1.0
>!AEffaceableNOR 1.0
|IOBufferCopy!C 1.1.0
|IOBufferCopyEngine!F 1
|IONVMe!F 2.1.0
>!A!ILpssI2C 3.0.60
|IOAHCI!F 290.0.1
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>!A!ILpssGspi 3.0.60
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
>!ASMCRTC 1.0
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
>!AKeyStore 2
>!UTDM 489.120.1
|IOSCSIBlockCommandsDevice 422.120.3
>!ACredentialManager 1.0
>KernelRelayHost 1
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
|CoreAnalytics!F 1
|IOTimeSync!F 840.3
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 7.0.5f6
|IO!BPacketLogger 7.0.5f6
|IOUSBMass!SDriver 157.121.1
|IOSCSIArchitectureModel!F 422.120.3
|IO!S!F 2.1
|IOUSBHost!F 1.2
>usb.!UCommon 1.0
>!UHostMergeProperties 1.2
>!ABusPower!C 1.0
|IOReport!F 47
>!AACPIPlatform 6.1
>!ASMC 3.1.9
>watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1
 
This time, I opened Illustrator CC2020, when to the application menu to choose another workspace and got the spinning beachball followed by shutdown.

Go to Preference > Performance > turn off "GPU Performance"

Also make sure you're running the absolute latest version of CC2020 apps. There are font issues that are/were resolved. Something with specific font licensing changed recently too.

If this doesn't work around, make sure you submit a report to Adobe.
 
Go to Preference > Performance > turn off "GPU Performance"

Also make sure you're running the absolute latest version of CC2020 apps. There are font issues that are/were resolved. Something with specific font licensing changed recently too.

If this doesn't work around, make sure you submit a report to Adobe.

I will give that a try - just turned off GPU in Illustrator and Photoshop. I am on the latest versions of everything.
 
I now have my replacement machine w/ Pro Vega II GPU (instead of the W5700X) and things look good so far. No kernel panics, no perf issue, no screen artifacts appearing in certain scenarios. Fingers crossed it stays this way (still early), but I'm well past the point where the 2 previously equipped W5700X machines crashed. Same software install and use case patterns.

Based on what I've experienced and discussion with Apple support engineer (see previous comments), I think it's safe to say the W5700X option isn't at release quality. I'm sure Apple will sort this out eventually, but I couldn't wait.
 
I now have my replacement machine w/ Pro Vega II GPU (instead of the W5700X) and things look good so far. No kernel panics, no perf issue, no screen artifacts appearing in certain scenarios. Fingers crossed it stays this way (still early), but I'm well past the point where the 2 previously equipped W5700X machines crashed. Same software install and use case patterns.

Based on what I've experienced and discussion with Apple support engineer (see previous comments), I think it's safe to say the W5700X option isn't at release quality. I'm sure Apple will sort this out eventually, but I couldn't wait.
This isn’t a system wide across the board issue. I have a w5700x the only crashing I have is intermittently after the system has been asleep.
 
This isn’t a system wide across the board issue.
I'm most definitely not suggesting a system board or system-wide issue. Quite the opposite actually.

As posted, I've had two 7.1 machines equipped with W5700X. Both machines hung and crashed regularly (every 1-2 days), and the symptoms suggest GPU related. After contacting Apple support about my suspicion it's an issue with GPU, they simply said 'We're aware of the issue and working on a fix."

My latest system with Pro Vega II is otherwise identically equipped to my latest W5700X system. The Pro Vega II system has, so far, been rock solid and my confidence is high that I'll be able to stick with the machine (as opposed to returning everything and sticking with my iMac Pro).

I have a w5700x the only crashing I have is intermittently after the system has been asleep.

And you're OK with this?
 
Last edited:
I'm most definitely not suggesting a system board or system-wide issue. Quite the opposite actually.

As posted, I've had two 7.1 machines equipped with W5700X. Both machines hung and crashed regularly (every 1-2 days), and the symptoms suggest GPU related. After contacting Apple support about my suspicion it's an issue with GPU, they simply said 'We're aware of the issue and working on a fix."

My latest system with Pro Vega II is otherwise identically equipped to my latest W5700X system. The Pro Vega II system has, so far, been rock solid and my confidence is high that I'll be able to stick with the machine (as opposed to returning everything and sticking with my iMac Pro).



And you're OK with this?
at the moment it’s impossible to say if it’s an adobe issue or Apple. It only crashes when launching an adobe app. Although it’s not happened in over a week.

taking action before even knowing what the problem is seems silly. You’ve not solved it, you’ve just got w different GPU. Which is super for you, but I have absolutely no use for that card. The software I use just cannot utilise it.
 
at the moment it’s impossible to say if it’s an adobe issue or Apple. It only crashes when launching an adobe app. Although it’s not happened in over a week.

I don't think it's an Adobe issue. If you go back and look at my earlier posts you'll see I ran into issue with Chrome client area rendering as well.


taking action before even knowing what the problem is seems silly. You’ve not solved it, you’ve just got w different GPU. Which is super for you, but I have absolutely no use for that card. The software I use just cannot utilise it.

What it silly is paying they money Apple is charging for Mac Pro and getting a machine that crashes regularly with only the most mainstream applications installed.

It is not my job to solve the problem, nor am I interested in solving it. There's also no guarantee Apple will solve it before return window closes, so it's super for you that you don't need to be concerned about such things.

I agree it sucks to pay for something that's not needed (I also don't need the Pro Vega II, which is why I opted for W5700X in the first place). However, the incremental cost for the Pro Vega II is small relative to the total system cos w/ displayt, so it's well worth it to me in having what now appears to be a reliable machine.
 
Last edited:
  • Like
Reactions: yurc and OkiRun
I am really thinking there is something wrong with the card - look at my posts #24 & #25 I just made here: https://forums.macrumors.com/thread...randomly.2245744/?post=28679372#post-28679372

Mac Pro is totally dead now, yet diagnostics say the machine is fine when trying to startup followed by "No Signal" message on two of my monitors and black screen on third monitor. I will have to contact AppleCare tomorrow - hopefully they could just send me another graphics card to try - not looking forward to shipping this beast back! Not to mention that all my work from the past two weeks is now on this machine! I expected incompatibilities with this upgrade, but never had a Mac in 30 years that would not start up!
 
I am really thinking there is something wrong with the card - look at my posts #24 & #25 I just made here: https://forums.macrumors.com/thread...randomly.2245744/?post=28679372#post-28679372

Mac Pro is totally dead now, yet diagnostics say the machine is fine when trying to startup followed by "No Signal" message on two of my monitors and black screen on third monitor. I will have to contact AppleCare tomorrow - hopefully they could just send me another graphics card to try - not looking forward to shipping this beast back! Not to mention that all my work from the past two weeks is now on this machine! I expected incompatibilities with this upgrade, but never had a Mac in 30 years that would not start up!

Can you describe how status indicator led behave when no signal message appear? It’s solid white or blinking? Have you tried with third party PCIe AMD GPU? (not Apple MPX module)

Sorry to hear your 7,1 condition, ask Apple if possible send some replacement parts, sending back heavy tower is cumbersome indeed…
 
I’ve not had any issues with Adobe CC apps (mainly use Lightroom and Photoshop), but did see some weird issues with VMWare fusion making my system pretty much unresponsive. I switched off 3D acceleration in the VMs and haven’t seen any issues since

I’ve been impressed with the performance and stability of the W5700X apart from that one issue
 
Can you describe how status indicator led behave when no signal message appear? It’s solid white or blinking? Have you tried with third party PCIe AMD GPU? (not Apple MPX module)

Sorry to hear your 7,1 condition, ask Apple if possible send some replacement parts, sending back heavy tower is cumbersome indeed…

Status indicator light glows solid white (never has blinked). I don't have a 3rd party card that will work in that machine.
 
Quick PP and 7,1 question....
I'm trying to save a PP project as a final cut pro .xml file so I can use Xtocc and import into FCPX. However, the .xml file that PP creates isn't recognized by XtoCC or even Davinci if saved as that type file...
Any thoughts on the problem?
 
Glad to hear you're your back up and running -- you may want to consider asking Apple to extend your return window so you have the little extra time needed to ensure everything is sorted out and that you're satisfied.

As per your other post, I suspect Apple will sort out the W5700X issue soon enough and it's just a matter of if you're OK to wait. 10.15.6 is out now so hopefully that fixes it.
 
  • Like
Reactions: choreo
Look at this:

Does not work great, but has prevented a complete frame by frame recut more than once.
Thanks ~ that did work. Can't understand why XtoCC didn't. Another kink to iron out in the future.
I noticed that all the audio clips turned a yellow shade meaning moderate issue. I think related to sound quality as all the clips transferred. Editor went in and equalized the clips but the color stays the same. Oh well. A kink to iron out in the future.
But again ~ thanks so much for the recommendation.
 
Just had my 4th documented freeze in Illustrator CC (latest version). Getting pretty old now. The last couple freezes were today even after the OS update to 10.15.6 yesterday. Unlike the freeze I described in Post #33, now the cursor just freezes on the screen usually right after a open a small file in AI before even starting work. Keyboard and mouse - no response. Computer did not shut down and logout as before - just sits there unresponsive with the white power light glowing solid - stuck in AI?

I have never had a freeze before this Mac where I could not force-quit the offending app or just that app would quit, so has me concerned.

Have not seen any freezes "yet" in my other Adobe apps. Been working in Photoshop, Lightroom and worked 3 hours solid in InDesign last night without a glitch. I tried turning GPU on and off in AI and it froze both ways. What is also strange is after a freeze and a forced Mac shutdown, I can open the same file in AI and work on it and save it without issues? Also tried resetting AI Prefs before last freeze.

I also saw one strange anomaly in Photoshop yesterday when using Levels on an image where the screen image would redraw in blocks (like when rendering a 3D model - left to right/top to bottom - every time I moved a slider? Restarted Photoshop with same image and no problems using Levels in real-time.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.