Hi,
I have an iMac i5 / 2.5 Ghz / 4gB /mid 2011. I have just installed Yosemite
I get continuous crashes of interface. I'm not able to figure out because it's happening. It happens about once por day, and I always do something different every time. I'm not able what it could be. It happens suddenly, than I can't do anything more, and I force to re-start the iMac manually.
Can someone help me ?
Thanks
iMac, OS X Yosemite (10.10.1)
Can you explain in more detail what " continuous crashes of interface" means? Does that mean the computer won't run at all and you are forced to restart, or does it mean something else?
Hi,
I mean that the interface becomes suddenly stuck. it seems that nothing happened, but you can't click in any places. It seems that it's freezed. I would like to get some reports about that, but from console log I'm not able to undestand anything.
The other day it stucked when I was setting the screen brightness, and today I was talking on Skype.
PPlease post an EtreCheck report of your system. Google it and you will find the download.
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. Initially the words "String Matching" are shown in that box. 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.
Thanks a lot.
I'm going to try to get these reports.
I seem to be having a similar issue since i upgraded to Yosemite. My screen goes pixelly and mouse works but everything else is frozen. If i wait long enough computer restarts by itself and says there has been a graphics issue and system needed to reboot?
iMac (21.5-inch, Mid 2011)
I checked and before the BOOT_TIME's row I have a lot of lines.
Beolow you can find the first lines
22/12/14 19:07:10,179 SubmitDiagInfo[311]: SubmitDiagInfo sucessfully uploaded 78 diagnostic messages
22/12/14 19:07:10,187 SubmitDiagInfo[311]: Submitted problem report file:///Library/Logs/DiagnosticReports/TeamViewer_Service_2014-12-22-183638_iMa c-di-Rodolfo.crash
22/12/14 19:07:15,215 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
22/12/14 19:07:20,000 kernel[0]: ** GPU ASIC Log Start **
Then there are a lot of lines like these... a lot !
22/12/14 19:07:20,000 kernel[0]: : 0x00006741 : 0x00000092 : 0x00000001 : 0x00000018 : 0x0000a880 : 0x00000001 : 0x00000001 : 0x00006741
22/12/14 19:07:20,000 kernel[0]: : 0x00000001 : 0x00000015 : 0x00000000 : 0x00000001 : 0x00000047 : 0x00000000 : 0x00000001 : 0x00000058
22/12/14 19:07:20,000 kernel[0]: : 0x00000012 : 0x00000001 : 0x00000055 : 0x00000000 : 0x00000001 : 0x0000004a : 0x0000106b : 0x00000001
22/12/14 19:07:20,000 kernel[0]: : 0x0000004d : 0x00006741 : 0x00000000 : 0x00000010 : 0x00e30800 : 0x00000000 : 0x00000021 : 0x00000080
22/12/14 19:07:20,000 kernel[0]: : 0x00000000 : 0x00000011 : 0x00000007 : 0x00000002 : 0x00002254 : 0xffc0f001 : 0x00000002 : 0x0000263d
22/12/14 19:07:20,000 kernel[0]: : 0x00000001 : 0x00000002 : 0x000021a0 : 0x80838647 : 0x00000002 : 0x0000219f : 0x00020586 : 0x00000002
22/12/14 19:07:20,000 kernel[0]: : 0x0000219d : 0x20000000 : 0x00000002 : 0x0000219e : 0x00011002 : 0x00000002 : 0x000021da : 0x0a000c02
22/12/14 19:07:20,000 kernel[0]: : 0x00000002 : 0x000021db : 0x00000080 : 0x00000002 : 0x000021dd : 0x00000002 : 0x00000002 : 0x000021e0
22/12/14 19:07:20,000 kernel[0]: : 0x00700072 : 0x00000002 : 0x000021e0 : 0x00700072 : 0x00000002 : 0x000021e1 : 0x00c000c3 : 0x00000002
22/12/14 19:07:20,000 kernel[0]: : 0x000021e2 : 0x01980198 : 0x00000002 : 0x000021e3 : 0x01a001a0 : 0x00000002 : 0x000021e5 : 0x00530055
22/12/14 19:07:20,000 kernel[0]: : 0x00000002 : 0x0000217f : 0x00000000 : 0x00000002 : 0x000021b6 : 0x00000000 : 0x00000002 : 0x00003041
22/12/14 19:07:20,000 kernel[0]: : 0x00000a0d : 0x00000002 : 0x00003040 : 0x00200010 : 0x00000002 : 0x00003042 : 0x00000000 : 0x00000002
Than in the middle of those rows (that I've writen above) there are this 2 lines
22/12/14 19:07:21,000 kernel[0]: ** GPU ASIC Log End **
22/12/14 19:07:29,000 kernel[0]: ** GPU ASIC Log Start **
Then there are other similar lines like above
22/12/14 19:07:29,000 kernel[0]: : 0x00006741 : 0x00000092 : 0x00000001 : 0x00000018 : 0x0000a880 : 0x00000001 : 0x00000001 : 0x00006741
22/12/14 19:07:29,000 kernel[0]: : 0x00000001 : 0x00000015 : 0x00000000 : 0x00000001 : 0x00000047 : 0x00000000 : 0x00000001 : 0x00000058
22/12/14 19:07:29,000 kernel[0]: : 0x00000012 : 0x00000001 : 0x00000055 : 0x00000000 : 0x00000001 : 0x0000004a : 0x0000106b : 0x00000001
22/12/14 19:07:29,000 kernel[0]: : 0x0000004d : 0x00006741 : 0x00000000 : 0x00000010 : 0x00e30800 : 0x00000000 : 0x00000021 : 0x00000080
22/12/14 19:07:29,000 kernel[0]: : 0x00000000 : 0x00000011 : 0x00000007 : 0x00000002 : 0x00002254 : 0xffc0f001 : 0x00000002 : 0x0000263d
22/12/14 19:07:29,000 kernel[0]: : 0x00000001 : 0x00000002 : 0x000021a0 : 0x80838647 : 0x00000002 : 0x0000219f : 0x00020586 : 0x00000002
22/12/14 19:07:29,000 kernel[0]: : 0x0000219d : 0x20000000 : 0x00000002 : 0x0000219e : 0x00011002 : 0x00000002 : 0x000021da : 0x0a000c02
22/12/14 19:07:29,000 kernel[0]: : 0x00000002 : 0x000021db : 0x00000080 : 0x00000002 : 0x000021dd : 0x00000002 : 0x00000002 : 0x000021e0
22/12/14 19:07:29,000 kernel[0]: : 0x00700072 : 0x00000002 : 0x000021e0 : 0x00700072 : 0x00000002 : 0x000021e1 : 0x00c000c3 : 0x00000002
22/12/14 19:07:29,000 kernel[0]: : 0x000021e2 : 0x01980198 : 0x00000002 : 0x000021e3 : 0x01a001a0 : 0x00000002 : 0x000021e5 : 0x00530055
22/12/14 19:07:29,000 kernel[0]: : 0x00000002 : 0x0000217f : 0x00000000 : 0x00000002 : 0x000021b6 : 0x00000000 : 0x00000002 : 0x00003041
And in the end there are this two lines
22/12/14 19:07:29,000 kernel[0]: ** GPU ASIC Log End **
22/12/14 19:08:03,000 bootlog[0]: BOOT_TIME 1419271683 0
--------------------------------
I hope all of this can be helpful.
Thanks
hi,
Thnaks,
I checked but I think this is not my problem. That bug happens only on iMac 27" with 3.1GHz quad-core Intel Core i5 or 3.4GHz quad-core Intel Core i7.
I have an iMac i5 / 2.5 Ghz / 4gB, furthermore the symptoms are completely different, because I don't get white or bluedistorted displaywith vertical lines, or to turn black, I simply get interface stuck, and besides this happens sometimes.
What do you think it could be if you watch the logs that I posted above ?
Thanks
Yes, I think it's the same trouble.
Have you found some solutions to fix the problem ?
The GPU is faulty and must be replaced, whether it's covered by the recall or not.
iMac Crash with Yosemite
