Temporary freezes after fitting SSD and new ram

It's my experience that the Macbooks are very picky about SSD drives. I tried an OCZ (which gave crashes and kernel panics) before settling on a Corsair. What's your brand?

That's a rebranded disk. However, I wouldn't be surprised if it's the SSD causing the trouble. There's a rather interesting public discussion going on about the reliability of SSDs. You could try to run XBench though. It's a benchmarking utility and you can run it specifically on the disk. Perhaps it'll make it clear that the disk is at fault.

I do not want to "barge in", but this thread is not exactly productive.

First do never use any hack when it is not absolutely certain that it is not crapware: in the (Snow) Leopard period Oskar Groth made a hack called Trim Enabler to install trim, it was a bad idea to just replace the involved kext file with another one, and caused a lot of irregularities everywhere. Trim enabler did wrong in Lion, by replacing the kext file again with one that did not have the correct programming at all.

In that period Grant Pannel came witth a correct solution and gave the exact Terminal commands to establish trim on a non Apple SSD. As well in SL as Lion: he replaced just the part where the names of the Apple SSD were. Correct in SL and Lion too.

The link that Shootist gave was indeed a compiled script based on the Grant Pannel solution, but written by someone else. Grant Pannel himself has presented a compiled script on his blogs.

Secondly: the "hangs" have nothing to do with the trim being there or not.

Thirdly: the OWC people are right: their SSD has "Garbage Collection" and it is not necessary to install trim. But trim IS better than Garbage Collection so it is not a bad idea to install it. BUT DO it ONLY when the system runs well. And use Grant Pannel's solution (certainly NOT Trim Enabler). You will find that after a OS update the trim must be re-installed when the update overwrites the kext file. For the next OS Mountain Lion first research to see if trim is also installed on non-Apple SSD and/or the kext structure is changed before installing it.

Shootist: addition on point "Firstly": the Toby script does not empty the system caches and so it is better not to use that one, but use the Grant Pannel solution....

Erroll: that shootist file was what I called the "Toby" script, it is correct but it does not empty the system caches and thus as long as those are not emptied you will not see Trim enabled (and you have to restart). Let it as it is right now. It has nothing to do with the problem you want to solve. Or if you want, re-install the Snow Leopard 10.6.8.1 Combo Update, which may also help eliminate your problem.

If you want help with Trim start a new thread.

Read on the internet about what trim is and how to apply it correctly, you could start here: http://digitaldj.net/2011/07/21/trim-enabler-for-lion/ after you have read the all abouts of trim and garbage collection.

Lex.

OK, keep us informed.

It may be that it is the Ram: can you just take them out and reinstall?

Also it can be the SSD: it is the Sata3 (6GB) and it is backwards compatible to 3GB, but maybe your MBP is older and has the Sata2 connector and then it could have a negotiated link speed of 1.5GB/s (look in System Preferences Serial-ATA Linkspeed and Negotiated Link Speed). If it indeed is connected with a lower negotiated link speed than the linkspeed, do not use the "restart" option in Apple menu, but choose to "Shutdown" and pressing the on/off button to start afterwards.

Ah yes linkspeed: what is the SSD spec? Sata 3 (6GB)?.

If you run from a clone, run the repair disk permissions in Disk Utility. Although it is a remnant of history, it can do something when you change from SSD to HDD and vice versa.

Trim has nothing to do with it, and you can do it or not, but IF do it with the "Pannel" script. You can always do it later, and run "erase free space" in Disk Utility before installation .

EDIT: yes the 6GB/s SSD, maybe that is the problem, I do not know, depends on the controller and the downwards compatibility: 6GB to 1.5GB is two steps...

Ask the people at OWC on the support page.

Far from barging in, you explained very well. Some grammar mistakes and stuff, but the gist of your rant and logic was clear. Thanks for taking the time to put your understanding into words. Some of us are listening.

Hi Erroll,

I'm glad that I'm not the only one suffering from the freezes. I have a Macbook8,1 machine (late 2011) and I also bought the Mercury EXTREME Pro 6G SSD and 16GB of RAM. I installed the RAM about a day before I installed the SSD and I never saw any freezing issues. It's not unitl I installed the SSD, that I saw the issue. Like you, the system is blazing fast, until it freezes (exactly the way you describe!).

I have an open support ticket with OWC, and they had me upgrade the firmware on the SSD, which I did tonight, but I still have the issue. OWC is suggesting I re-install the OS from scratch rather than doing what I did; I made an image of my old HDD and restored it onto the SSD (which was very convenient as all of my files, settings, etc were exactly how I left them in the old HDD). I'm hesitant to do the OS reinstall because I'm a software developer and re-creating my development environment would be a royal pain.

Did you ever figure out the issue?

Hi Errol and Dexter,

I have the same problem as you guys, and i'm running on MBP Early 2011, 8GB RAM and a Kingston SV300S37A/240G , did any of you manage to fix the problem?