Awesome. I turned on my MacBook Pro this evening, and all I got was a black screen. Waiting a while and tinkering around with volume settings suggested that it did boot, but I'm not getting any video output.

I suppose it's become a victim of the renowned faulty NVIDIA 8600M FGT graphics processor. UGH. The only Mac store I've got around me is Machines at City Square, JB; should be fine since I bought it from Machines at Midvalley Megamall. I should be sending it in either tomorrow or on Wednesday. Thank goodness I've got extended AppleCare.

Or the entire logic board, as I've read from various articles about the same problem. But I do hope it'll take that long, and not any more than.

Assuming the logic board has to be replaced, will my hard drive be compromised in any way? I do have Time Machine backups, but I'm still a little concerned over whether they'd do anything to my hard drive.

As in, all the data on my hard drive will be wiped?

Ah, alright. Thanks! Yeah, I use Time Machine for my backup purposes, so that should be alright.

ETA: Don't want to double-post, so I'm sticking this here. I sent my MBP to Machines at City Square this morning. They'll be sending it to KL at the end of the week for repair. I should get it back within the next two weeks. *crosses fingers*

This post has been edited by equustel: Jun 23 2009, 01:58 PM

dvlzplayground: Yeah, I saw posts on other forums about this issue prior to Apple's official acknowledgement, and they were like, "The cost would be [insert exorbitant amount here]. I'd just be better off getting a new laptop."

Just got back my MBP! The data's all intact, thank goodness. I asked the salesperson what had been replaced exactly, but he said the service centre never furnished any details to them, just that "repairs were done". When I turned it on though, the date was reset to January, 2000/2001 (can't remember which). Hmm.

Also, I checked "About This Mac", and the video card is still the same one: NVIDIA 8600M GT. I'm a bit "eh" because what if it spoils again? And since no exact details were given on what went wrong in the first place, I've no way to know what not to do to trigger it again. Oh, well. I got it back, and my data's still all there, so it's all good-ish.