Kernel Panic Reports are stored in the Folder at:
/Library/Logs/DiagnosticReports
If you copy and paste that string into:
Finder > Go menu > Go to Folder
it will take you to the Folder where those reports are stored.
Kernel panic reports are named with Date&Time and start or end in ‘panic’
If you find one, please post as much as you can here, by using the “additional text” Icon in the reply footer (looks like a paper with writing). (Once the report devolves into incessant software-names or incessant Base-64 dumps with lots of AAAAAA lines, you are done.)
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.
If you post your kernel panic here in its entirety, using the additional text icon in the reply footer, we do have some Readers (typically with developer background) who can attempt to interpret those panic reports. Even if no clear symptom emerges, this can still save a step if you DO need to contact Apple support later, because Apple Support specialists can read the panic reports you posted here, if you tell them what discussion or what Avatar.
--------
Based on what you have already posted, there is a decided NON-Trend. The panics occur "all over the Map" for different panic reasons and in different BSD processes, with different extensions present.
A Non-Trend suggests you may have RAM memory problems. MacOS slightly randomizes the load point of key routines on each startup, as a hedge against fixed-address attacks. This causes a marginal memory cell to move into different routines each time your Mac starts up. This causes random and bizarre non-correlation in your panic reports from one run to the next.
