MacBook running poorly after Yosemite update

Question

Since updating to Yosemite last week, my MacBook Pro has been running very poorly. I have experienced a series of crashes, which I think I have attributed to use of Preview, frequent "rainbow wheels," freezing, and program errors when trying to perform just basic tasks, and a distorted login screen image. Additionally, just today, Mail will not send e-mails because it claims that it cannot detect the server, but I have not changed any preferences and am having no issues sending mail from my iPhone or iPad. Is anyone having similar issues? And any guesses on when the first update may be available to correct some of these bug fixes?

Answer 1

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. Click Utilities, then Console in the icon grid.
In the Console window, select
          DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar.
A GPU restart report has a name that begins with "Kernel" and ends in ".gpuRestart".There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A GPU restart report has a name that begins with "Kernel" and ends in ".gpuRestart". Select the most recent of each. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.