MBP 2014 Suddenly Won't Boot Up

[Hugetrn]

Hello everyone,

I've been using my MBP for over 4 years and ever since the first time I tried to boot it last night, it hangs at the spinning wheel screen after the progress bar.

At first, it starts booting as usual. Progress bar fills up to a quarter of it and then the screen goes totally black. It goes into this loop where the white spinning wheel appears then cursor appears for a second and it goes back to the white spinning wheel. It does this forever and never completes the booting process.

It gives me this message:

Failed to send exception EXC_CORPSE_NOTIFY. error code: -308

It seems to be giving me the warning after this line:

IO80211Interface::updateReport _peerManager is missing

I tried resetting my SMC, NVRAM and PRAM. I ran First Aid in recovery mode nothing came up.

I was thinking it might be a hardware issue but I have Windows BootCamp installed and I am able to boot it as usual and everything runs smoothly.

I really want the option to reset my mac to be the last resort. Is there anything I can do to boot my MBP again as the way it was?

Thanks in advance!

 

[Fishrrman]

I have no interest in Windows so I don't use BootCamp.

If you are able to boot into recovery mode, this would indicate there is no hardware problem with the Mac (other than possibly the drive).

But then, if you can boot into Windows without problems, that further indicates that there seem to be no -hardware problems- with the drive itself.

I'm going to -guess- that -something- you did with Windows has messed up the Mac partition on the drive (software problem).

I have no idea whether the following will work.
Do it only if you have a good backup of your Mac partition:
I'd try to boot to internet recovery.
Then, I'd erase the Mac partition (Mac partition ONLY, not the entire drive).
Then, I'd do a clean install of the Mac OS to it.
Then, I'd restore my files/apps from my backup.

If that didn't work, I'd do this:
- Boot from internet recovery or another drive
- Erase the ENTIRE internal drive (including the BootCamp partition)
- Re-install the OS
- Re-install my files
- I would not re-install BootCamp. If I -had to have- access to Windows, I'd install Parallels or VMWare Fusion and then run Windows "under emulation".
Far less trouble that way.

 

[Hugetrn]

I have no interest in Windows so I don't use BootCamp.

If you are able to boot into recovery mode, this would indicate there is no hardware problem with the Mac (other than possibly the drive).

But then, if you can boot into Windows without problems, that further indicates that there seem to be no -hardware problems- with the drive itself.

I'm going to -guess- that -something- you did with Windows has messed up the Mac partition on the drive (software problem).

I have no idea whether the following will work.
Do it only if you have a good backup of your Mac partition:
I'd try to boot to internet recovery.
Then, I'd erase the Mac partition (Mac partition ONLY, not the entire drive).
Then, I'd do a clean install of the Mac OS to it.
Then, I'd restore my files/apps from my backup.

If that didn't work, I'd do this:
- Boot from internet recovery or another drive
- Erase the ENTIRE internal drive (including the BootCamp partition)
- Re-install the OS
- Re-install my files
- I would not re-install BootCamp. If I -had to have- access to Windows, I'd install Parallels or VMWare Fusion and then run Windows "under emulation".
Far less trouble that way.

Thank you for your reply I would guess the same but it had been more than 3 months since the last time I booted Windows on my MBP. I believe I left my MBP idle two days ago while it's running on macOS Sierra and I'm assuming something happened when it went to sleep.

As for your suggestion, I thought of recovering data and re-installing the OS. It's sort of a tedious work around to a problem that I don't have the solution to. Without knowing it's reason or how to fix it, I will always be skeptical as to whether it will happen again or my MBP will boot as usual. I made a research on the internet with the error code I mentioned above and nothing came up. I think I have no option but to re-install everything. Thank you.