Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Bootcamp crashes after launch

Since upgrading to MacOS HighSierra Bootcamp do not launch, it crashes after the first screen.


Process: Boot Camp Assistant [572]

Path: /Applications/Utilities/Boot Camp Assistant.app/Contents/MacOS/Boot Camp Assistant

Identifier: com.apple.bootcampassistant

Version: 6.1.0 (6067.1.3)

Build Info: BootCampAssistant-6067001003000000~1

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Boot Camp Assistant [572]

User ID: 502



Date/Time: 2017-10-14 11:28:35.924 +0200

OS Version: Mac OS X 10.13 (17A405)

Report Version: 12

Anonymous UUID: 60B1B825-ACCE-520D-DB2F-0D20A1F2FC1D





Time Awake Since Boot: 430 seconds



System Integrity Protection: enabled



Crashed Thread: 0 Dispatch queue: com.apple.main-thread



Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00001700830ebec8

Exception Note: EXC_CORPSE_NOTIFY



Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [0]



VM Regions Near 0x1700830ebec8:

__LINKEDIT 00000001145f2000-000000011460d000 [ 108K] r--/rwx SM=COW /usr/lib/dyld

-->

MALLOC_NANO 0000600000000000-0000600000400000 [ 4096K] rw-/rwx SM=PRV



Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 libobjc.A.dylib 0x00007fff54629174 objc_release + 36

1 com.apple.CoreFoundation 0x00007fff2dcc5dae cow_cleanup + 126

2 com.apple.CoreFoundation 0x00007fff2dbc927d -[__NSArrayM dealloc] + 45

3 libobjc.A.dylib 0x00007fff5462a042 (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 812

4 com.apple.CoreFoundation 0x00007fff2dbe04f6 _CFAutoreleasePoolPop + 22

5 com.apple.Foundation 0x00007fff2fcdae75 -[NSAutoreleasePool drain] + 144

6 com.apple.AppKit 0x00007fff2b226865 -[NSApplication run] + 860

7 com.apple.AppKit 0x00007fff2b1f59a6 NSApplicationMain + 804

8 libdyld.dylib 0x00007fff55221144 0x7fff55220000 + 4420



Thread 1:

0 libsystem_kernel.dylib 0x00007fff553716da __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff554ab26f _pthread_wqthread + 1552

2 libsystem_pthread.dylib 0x00007fff554aac4d start_wqthread + 13



Thread 2:

0 libsystem_kernel.dylib 0x00007fff553716da __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff554ab26f _pthread_wqthread + 1552

2 libsystem_pthread.dylib 0x00007fff554aac4d start_wqthread + 13



Thread 3:

0 libsystem_kernel.dylib 0x00007fff553716da __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff554ab06a _pthread_wqthread + 1035

2 libsystem_pthread.dylib 0x00007fff554aac4d start_wqthread + 13



Thread 4:

0 libsystem_kernel.dylib 0x00007fff553716da __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff554ab26f _pthread_wqthread + 1552

2 libsystem_pthread.dylib 0x00007fff554aac4d start_wqthread + 13



Thread 5:

0 libsystem_pthread.dylib 0x00007fff554aac40 start_wqthread + 0

1 ??? 0x000070000e246b60 0 + 123145539578720



Thread 6:

0 libsystem_pthread.dylib 0x00007fff554aac40 start_wqthread + 0



Thread 7:

0 libsystem_kernel.dylib 0x00007fff553716da __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff554ab26f _pthread_wqthread + 1552

2 libsystem_pthread.dylib 0x00007fff554aac4d start_wqthread + 13



Thread 8:

0 libsystem_pthread.dylib 0x00007fff554aac40 start_wqthread + 0

1 ??? 0x0002000000030002 0 + 562949953617922



Thread 9:: com.apple.NSEventThread

0 libsystem_kernel.dylib 0x00007fff55367e76 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff55367390 mach_msg + 60

2 com.apple.CoreFoundation 0x00007fff2dc20c45 __CFRunLoopServiceMachPort + 341

3 com.apple.CoreFoundation 0x00007fff2dc1ff97 __CFRunLoopRun + 1783

4 com.apple.CoreFoundation 0x00007fff2dc1f607 CFRunLoopRunSpecific + 487

5 com.apple.AppKit 0x00007fff2b36f1f1 _NSEventThread + 184

6 libsystem_pthread.dylib 0x00007fff554ab6c1 _pthread_body + 340

7 libsystem_pthread.dylib 0x00007fff554ab56d _pthread_start + 377

8 libsystem_pthread.dylib 0x00007fff554aac5d thread_start + 13



Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x00001700830ebea8 rbx: 0x000060800008da70 rcx: 0x0000000000000002 rdx: 0x0000000000000010

rdi: 0x000060800005e8d0 rsi: 0x0000000000000001 rbp: 0x00007ffee4d2a520 rsp: 0x00007ffee4d2a520

r8: 0x000060800005caa0 r9: 0x00007fff88051390 r10: 0x00007fff88046af0 r11: 0x00007fb2db0087a0

r12: 0x0000000000000002 r13: 0x0000604000058cf0 r14: 0x000060800008da70 r15: 0x0000000000000000

rip: 0x00007fff54629174 rfl: 0x0000000000010202 cr2: 0x00001700830ebec8


Logical CPU: 0

Error Code: 0x00000004

Trap Number: 14





Model: Macmini6,2, BootROM MM61.010B.B00, 4 processors, Intel Core i7, 2,3 GHz, 16 GB, SMC 2.8f1

Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0198, 0x393955353432382D3036332E4130304C4620

Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0198, 0x393955353432382D3036332E4130304C4620

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x10E), Broadcom BCM43xx 1.0 (7.21.190.13.1a3)

