APPLICATION ERROR

Anonymous
2009-12-08T18:37:45+00:00

I lost all sound on my computer.  When I try to click on the sound volumn icon on my desk top I get the following error message:

 SNDVOL32.EXEC APPLICATION ERROR

The application failed to initalize properly(0xc0000005)

I have already downloaded new sound drivers off the internet but that didn't fix the problem.

Any ideas out there?  Pleae help..........  I need my sound back on.

Many thanks,

RT

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2010-01-08T22:08:14+00:00

WELL GLORY HALALUYA, I'VE GOT SOUND !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1

Here's what I did:  Restarted my computer in safe mode and clicked on "Last Known Configuration that Worked."  I then reloaded new sound drivers again (REALTECK AC97) and low and behold sound came back............

That's all I know. 

We'll see how long it last but for now I am one happy camper !

Again my personal thanks to each and every one of you who contributed to this post.  If I could I'd buy you all a beer !

Sincerely,

RT

Was this answer helpful?

0 comments

59 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2010-01-18T04:55:33+00:00

    I had the same problem. I did what Faizz suggested and my problem is gone. Thanks for the help!!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-01-17T05:39:41+00:00

    You guys are awesome!  I knew that once I got back from vacation, it would be figured out.  The registry fix of changing "aux" from "c:\windows\system32\wdmaud.drv" to "wdmaud.drv" worked for me too!  Thanks.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2010-01-13T22:41:03+00:00

    Sos un groso chabon

    You are the bigone!!!!!!!

    Was this answer helpful?

    0 comments