Just got the ne MBP with the M1 chip and it is constantly crashing when I the computer hooked up to a Samsung external monitor. It happens around 1-5 times a week ususally when I'm on Word for too long. What can I do? I'm on the latest software update.
Panic Reports are stored at:
/Library/Logs/DiagnosticReports
If you copy and paste that string into:
Finder > Go menu > Go to Folder
it will take you to where those reports are stored.
They are named with Date&Time and end in .panic
If you find one, please post the entire report here, by using the “additional text” Icon in the reply footer (looks like a paper with writing).
Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.
There are three quick take-aways from any panic report.
1) The panic-reason,
2) the extensions present at the "scene of the crime", and
3) the BSD process in which the problem occurred.
One more item that is important is the names of any third-party Extensions you have added. They are shown FIRST in the extensions loaded section
————
Take look at your other reports. What you are trying to determine is whether there is a TREND.
Case A) There is a trend: This same panic occurs in each case, with the same extensions present, in the same BSD process. A trend can indicate corrupted software or a Hardware problem that can be tracked down and solved.
Case B) There is a decided NON-Trend. The panics occur "all over the Map" for different panic reasons and in different BSD processes, with different extensions present.
A Non-trend suggests you may have RAM memory problems. MacOS slightly randomizes the load point of key routines on each startup, as a hedge against fixed-address attacks. This causes a marginal memory cell to move into different routines each time your Mac starts up.
If the above is just "word-salad" to you, just ask and Readers can explain a bit more.
Panic Reports are stored at:
/Library/Logs/DiagnosticReports
If you copy and paste that string into:
Finder > Go menu > Go to Folder
it will take you to where those reports are stored.
They are named with Date&Time and end in .panic
If you find one, please post the entire report here, by using the “additional text” Icon in the reply footer (looks like a paper with writing).
Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.
There are three quick take-aways from any panic report.
1) The panic-reason,
2) the extensions present at the "scene of the crime", and
3) the BSD process in which the problem occurred.
One more item that is important is the names of any third-party Extensions you have added. They are shown FIRST in the extensions loaded section
————
Take look at your other reports. What you are trying to determine is whether there is a TREND.
Case A) There is a trend: This same panic occurs in each case, with the same extensions present, in the same BSD process. A trend can indicate corrupted software or a Hardware problem that can be tracked down and solved.
Case B) There is a decided NON-Trend. The panics occur "all over the Map" for different panic reasons and in different BSD processes, with different extensions present.
A Non-trend suggests you may have RAM memory problems. MacOS slightly randomizes the load point of key routines on each startup, as a hedge against fixed-address attacks. This causes a marginal memory cell to move into different routines each time your Mac starts up.
If the above is just "word-salad" to you, just ask and Readers can explain a bit more.
I was able to locate the log but none of the files end with .panic. Instead I went to app > console > crash report.
This is from the most recent crash yesterday:
Process: CVMServer [617]
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 [617]
User ID: 0
Date/Time: 2021-04-13 15:00:45.649 -0700
OS Version: macOS 11.2.3 (20D91)
Report Version: 12
Anonymous UUID: 521F5AE6-06A1-9F60-F945-680D52A9935B
Sleep/Wake UUID: B86CD106-6C44-4534-BFF9-BCC5022B3D72
Time Awake Since Boot: 14000 seconds
Time Since Wake: 4500 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000100bc4000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Bus error: 10
Termination Reason: Namespace SIGNAL, Code 0xa
Terminating Process: exc handler [617]
VM Regions Near 0x100bc4000:
MALLOC metadata 100bc0000-100bc4000 [ 16K] r--/rwx SM=PRV
--> VM_ALLOCATE 100bc4000-100bd4000 [ 64K] rwx/rwx SM=PRV
__TEXT 100d58000-100dd4000 [ 496K] r-x/r-x SM=COW /usr/lib/dyld
Application Specific Information:
dyld3 mode
Thread 0 Crashed:
0 libsystem_platform.dylib 0x000000019d5199cc _platform_memmove + 156
1 CVMServer 0x0000000100b63364 cvmsServerElementBuild + 2920
2 CVMServer 0x0000000100b65904 __cvmsServInitializeConnection_block_invoke + 2372
3 libxpc.dylib 0x000000019d23d958 _xpc_connection_call_event_handler + 164
4 libxpc.dylib 0x000000019d23c460 _xpc_connection_mach_event + 960
5 libdispatch.dylib 0x000000019d3254ec _dispatch_client_callout4 + 20
6 libdispatch.dylib 0x000000019d33f610 _dispatch_mach_msg_invoke + 472
7 libdispatch.dylib 0x000000019d32c648 _dispatch_lane_serial_drain + 272
8 libdispatch.dylib 0x000000019d340320 _dispatch_mach_invoke + 468
9 libdispatch.dylib 0x000000019d32c648 _dispatch_lane_serial_drain + 272
10 libdispatch.dylib 0x000000019d32d2cc _dispatch_lane_invoke + 408
11 libdispatch.dylib 0x000000019d3373fc _dispatch_workloop_worker_thread + 708
12 libsystem_pthread.dylib 0x000000019d4ce060 _pthread_wqthread + 276
13 libsystem_pthread.dylib 0x000000019d4ccd94 start_wqthread + 8
Thread 1:
0 libsystem_kernel.dylib 0x000000019d49fd20 __sigsuspend_nocancel + 8
1 libdispatch.dylib 0x000000019d337d70 _dispatch_sigsuspend + 48
2 libdispatch.dylib 0x000000019d337d40 _dispatch_sig_thread + 60
Thread 2:
0 libsystem_pthread.dylib 0x000000019d4ccd8c start_wqthread + 0
Thread 3:
0 libsystem_pthread.dylib 0x000000019d4ccd8c start_wqthread + 0
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000100bc4000 x1: 0x0000000105000040 x2: 0x0000000000001fe0 x3: 0x0000000100bc4020
x4: 0x0000000000000003 x5: 0x0000000000000020 x6: 0x0000000000000000 x7: 0x00000000000009b0
x8: 0x5b3dacef445e008f x9: 0x5b3dacef445e008f x10: 0x0000000000000018 x11: 0x000000000000e000
x12: 0x0000000000050081 x13: 0x00000000ffffffff x14: 0x000000002c9985bb x15: 0x000000000000894e
x16: 0xda6480019d519930 x17: 0x0000000100b681e0 x18: 0x0000000000000000 x19: 0x0000000140805480
x20: 0x0000000000000000 x21: 0x000000014760e820 x22: 0x0000000140805be0 x23: 0x0000000000002000
x24: 0x0000000140805878 x25: 0x0000000140805810 x26: 0x0000000000000000 x27: 0x0000000100b6c010
x28: 0x0000000000000001 fp: 0x000000016f32a4d0 lr: 0x0000000100b63364
sp: 0x000000016f32a3c0 pc: 0x000000019d5199cc cpsr: 0x80001000
far: 0x0000000000000000 esr: 0x00000000
Binary Images:
0x100b5c000 - 0x100b67fff CVMServer (177.22) <66F6725C-8F62-3BC2-934F-E59C45D18C6E> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/CVMServer
0x100d58000 - 0x100dd3fff dyld (832.7.3) <4AB185B3-DC20-3C03-A193-67C0E6C589D7> /usr/lib/dyld
0x19d22e000 - 0x19d22ffff libsystem_blocks.dylib (78) <9B6D4883-03E9-3785-851E-EA79FA64ADC1> /usr/lib/system/libsystem_blocks.dylib
0x19d230000 - 0x19d267fff libxpc.dylib (2038.80.3) <BD0DFD42-0DC3-3F3D-9C04-5A2B3D93794D> /usr/lib/system/libxpc.dylib
If the above is too complex, you could run Etrecheck, a "discovery" Utility.
Launch it, change its preferences to "Allow full disk access" then say GO, it will generate a report with an appended digest of problem reports at the end. That report can be posted back in a reply on the forums:
Using EtreCheck to Troubleshoot Potential… - Apple Community
.
Hello bwang34,
Thanks for reaching out in Apple Support Communities. We understand that you're having trouble with your Mac. It looks like the Mac is crashing, when you connect a Samsung external monitor. We're happy to help. Are you using the right adapter to connect the external monitor? This can help us to narrow down the cause of this issue. Have you checked to make sure your external monitor is compatible with your Mac?
Check out the following support articles:
Use external monitors with your Mac
Identify the ports on your Mac
Adapters for the Thunderbolt 3 or USB-C port on your Mac or iPad Pro
Get help with video issues on external displays connected to your Mac
Cheers!
Not yet. you still could have a wildly different problem.
Use Apple Diagnostics to test your Mac - Apple Support
.
.
Did you run diagnostics under the Exact conditions specified (power adapter connected, all possible peripherals disconnected)?
If not, you can not draw any conclusions.
Thanks for bringing this up. I have the exact problem with the new MBA. The crash happens when I am working on Word (2016)..especially when working for a long time. This does not seem to happen when I am connected to my office external monitor (Dell) using an HDMI adaptor, but crashes when using my home monitor (BenQ) using a VGA adaptor. Both thunderbolt adaptors are Belkin.
yemmae--
please start a new discussion if you would like assistance. This one is already crowded with information specific to the failures experienced by bwang34, and despite very similar symptoms, is unlikely to be caused by the exact same failure.
In your new discussion, please provide many more specific details, such as any panic reports or Etrecheck reports you have produced.
kernel protection failure and Bus error do not bode well for the health of your Mac.
Be sure to add "run the diagnostic" to your to do list.
I ran the diagnostic and it said that it could be a power adapter issue since it wasn't tested (PPP007) or a trackpad issue (NDR005 , NDR 006). Both seem unlikely and irrelevant to the issue I am experiencing. Any advice? Thanks.
My monitor is compatible and I'm using the correct thunderbolt adapter.
Could you elaborate? I purchased this computer only a couple of months ago and i'ts been doing this ever since. Should I bring it in to Apple?
MBP M1 constantly crashes when hooked up an external monitor?
