You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

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

CVM Server Crash / restart in BigSur 11.2 on M1 MacBook Air

My M1 MacBook Air keeps restarting with CVMServer crashing with invalid memory access errors.


rocess: CVMServer [1054]

Path: /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/CVMServer

Identifier: CVMServer

Version: 177.22

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

Responsible: CVMServer [1054]

User ID: 0

Time Awake Since Boot: 780 seconds

Time Since Wake: 130 seconds


System Integrity Protection: enabled


Crashed Thread: 0


Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000104eb8000

Exception Note: EXC_CORPSE_NOTIFY


Termination Signal: Bus error: 10

Termination Reason: Namespace SIGNAL, Code 0xa

Terminating Process: exc handler [1054]


Posted on Feb 21, 2021 6:02 PM

Reply

Similar questions

16 replies

Feb 23, 2021 1:23 PM in response to adyav

Hello adyav,


​Thank you for using the Apple Support Communities. It's definitely important to make sure your Mac is running as expected, and we'll be happy to help. It looks like your MacBook Air M1 is restarting unexpectedly, correct?


To get a few details, how frequently is this happening?


From your post, it looks like it might be happening fairly soon after starting up. Is that right? Is it happening when you use a particular app, or does it vary?


To troubleshoot, you might try booting up into safe mode to see if you can replicate the behavior there. This will help to rule out some software causes. You'll want to use the steps in the "Apple silicon" section of this link: How to use safe mode on your Mac. Let us know how it goes.


Cheers.

Mar 9, 2021 2:56 PM in response to adyav

adyav,


Thanks for letting us know! It sounds like the issue persists in safe mode as well.


Do you have any peripherals connected to your Mac when the issue occurs, like hard drives, docks, hubs, printers, etc? If so, try disconnecting those and test; does that make a difference?


If not, updating to the latest version of macOS Big Sur is a good next step. Be sure to back up beforehand:


Back up your Mac with Time Machine


How to update the software on your Mac


If the issue persists even after updating and testing without peripherals, see if you can replicate the issue in a newly-created administrator account next. This will tell you if you have a system-wide or user-specific issue, and will help work out a path forward. Here’s how to Set up users, guests, and groups on Mac.


Best wishes.

Mar 7, 2021 4:47 PM in response to adyav

One more cash today:


rocess: CVMServer [563]

Path: /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/CVMServer

Identifier: CVMServer

Version: 177.22

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

Responsible: CVMServer [563]

User ID: 0


Date/Time: 2021-03-07 08:11:16.462 -0500

OS Version: macOS 11.2.2 (20D80)

Report Version: 12



Time Awake Since Boot: 9600 seconds

Time Since Wake: 390 seconds


System Integrity Protection: enabled


Crashed Thread: 1


Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x00000001024a8000

Exception Note: EXC_CORPSE_NOTIFY


Termination Signal: Bus error: 10

Termination Reason: Namespace SIGNAL, Code 0xa

Terminating Process: exc handler [563]


VM Regions Near 0x1024a8000:

MALLOC metadata 1024a4000-1024a8000 [ 16K] r--/rwx SM=PRV

--> VM_ALLOCATE 1024a8000-1024b8000 [ 64K] rwx/rwx SM=PRV

__TEXT 10276c000-1027e8000 [ 496K] r-x/r-x SM=COW /usr/lib/dyld


Application Specific Information:

dyld3 mode


Thread 0:

0 libsystem_kernel.dylib 0x0000000194107d20 __sigsuspend_nocancel + 8

1 libdispatch.dylib 0x0000000193f9fd70 _dispatch_sigsuspend + 48

2 libdispatch.dylib 0x0000000193f9fd40 _dispatch_sig_thread + 60


Thread 1 Crashed:

0 libsystem_platform.dylib 0x00000001941819cc _platform_memmove + 156

1 CVMServer 0x0000000102447364 cvmsServerElementBuild + 2920

2 CVMServer 0x0000000102449904 __cvmsServInitializeConnection_block_invoke + 2372

3 libxpc.dylib 0x0000000193ea5958 _xpc_connection_call_event_handler + 164

4 libxpc.dylib 0x0000000193ea4460 _xpc_connection_mach_event + 960

5 libdispatch.dylib 0x0000000193f8d4ec _dispatch_client_callout4 + 20

6 libdispatch.dylib 0x0000000193fa7610 _dispatch_mach_msg_invoke + 472

7 libdispatch.dylib 0x0000000193f94648 _dispatch_lane_serial_drain + 272

8 libdispatch.dylib 0x0000000193fa8320 _dispatch_mach_invoke + 468

9 libdispatch.dylib 0x0000000193f94648 _dispatch_lane_serial_drain + 272

10 libdispatch.dylib 0x0000000193f952cc _dispatch_lane_invoke + 408

