Forgive me Kevin Monahan , but your response is incredibly frustrating given the fact that many of us on this thread have taken out computers to Apple, had our hardware check out as working fine, then dealt with this issue again. In my case every time I took it to Apple it "checked out fine", yet it took multiple calls to senior advisors, 3 appointments and 2 major hardware replacements before it was (for now) solved, and still nobody on either Adobe or Apple's end can tell me what is actually causing this issue. If you read over this thread you'll find multiple users speaking with different techs at Apple, Adobe, and AMD, and we all tend to get different information and varying levels of service. So advising us to take our computer back to Apple so they can tell us it works fine (and losing weeks on our machine in the process) is not good advice. Kevin, please, I'm asking you to step out of the procedure box for a minute and think logically here. We need real, proactive, out of the box action to get this done right. If Adobe and Apple work together to fix this issue, it will get fixed, but again, it's a matter of not hitting either of them hard enough in the wallet to get you guys sufficiently motivated. I guess what I'm saying is... I wish you guys and Apple would nut-up, get in contact about this, get your hand on a symptomatic computer and figure it out. But we won't get that at this rate Kevin. We'll get more thread entries by buffoons like me raving about how Adobe is out to get them I guess...
... View more