Reboot fail after installing El Capitan help!!

Hi! and sincere thanks to all of you who have helped with this problem. The last post was a month ago today, so I hope you'all are still checking in.

Just briefly, this is my first Mac; I inherited it last fall (2015) from a family member but with a clean Yosemite install. It's a late 2011, 15" , I7, etc. It began having the same problem(s) described in this thread about 4-6 weeks ago, probably when I upgraded initially to El Capitan or the latest version - not sure which.

I'm having one additional twist that I haven't read in any of the other posts: after the startup chime, my login screen is not the smooth pale blue, but rather has pinkish blue horizontal lines. The login box, the shutdown, restart, etc. are all still legible, but it will NOT BOOT from this screen. I've tried 100 times at least, not even in safe or recovery but instead will go to the "smooth" pale blue screen that I assume is what's called the "blue screen of death". After a few seconds here - maybe 15 or 20 seconds - it restarts on it's own back to the "blue lines" login.

Well, magically yesterday the login was smooth (no horizontal pinkish blue lines) and it booted. Guess it was my Valentine Day gift!! While it was up I went thru all the kext files as advised. There are no "Not Signed" and only one "Loadable: No". The "Loadable: No" is AppleOSXUSBNCM.kext (I think -should have written it down). I was not able to either move or delete it because it's a "required system file" or something like that.

There is one, however, named "Unsupported". It showed in the text file on my desktop, but I could never find it in Finder. I found the one immediately preceding it, but "Unsupported" did not show in Finder. It was signed by Apple....something or other.

Sadly, when I did a restart, it's back to the "blue lines" again, so I'm down. I hope I have made a small contribution here with my unique version of the much larger problem.

Where do I go from here?

Thanks!!

Considering the age of your Mac (2011) this could be a hardware issue. If it is a hardware issue, it's usually cheaper to buy a new Mac than repair.

Do you have access to another Mac? If yes, you can use screen sharing to see if the problem Mac looks the same when viewed using screen sharing. This would rule out the monitor but there are other parts like a graphics card that could be going bad. If you could take your Mac into an Apple Store they could run hardware tests.

eg. I have a 2006 iMac. The monitor is shot. It's so bad you can't see anything. However, when I screen share, I can use the old iMac without any issues.

I'm in denial for the present anyway that this is a hardware problem. This computer worked perfectly for a couple of months and only began the freezing, crashing, not booting after I upgraded to El Capitan. This could be coincidence, but in reading thru this thread and others, 90% of the symptoms I'm having are mentioned by others and have been solved with software changes.

Unfortunately, I don't have easy access to another Mac. My workplace has always used windows computers, so I have done the same. I have an external monitor; do you think connecting connecting to it would test the graphics card/monitor? Is the graphics card on the logic board? A logic board for this model is $159, and the instructions for replacing it seem pretty straight forward - provided you have the tools.

Thanks!

Try booting into the Recovery Drive. If you see a strange screen in recovery, you'll know it's hardware.

Boot into the Recovery Drive by holding down Command R when restarting.

When you log in you'll see something similar to this. A gray background with a box OS X Utilities.

Lost my text when I inserted the images. Oh well, bottom line is that booting with command R bypasses the login and goes to the smooth blue screen - after 2-3 minutes. Also, doesn't restart itself as it does with a normal login boot attempt. I was successful with command R a couple of times early on. I reinstalled El Capitan and even bought a new hard drive and tried to do a clean install to the new disk. That didn't work, but it may not have been the computer's fault.

Hope you can see the difference in the images. The top one is what I get now when I startup - blue horizontal lines but still legible. The 2nd is the smooth screen that I think everyone calls the blue screen of death. I can go to terminal using command S and to disk option with the option key, but right back to the blue lines when I choose the hard drive.

I've been looking at the new Macbooks. They're really tempting put I'm not giving up on this one just yet. With the I7 chip, this one still a better computer than what I can get for $500 in a windows machine.

Thanks again for your help.

When you booted into the recovery drive using Command R, did you ever see the box with OS X Utilities? If not, I suspect it's your install. I suggest you create a USB installer and try installing El Capitan from the USB drive. You'll need a working Mac to download El Capitan installer and prepare the USB drive.

http://blog.macsales.com/33160-how-to-create-a-bootable-el-capitan-usb-install-d rive-with-diskmaker-x

BTW, the MacBook was on sale for $300 off. Just ended. http://9to5toys.com/2016/02/11/12-inch-retina-macbook-sale/

This site posts weekly updates to deals.

Story of my life, a day late and a megabyte short. Thanks for the links; I'll find a Mac and try to create a USB installer. To your question - when this problem first began, I was successful 2 maybe 3 times in booting into the recovery drive but not in the last couple of dozen attempts. Just goes from blue lines to smooth blue.

Thanks again,

Since you were able to boot into recovery but cannot now, this seems to point to hardware. Let us know if you can boot up after running El Capitan from the USB Installer.

Will do.

Tks,

Hello GS from NL,

I've followed this thread for a while, but have perhaps a unique problem. Installed El Capitan on mid-2007 iMac. Stuck in reboot. Starts up with some progress before shutting down and rebooting continuously. Never completes the progress bar. No startup mode works for me. Safe Mode doesn't work. Neither does Recovery Mode. I am able to startup in Target mode and connect via Firewire from my MBP. Familiar enough with Terminal to cut and paste, but not sure how to find and delete kexts via Target Mode. Is there a simple command line prefix I can use to run your fix? Don't want to run Terminal on my MBP instead of the iMac.

Thanks in advance for your help.

Vance

Hi Tsofa:

I am having the same issue as many others. My imac keeps restarting after upgrading to el crapitan from snow leopard.

I tried using this terminal kexts command that you mentioned but it isn't working for me.

cd "/Volumes/Macintosh HD/Library/Extensions/" ; mkdir Unsupported ; mv hp* Unsupported ; mv B* Unsupported ; cd "/Volumes/Macintosh HD/System/Library/Extensions/" ; mkdir Unsupported ; mv Elt* Unsupported ; mv ssud* Unsupported ; rm -Rf /Volumes/Macintosh\ HD/Library/Application\ Support/Rox* ; rm -Rf /Volumes/Macintosh\ HD/Library/Application\ Support/Check* ; rm -Rf /Volumes/Macintosh\ HD/Library/Filesystems/*fuse* ; rm -Rf /Volumes/Macintosh\ HD/var/folders/*

My HD is called MacOsx there is no HD in the name. Do I deleted everywhere it says Macintosh HD and replace it with MacOsx. Also I noticed that in other parts of the command it reads Volumes/Macintosh\HD/Library/Application with this I am confused at what not to put. Do I remove both Macintosh\HD or just Macintosh?

Thank you so much it helped me alot

macbook air 2011, stuck at boot screen after osx update...

This helped

https://www.justinsilver.com/technology/os-x-el-capitan-10-11-1-hanging-on-boot- fixed

1) boot to recovery mode (hold cmd-R at boot)

2) in terminal compare kexts in "/Library/Extensions/" and "/Volumes/Macintosh HD/Library/Extensions/"

and remove some kexts from "/Volumes/Macintosh HD/Library/Extensions/"

in my case HP and Canon printers

3) reboot and everything works again

still loading..... can't boot, now I'll try to clean install after cleaned up the partition

Thank you so much GSfromNL! After 2 days trying everything to reboot, your "step by step" help me and i got it working!