Finder crash & battery number of cycles error?

Question

Hello everyone,
First of all, this is about my Macbook Air mid2011 13inch.
I started to use this Macbook since beginning of August in 2011.
Begin of September 2014, my battery number of cycli was 1159
I use this Macbook like almost everyday since I bought it and even when I don't use it, I keep running it like 24/7.
Calculation: Beginning of August 2011 - Begin of September 2014 = approx. 36 months = 1095 days
Battery number of cycli in 1095 days = 1159
Each day was around +1,05 cycli.
But here is the problem:
My battery was defect after reach the 1000 cycli, the Macbook was out of battery every 1 hour instead of 7 hour.
I went to the AppleStore on 10th September to change my Battery.
The employee has replaced a new battery for me. The battery number of cycli of my Macbook Air went to 1.
That's a good news.. BUT after the replacement, I noticed that there are 2 problems with my Macebook Air.
1. My Finder keep crashing all the time!
2. I have only used 17 days after the battery replacement and the number of cycli is already 45!
Each day is now around +2.64 cycli.
I suspect that this Macbook wil reach number of cycli 1000 within 13 months.. why? 13 months = 365/12*13 = 395 days
395 days * 2.64 cycli a day = 1042 cycli

Answer 1

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.
Step 1
For this step, 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.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if iTunes crashed, you would enter "iTunes" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them 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 which is irrelevant to 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.
Step 2
In the Console window, select
          DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. 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 crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. 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, 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.