Hacker News new | ask | show | jobs
by bbulkow 4268 days ago
I have a mid-2012 rMBP. I had terrible crashing problems - twice a day. Worse than any PC I ever had.

I had to take it in. And pay $550. Even though it's clearly a common problem, if not a design problem, something similar. Go check out the big apple support log on the problem.

I lost two weeks of productivity, because they failed to fix it the first time (it got worse).

If you have GPU panics, and you don't get your hardware fixed, you get what you deserve. Sorry for that. It's hard to get to a repair center or genius place? Sorry for that too.

Nothing to do with 10.10.

I've installed 10.10. It's running nicely.

What should you expect? Look through Ars' list. The changes are updates to the on-board apps - none of which I use (message center? no. Mail? no. etc). There are additional internal APIs for IOS tooling - good for the long term, nothing for now.

Mavericks was an important release. It treats multiple screens in a sensible way - finally addressing a weakness inherent in macs since '85. There has always been the Special Screen with real estate taken by the menu bar, no matter how many screens you have, you drag the cursor back to that screen over and over.

10.10 is not Mavericks.

In 10.10, you'll see some newer, cleaner fonts and icons, that's it.

3 comments

Pay $550? Why? Apple will do any repair for like $399 (or at least they used to) so long as you didn't mind it being sent out. I guess maybe that answers my question if you needed it back immediately. :)

For future reference, if they botched it the first time, you should call Apple corporate and yell. They messed something up in a repair for my work laptop once and it took one phone call to get a new one immediately. I had to make it clear that it was their fault and I had to have it for work and school, but they were super accommodating (and the new one worked like a charm).

I was crashing multiple times a day with GPU stacks in the crash log while viewing or editing video. It turned out to be memory with incompatible speed -- swapped out, no crashes since.
you probably put bad memory in it. That's the usual reason. You need to read the specs carefully when buying cheap RAM