Windows 10 installation crashing

Question

Level 1

8 points

Windows 10 installation crashing

I've been having serious issues trying to reinstall bootcamp and Windows 10 on my 27" iMac 2017 Fusion drive. The latest Windows update 1903 caused the system to crash after a few seconds after starting up Windows.

I removed the partition using bootcamp assistant in Mac OS Mojave. I've then tried making a fresh partition and tried installing Windows 10 (both ISOs from the official windows site (Both on separate occasions with the May 2019 and Oct 2018 updates). The windows setup puts the necessary files on the partition just fine during the first restart. However once the machine restarts for a second time it only goes for about 1 min before I get a blue screen of death. After this I get a number of kernel panics trying to get back into Mac. I end up having to reset the PRAM/NVRAM and the SMC.

Things I have tried:

Taking out third party RAM
Run an apple hardware check by holding down D during startup (this was fine)
Memtest86 bootable USB, 4 hour check said RAM was fine. Even third party RAM.
The only things that are connected to the computer during the Windows install is an Apple Keyboard, MS mouse and an ethernet cable (no extra drives or USB sticks)
Reformating the whole drive, rebuilding the fusion drive and reinstalling El Capitan. After doing this I still get the same errors trying to install Windows 10 as mentioned above.
Reformated again, went straight to Mojave and tried installing Windows again, same problem.

Any help would be great.

Just as a side question, is there anyway to take an image of a bootcamp partition on another Mac and restore a partition on this affected Mac so I don't have to go through the install process. I would like to avoid spending 40 dollars on WinClone if I don't know it's going to work.

Cheers

iMac 27", macOS 10.14

Posted on Jun 25, 2019 6:00 PM

Reply

Answer 1

kmh0

Level 1

4 points

Jul 1, 2019 5:18 PM in response to Loner T

I was having this same exact problem. It was due to the fast startup option that comes with Windows 10 build 1803 and 1903. It never seemed to cause an issue until last weeks update. The problem is that you can't get to that option in power controls when booted in safe mode.

I was finally able to boot with boot logging enabled and disable fast start up. No issues since.

Reply

Answer 2

Loner T

Level 9

59,536 points

Jul 1, 2019 5:38 PM in response to kmh0

kmh0 wrote:

I was having this same exact problem. It was due to the fast startup option that comes with Windows 10 build 1803 and 1903. It never seemed to cause an issue until last weeks update. The problem is that you can't get to that option in power controls when booted in safe mode.

The assumption that Fast Startup is beneficial on a modern system is questionable. This bug has been around for years, since W7/W8.1 days. See Boot Camp: Thunderbolt devices not recognized after Windows 8 upgrade - Apple Support for reference.

I was finally able to boot with boot logging enabled and disable fast start up. No issues since.

Nice! 👍

Reply

Answer 3

Loner T

Level 9

59,536 points

Jun 25, 2019 6:15 PM in response to brentseale

Have you tried W10 1709? Have you run a SMC/NVRAM Reset after every failed attempt at installation of Windows?

Winclone restore between two different models requires a Windows SysPrep (aka generalization), and then re-installation of BC drivers of the destination Mac. It is a non-trivial process. See https://twocanoes.com/getting-started-winclone/migrate-boot-camp-new-mac/ for reference.

Reply

Answer 4

Loner T

Level 9

59,536 points

Jun 25, 2019 6:28 PM in response to brentseale

Can you post the output of

diskutil list

diskutil apfs list

Your issue points to a bad driver, but let us first eliminate quirks of partitioning.

Reply

Answer 5

brentseale Author

Level 1

8 points

Jun 25, 2019 9:42 PM in response to brentseale

Just as a side note. I started windows in safe mode. It doesn't crash. So it must be a driver. I just don't know how to solve the problem when I only have 1 and a half minutes before I get a crash.

Reply

Answer 6

Loner T

Level 9

59,536 points

Jun 25, 2019 6:58 PM in response to brentseale

If the Windows installation fails, does it leave behind OSXRESERVED and BOOTCAMP partitions? If yes, it is worthwhile looking at them.

If the RAM is outside the Mac, we should be fine.

Reply

Answer 7

Loner T

Level 9

59,536 points

Jun 26, 2019 4:51 AM in response to brentseale

Run msconfig and enable Boot logging. Check the Boot log for the driver being loaded. You can also look at Windows Event Viewer.

Reply

Answer 8

brentseale Author

Level 1

8 points

Jun 25, 2019 6:32 PM in response to Loner T

diskutil list:

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk2 2.0 TB disk0s2

/dev/disk1 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *121.3 GB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_APFS Container disk2 121.1 GB disk1s2

/dev/disk2 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +2.1 TB disk2

Physical Stores disk0s2, disk1s2

1: APFS Volume Macintosh HD 48.7 GB disk2s1

2: APFS Volume Preboot 46.1 MB disk2s2

3: APFS Volume Recovery 509.7 MB disk2s3

4: APFS Volume VM 4.3 GB disk2s4

Reply

Answer 9

brentseale Author

Level 1

8 points

Jun 25, 2019 6:33 PM in response to brentseale

APFS Container (1 found)

|

+-- Container disk2 9EA89D64-2AC4-4200-86BA-103B35BB14B5

====================================================

APFS Container Reference: disk2 (Fusion)

