Since this thread is apparently still alive, a quick update from my recent experiences:
I maintain all of my working code in a Google Drive-synced folder. Last week, I was working on one of my projects on my secondary Windows machine (7 Pro 64 bit). Everything was as normal, and I went to lunch and locked my workstation. Coming back, I noticed that Google Drive was in the process of syncing, but thought nothing of it. I started back working on a particularly annoying bit of code, and after a restart, I started getting those pesky audio errors.
Not putting two and two together, I assumed there was something wrong with my audio files and commented out all music in the particular scene. No joy. No matter what I did, from stopping play to niling references to the “music” module I have, had any affect. Then I stopped the Google Drive sync.
Wonder of wonders, the errors went away. I started the sync again, and lo and behold, the same audio errors.
This is far from scientific, but anecdotally, one might conclude that, if the audio file and/or directory which holds the audio file is in a state of flux (owned by the operating system, being modified, being scanned by spyware program, etc.) then one is going to encounter these errors.
Again, nothing scientific and I’m not at a point where I can stop and test my hypothesis, but it’s something to keep in mind if anyone gets these errors, and maybe gives a startpoint for Corona testing.