1.16.5 crashing M1 Mac Mini

[ionblue]

I needed to rip some discs today and downloaded the latest (1.16.5) and 3 times in a row after opening it and selecting a disc, the system froze, flashed purple on the screen, and rebooted. It created crash reports to send off to Apple so I did that.

I downgraded to 1.16.4 and all is well. Ripping 2 movies as I write this.

Anything I can provide to help track this down?? Not sure if it's OS (Monterey) or MakeMKV.

[mac35years]

I just tried using my new M1 Mini for ripping and experienced the same behavior. Only happened on a BluRay disk, was able to pull from DVD just fine. But the behavior you described is exactly what mine did. Freeze, flash, reboot.

[JohnOCFII]

This may be related. I have a new MacBook Pro 16" with M1 Pro processor. I've attempted to create backups from a few discs. I tried 3 DVDs, and they all worked fine. I've tried 3 Blu-ray discs and they have all failed with similar kernel panics! The failure might not happen for 10-20 minutes into the process.

I've seen some notes about dropping back to MakeMKV 1.16.4, and I saw one forum note suggesting that using a powered USB hub (or perhaps separately powering your Blu-ray drive) might also resolve the issue.

Here's the top of the kernel panic I'm seeing:

Code: Select all

panic(cpu 0 caller 0xfffffe002b8b3e78): vm_object_iopl_request: missing/bad page in kernel object @vm_pageout.c:9356
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 21D49
Kernel version: Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: 6FE5ED520EAABAFE218814C92CA517B4
Kernel UUID: BADF56F4-2876-3FF4-AC12-F25E78B09AA1
iBoot version: iBoot-7429.81.3
secure boot?: YES
Paniclog version: 13
KernelCache slide: 0x0000000023e64000
KernelCache base:  0xfffffe002ae68000
Kernel slide:      0x0000000024698000
Kernel text base:  0xfffffe002b69c000
Kernel text exec slide: 0x0000000024780000
Kernel text exec base:  0xfffffe002b784000
mach_absolute_time: 0x2fe30a9817a
Epoch Time:        sec       usec
  Boot    : 0x61feb36c 0x000307b7
  Sleep   : 0x62014b73 0x000090e5
  Wake    : 0x62014bb4 0x00058dd2
  Calendar: 0x62015eba 0x00024477

