![]() (That sort of problem has happened in the past, but rarely.) The lack of "beachball" chatter would tend to imply there's something else involved here. ![]() We'd usually be hearing about "beachballs" everywhere, if the problem were generic to OS X, or to a particular series of MacBook running 10.7.5. While it's certainly possible that the trigger is OS X, it would be fairly unsual for this "beachball" to show up at just one site and not everywhere that's running 10.7.5. Particularly rare if the systems were not acquired from the same source and at the same time if the systems lack nearby serial numbers and all.) (Full disclosure: I have seen similar systems all have similar failures, when a batch of systems were purchased together and a common component was malfunctioning a bad batch of widgets was used in all of the systems. A trigger that's probably not local hardware double hardware failures can and do happen, but they're not common. If so, that can point to a common trigger. "My wife's computer was the first to have issues." So you have two entirely separate OS X systems (both presumably running 10.7.5?), and both with similar "beachball" wait cursor symptoms? Be sure to read the procedure carefully and follow all the steps exactly as written, even if they seem inapplicable or trivial. System performance problems for reasons that cannot be isolated to any other cause justify an SMC reset.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |