-
All replies
-
Helpful answers
-
May 4, 2015 12:41 PM in response to VsubbMOWby Drew Reece,VsubbMOW wrote:
Are there any way to roll back to 10.10.2 without reinstalling all of my software and settings?
Only if you have a full backup from before 10.10.3 was installed. Apple don't offer tools to undo an update. You will also need an archive of the 10.10.2 installer as the App store will now give you the 10.10.3 version when you download 10.10.
If you need help making a backup of this system ask, you can do that in recovery mode, you may find a clean install will resolve the issues. However it could be a hardware issue that has appeared with 10.10.3.
AHT may show hardware faults, but sometimes it will not catch a hardware error…
Using Apple Hardware Test - Apple Support (use cmd+L to run in 'loop mode' for normal & extended test modes).
How was safe mode? That can indicate if the issue is in whatever third party items you have still installed.
http://etresoft.com/etrecheck <= will show us what is on the OS if you still want to look at the existing OS, but I think it may be time to cut your losses & try a clean install, even if it is only onto an external disk - just to see if the Mac will boot 10.10.3 without the panics.
-
May 4, 2015 1:09 PM in response to VsubbMOWby ChingisRuth,Its not a hardware error its Java software that causes most spinwheel nightmares with the recent 10.10.3
I recommend clean reinstall [erase data on Macintosh HD in Disk Utility on recovery partition] especially if you initially installed Yosemite with app store only.
Answer to Yosemite Freeze / Spindump
Also this article to disable Java could be of use Java for OS X 2014-001: How to re-enable the Apple-provided Java SE 6 web plug-in and Web Start features - Apple Support
-
May 4, 2015 3:02 PM in response to VsubbMOWby Jippie44,Before going into all kind of fixes and (re)installing you might want to wait for the Apple-update or go back to 10.10.2. These problems (just like the wifi/bluetooth-issues) are widespread and well documented. We can try to fix what we want, but -in this case- the fix has to come from Apple. Let's hope we don't have to wait until 10.11 Yellowstone for bugsfixes. That failed 'Recovery'-update made clear that Apple is aware of the issues. At the same time they also made clear that they have no control over it. And the problems are so diverse, 7 months after release of yosemity; I've never seen anything like this in 28 years working with macs.