Looks like I'm in for another episode of failed startups. The installation appears to have gone without a problem, but upon rebooting, the loading bar has stopped at about 90%. I let it sit there for about an hour, but no change. Things I have already tried:
Hopefully this is just something I may have missed...
Well, after taking my computer over to the Apple Store, I received the confirmation of what was causing the error. My computer was actually one of the rare cases of:
https://www.apple.com/support/macbookpro-videoissues/
I was told that the computer will be fixed at no charge and will be getting it back in about one week. Thank goodness the issue came up before Feb 2016, or my computer would not have been covered.
I would like to share the symptoms with everyone here on the forums: please note that the symptoms are actually similar to those causee by the rogue kexts that are so well known for causing boot problems.
The affected macs are listed in the above link from Apple. If yours falls under the affected models, and you experience the aforementioned symptoms, keep this in mind. If you are experiencing these symptoms, but you can still log on, make a backup ASAP. If you can no longer access your information due to no longer being able to boot into any partition, don't worry, there's still a way to back up at least some of your most important files. Go to the following link for instructions on backing up your files from Single User Mode:
jsalovaara.com/blog/backing-up-files-to-a-usb-drive-using-single-user-mode.html
If this applies to you, take your laptop to your nearest Apple Store to get it checked out. Once there, they will confirm whether it is covered by that repair program. If so, they will repair it free of charge and will have it back to you within a week.
Thats all there is for this issue, best of luck to everyone and hopefully no one else has to go through all of this trouble!
Actually those last two are legacy OS X - not used any more but almost certainly benign. Get rid of APowersoftAudioDevice.kext though.
Have a check on your system for soundflower with:
find / -iname "Soundflower*"
It'll take a while to run...
Alright, I have gotten rid of the Apowersoft kext
rrunning that command now.
Btw, the way you posted the picture of the log worked if you need to do somethign similar again...
jjust finished running the command,money got the following output:
That means it's not there - the log must be from a launch daemon/agent that tries to find it but fails.
Try rebooting.
Actually, before you reboot, one more kext sniffer you could try is:
find /Library/Application\ Support -name *.kext
^^^ That last command needed an edit: the leading \ should have been a /
ttrying the command now
it appears to have found nothing with that command
Okay, try rebooting...
An NVRAM reset may or may not be necessary...
Still wondering about that reference you saw in the log... Another long-running command to find it might be:
find / -iname *Cycling74*
jjust tried rebooting and had no luck, I'll go into SUM and run the command you just suggested.
well, according to the output, there is one .plist file with Cycling74 on the system, shall I delete it?
