Due to recent updates I was having the same problem described here. Interesting thing is it was nothing to do with audiodg.exe at all. Whether it was what came from Microsoft or not something changed...