jason birch jÊ*܅جrë,Š‰ìš+¢ÊµÊ&

Yes, I have also encountered this issue before. Considering I am also running
a Creative card (Soundblaster Live! 5.1) it may be an issue simply with these
cards. Unfortunately for myself, I am running the x64 version, and Creative
are, to say the least, sloppy and negligent with their drivers. It took a
while, but I had to use the 64-bit XP drivers, and so far I've only moderate
success... I achieve only stereo sound, not 5.1, and I dont achieve 24-bit
quality either (both the sound card and speakers are 24-bit capable). In
fact, unless I am planning to watch a movie, I usually make a habit of ending
this task immediately, before it begins to eat in excess of 1.5 GB of RAM...
It is also interesting to note that, at least for me, audiodg.exe is NOT a
32-bit process, so I know not why it would be stored in System32, and not
SysWOW64. Oh never mind, it is contained within both, the x64 version a
noticiable 38 KB smaller. It is quite the feat of this 78 KB application to
create a proverbial sink of RAM.

It is interesting to note though I have seen this process at roughly 1 GB of
RAM, and upon checking later found it at an acceptable (yet perhaps
unreasonable) 200 MB. In general though, it is more of a steady climb than
decline.

Unfortunately for you, ThrmanMunson15, I've not had issues with CPU usage
with this process. I am also able to end it, and with extreme prejudice. I
am, however, unable to create a dump of the process, and not for lack of
space.

Again, I know not if this is a problem with the 64-bit compatibility, the
sloppy driver support of creative, or a uncommon Vista flaw, but it wasn't
covered in the latest 5 updates I need to restart to install now

Believe me, I looked.

jason birch jÊ*܅جrë,Š‰ìš+¢ÊµÊ&

Yes, I have also encountered this issue before. Considering I am also running
a Creative card (Soundblaster Live! 5.1) it may be an issue simply with these
cards. Unfortunately for myself, I am running the x64 version, and Creative
are, to say the least, sloppy and negligent with their drivers. It took a
while, but I had to use the 64-bit XP drivers, and so far I've only moderate
success... I achieve only stereo sound, not 5.1, and I dont achieve 24-bit
quality either (both the sound card and speakers are 24-bit capable). In
fact, unless I am planning to watch a movie, I usually make a habit of ending
this task immediately, before it begins to eat in excess of 1.5 GB of RAM...
It is also interesting to note that, at least for me, audiodg.exe is NOT a
32-bit process, so I know not why it would be stored in System32, and not
SysWOW64. Oh never mind, it is contained within both, the x64 version a
noticiable 38 KB smaller. It is quite the feat of this 78 KB application to
create a proverbial sink of RAM.

It is interesting to note though I have seen this process at roughly 1 GB of
RAM, and upon checking later found it at an acceptable (yet perhaps
unreasonable) 200 MB. In general though, it is more of a steady climb than
decline.

Unfortunately for you, ThrmanMunson15, I've not had issues with CPU usage
with this process. I am also able to end it, and with extreme prejudice. I
am, however, unable to create a dump of the process, and not for lack of
space.

Again, I know not if this is a problem with the 64-bit compatibility, the
sloppy driver support of creative, or a uncommon Vista flaw, but it wasn't
covered in the latest 5 updates I need to restart to install now

Believe me, I looked.