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 No 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 No comments

59 additional answers

Sort by: Newest
  1. Anonymous
    2009-12-19T20:29:31+00:00

    Yes, I did a safety scan, and it was just a bunch of problems related to the java software. I scanned with AVG as well, and no problems were found; used SuperAnti-Spyware, too. I turned off system restore because I didn't really think I needed it, because, I usually just do a new installation if something gets too bad.

    My sound works, and it appears on the taskbar, it's just that I can't use the control panel to adjust the audio even though I can use the soundmax one. My scanner won't work either, still. I had done the second new install mainly because the scanner just wouldn't start out of nowhere, now the problem has randomly returned.

    One thing, though. Before the new installation after a year had passed, I had never installed the .net framework 4.0 beta 2. Even though I uninstalled it, I think there might've been some wrong doings somewhere when I did, and the problem presented itself later, but even reinstalling it didn't change anything afterwards.

    Was this answer helpful?

    0 comments No comments
  2. 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

  3. Anonymous
    2009-12-19T18:03:27+00:00

    Thanks for your input Feruken.  Lets hope the Support Engr's can come up with something to help us both.

    Was wondering, did you do any of the things listed in Mary's suggestions above? 

    Best regards,

    RT

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2009-12-19T11:40:45+00:00

    I'm having this problem, too along with another one, and they seem to be from the same source. I've had this problem before after doing a new installation, then I couldn't figure it out and thought that it was my fault, and went ahead and did a new install.

    After the new installation everything was back to normal. About two days later I started getting the same errors. I'm getting it with sndvol32.exe, and with mpnex20.exe. This just came out of nowhere, when I try to open volume control the error pops up, and when I try to use my scanner (Canon) as well.

    I did a memtest scan and no problems came up with my ram. I reinstalled the scanner drivers, and the problem is still there. I'm not sure what is associated with helping to run these applications, but these problems just randomnly came up while regularly using the pc.

    So this is the second time now, after the new install. I did a new installation to begin with because my last install was a year old. I didn't have these problems at all, all that time until after the new install.

    I'm not sure, but could it have anything to do with .net framework? I'm using Windows XP Home Edition with Service Pack 3.

    Was this answer helpful?

    0 comments No comments