11 libdispatch.dylib 0x0000000193f9f3fc _dispatch_workloop_worker_thread + 708

12 libsystem_pthread.dylib 0x0000000194136060 _pthread_wqthread + 276

13 libsystem_pthread.dylib 0x0000000194134d94 start_wqthread + 8


Mar 7, 2021 4:51 PM in response to ryane77

This is not specific to an app. And not just after a startup either. Its completely random. I got a crash just now as well. All I had done was installed jupyter notebook within my VS code ( M1 Compatible Version ). I got a purple flash on the screen and the notebook restarted. Here is the summary.


rocess: CVMServer [563]

Path: /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/CVMServer

Identifier: CVMServer

Version: 177.22

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

Responsible: CVMServer [563]

User ID: 0


Date/Time: 2021-03-07 08:11:16.462 -0500

OS Version: macOS 11.2.2 (20D80)

Report Version: 12


Time Awake Since Boot: 9600 seconds

Time Since Wake: 390 seconds


System Integrity Protection: enabled


Crashed Thread: 1


Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x00000001024a8000

Exception Note: EXC_CORPSE_NOTIFY


Termination Signal: Bus error: 10

Termination Reason: Namespace SIGNAL, Code 0xa

Terminating Process: exc handler [563]


VM Regions Near 0x1024a8000:

MALLOC metadata 1024a4000-1024a8000 [ 16K] r--/rwx SM=PRV

--> VM_ALLOCATE 1024a8000-1024b8000 [ 64K] rwx/rwx SM=PRV

__TEXT 10276c000-1027e8000 [ 496K] r-x/r-x SM=COW /usr/lib/dyld


Application Specific Information:

dyld3 mode


Thread 0:

0 libsystem_kernel.dylib 0x0000000194107d20 __sigsuspend_nocancel + 8

1 libdispatch.dylib 0x0000000193f9fd70 _dispatch_sigsuspend + 48

2 libdispatch.dylib 0x0000000193f9fd40 _dispatch_sig_thread + 60


Thread 1 Crashed:

0 libsystem_platform.dylib 0x00000001941819cc _platform_memmove + 156

1 CVMServer 0x0000000102447364 cvmsServerElementBuild + 2920

2 CVMServer 0x0000000102449904 __cvmsServInitializeConnection_block_invoke + 2372

3 libxpc.dylib 0x0000000193ea5958 _xpc_connection_call_event_handler + 164

4 libxpc.dylib 0x0000000193ea4460 _xpc_connection_mach_event + 960

5 libdispatch.dylib 0x0000000193f8d4ec _dispatch_client_callout4 + 20

6 libdispatch.dylib 0x0000000193fa7610 _dispatch_mach_msg_invoke + 472

7 libdispatch.dylib 0x0000000193f94648 _dispatch_lane_serial_drain + 272

8 libdispatch.dylib 0x0000000193fa8320 _dispatch_mach_invoke + 468

9 libdispatch.dylib 0x0000000193f94648 _dispatch_lane_serial_drain + 272

10 libdispatch.dylib 0x0000000193f952cc _dispatch_lane_invoke + 408

11 libdispatch.dylib 0x0000000193f9f3fc _dispatch_workloop_worker_thread + 708

12 libsystem_pthread.dylib 0x0000000194136060 _pthread_wqthread + 276

13 libsystem_pthread.dylib 0x0000000194134d94 start_wqthread + 8


Mar 9, 2021 3:52 PM in response to adyav

adyav,


To double-check, it happens both with and without the external monitor connected and you don’t have any other peripherals or devices connected, correct?


Also, were you able to test it out in a new administrator account yet? It sounds like it may take a bit of time to test and determine if the issue happens there or not based on how long you mentioned it took in safe mode; let us know what you find. This information will help work out your next best steps.


Take care.

Mar 10, 2021 5:36 AM in response to ryane77

Same here on an mac mini m1: I get 2 to 3 a day.


Path: /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/CVMServer

Identifier: CVMServer

Version: 177.22

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

Responsible: CVMServer [684]

User ID: 0


Date/Time: 2021-03-10 09:52:33.503 +0100

OS Version: macOS 11.2.2 (20D80)

Report Version: 12

Anonymous UUID: 8F34A599-9641-E156-C2EE-D0F761D70E2D



Time Awake Since Boot: 180 seconds


System Integrity Protection: enabled


Crashed Thread: 0


Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000102c98000

Exception Note: EXC_CORPSE_NOTIFY


Termination Signal: Bus error: 10

Termination Reason: Namespace SIGNAL, Code 0xa

Terminating Process: exc handler [684]


VM Regions Near 0x102c98000:

__LINKEDIT 102c94000-102c98000 [ 16K] r--/r-- SM=NUL /usr/lib/dyld

--> VM_ALLOCATE 102c98000-102ca8000 [ 64K] rwx/rwx SM=PRV