Bluetooth: Version 6.0.0f7, 3 services, 27 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

Network Service: Wi-Fi, AirPort, en1

Serial ATA Device: Samsung SSD 850 EVO 500GB, 500,11 GB

USB Device: USB 2.0 Bus

USB Device: Hub

USB Device: USB 2.0 Bus

USB Device: Hub

USB Device: Hub

USB Device: IR Receiver

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

USB Device: USB 3.0 Bus

USB Device: ASMT1051

USB Device: Hub

USB Device: Hub

USB Device: USB3.0-CRW

USB Device: Hub

USB Device: Hub

USB Device: Newer Technology

Thunderbolt Bus: Mac mini, Apple Inc., 23.4

Mac mini, macOS High Sierra (10.13)

Posted on Oct 14, 2017 2:38 AM

Reply
23 replies

Oct 14, 2017 9:21 AM in response to jbburf

jbburf wrote:


I'm seeing the same thing. I am trying to set up a USB drive with Windows 10 on it via Boot Camp Assistant. I launch the assistant and it quits immediately upon clicking "Continue" on the attached screenshot:


User uploaded file


Strangely, the third checkbox is disabled some of the time and enabled and checked at other times.

Do you have any external storage/hubs connected to your Mac? What is the year/model of your Mac? You should start a new discussion to avoid confusion.

Oct 14, 2017 10:01 AM in response to Micha B.

Micha B. wrote:


4. I removed my external USB HD with TimeMachine backup and then Bootcam starts as expected.

This is what I had suggested earlier. 😉

Disconnect all external devices, except Monitor/Keyboard/Mouse, run SMC and NVRAM Reset and check if you can click on Continue.

Micha B. wrote:


But: Disable SIP could noot be the soulution, I think.

It is a debugging tool, not a solution, to check if there are permission or access issues.


Are you able to install Windows?

Oct 14, 2017 10:45 AM in response to Loner T

The issue is not related to SIP. It occurs only with my connected external USB HD they contains two partions: one for files (APFS) and one for Time Machine (Mac OS Extended Journaled). My internal SSD was upgraded to APFS while installing OS X 10.13. The same configuration (without APFS) worked fine before with OS X 10.12.

Oct 14, 2017 12:02 PM in response to Micha B.

Micha B. wrote:


The issue is not related to SIP. It occurs only with my connected external USB HD they contains two partions: one for files (APFS) and one for Time Machine (Mac OS Extended Journaled).

HS is much more intolerant of external storage and Sierra and older macOS versions are. 2010 Macs allow a USB to be connected, even though they do not support USB installation.

Micha B. wrote:


My internal SSD was upgraded to APFS while installing OS X 10.13. The same configuration (without APFS) worked fine before with OS X 10.12.

The APFS upgrade is also problematic on most Macs. You may run into issues while partitioning your internal APFS disk container. You have not reached that stage yet. In many cases, users have had to use a TM backup to erase/restore and then partition for BC/Windows.

Oct 15, 2017 1:56 AM in response to Loner T

"HS is much more intolerant of external storage and Sierra and older macOS versions are. 2010 Macs allow a USB to be connected, even though they do not support USB installation."


I want to use my internal drive for Windows partition, not an external USB drive.


"The APFS upgrade is also problematic on most Macs. You may run into issues while partitioning your internal APFS disk container. You have not reached that stage yet. "


While installing OS X 10.13 nobody asked me 'Do you want update your file system?'. The installation did this automatically. If you think that APFS is problematic in combination with BootCamp then this is a bug for me or Apple did not tested it enough.

Oct 15, 2017 6:31 AM in response to Micha B.

Micha B. wrote:


"HS is much more intolerant of external storage and Sierra and older macOS versions are. 2010 Macs allow a USB to be connected, even though they do not support USB installation."


I want to use my internal drive for Windows partition, not an external USB drive.

For your specific model, since it has not built-in Optical drive, there are two methods of using a Windows Installer, an external Apple Superdrive or a USB2 Flash drive (8+Gb) which is erased/formatted by BCA to build a bootable USB Installer. Do not use external USB HDDs instead of a flash drive, otherwise you will see more issues.


Micha B. wrote:



"The APFS upgrade is also problematic on most Macs. You may run into issues while partitioning your internal APFS disk container. You have not reached that stage yet. "


While installing OS X 10.13 nobody asked me 'Do you want update your file system?'. The installation did this automatically. If you think that APFS is problematic in combination with BootCamp then this is a bug for me or Apple did not tested it enough.

See Using the macOS High Sierra OS installer’s startosinstall tool to avoid APFS conversion | Der Flounder .

Bootcamp crashes after launch

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