Hmmm. It seems that I have a hardware issue after all.
That's an assumption. What you have is an issue, to be sure. It remains to be seen exactly what kind of issue.
Right now I did nothing. I was leaning towards my Mac to browse some stuff, and when leaned back to play, no sound.. After two minutes the DSP error message came up. And they occur randomly. No spesific tasks. Twice an hour, or once a day, no spesific timeframe.
When contacting support (or just posting problems here for that matter), the single most important thing you can provide is what's known in the trade as "steps to reproduce."
A professional software QA person's routine is typically a) encounter a bug, b) fool around with the system until s/he can reproduce it each time from a well known starting point and a specific series of steps, and then c) report the bug, including the steps.
I can tell you from three decades in the biz that people who are able to give me that kind of feedback are my personal heroes. It makes it so much easier to find and reproduce the problem. If I can't do that, then I can't reproduce it in the debugger to figure it out. Equally important, once I (alledgedly) fix it, if I don't know for sure how to make the bug happen, I don't know if I really fixed it or not.
All of this is to encourage you to think like a professional tester when you run into trouble. It may be that you have a faulty unit, but it's also possible these are residual effects from having a beta installed on your system. If you can figure out how to reproduce it (which may take a little work on your part), then when you contact support either they'll be able to walk you through a solution or know for sure if it's hardware. And when it's related to a beta (even if it's no longer installed), you give the devs a fighting chance to find and fix the bug, which they very much want to do.
If you approach things in this manner, it helps people in their efforts to help you.