Bootcamp/Win 10 corruption - Macbook Pro 2015 is crashing

Here is my scenario:

  • I've had a Macbook Pro Retina 2015 for a while.
  • I recently upgraded to Catalina
  • I decided to give bootcamp a try after wanting to do this for a long time!
  • So i go through the procedure with a few hickups. I partitioned my exisiting 1 TB SSD to 500/500.
  • I installed Win 10 on one 500 GB partition.
  • Everything seemed fine. I could switch between MacOSX and Win 10 without issues (by holding Option Key).
  • A few days ago I decided to try to install a Printer connected via USB Cable to my Mac. I was having issues so I decided to boot into Win 10 to see if it worked. Win 10 could not see the Printer so I decided to boot back into MacOSX. I think i may have performed a hard shutdown to force a reboot. So by holding Option key I decided to go to MacOSX.
  • So somehow I believe the win side of things got corrupted. I noticed while on the MacOSX side, after a bit, my mouse would show the spinning beach ball. Then y MacOSX would freeze, and then eventually MacOSX would reboot, and I would get a blue screen of death:
  • So I have to hold down the power button to reboot. If I do nothing I get booted right into the blue screen of death.
  • So I have to always hold down the Option key to boot into MacOSX. When in MacOSX I have less than 5 mintues before the spinning ball shows up - then system locks - then crash - then blue screen.
  • If I hit F1 in Recovery Enviro - nothing happens - if I hit F8 the screen just blinks on/off.
  • So I figured I would at least try to fix this using Bootcamp Assistant - maybe try to remove my installation of Win 10.
  • When I launched Bootcamp it only gave me the option to create a new Win Bootdisk. There was nothing in options to remove an existing Win installation.
  • So I figured I would use Disk Utility and just remove the Win10 Partition. I thought that would fix my woes. Ha - no go. My Mac still thinks there is a Win Partition, I still get booted into Blue Screen of Death on reboot.
  • QUESTION: How does this happen - if there is no WIn 10 why does it still think there is one?????
  • So here is my dilemma: I called Apple support. They said no problem we will go through the process of using web install of Catalina while erasing your HD (so a fresh install). So I hold down Option/CMD/R. I get to the Password screen - input my password - spinning ball - nothing - try again and the password input shakes to say wrong password. So Apple support says to select Forgot PW. It then asks for my apple ID and PW - that works - asks for two form identification from my iPhone - then gives me a message that my apple ID does not allow for erase of my Macbook! So Apple support says okay then hold cmd/R and try that. I'm like what the heck is the difference. Well same thing thing happened - I can not erase my Mac and reinstall Catalina.
  • So I figure I'll create an external MACOSX boot disk (USB) by downloading full install from internet. Well i can never get passed the spinning ball/freeze/crash/bluescreen of death.
  • So Apple says - go to an authorized Apple dealer since Apple stores are closed. i'm like is this going to cost me money - they say of course. It turns out I got quoted for $125 to force a erase and reinstall of Catalina.
  • Questions: How did this happen? Why is it so hard to recover from this blue screen of death? Is it too late to fix this issue - or at least allow for my Mac to not shutdown?
  • I'm disappointed with MacOSX/Bootcamp. Something like this should NEVER happen, and if it did there should be a recovery mode.
  • I look towards your expert knowledge - PLEASE HELP!
  • Thanks

MacBook Pro Retina

Posted on Jun 3, 2020 6:44 AM

Reply

Similar questions

53 replies

Jun 8, 2020 11:46 AM in response to Loner T

Still confused. I formatted the MBP SDD using APFS and entitled it "Untitled".


The Apple SSD (Top) is classified as "disk2"

The Container that is created during erase is disk 3 - physical stores: disk2s2

And "Untitled" is below this Container as disk3s1


Here is diskutil list output:


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      APFS Container Scheme -                      +1000.0 GB  disk1


                                 Physical Store disk0s2


   1:                APFS Volume OpusIII - Data          101.6 GB   disk1s1


   2:                APFS Volume Preboot                 81.0 MB    disk1s2


   3:                APFS Volume Recovery                528.5 MB   disk1s3


   4:                APFS Volume VM                      4.3 GB     disk1s4


   5:                APFS Volume OpusIII                 11.0 GB    disk1s5




/dev/disk2 (external):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                         1.0 TB     disk2


   1:                        EFI EFI                     209.7 MB   disk2s1


   2:                 Apple_APFS Container disk3         1.0 TB     disk2s2




/dev/disk3 (synthesized):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      APFS Container Scheme -                      +1.0 TB     disk3


                                 Physical Store disk2s2


   1:                APFS Volume Untitled                757.8 KB   disk3s1



Do I unmount anything? I get the error below "Error: -69614: The disk is already in use by APFS"


I still do not know what you are having me do, and how the Mac Mini comes into play. I changed your "-secondary disk1s2" to "disk2s2" since I believe things changed from last time I posted (see above).


I get this:


Geralds-Mini:~ geraldohara$ diskutil apfs createContainer -main disk0s2 -secondary disk2s2 


Creating container with disk0s2 disk2s2


Started APFS operation on disk0s2


Creating a new empty APFS Container


Error: -69614: The disk is already in use by APFS


Geralds-Mini:~ geraldohara$ 


Here's is what it looks like in DU:





Jun 10, 2020 7:50 AM in response to oharag

From MacBook Pro (Retina, 15-inch, Mid 2015) - Technical Specifications, you have the following storage options...


Storage

  • 2.2GHz - 256GB
  • 256GB PCIe-based flash storage
  • Configurable to 512GB or 1TB flash storage.
  • 2.5GHz - 512GB
  • 512GB PCIe-based flash storage
  • Configurable to 1TB flash storage.


If your MBP boots, can you check About This Mac -> Storage? It should look similar to




Jun 11, 2020 5:19 AM in response to Loner T

Did the output tell you anything? Were you thinking my SSD was a 3rd party? Do you think it’s the cause of all my problems? It seemed that something happened during switching between switching between Bootcamp and MacOS. Something got corrupted. Do you think it’s a fault with the SSD? Diskcheck produced no errors. Diagnostics no problems. The only way I could recover was through cloning. Once cloned I get the same issue on my MBP - after 5 minutes I get spinning ball and then reset.

Jun 11, 2020 4:56 PM in response to oharag

oharag wrote:

How do SSD go bad? It's Solid State!!!

Mechanically, they may be fine, but SSDs can wear-out.

So for $300 wouldn't it be better to just purchase a replacement SSD? I've heard of horror stories trying to get Catalina to recognize a blank drive inside an MBP. I'm sure it's not an easy process - similar to what we went through these past few weeks.

Do you have a recommendation on an ssd replacement for 2014 MBP?

Since Apple SSDs for your model are proprietary, you may need to look for a used Apple SSD of the size you want.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Bootcamp/Win 10 corruption - Macbook Pro 2015 is crashing

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.