Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

My 21.5 iMac Mid-2011 OSX Yosemite Problems HALP!

NOTE: SORRY FOR MY S**TY GRAMMAR

I use an 21.5 4GB RAM iMac Mid-2011 for 4 years now and it doesn't have any problem when it was on Mountain Lion - Mavericks, but after i updated to Yosemite for about 3 months I have some problems.

First, When I using browsers (ANY BROWSERS) for about 10 - 20 mins, the whole mac froze..(except the cursor with spining beach ball) I can't force quit or do any command other than manually power off the computer by press and hold the power button and wait for an hour to decreasing the risk of getting the flashing folder with question mark.


Another problem I have is every time I restart the computer. It shutdown and restart but when booting a flashing folder with question mark appear and I can't get pass it so I have to manually hold the power button to shut down and wait again...




Did anyone have those kind of problems? Can you fix it?



Any suggestion will be cool guys!

iMac, OS X Yosemite (10.10.3), 4GB Ram Intel i5

Posted on May 29, 2015 7:19 PM

Reply
12 replies

May 29, 2015 7:56 PM in response to McWebsterTH

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.

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. Enter "BOOT_TIME" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.

If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

When posting a log extract, be selective. A few dozen lines are almost always more than enough.

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

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.

Step 2

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.

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 shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.

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.

When you post the log extract or the crash report, 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.

May 30, 2015 6:16 AM in response to McWebsterTH

Mavericks also chews through RAM like no tomorrow! (I have the same machine)

Unless you saved the .app of Mavericks (the file that appeared when you downloaded it-usually called Install OSX Mavericks) or your iMac came out of the factory with the recovery partition of Mavericks (which it did not) then you have no way of retrieving it.


Apple have removed Mavericks from public download but its earlier OSX cousins: Mountain Lion and Lion (10.8 & 10.7 respectively) are still available for purchase.


Good Luck 😉

May 31, 2015 3:10 AM in response to McWebsterTH

To tell you the truth I bought this system from eBay about 4 months ago! I purchased it because it had a 3rd SATA slot where I could add an SSD and mod this machine to my heart's content 🙂

I have had no problems and it has worked flawlessly since I purchased it-albeit some cheap RAM sticks that kept triggering kernal panics every time they were addressed!

I have been inside this baby plenty of times and I have been impressed by the way it is so expertly designed fitting each of its components in neatly but still packing the power you will find in any desktop PC (albeit its weak GPU 😉).


On another note I remember that there was a recall for our specific machines that were fitted with Seagate HDD's, unfortunatley that has expired 😟

Could you please verify what disk you have for me (just out of curiosity) by going to Finder->Applications->Utilities->Disk Utility and looking in the left pane for the name of the disk (should start with ST********* if you have a Seagate or WDC****** if a Western Digital.

Its just the way with Hard Drives - it's not a matter of if - but when they will fail.


But like you I am feeling the constraints of the iMac and while I love Macs and Apple (always will) I am feeling like a change and have been thinking about building myself a compact (but powerful) gaming machine.

Its just the way with electronics - it will always be superseded by something more powerful the next year or so!


Hope this helps 🙂

My 21.5 iMac Mid-2011 OSX Yosemite Problems HALP!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.