Constant freezing and sudden kernel panics

Hi,

Page fault tends to be memory error. Try to run Apple Diagnostics if it reports memory related errors(PPM001 to PPM 015).

Use Apple Diagnostics to test your Mac - Apple Support

If it detects errors, contact Apple Support or make Genius Bar reservation if your local retail Apple Store is open or find opened local Apple Authorized Service Provider to be examined your MacBook Pro.

Official Apple Support

https://www.apple.com/retail/geniusbar/

Apple - Find Locations - Location Selector

That isn't necessarily true. Diagnostics are only useful when they report an issue. A passing diagnostic means that those tests were unable to detect a problem at that time. 95% of the time diagnostics will never show a problem even though it is known that a hardware issue actually exists.

Try running Memtest86 to see if any memory errors are detected. You can create a bootable Memtest86 USB stick by using the downloaded Memtest86 .iso or .img file as a source for Etcher. Option Boot the USB stick and select the orange icon labeled "EFI".

Do you have any other Kernel Panic logs that you can post so we can see if there may be any pattern to them? The Kernel Panic logs are located in the "/Library/Logs/DiagnosticReports" folder and their file names begin with "kernel" and end in ".panic". Post several more of the recent panic logs if possible.

To look for possible software issues run EtreCheck and post the report here using the "Additional Text" icon which looks like a piece of paper.

Also disconnect all external devices in case one of them is causing a problem. The last loaded driver was:

com.apple.driver.AppleMikeyHIDDriver

You may also want to run Disk Utility First Aid on the drive as well.

Try running Disk Utility First Aid on the hidden Container. Within Disk Utility click "View" and select "Show All Devices" so that the hidden Container (and physical drive) appears on the left pane of Disk Utility. Even if First Aid shows everything as "Ok" click "Show Details" and manually scroll through the report to see if there are any unfixed errors listed. If there are unfixed errors, then you will need to erase the whole partition/Container (?) before restoring from a backup or clone. Normally I just erase the whole physical drive so I'm not sure how to instruct you if there are unfixed errors.

The EtreCheck report shows that System Integrity Protection (SIP) is disabled which is very dangerous to do on a Mac because a simple app update could break macOS like when a Google Chrome update prevented Macs from booting which had SIP disabled:

https://arstechnica.com/information-technology/2019/09/no-it-wasnt-a-virus-it-was-chrome-that-stopped-macs-from-booting/

You have a 15" MBPro (2015) model so there is always a chance the GPU could have issues. The 15" & 17" models from 2008+ are known to have GPU issues although I believe it is more common with the 2011 and earlier models although I know the 2013 model had known issues. You can use the Unigine Benchmark Demos (Valley and Heaven are the only macOS ones) to stress the GPU. I also like to use "gputest", but the app is really old and the GUI no longer works so the app must be launched using the command line after first getting Gatekeeper approval. There is a shell script included with the app which gives some examples of how to launch the app using the command line. You also have to be careful clicking the links to access the download since it has you jump through several pages before you get the actual download link (there are sometimes other "Download" buttons shown which can trick you).

gabelaya wrote:

There's one interesting thing - sometimes I run win10 with bootcamp and I've never faced any of these problems.

That may indicate a software issue on the macOS side so posting an EtreCheck report may help to see if this might be the case. Of course macOS and Windows can leverage the hardware differently where macOS is accessing or using the hardware in a way that exposes a fault. Since I don't see any patterns in the panics a memory issue is a real possibility as well (macOS may be using a section of memory that Windows is not accessing could be the difference).

ADP000 is "No Fault Found" which is most definitely NOT the same as "All is Well".