Kernel Panic Restart

I do not see a "Smoking Gun" in the panic report or the EtreCheck report.

Yes, the panic reports says you have one 3rd party kernel extension, but MalwareBytes has a good reputation, and except for once about a year ago, which the author quickly addressed and apologized for, has not been responsible for any panics.

I think you have 3rd party RAM (G.Skill ???), but I'm not sure. 3rd party RAM has been known to cause kernel panics (2nd most common cause). If you do have 3rd party RAM, I would run Rember overnight

<http://www.kelleycomputing.net/rember/>

.

Quit as many apps and background tasks as you can (such as menu bar items) so more RAM is available for testing.  Booting into Safe mode <http://support.apple.com/kb/ht1564> can also free up more RAM for testing, by not loading any 3rd party additions you may have installed.

.

Set Loops: [X] Maximum

and run overnight

You appear to have an external disk (or 2) plugged in. A lagging behind 3rd most common kernel panic cause is a broken USB device, broken USB cable, broken USB Hub.

After that way in the back, barely insight of the leaders is Apple hardware.

You say kernel panics (as in multiple). Can you look at the kernel panic reports and see if they are all basically the same. It would be very interesting if some of the panic reports including a "Backtrace" that mentioned the kernel extensions macOS was in when the panic occurred. If you have some of those And they are consistent, that might help point in a direction.

Again, with out a smoking gun, I do not have a lot I can point at. If I had to guess, I would lean towards 3rd party RAM, but it is not a strong leaning.

Well the first panic signature was:

panic(cpu 3 caller 0xffffff80289898cf): Kernel trap at 0xffffff8028980e42, type 13

The second panic signature was:

panic(cpu 1 caller 0xffffff8006f81241): assertion failed: total_sbmb_cnt >= 0, file: 
/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.57/bsd/kern/uipc_socket2.c, line: 2489

If there are additional random signatures, that points to hardware. Software induced panics then to be in the same place.

Just based on statistics as observed via years of reading panic "tea leaves" in these forums, 3rd party RAM is the most likely (and least expensive to repair) possibility.

After that is something in your motherboard, which has also been working for years.

Hardware can break. Thermal heading and cooling can stress components. Accumulated dust can increase internal temperatures, etc...

So it is easy to start with Rember run overnight. If it finds something you will know. If it does not find anything, you are left with the same choices.

Another way to isolate RAM is to put back the original RAM and see if the problem continues. Painful I know (I've owned 32GB Macs and recently had to go back to 16GB and it is most annoying; I've had to cut back on the current tasks I keep running). But as an experiment, it is cheap and fairly easy.

The external device test is just to unplug everything. If you use a corded keyboard and mouse, then see about using a Bluetooth keyboard and mouse, or another keyboard and mouse. It is important to eliminate all existing external devices and wiring, so no reusing cables. Again, this is an experiment to eliminate external devices (mostly USB) as being a cause.

You can also make a Genius Bar appointment at an Apple Store and have them look at hour Mac.

My MacBook Pro is experiencing kernel panic with Microsoft Word; MacOS 10.15.1 and MS word 16.3. A quick google search will reveal that users have been experiencing a kernel panic since the first week in November. I have been working with senior apple advisers and 2 out of 3 have been helpful. However, none of them were aware that this is an ongoing issue nor the magnitude of the number of user effected.

I fixed a Kernel Panic on my Macbook Pro by downgrading Microsoft Word from 16.31 to 16.29. This may work for you if you use Word.

Search in the MS Support for instructions. Many people are experiencing the same issue with macOS 10.15.1 and MS Word 16.31.

I wonder if it was related to a security update. I just installed High Sierra on a battle worn used Mac and it has begun crashing (I've owned it less than 48 hours). I noticed that in my case, the panics and window server crashes happen much more often when listening to audio (usually reboots or logs me out in under ten minutes) whereas when I'm simply using programs it's a less common occurrence.

I may re-install and opt out of the cumulative security patches until this stabilizes, but only because this machine is not my daily-driver.

I should also note that this is on macOS 11.13.6 on a 17" 2010 MBP. I don't have these issues on my 15" 2012 running macOS 11.14.6.

Update here. It turns out that my Macbook Pro actually suffers from issues with switching between the integrated and discreet GeForce GT 330M video. I'm not sure why it crashes core audio. To rule out the security update, I ran a Linux live CD and it also had intermittent crashes across various applications relating to the graphics.

The workaround until I can do the board-level re-work is to disable GPU switching. It hasn't crashed since.

With the variety of Apps panicking I think Bob is likely correct about RAM being the cause.

Good work, thanks for the report. :)

:)