RPC Call Terminated Unexpectedly

  • Thread starter Thread starter Edward W. Thompson
  • Start date Start date
E

Edward W. Thompson

I am running WINXP Pro SP2 and have both NOD32 and Kaspersky AVPs installed
together with Ad-Aware and Spybot Search and Rescue. All programs are fully
up to date.

I have just started to get the message 'Remote Procedure Call terminated
unexpectedly' that restarts the machine automatically. The problem occurs
at infrequent intervals, say once a day. I haven't associated the problem
with any particular activity as yet.

I have checked for the 'blaster worm' (Symantec fixblast.exe) but nothing
was found. I have just changed the Remote Procedure Call Services to 1st
and 2nd to restart service and 3rd to machine restart and don't yet know how
successful that will be in masking the problem..

Does anyone have any idea what the cause of the problem might be and how to
address it rather than mask it as I have tried to do.
 
Thanks Chas. Yes, I do run both AVPs full time as well as Spyguard,
Teatimer (Spybot) and Ad-Watch (Paranoid? What me?). I didn't realize that
that can cause a RPC Call problem. As the 'problem' is intermittent I think
I may try to live with it to preserve my peace of mind re virus/malware
infections, further don't know yet how effective the resetting the RPC
reset/restart properties is yet.

Many thanks for your pointer to the possible cause of the problem which may
be traceable to when I installed Kaspersky as a 'belt and braces' virus
protection.
 
Edward said:
I am running WINXP Pro SP2 and have both NOD32 and Kaspersky AVPs installed
together with Ad-Aware and Spybot Search and Rescue. All programs are fully
up to date.

I have just started to get the message 'Remote Procedure Call terminated
unexpectedly' that restarts the machine automatically. The problem occurs
at infrequent intervals, say once a day. I haven't associated the problem
with any particular activity as yet.

I have checked for the 'blaster worm' (Symantec fixblast.exe) but nothing
was found. I have just changed the Remote Procedure Call Services to 1st
and 2nd to restart service and 3rd to machine restart and don't yet know how
successful that will be in masking the problem..
Click to expand...

It may well be a Blaster family worm, without being one the Symantec fix
deals with. You need

1. Make sure you have a firewall in place and that it is blocking the
NetBIOS ports on your internet connection (the original XP one before
SP1 did not do this by default)

2. A wider range of fixes - see
http://www.kellys-korner-xp.com/xp_w.htm#worm
 
Back
Top