OS X Beta unresponsive on startup, crashes randomly during normal use

I have been experiencing some very frustrating issues in the past couple of weeks. First of all, my computer (2011 15" MBP) has randomly crashed 4 times during the aforementioned timeframe. Each time I have had to reboot the computer multiple times, and have only gotten into the recovery mode twice. During startup, when I try going into record very mode, it will load until about 1/2 way. It will then proceed to go to a white screen and do nothing else. At this point the fans will gradually go up to full speed. Resetting the NPRAM has had not effect. Booting into safe mode is made impossible due to the same issue. Eventually after rebooting many times, the computer will finally complete the boot process and will work like normal. I have already run single user mode and run the fsck -fy command. Booting in verbose mode has produced some information that I find might be useful. It will run fine until it freezes up. The last couple of lines go as follows: VBoxFltDrv: version 4.3.18 r95616 VBoxAdpDrv: version 4.3.18 r95616. That was until yesterday when I decided to get rid of VirtualBox completely. Now the problem is that booting in verbose mode reveals a stall that always takes place on the following line: en2: promiscuous mode enable succeeded. As of this post, I have still not gotten the computer to boot successfully. The stall always takes place at the aforementioned line.

It is indeed odd that the issue is not fixed after having removed the kext.

I have opted to manually rid myself of ControllerMate and have run the command. I will post the results as soon as it is complete.


Also, I removed the correct answer marking until I am sure the problem is solved. I would not want to confuse others who might be having the same or very similar issues.

... and if you want to remove them all in one fell swoop, append -delete:

sudo find / -iname *controllermate* -delete

Whoops, I will go ahead and redo the command with the corrections. I will go ahead and delete as well, thanks!


I will also report back with results.

Run it first without the -delete

Then run it with the -delete

and then run it again without the -delete


This may sound unnecessary, but the first time is so that you can see what's there and the last time is to make sure that all got deleted (because safety measures in the -delete command can prevent some files being deleted)

Alright, will do!

Well, I did everything needed to get rid of the ComtrollerMate problem, but once again, the system will not boot. Not sure what's going on here.

Neither am I, but now is your opportunity to capture the verbose boot - maybe helpful; maybe just for posterity 🙂

ccurrently in Single User mode looking through the system.log to try and find a clue. I'll post whatever I can find in the logs.

ok, so I am now in verbose mode and have gotten some potentially good feedback. The last few lines go as follows:


  • en2: promiscuous mode enable succeeded
  • NTFS driver 3.13 [Flags R/W].
  • NTFS volume name BOOTCAMP, version 3.1.
  • NTFS-fs error (device /dev/disk0s4, pid 201): ntfs_restart_page_header_is_valid(): $LogFile version 2.0 is not supported. (This driver supports version 1.1 only).
  • NTFS-fs error (device /dev/disk0s4, pid 201): ntfs_restart_page_header_is_valid(): $LogFile version 2.0 is not supported. (This driver supports version 1.1 only).
  • NTFS-fs error (device /dev/disk0s4, pid 201): ntfs_logfile_check(): Did not find any restart pages in $LogFile and it was not empty.
  • NTFS-fs Warning (device /dev/disk0s4, pid 201): ntfs_system_inodes_get(): $LogFile is not clean. Will not be able to remount read-write. Mount in Windows.
  • nspace-handler-set-snapshot-time: 1441563778


After last message, it stalls completely. I would guess this has a lot to do with Bootcamp, but not sure exactly what or why.

Accepted Answer

Looks that way. I did some googling and it looks like it's because of Windows not shutting down properly (It does a kind of partial shutdown/hibernation that allows it to boot quicker, but this can cause issues on dual boot machines). You need to boot back into bootcamp and shutdown Windows properly.

Tends to happen more with Win8

Here's some copy-pasted help with that:


To do this, call up the Power Options program. Unfortunately, you can't simply type "power options" in the Start screen the way you used to do in Windows 7 and Vista. The search facility in the Windows 8 start screen is crippled and not very user friendly (so what else is new?), requiring additional intervention and some prior knowledge of where things are located. Instead, start by typing "power" (without the quotes) in the start screen. This will bring up the Search panel on the right side of the screen. Use your mouse to click the line that says "Settings" in that panel. On the left, you should be able to spot the "Power Options" line. Click it. (If you are familiar with the Windows+X keyboard shortcut, you can also use it to bring up a menu from which "Power Options" can be accessed. Like I said, you need a fair amount of prior knowledge before you can use Windows 8.)

The Power Options window will appear. Click the line "Choose what the power buttons do" on the left side of the screen. This will cause the System Settings window to appear. Click the line "Change settings that are currently unavailable" somewhere under the top paragraph of that window.

When you do that, some new options will appear below. If your screen is small, you may not be able to see everything. If so, scroll down (eg by using the scroll bar on the right).

In the section with the heading "Shutdown settings", you should be able to see 4 items. Click the box for "Turn on fast startup (recommended)" to uncheck it.

Click the "Save changes" button found at the bottom of the window. This will return you to the Power Options window. Now click the "X" (close button) on the top right corner of the window to exit this program.

From now on, every time you click "Shut down" from the settings panel, Windows 8 will do a genuine shutdown.

Here's the full article if you're interested: http://www.howtohaven.com/system/how-to-shutdown-windows-8.shtml

ALright, as soon as I can get the computer to boot correctly, I will go ahead and boot Win. This little issue will not allow it to boot anything until whenever it decides to work correctly.

OK, o my laptop finally booted after several tries. I've gone on and followed the instructions. Oddly enough, on my system that option is already unchecked. My guess is that this could also happen because when I quit out of Windows, I always just restart instead of completely shutting down. It would seem that this would have the same effect. I will shut the system down all the way this time when quitting Windows and see if that does the trick. I'll post an update after some amount of time of normal computer usage. Hopefully this solves the issue because it's been quite a hassle lately.

OS X Beta unresponsive on startup, crashes randomly during normal use
 
 
Q