kernel panic – What is causing my Mac Studio window server and entire system crash every day all year with 8K screen?

I’ve been having same the crash on my Mac Studio numerous times every day since first installing macOS Sonoma about a month after it was first released last fall.

I’m using a Samsung NEO QLED 8K TV as the monitor.

It often happens right when I’m in the middle of a data backup or upload after I walk away from the computer. It never happens when I am actually typing on the computer or moving the mouse, but randomly anytime after that. Sometimes a minute after I walk away. Sometimes an hour. I have tried all sleep and power settings, screensavers, etc.

At first I expected Apple to fix it in the point release, because I have clicked report every time, but it’s never been fixed.

I’ve used the same monitor since the beginning of August 2023, and never had this crash for several months until the first day I installed macOS Sonoma, and have had it every day since then when my computer has been used more than a trivial amount.

Is anyone else seeing this?

Apple is not doing anything about it even though I have reported it every day to them with the automatic Report button.

It’s obviously not caused by the monitor since the same monitor never caused the crash anytime until the day I installed Sonoma.

But it could be related to the monitor, like a windows server bug when trying to drive 8K to the screen. It only happens while I’m not typing or moving the mouse, though.

SAMSUNG:
  Resolution:   7680 x 4320 (4320p/8K UHD 2 - 8K Ultra High Definition)
  UI Looks like:    3840 x 2160 @ 60.00Hz
  Main Display: Yes
  Mirror:   Off
  Online:   Yes
  Rotation: Supported
  Automatically Adjust Brightness:  No
  Television:   Yes

Mac Studio
2023
Chip Apple M2 Max
Memory
32 GB
Startup disk
Macintosh HD
Serial number
G4...
macOS Sonoma 14.6.1
More Info..
Regulatory Certification
TM and © 1983-2024 Apple Inc.

Your computer was restarted because of a problem.
This report will be sent automatically to Apple.
› Comments
Problem Details and System Configuration
panic(cpu 3 caller Oxfffffe00271922dc): Kernel data abort. at pc Oxfffffe0027eaa414, 1r 0xa5917e0027eaa40c (saved state:
Oxfffffe73cf1bb360)
0x0000000000000027 ×1:
0х0000000000000000
Oxfffffe00253cfdd0 x5:
0X0000000000000000
0x0000000000000000 ×9:
Oxfffffe29c865720
х12: 0x0000020000000000 x13:
0x0000000000000000
x16: 0xfffffe00269a4e40 x17:
0x000000000000ae56
x20: 0xfffffe202ed46000 x21:
0X0000000000000000
x24: 0xfffffe24f3b0cc0 x25:
0x0000000000000000
x28: 0xfffffe002a117000 fp:
Oxfffffe73cf1bb730
Oxfffffe0027eaa414 cpsr: 0x60401208 x2:
0х0000000000000000
х6:
0X0000000000000000
x10: 0x0000000000000002 x14:
0x0000000000000000
х18:
0x0000000000000000 x22:
0x0000000000000001
х26: 0x0000000000000000
1r:
0xa5917e0027eaa40c
esr: 0x96000006
x3:
00000000000000
X7 :
0x00000000ca6e000e
x11: 0x0000000000000000
x15: 0x0000000000000010
x19: 0x0000000000000000
х23: 0x0000000000000000
x27: 0xfffffe202ed48540
sp:
Oxfffffe73cf1bb6b0
far: 0x00000000000001ec
Debugger message: panic
Memory ID: Oxff
OS release type: User
OS version: 23G93
Kernel version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:04 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_6020
Fileset Kernelcache UUID: C58433CAF051B51A1E8941427B6C3CF3
Kernel UUID: 5CDB68A-1888-3A5C-92B3-86C864439A24
Boot session UUID: 699FAEBD-1CF2-4365-8499-6243F3EC91EF
iBoot version: iBoot-10151.140.19
secure boot?: YES
roots installed: 0
Paniclog version: 14
KernelCache slide: 0x0000000013a8000
KernelCache base:
Oxfffffe00253ac000
Kernel slide:
0x000000001€360000
Kernel text base:
Oxfffffe00253b4000
Kernel text exec slide: 0x000000001f924000
Kernel text
exec base:
Oxfffffe0026928000
mach
_absolute_time: 0x43eaa3d8e73
Epoch
Time:
sec
usec
Boot
: 0x66c1ca7
0x000568a4
Sleep
0x00000000
0x00000000
Wake
0x00000000
0x00000000
Calendar:
0x66d01443
0x00091cbf
Zone info:
Zone map:
Oxfffffe102ea10000 - 0xfffffe302ea10000
• VM
Oxfffffe102a10000 - 0xfffffe14fb6d000
• RO
Oxfffffe14fb6d000 - 0xfffffe1695074000
GENO
: Oxfffffe1695074000 - 0xfffffe1b61d40000
• GEN1
Oxfffffelb61d40000
- Oxfffffe202ea0c000
• GEN2
: Oxfffffe202ea0c000
Oxfffffe24fb6d8000
• GEN3
: Oxfffffe24fb6d8000
- Oxfffffe29c83a4000

