Solved Resource use spike when audio playback begins, Windows 7

[ChochoYubi]

When I begin playing an audio file on the computer, CPU and memory use spike (I think the CPU goes up to 50%) for the next 2-3 minutes. The audio player software hangs during that time, and no sound comes out.
After the 2 or 3 minutes have passed, audio playback resource use drops to normal and remains that way.
The usage spike happens only the first time the audio player is used after booting. After that, it operates normally even if the program is closed and reopened, or if another audio player is used.
The problem occurs in the same way no matter which audio player I use (foobar2000, mpxplay, 1by1) and no matter what file format is played (mp3, FLAC, ALAC).

The Task Manager seems to show that audiodg.exe is using a lot of CPU during this time. I say "seems" because the CPU number under audiodg.exe seems to go up to 7 or so, but I haven't seen it reach anywhere near 50 or 100.
All the Enhancements for playback devices are unchecked.

This problem has begun within the past year, I think, on a 4-year-old computer. I haven't changed any audio settings manually.

This isn't a fatal problem, but it does make my computer unusable for 3 minutes each day. I'd be very grateful for any suggestions.

 

[fireberd]

From your description, I would say its not really an audio problem, but the audio is byproduct of whatever is causing the problem.

One suspect is memory (RAM). With only 2GB of RAM that is a very low amount. I would suggest upgrading to 4GB of RAM, if the PC will support that as the first step. The CPU is probably a bottleneck too.

 

[ChochoYubi]

Thanks for the suggestion!
It is true that the computer could use more RAM, so I'll order another 2GB to get up to the 32-bit Win 7 limit of 4GB.

But is that all it could be? Just curious since the lag time is the same whether or not other programs are open, and regardless of the quality of the audio file or the memory footprint of the software used to play it. I would think those would have some impact if it were just a question of not enough RAM.
Though I'm happy to admit being very much an amateur here.

 

[fireberd]

Many factors, memory is one possibility. The speed of the CPU is another and this one is a relatively slow CPU.

Sound is always on a shared Interrupt with a higher priority device and thus can suffer because of that.