For me, -84 was problematic. In another thread, a user said -84 solved their issue.
It appears that there may be some regressions between 5.15.0-83 and 5.15.0-86
So testing each of these kernels, then locking in the one that works seems to be the workaround for now.
This actually reminds me of this thread in which @ERZ suggested that there is an instability in Zorin OS recently.
While we have not been inundated with help requests - we have seen four (or maybe more) individual users all note some issues with the kernels lately - myself included as one of them.
The good news is that the ZorinGroup is already testing the next kernel - so, we really shouldn't have very long to wait.