RPC Service Fatal Error (crash/reboot), XP Pro. Help please!

[EBGIRL]

This is very interesting thanks. I have been struggling with W32.Spybot.worm for 4 days, and one of the quarantined files is webdav.exe. , application file C:\Doc and settings\All users\Start Menu

I noticed that 2 days before this worm was discovered by NortonAV, that i was getting the rebooting problem like you state.
And given so many are flocking here via google with the same problem, you might read the W32.Spybot.worm post.

I HAVE SEVEN FILES QUARANTINED, AND ONE IS THE ABOVE. [webdav.exe]tHE ONE FINAL PROBLEM IS IT

the virus IS INSTALLED IN THE MSCONFIG.32.EXE file. Major prob.
If this is not a virus, but some misled spybot garbage, I sure would like to find out BEFORE reformatting! Guess I will keep checking in here, as our problems are similar. And, no I do not have Kazza, but do download freeware for graphic installations into Paintshoppro. Do you think we have a bigger problem out there than Norton has let on? Noticing how many came here in just a few days, makes me wonder...Norton calls this virus rare, but it sure doesnt look that way to me. Thanks.

[ezz]

I have the same problem also. Used www.anitvirus.com and it found one virus in two locations. ADW TENGET.A the files were c:\prgramfiles\filesubmit\shine xp\nlp38.exe , and c:\windows\system\winstart001.exe..deleted them.
Ive installed the patch, and stoped sharing my folders (read somewhere else about that)

ALSO I ran a scan with norton and it didnt find anything. While i was writing this it found the Backdoor.sdbot virus..Source: C:\temp\V60K3Fa06112.. deleted it. That has something to do with IRC so i dont think that would be the problem, but the first time i have ever encountered it.


After deleting and patching I havent had the problem in about an hour.

[ezz]

Well its been forever so I think the patch worked.. also the entire folder, filesubmit, where the virus was found was BS. so if your having this problem check and remove that folder. nobody has been posting on this so i guess the patch worked for everyone.

[njovin]

you need to read all of the info in this thread and REMOVE the trojan before you install the patch. That is probably what is preventing the patch from installing, just like on many systems it prevents the msconfig or taskmgr programs from running. So follow the directions for removing the trojan and THEN do the update so you don't get hit again.

[ESALADUANE]

Here are two tools that you need. Install the patch first. Also, make sure you have and are using a firewall.

Patch from Microsoft:
http://support.microsoft.com/default...b;en-us;823980

or here:
http://www.microsoft.com/technet/tre...n/MS03-026.asp

Removal tool for W32.Blaster.Worm
http://www.symantec.com/avcenter/ven...ster.worm.html

[jrolen]

I have no grapics on my computor .The only thing that will come up is windows xp and then the screen gose blank.I have tride to get into my bios and I guess I am not doing it correctly .when I try to stat up in safe mode it gives me a list of drivers I have no idea what I am suppose to do with them

[joe113]

Hi, I'm new here. I got the error, The Remote Procedure Call (RPC) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Reboot the machine. It happened overnight. As I don't have the blaster worm or any other virus or trojan's on the machine and I have the patch since it came out, I was wondering what are the other reasons that this error message would come up. Thanks in advance,

Joe.

[PurpleHaze]

I had the exact same problem, very frustrating. I tried everything mentioned in this forum and anything else I could find. In one of the forums, somebody said it's a memory problem and everybody flamed him for such a ridiculous solution. I laughed at it a bit too, but I'll be damned if he wasn't right.

In my case, I had my memory timings tightened up a bit and everything ran smoothly all winter. When it got warmer and the CPU was running at a heavy load was when I started getting the problem. My temps didn't seem out of line, so I never thought it might be an overheating issue but all I needed to to was let bios autodetect my memory settings and I haven't had any problems since.

Might not be the solution for everyone, but it worked for me.