If there's a suspicion on Goom, a couple of things to experiment with:
a) Switch to another visualisation for a few days. If the issue still happens it's not specific to Goom. If it doesn't it points the finger more firmly towards Goom.
b) Change Goom settings to manual and work your way through the list of individual visuals. Each one uses different shaders so can potentially result in different behaviour. The theory is that something in the shaders (which have seen quite a bit of change for K22 might disagree and cause issues. See if you can pinpoint specific visuals that cause problems.
NB: I've also seen the errors related to ID3 tags, but if the software is flagging those issues it suggests it's reading the file and then reporting; which suggests gracefull handling of those issues and thus (IMHO) they aren't likely to be the cause of a crash.