Zone info:
Foreign   : 0xfffffe00342e0000 - 0xfffffe00342f4000
Native    : 0xfffffe1000344000 - 0xfffffe3000344000
Readonly  : 0xfffffe14cd010000 - 0xfffffe16669a4000
Metadata  : 0xfffffe6d5d2ac000 - 0xfffffe6d691e0000
Bitmaps   : 0xfffffe6d691e0000 - 0xfffffe6d74c0c000
CORE 0 PVH locks held: None
CORE 1 PVH locks held: None
CORE 2 PVH locks held: None
CORE 3 PVH 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 0 is the one that panicked. Check the full backtrace for details.
CORE 1: PC=0x00000001bc1b3b50, LR=0x00000001bc0533d8, FP=0x000000016bc86e40
CORE 2: PC=0xfffffe002b80af50, LR=0xfffffe002b80af4c, FP=0xfffffe601e43bef0
CORE 3: PC=0xfffffe002b80af4c, LR=0xfffffe002b80af4c, FP=0xfffffe60dc7b3ef0
CORE 4: PC=0xfffffe002b80af4c, LR=0xfffffe002b80af4c, FP=0xfffffe60ed203ef0
CORE 5: PC=0xfffffe002b80af4c, LR=0xfffffe002b80af4c, FP=0xfffffe601e1abef0
CORE 6: PC=0xfffffe002b80af4c, LR=0xfffffe002b80af4c, FP=0xfffffe601e17bef0
CORE 7: PC=0xfffffe002b80af4c, LR=0xfffffe002b80af4c, FP=0xfffffe60dc203ef0
CORE 8: PC=0xfffffe002b80af4c, LR=0xfffffe002b80af4c, FP=0xfffffe60dc3b3ef0
CORE 9: PC=0xfffffe002b80af4c, LR=0xfffffe002b80af4c, FP=0xfffffe60ce7abef0
Panicked task 0xfffffe200012ed48: 151133 pages, 15 threads: pid 341: ArqAgent
Panicked thread: 0xfffffe1fffaa6080, backtrace: 0xfffffe606ea5a680, tid: 790210
		  lr: 0xfffffe002b7d64e8  fp: 0xfffffe606ea5a6f0
		  lr: 0xfffffe002b7d61b8  fp: 0xfffffe606ea5a760
		  lr: 0xfffffe002b9162bc  fp: 0xfffffe606ea5a780
		  lr: 0xfffffe002b9086c8  fp: 0xfffffe606ea5a800
		  lr: 0xfffffe002b906118  fp: 0xfffffe606ea5a8c0
		  lr: 0xfffffe002b78b7f8  fp: 0xfffffe606ea5a8d0
		  lr: 0xfffffe002b7d5e2c  fp: 0xfffffe606ea5ac70
		  lr: 0xfffffe002b7d5e2c  fp: 0xfffffe606ea5ace0
		  lr: 0xfffffe002bfe9738  fp: 0xfffffe606ea5ad00
		  lr: 0xfffffe002b8b3e78  fp: 0xfffffe606ea5aeb0
		  lr: 0xfffffe002b8b27e8  fp: 0xfffffe606ea5afd0
		  lr: 0xfffffe002bf24b48  fp: 0xfffffe606ea5b0f0
		  lr: 0xfffffe002bf24384  fp: 0xfffffe606ea5b120
		  lr: 0xfffffe002db45400  fp: 0xfffffe606ea5b1e0
		  lr: 0xfffffe002db430c0  fp: 0xfffffe606ea5b210
		  lr: 0xfffffe002ba863cc  fp: 0xfffffe606ea5b2b0
		  lr: 0xfffffe002ba79484  fp: 0xfffffe606ea5b330
		  lr: 0xfffffe002e422ea4  fp: 0xfffffe606ea5b380
		  lr: 0xfffffe002e4228f0  fp: 0xfffffe606ea5b450
		  lr: 0xfffffe002e422520  fp: 0xfffffe606ea5b4c0
		  lr: 0xfffffe002e42238c  fp: 0xfffffe606ea5b5a0
		  lr: 0xfffffe002e42c9bc  fp: 0xfffffe606ea5b6b0
		  lr: 0xfffffe002e41a56c  fp: 0xfffffe606ea5b710
		  lr: 0xfffffe002ba2f310  fp: 0xfffffe606ea5b8c0
		  lr: 0xfffffe002ba34d90  fp: 0xfffffe606ea5bad0
		  lr: 0xfffffe002ba34200  fp: 0xfffffe606ea5bb30
		  lr: 0xfffffe002e42cf2c  fp: 0xfffffe606ea5bbd0
		  lr: 0xfffffe002e4193f8  fp: 0xfffffe606ea5bc00
		  lr: 0xfffffe002ba6cf08  fp: 0xfffffe606ea5bcc0
		  lr: 0xfffffe002bd4c7c8  fp: 0xfffffe606ea5bd50
		  lr: 0xfffffe002bd4c4ac  fp: 0xfffffe606ea5bdb0
		  lr: 0xfffffe002be3d1ac  fp: 0xfffffe606ea5be50
		  lr: 0xfffffe002b9061e8  fp: 0xfffffe606ea5bf10
		  lr: 0xfffffe002b78b7f8  fp: 0xfffffe606ea5bf20
      Kernel Extensions in backtrace:
         com.apple.iokit.IOStorageFamily(2.1)[405D4475-3CBA-3113-A037-4BE7AD5EC73A]@0xfffffe002db2dc60->0xfffffe002db4e7eb
         com.apple.filesystems.udf(2.5)[5E91CB2A-5121-38C9-A5B5-F48CA297CCB5]@0xfffffe002e417230->0xfffffe002e4469eb

[dcoke22]

What version of MacOS are you on? I've been running MakeMKV 1.16.5 on Intel on Big Sur without any issues.

[JohnOCFII]

What version of MacOS are you on? I've been running MakeMKV 1.16.5 on Intel on Big Sur without any issues.

This M1 MacBook Pro is running Monterey 12.2. My guess is this is somehow M1 chip related.

[dcoke22]

Maybe. I have used MakeMKV 1.16.4 on Big Sur on an M1, but not extensively. It sorta feels like a Monterey 12.2 bug, but that's just a guess.

[JohnOCFII]

Another data point -- I installed version 1.16.4, and was able to successfully run though Disc 1 of Iron Man without issue. I thought that was pointing to 1.16.5 as the issue, but when I started on Disc 2 (special features) I had a kernel panic. After the MacBook Pro restarted, MakeMKV restarted, and I had a second kernel panic right away.

[Carl Johan]

I have a Macbook Pro with M1 Max. Attempts to play one disk particular on VLC or access the actual data, as in syncing it to another folder w. rsync, will cause MacOS Monterey to crash. I have also been unsuccessful trying to create an image or a makemkv backup because of errors, so the disk is probably not 100%.

BR CJ

[Fotis]

same here! Freeze (even the mouse cursor), purple screen flashing and then reboot!
running makeMkv 1.16.7 on macOS Monterey 12.3.1 on a 2021 imac (with M1).

[tvillini]

