svchost.exe application error

erice

Can anyone help me with this problem. I run Windows XP and all the update have been installed. I get this message over and over.

svchost.exe application error
The instruction at "0x009A96BC" referenced at "0X00000000" the memory
could not be "written".

Click on OK to terminate the program
Click on CANCEL to debug the program

I have tryed both without curing the problem.

Thrax

http://icrontic.com/articles/diagnose_with_memtest86

Please follow this guide and report back with your results.

BLuKnight

We ran into this one all the time back in my IT days. (Okay, yeah that was only 3 months ago.)

Quick question, if you acknowledge the error, does it freeze up your machine? If so, do the following but don't touch that error message. First of, disable Windows Update under the System Properties. Reboot the computer. Then do another Windows Update via http://windowsupdate.microsoft.com. Make sure you get the optional ones that apply to Windows only. After performing the update, reboot again. Turn on Windows Update and then reboot. That should do it. If not, there's a patch you can get from MS... but last I heard, it was part of the Windows updates. Let me know if this doesn't work and I'll see if I can dig up the link to the patch.

stoopid

That error literally means any windows service has gone belly-up. Generally when I see these errors nowadays it's because a piece of malware is using the process to execute itself on a PC. It is not an exe that relates to a specific application.

http://www.bleepingcomputer.com/tutorials/tutorial83.html

erice

OK I ran Memtest86+ and I got the following results;

In 3 passes I got 4 errors on Tst 5

0000F03DEE8 - 240.8 mb - Err-Bits 00002000 - Count Chain 1
Good FFFFDFFF Bad FFFFFFFF

0000F04F750 - 240.9 mb - Err-Bits 00002000 - Count Chain 1
Good FFFFDFFF Bad FFFFFFFF

0001003DEC8 - 256.8 mb - Err-Bits 00002000 - Count Chain 1
Good FFFFDFFF Bad FFFFFFFF

0001004F730 - 256.9 mb - Err-Bits 00002000 - Count Chain !
Good FFFFDFFF Bad FFFFFFFF

What Next?

Thrax

You have bad memory. If you have multiple sticks of RAM, run memtest on each one individually to find which one the bad one is. Throw the bad one out and replace it.

erice

Thrax wrote:

You have bad memory. If you have multiple sticks of RAM, run memtest on each one individually to find which one the bad one is. Throw the bad one out and replace it.

Thanks for the help - will do.