Dispatch continuations 103000000-107000000 [ 64.0M] rw-/rwx SM=PRV


Application Specific Information:

dyld3 mode


Thread 0 Crashed:

0 libsystem_platform.dylib 0x0000000197c559cc _platform_memmove + 156

1 CVMServer 0x0000000102b33364 cvmsServerElementBuild + 2920

2 CVMServer 0x0000000102b35904 __cvmsServInitializeConnection_block_invoke + 2372

3 libxpc.dylib 0x0000000197979958 _xpc_connection_call_event_handler + 164

4 libxpc.dylib 0x0000000197978460 _xpc_connection_mach_event + 960

5 libdispatch.dylib 0x0000000197a614ec _dispatch_client_callout4 + 20

6 libdispatch.dylib 0x0000000197a7b610 _dispatch_mach_msg_invoke + 472

7 libdispatch.dylib 0x0000000197a68648 _dispatch_lane_serial_drain + 272

8 libdispatch.dylib 0x0000000197a7c320 _dispatch_mach_invoke + 468

9 libdispatch.dylib 0x0000000197a68648 _dispatch_lane_serial_drain + 272

10 libdispatch.dylib 0x0000000197a692cc _dispatch_lane_invoke + 408

11 libdispatch.dylib 0x0000000197a733fc _dispatch_workloop_worker_thread + 708

12 libsystem_pthread.dylib 0x0000000197c0a060 _pthread_wqthread + 276

13 libsystem_pthread.dylib 0x0000000197c08d94 start_wqthread + 8


Thread 1:

0 libsystem_kernel.dylib 0x0000000197bdbd20 __sigsuspend_nocancel + 8

1 libdispatch.dylib 0x0000000197a73d70 _dispatch_sigsuspend + 48

2 libdispatch.dylib 0x0000000197a73d40 _dispatch_sig_thread + 60


Thread 2:

0 libsystem_pthread.dylib 0x0000000197c08d8c start_wqthread + 0


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

x0: 0x0000000102c98000 x1: 0x0000000107000040 x2: 0x0000000000001fe0 x3: 0x0000000102c98020

x4: 0x0000000000000003 x5: 0x0000000000000020 x6: 0x0000000000000000 x7: 0x0000000000000ef0

x8: 0xf459c97d32fc001c x9: 0xf459c97d32fc001c x10: 0x0000000000000018 x11: 0x000000000000e000

x12: 0x0000000000a20004 x13: 0x0000000001a20004 x14: 0x000000000000001e x15: 0x000000000000c6ba

x16: 0xba4e800197c55930 x17: 0x0000000102b381e0 x18: 0x0000000000000000 x19: 0x000000012760ebb0

x20: 0x0000000000000000 x21: 0x0000000130804870 x22: 0x0000000130904270 x23: 0x0000000000002000

x24: 0x000000012760d768 x25: 0x000000012760d700 x26: 0x0000000000000000 x27: 0x0000000102b3c010

x28: 0x0000000000000001 fp: 0x000000016d3e64d0 lr: 0x0000000102b33364

sp: 0x000000016d3e63c0 pc: 0x0000000197c559cc cpsr: 0x80001000

far: 0x0000000102c98000 esr: 0x9200004f




Mar 15, 2021 2:01 AM in response to adyav

I've just started experiencing these issues as of today (8GB M1 Mac Mini). The only thing that changed is that I added an external drive (G-Technology 2TB USB-C). I have been trying to copy an old external drive (that had FW800 connector for high speed *sad face*) onto this new USB-C drive. I was experiencing crashes transferring from old-drive-to-USBC-drive OR from HDD-to-USBC drive. NOT old-drive-to-HDD. I have had four full reboot crashes with the same Exception Type BUT Exception Code "...100b94000".


By playing around with Disk Utility I discovered that there are two file systems for OSX (I am a Mac novice). So I used Disk Utility to change the USBC drive file format HFS+ to APFS. I am now 15% into a file transfer (old-drive-to-USBC-drive) with no issues touch wood. I was also trying to copy files to the USBC drive from HDD which were getting other errors. So I am wondering if there is a correlation between the file structure and this error?


You note that you are using an external drive. Is it using HFS+? Perhaps try un-mounting it for a day?

Apr 12, 2021 11:05 PM in response to Zigzag69

I get more or less one crash a day, if I use it more, I get multiple reboot a day. It is unusable for me.

Last one:


Process:               CVMServer [773]
Path:                  /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/CVMServer
Identifier:            CVMServer
Version:               177.22
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
Responsible:           CVMServer [773]
User ID:               0

Date/Time:             2021-04-13 06:58:23.417 +0200
OS Version:            macOS 11.2.3 (20D91)
Report Version:        12
Anonymous UUID:        8F34A599-9641-E156-C2EE-D0F761D70E2D


