Mac Pro 2020 Big Sur Shut Down / Crashed at Night - Help Requested to Interpret Log File

Console logs are great for developers, but are not very useful for system problem. form that one, WindowServer killed or terminated all the running processes, then the console stoped working. The WHY is not apparent there.

--------

Panic Reports are stored at:

/Library/Logs/DiagnosticReports

They are named with Date&Time and end in .panic

You can post the entire report here, by using the “additional text” Icon in the reply header (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

Update: issues still persisted after removing dual VMs, and even after a clean install of Mac OS. In my case, it appears to be a GPU hardware issue since I can reproduce crashes consistently by running graphics stress-test applications. Perhaps it's not a good idea to run two 4k displays for so many hours on these machines, seems to cause long-term issues with the hardware.

Perhaps you should take a look at an etrecheck report, pre-laundered for posting back here on the forums:

Using EtreCheck to Troubleshoot Potential… - Apple Community

.

I also have this issue, it is also accompanied by a window server failure.

Nothing unusual going on the system, just Firefox, Finder, Dropbox, and VLC media player.

I am connected to two 4k external displays. I also noticed that after a reboot spotlight search stopped working.

The crash occurred at 16:00 hrs in the attached logs. There is a console.log output of the 15 minutes before the crash, and also a truncated log from /Library/Logs/DiagnosticReports with details of the WindowServer failure.

Also, here is an EtreCheck Report:

Your speculation that these Macs can not survive when left on for long periods is not accurate as written, and can not be allowed to stand as general advice.

Your Mac should be able to run for long periods with large displays connected and active as much as 24/7 for years on end.

If it develops a hardware problem under normal operating conditions, that is not a diabolical latent defect, but ordinary Hardware failure due to Bad Luck.

Thank you for taking a look. I've removed one of the hypervisors and investigated the suspicious plist, it is an application that I use,I will update if issues persist

[Link Edited by Moderator]

I have those 4k displays too and I was wondering if after a few months it was those as well.

Kernel Extensions:

/Applications/Parallels Desktop.app

[Not Loaded] prl_hypervisor.kext (16.1.1 49141 - SDK 10.11)

[Not Loaded] prl_netbridge.kext (16.1.1 49141 - SDK 10.9)

[Not Loaded] prl_usb_connect.kext (16.1.1 49141 - SDK 10.9)

[Not Loaded] prl_vnic.kext (16.1.1 49141 - SDK 10.9)

...

/Applications/VMware Fusion.app

[Not Loaded] vmioplug.kext (19.9.0)

[Not Loaded] vmnet.kext (12.0.0)

[Not Loaded] vmmon.kext (12.0.0)

You can not run more than one Hypervisor and have your Mac work normally. Choose one or the other and remove the other.

This item is not findable in a simple web search Etrecheck thinks it might be malware:

[Loaded] homebrew.mxcl.asimov.plist (? aab9537f - installed 2020-06-18)