audiodg.exe permanently freezes

Jan 13, 2016 1:22PM PST

Hey guys,

I've got a problem with audiodg.exe, it freezes forever when I go to the "recording" tab and try to click on either of my two connected USB recording devices.

I'm using a Genesis USB headset and a Behringer Xenyx303 USB interface with a Shure mic plugged in. Both devices work fine on their own, but I'm completely unable to access them via audiodg, as the application will stop responding permanently. What's interesting, after the app goes blurry I can immediately terminate it just by clicking the "X" button and shutting down the process, but the process will remain in the list after this is done.

All the sound and USB drivers are up to date, there is very likely no driver conflict and both devices otherwise work fine. Their drivers have also been uninstalled and reinstalled ad infinitum, nothing seems to fix the problem. It is very important for me to be able to access these option menus for these two devices, without it I find myself unable to do any recordings.

My computer is an Acer emachines E725 laptop and the system's Win7 Ultimate 32-bit. I can provide any additional information you request. Please advise!

Discussion is locked

Reply to: audiodg.exe permanently freezes
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: audiodg.exe permanently freezes
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
- Collapse -
I'd try it with the OS the machine came with.
Jan 13, 2016 1:33PM PST
- Collapse -
not quite.
Jan 13, 2016 1:46PM PST

Thanks for the reply! I'll add a few things:
- The machine was supplied with Vista Home Basic 32 actually. Ones currently sold may have win 7 64, but that one didn't (maybe it has something to do with the fact that it was purchased in Poland) I upgraded the system to Win 7 Ultimate after a few years of using the PC
- My problem is relatively new. It could have occurred at the earliest after November 13 2015, the day I used the interface successfully to make a recording. Nothing in particular has changed about my system since that day, including the operating system

- Collapse -
So I'm left with
Jan 13, 2016 1:54PM PST

A machine failure (hardware) or another "not the OS the laptop came with" issue. Remember the clues in your post don't point to anything in particular. There is something about audiodg that is interesting. ""audiodg.exe" is a part of Windows Vista and Windows 7. System services like audio drivers run in different and isolated login session from the locally logged-in user in Windows Vista or Windows 7."

Now once in a while I run into machines corrupted by registry cleaners which can mess up those isolated login sessions. So far I hate to write this but when that happens we try the factory OS to see if that clears it up. If the client is reluctant we swap in a new blank HDD to run the test.

- Collapse -
so could I try a repair-reinstall of my current system?
Jan 13, 2016 1:57PM PST

Since I'm positive the OS has nothing to do with this problem since I've not always had it - could an upgrade reinstallation of the OS address the problem of the messed up login sessions?

I'd also add that only the recording devices create problems - the playback devices are freely accessible and editable via audiodg.

- Collapse -
Jan 13, 2016 2:02PM PST

Also, you mentioned registry cleaners. I do recall running ComboFix a very short while ago - it is it that might have messed up those login sessions you talked about. So what would my optimal course of action be?

- Collapse -
As a test
Jan 13, 2016 2:18PM PST

I slip in a blank HDD to install the factory issue OS and test again. There are folk that want the current OS fixed but as many are finding out, this is occurring less and less and rarely on forums today.

- Collapse -
WOT rating isn't good.
Jan 13, 2016 2:26PM PST
- Collapse -
I think that's the imposter site.
Jan 13, 2016 2:28PM PST

Bleepingcomputer writes:
"You should not run ComboFix unless you are specifically asked to by a helper. Also, due to the power of this tool it is strongly advised that you do not attempt to act upon any of the information displayed by ComboFix without supervision from someone who has been properly trained. If you do so, it may lead to problems with the normal functionality of your computer."

But there are folk that run it and later, well, you can't predict what will happen. Here I only know the OS is not stock and that's been a problem too many times.

- Collapse -
Yeah, this is on me.
Jan 13, 2016 2:38PM PST

I've ran ComboFix many times with no problems already, but that sure isn't any justification, nor does it absolve me of guilt. The thing ComboFix screwed up this time is very minor on the grander scale, so it probably screwed up more of those minor things before - it's just that I didn't need those, and I need this one. I'll go with a repair installation and let you guys know how it went.

CNET Forums

Forum Info