Kernal Panic, External Display Issue

Panic Reports are stored at:

/Library/Logs/DiagnosticReports

If you copy and paste that string into:

Finder > Go menu > Go to Folder

it will take you to where those reports are stored.

They are named with Date&Time and start or end in ‘panic’

If you find one, please post the entire report here, by using the “additional text” Icon in the reply footer (looks like a paper with writing).

Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.

There are three quick take-aways from any panic report.

1) The panic-reason,

2) the extensions present at the "scene of the crime", and

3) the BSD process in which the problem occurred.

One more item that is important is the names of any third-party Extensions you have added. They are shown FIRST in the extensions loaded section

MacBook Pro 13-in Touch Bar 2019 running 10.15.7

The issue in both cases is this one:

panic: "ACPI: Fatal opcode executed

In this case "illegal opcode" is akin to an error in calling sequence.

ACPI is the subsystem responsible keeping track of internal hardware components and their sleeping and waking states.

Extensions present at the scene the crime include ACPI drivers, PCI bus drivers and System Management Controller (SMC) drivers. Bad process is kernel_task, so Extensions may be an issue. they are:

com.google.drivefs.filesystems.dfsfuse 45.3.0

org.virtualbox.kext.VBoxNetAdp 6.1.4

org.virtualbox.kext.VBoxNetFlt 6.1.4

org.virtualbox.kext.VBoxUSB 6.1.4

org.virtualbox.kext.VBoxDrv 6.1.4

com.paragon-software.filesystems.ntfs 71.5.15

if you are not actively using VirtualBox on a daily basis, you should remove it to facilitate debugging.

I suggest you disable most automatic sleep especially power nap if available to you, as well as "wake for network access".

:

DON'T run third-party anti-Virus on your already very well protected Macintosh computer. It WILL cause crashes, typically for no reason at all.

The first is a sleep/wake problem, the other two involve dfr daemon, but I am having trouble finding out what that refers to.

That report mentions watchdog timer, but is not complete enough to tell why it fired. It may be getting to be time to ask Apple support for help with this one.