https://bugzilla.kernel.org/show_bug.cgi?id=204181
--- Comment #15 from Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) --- Thanks for the logs. I don't think this is related to your overclock.
Since this behavior wasn't previously observed during our 5.2 testing I think that either a patch got lost or changed during the submission process, or something from 5.3 was backported into 5.2 that shouldn't have been.
I don't think it's necessairly setup specific.