Similar issue... MacBook Pro M1 13". I was on 1.16.7, and it would fail gracefully-ish with an IPC error. So I tried the manual process where I would get the decrypt files, and copy them into a folder where I just copy the files. My freeze, purple flash, and reboot would happen when I just did a straight copy using Finder. I had just ripped 4 other movies before with no problems... but I had this with Spider Man - No Way Home.

The drive is external, but powered independently.

I too downgraded to 1.16.4 and it worked fine.

[ionblue]

Coming back to this as I had forgotten to provide an update...

It's definitely related to USB power consumption and probably has nothing at all to do with MakeMKV, unless it's doing something weird. The M1 Mini's USB ports are woefully underpowered, but even using a powered hub it might not make a difference.

I have a powered TB3 dock and a USB3.1 powered hub and with my BU40N plugged into either AND trying to use a ASUS BW-16D1HT which is in a powered enclosure (duh), I will get crashes and reboots when trying to rip 2 at a time. I ended up needing to have the BU40N plugged into the high power port of my dock AND use the splitter cable for extra power plugged into my UPS USB power port. It's kind of ridiculous, but I can rip 2 at a time now without crashing. I'm also now using 1.16.7 just so you know...

Anyway... just wanted to provide an update to all. Hope anyone else having issues can find a workaround.

[Fotis]

thanks for sharing! In my case it's definitely not a USB power issue, since my issue is with ripping from an ISO image, not a BR drive! I've had good luck falling back to 1.16.4

[dalosliandi]

I'm using MakeMKV 1.16.7 with macOS 12.4. I have successfully ripped about 15 UHD marvel movies from my personal collection over the past week or so. No crashes or kernel panics.

Here's my setup: My drive is a LG WH14NS40 (internal 5.25" drive) which has had its firmware downgraded from 1.03 to 1.02 and it's attached to a Vantec SATA to USB 3.0 12v powered Interface (model CB-ST00U3). The USB 3 cable is plugged into the front port of my CalDigit TS3 thunderbolt dock and that's connected to my Mac Studio (Base model) with a thunderbolt 3 cable. I'm saving the files directly to Sandisk 1TB USB 3.2 SSD which is directly connected to the Mac.

[JohnOCFII]

I haven't ripped and Blu-ray Discs for some time now. I've done quite a few regular DVDs without issue. One thing I _have_ been doing is stopping my Arq software backups (which run multiple times a day), just in case. Regular DVD ripping has been fine.

[rkric258]

Here has some guidance and steps to fix crashing on mac:
Remove all external devices excluding AC power connection, display, mouse, keyboard, and Ethernet connection.
Restart Mac and immediately press and hold the D key until Apple Diagnostics screen appears.
(If the screen does not appear, then turn off firmware password if any, or hold down Option + D during restart to start the diagnostics over the Internet).
When Apple Diagnostics is aware of your language choice, it displays a progress bar to check your Mac (which may take a maximum of 3 minutes).
When Apple Diagnostics finds any issues, it suggests solutions and displays reference codes.
Opt from the various options:
Press Command + R or click Run the test again to repeat the test.
Press Command + G or click Get started to fetch details about service and support options.
Press R or click Restart to restart your Mac.
Press S or click Shut Down to shut down your Mac.
When done, you need to Restart or Shut Down your Mac.


After upgrading your Mac to the latest macOS Monterey, Big Sur, Catalina, and Mojave, if the system freezes or slows down, then restarting your Mac in Safe Mode helps fix the frequently crashing issue.

Safe Mode loads only the important kernel extensions, verifies the startup disk and repairs directory issues (similar to Disk Utility’s verify and repair functionalities), prevents startup/login items to launch automatically, deletes cache files, and disables user-installed fonts.
these methods works Mac mini and imac or even macbook pro

To start your Mac in Safe Mode, do the following:

Restart Mac and immediately press and hold the Shift key until you see the login window.
After the Mac boots into Safe Mode, if no issue occurs then restart it again without pressing any key to start normally.
To know whether you are in the safe mode, open spotlight and type system information.
Use the software section of the system information window to verify the boot mode as Safe instead of Normal.
If the issue comes back in the normal mode, then the login items may be incompatible.
If the Mac does not boot into Safe Mode, then there is low space on the startup disk.
Clean up your Mac’s startup disk to allow your macOS to function correctly.
C. Delete Software Update Caches
If your Mac crashed during the auto software update, then you must clean the following files:

/Library/Preferences/com.apple.SoftwareUpdate.plist
/Home/Library/Caches/com.apple.SoftwareUpdate/
/Home/Library/Preferences/ByHost/com.apple.SoftwareUpdate.123.plist

Finally, a suggestion for you, If you are thinking to switch or move to laptop then I think macbook pro m1 variant will be a good option to getting better performance on regular and even heavy task.