Q: OS is "locking up"

When this happens, do a PRAM reset and see if that clears the hang: OS X Yosemite: Reset your computer’s PRAM

How to fix kernel panics after installing OS X updates | MacIssues

OS X- About kernel panics

Mac OS X- How to log a kernel panic

Visit The XLab FAQs and read the FAQ on diagnosing kernel panics

Please post the most recent panic log from the most recent crash you've experienced provided there is one.

If these are kernel panics they may be caused by hardware. Random panics may be caused by RAM modules going bad. They can also be caused by failing hard drives or motherboards. Run the Apple Hardware Test that came with your computer to check the hardware. Note any errors that occur and post them here.

Try these in order testing your system after each to see if it's back to normal:

1. a. Resetting your Mac's PRAM and NVRAM

    b. Intel-based Macs: Resetting the System Management Controller (SMC)

2. Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:

     Boot to the Recovery HD: Restart the computer and after the chime press and hold down the

     COMMAND and R keys until the Utilities menu screen appears. Alternatively, restart the

     computer and after the chime press and hold down the OPTION key until the boot manager

     screen appears. Select the Recovery HD and click on the downward pointing arrow button.

3. Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the Utilities menu. Repair the Hard Drive and Permissions as follows.

When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.

4. Reinstall the 10.10.4 update: OS X Yosemite 10.10.4 Combo Update.

5. Reinstall OS X: Reboot from the Recovery HD. Select Reinstall OS X from the Utilities menu, and click on the Continue button.

     Reinstall the 10.10.4 update: OS X Yosemite 10.10.4 Combo Update, if required.

Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

When the machine becomes unresponsive, note the exact time: hour, minute, second.  

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

The title of the Console window should be All Messages. If it isn't, select

          SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

          View ▹ Show Log List

from the menu bar at the top of the screen.

Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.

Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.

Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

When you post the log extract, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.