2 weeks out of a 3-year warranty ... it's no wonder some people think these things are timed! Late 2009 MBP 13". Trouble started yesterday morning. Opened the lid to wake it up and check emails etc ... I was greeted by a dialogue asking me to re-enter my Time Machine encryption password. I thought it was a bit odd, but nothing major. Everything seemed relatively normal until I realised nothing was actually responding. When I clicked on dock icons, they didn't bounce or even try to open. I couldn't drag windows around the screen. Nothing would do anything. Even the password I had just entered for Time Machine was still greyed out, not accepted nor refused. In fact, the only thing that would work was the Apple menu in the top left. I opened it and hit restart. It began to reboot, but ultimately froze. I did a hard shut down. To cut a long story short, it started up ok. However, my TM drive was corrupted (would not unlock) and so I erased that and restored from an TM image I had off-site. That was that sorted. But there were strings and strings of errors being generated in Console. Runtime corruption on my TM drive. Runtime corruption on Macintosh HD. Various other odd errors and problems. I ran a Disk Utility check on my boot drive, which highlighted 'file system errors'. Tried a repair, but this failed. Not looking good, but I've got a fresh backup at least. Thought it might be worth running Disk Utility from the ML recovery image to see if the repair had any more luck. It didn't. However, now the Mac won't boot at all. It gets to the grey apple screen, then a progress bar appears for about 30 seconds before it just powers itself off. What on earth has happened? Has my hard drive just died and taken down my backup drive with it? SMART readings for the boot drive are all ok. Really not a great time for this to happen. I just want to get things up and running again ASAP, but I do not want to simply erase and reinstall on a faulty HDD. Thoughts? To add, I've just done a memory upgrade to 8GB (about a week ago). Can't see why this would be causing these issues, but worth a mention!