audiodg.exe

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

tonight my computer keept on freezing on me. (nothing new with windows, i
they might do alot to fix that) normaly i know what to do in task manager to
fix it, however this time i came across audiodg.exe i have never seen this
program and it was sucking up all my computer usage. it was at 99% at one
point. i tired canceling it however it is a manditory program.
what does this program control, how can i stop it from using all my
computing power?
 
At the moment, there doesnt seem to be any references to that program you are
having problems. To narrow down the options, try following. A) check updated
audio drivers B) disable soundcard C) check dx diagnostics if that gives any
hints. If you find the cause send bug report about it. Thumbs up.
 
Actually this is a windows component. it is in the windows folder System32.
it is the Windows Audio Device Graph Isolation. from what i have noticed
atleast
with my systems is that any sound includeing the the interfacre sounds,
games,
and such some how cause this aplication to absorbe system resources. however
i cannot be sure as to the complications of audio drivers attributeing to
this program
from no clearing the resources used once they are no longer needed. On my
system
that has seemed to eat over 1.5 GB of ram it runs on a Creative Sound Blaster
Audigy 2 ZX Platinum. Now my second and third systems run off of the onboard
nforce 530 chipset and they do not exhibit this annomily.

Also it must be stated that all of the drivers are beta as well as the OS.
there
could be an unknow conflict between the said application and the drivers used.
tho i do not yet know the function of this program i can tell you that it
for lack of
a better was to describe it neither harmless nor harmfull it just seems to
eat
tons of resources some time and yet other times it just runs perfect i do feel
that it is on a system to system basis.
 
Actually this is a windows component. it is in the windows folder System32.
it is the Windows Audio Device Graph Isolation. from what i have noticed
atleast
with my systems is that any sound includeing the the interfacre sounds,
games,
and such some how cause this aplication to absorbe system resources. however
i cannot be sure as to the complications of audio drivers attributeing to
this program
from no clearing the resources used once they are no longer needed. On my
system
that has seemed to eat over 1.5 GB of ram it runs on a Creative Sound Blaster
Audigy 2 ZX Platinum. Now my second and third systems run off of the onboard
nforce 530 chipset and they do not exhibit this annomily.

Also it must be stated that all of the drivers are beta as well as the OS.
there
could be an unknow conflict between the said application and the drivers used.
tho i do not yet know the function of this program i can tell you that it
for lack of
a better was to describe it neither harmless nor harmfull it just seems to
eat
tons of resources some time and yet other times it just runs perfect i do feel
that it is on a system to system basis.
 
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.
 
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.
 
Back
Top