Time Awake Since Boot: 300 seconds

System Integrity Protection: enabled

Crashed Thread:        1

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       KERN_PROTECTION_FAILURE at 0x00000001048ec000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Bus error: 10
Termination Reason:    Namespace SIGNAL, Code 0xa
Terminating Process:   exc handler [773]

VM Regions Near 0x1048ec000:
    MALLOC metadata             1048e8000-1048ec000    [   16K] r--/rwx SM=PRV  
--> VM_ALLOCATE                 1048ec000-1048fc000    [   64K] rwx/rwx SM=PRV  
    __TEXT                      104990000-104a0c000    [  496K] r-x/r-x SM=COW  /usr/lib/dyld

Application Specific Information:
dyld3 mode

Thread 0:
0   libsystem_kernel.dylib        	0x00000001a2bf7d20 __sigsuspend_nocancel + 8
1   libdispatch.dylib             	0x00000001a2a8fd70 _dispatch_sigsuspend + 48
2   libdispatch.dylib             	0x00000001a2a8fd40 _dispatch_sig_thread + 60

Thread 1 Crashed:
0   libsystem_platform.dylib      	0x00000001a2c719cc _platform_memmove + 156
1   CVMServer                     	0x000000010488b364 cvmsServerElementBuild + 2920
2   CVMServer                     	0x000000010488d904 __cvmsServInitializeConnection_block_invoke + 2372
3   libxpc.dylib                  	0x00000001a2995958 _xpc_connection_call_event_handler + 164
4   libxpc.dylib                  	0x00000001a2994460 _xpc_connection_mach_event + 960
5   libdispatch.dylib             	0x00000001a2a7d4ec _dispatch_client_callout4 + 20
6   libdispatch.dylib             	0x00000001a2a97610 _dispatch_mach_msg_invoke + 472
7   libdispatch.dylib             	0x00000001a2a84648 _dispatch_lane_serial_drain + 272
8   libdispatch.dylib             	0x00000001a2a98320 _dispatch_mach_invoke + 468
9   libdispatch.dylib             	0x00000001a2a84648 _dispatch_lane_serial_drain + 272
10  libdispatch.dylib             	0x00000001a2a852cc _dispatch_lane_invoke + 408
11  libdispatch.dylib             	0x00000001a2a8f3fc _dispatch_workloop_worker_thread + 708
12  libsystem_pthread.dylib       	0x00000001a2c26060 _pthread_wqthread + 276
13  libsystem_pthread.dylib       	0x00000001a2c24d94 start_wqthread + 8

Thread 2:
0   libsystem_pthread.dylib       	0x00000001a2c24d8c start_wqthread + 0

Thread 3:
0   libsystem_pthread.dylib       	0x00000001a2c24d8c start_wqthread + 0

Thread 1 crashed with ARM Thread State (64-bit):
    x0: 0x00000001048ec000   x1: 0x0000000109000040   x2: 0x0000000000001fe0   x3: 0x00000001048ec020
    x4: 0x0000000000000003   x5: 0x0000000000000020   x6: 0x0000000000000000   x7: 0x0000000000000ef0
    x8: 0xe36d9c127a110093   x9: 0xe36d9c127a110093  x10: 0x0000000000000018  x11: 0x000000000000e000
   x12: 0x000000000010040b  x13: 0x00000000ffffffff  x14: 0x000000003e23c720  x15: 0x00000000000026e6
   x16: 0x0d7e0001a2c71930  x17: 0x00000001048901e0  x18: 0x0000000000000000  x19: 0x000000012f2055e0
   x20: 0x0000000000000000  x21: 0x000000012f1045a0  x22: 0x000000012f304270  x23: 0x0000000000002000
   x24: 0x000000012f2040e8  x25: 0x000000012f204080  x26: 0x0000000000000000  x27: 0x0000000104894010
   x28: 0x0000000000000001   fp: 0x000000016b68e4d0   lr: 0x000000010488b364
    sp: 0x000000016b68e3c0   pc: 0x00000001a2c719cc cpsr: 0x80001000
   far: 0x0000000000000000  esr: 0x00000000



Binary Images:


Apr 21, 2021 6:50 AM in response to adyav

Just got a Mac Book Air Serial number C02FK083Q6LR

Got exactly the same problem.

Machine justs crashes. twice a day.


Help!


----- Console Report below ----


Process: CVMServer [515]

Path: /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/CVMServer

Identifier: CVMServer

Version: 177.22

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

Responsible: CVMServer [515]

User ID: 0


Date/Time: 2021-04-21 14:09:59.628 +0100

OS Version: macOS 11.2.3 (20D91)

Report Version: 12

Anonymous UUID: 027D1B84-7C7F-CD92-1441-AF65E0E5588D


CVM Server Crash / restart in BigSur 11.2 on M1 MacBook Air

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