Problem with boot camp on MB Air 6,2 with Mojave

[Zeke]

I have wanted to install windows on my early 2014 macbook air (128GB HD) but didn't have enough space for boot camp to partition. So I found out about using NVMe blades with the Sintech adapter so bought a Crucial P1 and installed it without a problem.

https://forums.macrumors.com/threads/upgrading-2013-2014-macbook-pro-ssd-to-m-2-nvme.2034976/page-25

When I go to install Windows, boot camp successfully partitions and I'm able to create the bootable USB with drivers. Rebooting and running the setup for windows works successfully (format the BOOTCAMP partition, install Win10 Home) and then it reboots and fails. I get to a screen that says:


Your PC ran into a problem and needs to restart.

Then it restarts and hits another error saying the it needs to restart because windows wasn't installed correctly. End up having to go back to boot camp, delete the partition and try again. I've done this several times in different ways all with the same problem. Is this likely related to the new HD not matching the original? Anyone have experience and a solution with this?

Thanks!

 

[Zeke]

For what it's worth, I reinstalled the original SSD and was able to install Windows with no issue. Anyone know how if I should be able to clone this to a USB flash drive and then to the windows partition of the new drive with Sintech adapter?

 

[Mettwurst]

I'm stuck in a similar problem. Simply with a classic blue screen.

The trick is, I think, that you try to start Windows three times. After the system starts to boot, you should completely kill it again. You do that three times until you get into the "Startup Repair Tool", or something like that. Then you have to navigate through the GUI until you find the point "boot into Safemod".
Then Windows should start in Safemod and thereby "repair" your system.

Of course, be aware that every time the computer restarts, it reboots into the right place.

That certainly helped me a bit. Also, I installed Bootcamp 5 times the same day.

 

[tony1tf]

I'm stuck in a similar problem. Simply with a classic blue screen.

The trick is, I think, that you try to start Windows three times. After the system starts to boot, you should completely kill it again. You do that three times until you get into the "Startup Repair Tool", or something like that. Then you have to navigate through the GUI until you find the point "boot into Safemod".
Then Windows should start in Safemod and thereby "repair" your system.

I have a similar problem, but this 'fix' doesn't work on my MacBook Air mid 2103. I have just replaced the 128GB Apple SSD with a 512GB non-Apple "Eagle Eyes" "NEW 512GB SSD For APPLE 2013 2014 2015 2016 2017 MacBook Air 13" A1466 11" A1465" from eBay which uses an Intel SSD. I have written to the supplier to see if they have a suggestion. I have attached an image from the system report showing the correct BootCamp 100GB partition etc.

The Mac side of things is working fine, but the Win10 installation gives the BSOD and "Critical Process Died" error. Unfortunately, the proposed fix doesn't work, because the windows installation has not yet got an administrator user and won't let me boot into command prompt. It also won't let me boot into safe mode because it wants to continue the installation. Have been round the loop many times trying all the repair fixes I have seen, but they all assume that you have a damaged windows installation, rather than an incomplete new installation. Thoughts?

 

[tony1tf]

I have a similar problem, but this 'fix' doesn't work on my MacBook Air mid 2103. I have just replaced the 128GB Apple SSD with a 512GB non-Apple "Eagle Eyes" "NEW 512GB SSD For APPLE 2013 2014 2015 2016 2017 MacBook Air 13" A1466 11" A1465" from eBay which uses an Intel SSD. I have written to the supplier to see if they have a suggestion.

I just tried putting back the 128GB SSD drive in my MB Air, and installing windows again using the USB drive with the same downloads that I had used for the 512GB drive. This completed the Win 10 install with no problem, so the fault is definitely with the new SSD drive. Are there some special drivers I need to download to make windows compatible with the NVMe SSD, which is what I presume it is? The 512GB SDD has an adaptor with a sticky label keeping the drive plugged into it.

 

[tony1tf]

Sorted - had to do several things:

Found the drivers for the Intel chips on the SSD on the Intel website and substituted the Client-x64 folder for the Apple SSD drivers on the USB install disk.
In addition, when selecting the BootCamp partition during install, I selected the same Client-x64 folder on the install USB disk for the drivers, and the software correctly identified the Intel(R) SSD 660p Series, and installed the correct driver.
The install went OK except for a continual boot loop that was different from the previous BSOD - I got the "Computer restarted unexpectedly....." message, and no standard Win 10 fixes helped. However, shift F10 got me into command line where I could run regedit, and perform the fix in #1,685 which worked by magic!
The next reboot got me into the fresh Win 10 install, so I could log on, set Windows up, and run the BootCamp setup to get WiFi etc.
All seems to be OK now with the 512GB drive - I have a 120GB Windows partition.
Also, to help with looking at error messages in windows, I downloaded the 10 day evaluation copy of NTFS for Mac from Paragon Software.

Great forum here with really specific information to help us, so I hope that I have contributed.

Tony