2020 Intel MacBook Pro laptops suddenly dying and needing Revival

[MNussbaum]

Our fleet includes nearly (70) 2020 Intel MacBook Pro laptops running macOS Monterey 12.7.2, 12.7.3, and 12.7.4.

Over the past month, nearly a dozen of them have suddenly died. Each time it starts with the computer restarting without warning, sometimes more than once, before it won't power back on at all.

Each of these laptops have been brought across the street to Apple, where the majority of them have been able to be revived via Apple Configurator. None of them have had a reoccurrence of the issue after being revived so far.

Apple Diagnostics show no issues with the laptops and Apple support in the store and via their Help Desk Support have not been able to provide any insight or suggestions other than to bring it to them when it happens or to replace them.

Curious if anyone has seen any similar issues and has any ideas for preventing this. Wondering if there is any preemptive action we can take.

Notes:

We can't currently update these laptops beyond macOS Monterey because we use on-site SMB storage. In macOS Ventura and Sonoma, trying to save a file directly to SMB storage with Microsoft/Adobe applications results in the quarantine flag and the file being hidden. (A whole other disaster to deal with.)

We don't have a full-time, on-site IT person to attempt the DFU revive in office before sending them over to Apple.

[MNussbaum]

The most recent person to have this issue and get it resolved by Apple reviving it got a popup that said the following:

Panic Medic Boot

A third party kernel extension was preventing the machine from successfully booting. All third party kernel extensions have been disabled. You will be prompted to re-enable them in the Security & Privacy System Preferences pane as they are used.

Is there a good way to try to find which third party kernel extension may have caused this? Wondering if this could be a clue to what is causing this issue.

[shrisivakumaran]

You can collect sysdiagnose log which gathers system-wide diagnostic information and go through the logs of those system to find what went wrong on it.

[MNussbaum]

Thank you for the reply, Shri! I was finally able to get a full sysdiagnose log from a user who had this issue, though they experienced it on Friday afternoon and got it resolved and generated the files on Monday afternoon. Will these logs go back that far or is there somewhere I can look on their computer that will go back to the timeframe needed? Are there particular files I should be looking in for this specific issue?

[shrisivakumaran]

You can check for spin logs or crash reports/dump also check for kernel extension logs as well. It will have older logs also