Remote Procedure Call (RPC)", shutdown, not blaster Virus!

[Pottsey]

No staff are in today so I took the opportunity to make sure all the computers are up-to-date. Upon reboot after afew updates 1 computer did a scandisk fond some errors now it refuse’s to work. Shortly after login in I get Remote Procedure Call RPC Service Termination unexpectedly, then a timer before a shutdown.

Everywhere I look says it’s the blater Viryus. I don’t see how that’s possbile, its got SP2, an up-to-date Virus checker and at most the security updates where a month old if that. Any ideas on what else could cause the problem?

[rvdmast]

First thing to try is to type

shutdown -a

in start-run, this will (hopefully) abort the pending shutdown and give you time to troubleshooot.
It might buy time to complete a full virusscan.
next thing to try is typing this in start-run:

SFC /SCANNOW

this will check the integrity of your windows
files & put them back from the original CD if needed.

[Pottsey]

This is bugging me now. 4 more workstations are doing the same thing, they all have the same symptoms and act like they have the blaster virus. Only there is no virus as they are all updated. It appears one of the windows updates has causeed the problem.

shutdown –a works but you have to type it every 2 mins. SFC /SCANNOW starts but never seems to do anything. The bar doesn’t move.

[localzuk]

Try running the SFC scan in safe mode.

[PEO]

isolate the machines from the network. Just in case

[Pottsey]

SFC doesn’t run in safe mode. System Restore won’t load, cannot even view event viewer or device manager either in safe mode or in normal boot.

Pretty much only leaves me with boot from XP CD, repair install but that will have to wait till next year. Have a good holiday all.

[localzuk]

It sounds like they are mucked up in a big way. I'd do a re-install/re-image.

[chesspdh]

I came to this page by searching on 'not blaster'. I was thinking 'not' because when I right clicked on the first remote procedure call listed, hoping to click on properties, nothing came up? Also the machine was updated to service pack 2? However, after running 'shutdown -a' in safe mode I was able to run a blaster fix {Symantec} tool to completion. {I did have to run 'shutdown -a' several times during the course of the fix, as the shutdown warning continued to pop up periodically.} After the tool had finished and I rebooted the machine displayed no more symptoms. I'm thinking now a variation of 'blaster'? Thanks for the tip.

[synaesthesia]

Threadnomancy!
Blaster was damned good fun, not even close to annoyance levels of Conficker but still something to tickle the fancy of the average technical bod