Problem Report for macOS
Your computer was restarted because of a problem.
This report will be sent automatically to Apple.
› Comments
Problem Details and System Configuration
• GENS DATA
: Oxfffffe29c83a4000 - 0xfffffe302ea10000
Metadata:
Oxfffffe10004b0000 - 0xfffffe10084b0000
Bitmaps: Oxfffffe10084b0000 - 0xfffffe100200000
Extra
: 0 - 0
TPIDRX_ELy = {1: 0xfffffe202d399fa0
0: 0x0000000000000003
Oro: 0x00000001616300 }
CORE
PVH locks held: None
CORE
1
PVH
locks held:
None
CORE
2 PVH
locks held: None
CORE
3
PVHI
locks
held: None
CORE
4
PVH
locks
held: None
CORE
5 PVH locks held: None
CORE
6 PVH locks held: None
CORE 7 PVH locks held: None
CORE
8 PVH locks held: None
CORE 9 PVH locks held: None
CORE 10 PVH locks held: None
CORE 11 PVH locks held: None
CORE 0: PC=0x0000000185c16b28, LR=0x0000000185ac82ec, FP=0x000000016cf260
CORE
1: PC=0x000000018e1fc3dc, LR=0x000000018df6ede4,
FP=0x000000016e94efa0
CORE CORE
2: PC=0x0000000185c50594, LR=0x000000018e0cdf5c,
FP=0x000000016f541a90
3 is the one that panicked. Check the full backtrace for details.
CORE
4: PC=0xfffffe00269b9de8, LR=0xfffffe00269b9de4, FP=0xfffffe73cecd7ef0
CORE CORE
5: PC=0x0000000185a684a0, LR=0x0000000185a67d70, FP=0x000000016f3b1a80
6: PC=0xfffffe00269b9de8, LR=0xfffffe00269b9de4, FP=0xfffffe73cd0bfef0
CORE
7: PC=0xfffffe00269b9de8, LR=0xfffffe00269b9de4, FP=0xfffffe73cebdbef0
CORE 8: PC=0xfffffe00269b9de8, LR=0xfffffe00269b9de4, FP=0xfffffe73cebcfef0
CORE 9: PC=0xfffffe00269b9de4, LR=0xfffffe00269b9de4, FP=0xfffffe73ce8d7ef0
CORE 10: PC=0xfffffe00269b9de4, LR=0xfffffe00269b9de4, FP=0xfffffe73cf1f7ef0
CORE 11: PC=0xfffffe00269b9de8,
LR=0xfffffe00269b9de4,
FP=0xfffffe73cf2dbef0
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 2 swapfiles and OK swap space
Panicked task 0xfffffe1b64d357d8: 11744 pages, 24 threads: pid 152: WindowServer Panicked thread: 0xfffffe202d399a0, backtrace: Oxfffffe73cf1baad0, tid: 3114
1r: 0xfffffe002697f48c
fp: Oxfffffe73cf1bab60
1r: Oxfffffe0026accabc
fp: 0xfffffe73cf1babd0
Ir: Oxfffffe0026acae88
p: Oxfffffe73cf1baca0
Ir: Oxfffffe002692f8cc
fp: 0xfffffe73cf1bacb0
Ir: Oxfffffe002697ed80
fp: 0xfffffe73cf1bb060
1r:
Oxfffffe0027187248
fp: Oxfffffe73cf1bb080
Ir:
Oxfffffe00271922dc fp:
1r:
Oxfffffe0026acc8d4
Oxfffffe73cf1bb200
fp:
Ir:
Oxfffffe0026acb028
fp:
Oxfffffe73cf1bb270
1r:
Oxfffffe002692f8cc
Oxfffffe73cf1bb340
fp:
1r:
Oxfffffe0027eaa40c
Oxfffffe73cf1bb350
fp:
Oxfffffe73cf1bb730
a:hhhhh：ラランカトレラクタ
Hide Details
OK

The important line above may be the line mentioning the window server:

Panicked task 0xfffffe1b64d357d8: 11744 pages, 24 threads: pid 152: WindowServer Panicked thread: 0xfffffe202d399a0, backtrace: Oxfffffe73cf1baad0, tid: 3114