Size (Capacity Ceiling): 2121312247808 B (2.1 TB)

Capacity In Use By Volumes: 63026262016 B (63.0 GB) (3.0% used)

Capacity Not Allocated: 2058285985792 B (2.1 TB) (97.0% free)

|

+-< Physical Store disk0s2 25C9511D-FBA9-49BD-8002-9604CA2F3107

| -----------------------------------------------------------

| APFS Physical Store Disk: disk0s2 (Secondary, Designated Aux Use)

| Size: 2000189177856 B (2.0 TB)

|

+-< Physical Store disk1s2 4A5C1481-DD11-47E0-BF51-7F199F66F584

| -----------------------------------------------------------

| APFS Physical Store Disk: disk1s2 (Main)

| Size: 121123069952 B (121.1 GB)

|

+-> Volume disk2s1 7907DEC3-D23D-3A51-B478-7E268EFDB287

| ---------------------------------------------------

| APFS Volume Disk (Role): disk2s1 (No specific role)

| Name: Macintosh HD (Case-insensitive)

| Mount Point: /

| Capacity Consumed: 49264574464 B (49.3 GB)

| FileVault: No

|

+-> Volume disk2s2 E870A192-16ED-4827-8CFE-339205AAF9C3

| ---------------------------------------------------

| APFS Volume Disk (Role): disk2s2 (Preboot)

| Name: Preboot (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 46067712 B (46.1 MB)

| FileVault: No

|

+-> Volume disk2s3 AFC9867B-CBB2-4072-A583-AE474DE46A9C

| ---------------------------------------------------

| APFS Volume Disk (Role): disk2s3 (Recovery)

| Name: Recovery (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 509726720 B (509.7 MB)

| FileVault: No

|

+-> Volume disk2s4 17C55604-D58C-4FAA-A8EB-2FCB9CE63552

---------------------------------------------------

APFS Volume Disk (Role): disk2s4 (VM)

Name: VM (Case-insensitive)

Mount Point: /Volumes/VM

Capacity Consumed: 4294987776 B (4.3 GB)

FileVault: No

Reply

Answer 10

brentseale Author

Level 1

8 points

Jun 25, 2019 6:54 PM in response to Loner T

I can't even get windows to install so I can't boot it into safe mode. Yes I let the BCA do the entire process. The only time I use the mouse and keyboard is during the first restart of Windows when I'm selecting which Windows (Home, Pro, etc) and partition to initiate the install. After it does that process and restarts, that's when the crashing begins.

Yes I don't have a windows partition yet. Those list shots are immediately after a fresh restore.

I'll try again and disconnect everything immediately after I select the partition to install in the windows installer.

As for the third party ram. It's currently sitting in a Tupperware container on my desk, and not in the computer. So it can no longer cause issues unless it already did it's damage to other parts of the computer that the apple hardware check failed to pick up.

Reply

Answer 11

brentseale Author

Level 1

8 points

Jun 25, 2019 9:01 PM in response to brentseale

This is my diskutil list:

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *121.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk2 121.1 GB disk0s2

/dev/disk1 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_APFS Container disk2 1.3 TB disk1s2

3: Microsoft Basic Data 719.3 GB disk1s4

/dev/disk2 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +1.4 TB disk2

Physical Stores disk0s2, disk1s2

1: APFS Volume Macintosh HD 64.6 GB disk2s1

2: APFS Volume Preboot 46.1 MB disk2s2

3: APFS Volume Recovery 509.7 MB disk2s3

4: APFS Volume VM 4.3 GB disk2s4

Reply

Answer 12

brentseale Author

Level 1

8 points

Jun 25, 2019 6:23 PM in response to Loner T

Hi LonerT,

Yes I've reset the SMC/NVRAM between each attempt.

The latest install attempt was Win10 1607. It's always the same problem.

Reply

Answer 13

Loner T

Level 9

59,536 points

Jun 25, 2019 6:43 PM in response to brentseale

There do not seem to any partitioning issues. Can you boot in Windows Safe Mode? I will assume you are allowing BC Assistant to do the entire process, without any manual intervention, unless Keyboard/Mouse interaction is requested.

Right now, you do not have a BC/Windows partition. I suggest disconnecting all external peripherals, disconnecting Ethernet once you see the Windows Installer screen for partition selection and retrying the installation. Do not forget a SMC/NVRAM Reset.

Third-party RAM is not recommended in a Mac. Some brands cause issues. Hynix and Samsung seem to the be most reliable.

Reply

Answer 14

brentseale Author

Level 1

8 points

Jun 25, 2019 8:59 PM in response to Loner T

Ok. I managed to get a lot further this time. I unplugged the ethernet, mouse and keyboard during the bit that I was getting stuck on. It went through further than before. I then had to plug in a keyboard to type in a new user profile name. I tried two apple keyboards and as soon as I would plug them in, the installation would crash and restart the computer. I then chose a different USB port and plugged in a gaming keyboard for our PC into the Mac. This bought me more time and I was able to type a name in. I unplugged it. Windows finally loaded, even got the desktop. Bootcamp drivers then started to install, but 1 minute into it, the system crashed and restarted. After a restart, Windows loads fine the desktop, but even while sitting idle for 1.5 minutes, it will crash and restart. This is the BSOD I keep getting. It's the same error I was getting during the installation.

Reply

Windows 10 installation crashing

Similar questions