2023 Mac Studio - macOS Ventura 13.5.2
No rhyme or reason. The computer constantly just crashes and restarts with the report log below. I don't know what to do or even how to troubleshoot it. The only peripheral is a Logitech MX dongle.
Drives like the MyBook came with software, and the manufacturer suggested you install that software.
What that software does is to "spare you the annoyance of having to re-initialize the drive" from its factory set Windows New Technology File System (NTFS, the W is silent because there are no other Operating Systems) or similar unusual (on a Mac) format. Instead, the software they provided would simulate a MacOS drive inside an NTFS file for your Mac.
The downside of using the manufacturer's software is that if the manufacturer's software is not loaded, the Macintosh Volume may not readable, or may not be writable. This means that in startup manager, Installer, and in Recovery such as after a data loss, the Macintosh Volume may not be visible.
The standard advice given here to all users, including novice users, is to discard the manufacturers software and NEVER use it. "Best Practice" is to erase the physical device when new, using only MacOS Disk Utility, and create the fundamental data structures needed for consistent, reliable use by MacOS.
Be sure to "show all devices" which will allow you to ERASE the entire Physical Device by its immutable manufacturer-given device-name, not just user created Volume-name such as ‘Macintosh HD’.
Drives like the MyBook came with software, and the manufacturer suggested you install that software.
What that software does is to "spare you the annoyance of having to re-initialize the drive" from its factory set Windows New Technology File System (NTFS, the W is silent because there are no other Operating Systems) or similar unusual (on a Mac) format. Instead, the software they provided would simulate a MacOS drive inside an NTFS file for your Mac.
The downside of using the manufacturer's software is that if the manufacturer's software is not loaded, the Macintosh Volume may not readable, or may not be writable. This means that in startup manager, Installer, and in Recovery such as after a data loss, the Macintosh Volume may not be visible.
The standard advice given here to all users, including novice users, is to discard the manufacturers software and NEVER use it. "Best Practice" is to erase the physical device when new, using only MacOS Disk Utility, and create the fundamental data structures needed for consistent, reliable use by MacOS.
Be sure to "show all devices" which will allow you to ERASE the entire Physical Device by its immutable manufacturer-given device-name, not just user created Volume-name such as ‘Macintosh HD’.
The reason I am suspicious is that your panic report says you ran out of dynamic memory allocation blocks, and pointed to a task with APFS running in it, suggesting something in the File system was causing this.
Your DiskUtil report calls out your boot drive physical drive. Your second drive is ONLY shown as a Disk Image (no physical drive) for your external drive. This suggests it is formatted as a Windows NTFS drive, and MacOS is being simulated (as a disk image) on that inherently NTFS drive.
Launch Terminal and enter:
diskutil list
and press return. Copy the text and post in a reply.
Constant crash and restart from kernel panic