During our Sunday worship service we had our Projection mac crash randomly. Its a 2013 Mac Pro (A1481). I'm under the impression it looks to be a GPU problem but wanting some insight from the community. Posted the Log above and I will post 2 more logs below
Mac Pro
attempting to read Logs without a real destination in mind is the path to madness.
If you want to post something that might be helpful, post a kernel panic report.
Kernel 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
If the above is just "word-salad" to you, just ask and Readers can explain a bit more.
attempting to read Logs without a real destination in mind is the path to madness.
If you want to post something that might be helpful, post a kernel panic report.
Kernel 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
If the above is just "word-salad" to you, just ask and Readers can explain a bit more.
Additionally… Post the EtreCheck report, and run Diagnostics.
To post the EtreCheck report, download and run the tool and share the report to the clipboard. Then open a new reply here, and press the button that looks like a printed page to open an additional text window large enough for the report, and paste the report into that text input window here.
If Diagnostics shows any errors—some errors can be persistent, while other errors can be transient—let us know.
to make more progress, we need to look at your Etrecheck report, and have you run the diagnostic. "No Fault found" is NOT the same as "all is well".
I was unable to paste the entire log so I am pasting the beginning and the end in additional text
Here is a link to the file if you need it: Kernel-2022-03-06-101805.panic
WindowServer stopped responding and the watchdog timer fired.
Here is the link to the panic log
Mac Pro 2013- Crashed During a Worship Service.
