Unsolved

This post is more than 5 years old

53 Posts

695

January 6th, 2004 17:00

nt authority/remote procedure call

my new dell should be here today,,was reformatting my 8100 to give to friend..Every time I go online,,get the dreaded red X error saying nt authority/system,,will shut down , remote procedure call was initiated. Any help here,,only happens when I go online with broadband connection. going through modem now..doesn't happen..have deleted connection and made new one,,,same results.

2 Intern

 • 

2K Posts

January 6th, 2004 17:00

That would be the MSBlaster virus. See the post here.

100 Posts

January 6th, 2004 17:00

hotheads,

After you have successfully removed the virus from your computer (following the directions provided by ddeerrff's link, and at http://support.dell.com/us/en/kb/document.asp?dn=1083290),  I would suggest installing firewall software such as ZoneAlarm.  At the very least, turn on Internet Connection Firewall (see this link http://support.microsoft.com/default.aspx?scid=kb;en-us;283673&Product=winxp)

53 Posts

January 6th, 2004 18:00

thanks dd,,so far so good,,,now how in the world do you figure that could happen,,,had absolutly no probs with this 8100 ,,kept norton running all the time. but when I did a clean install,,,this came up,,,my own paid for copy of xp professional.only thing I did after fresh install was make network connection...no other software installed..

2 Intern

 • 

4.4K Posts

January 6th, 2004 18:00

After the clean install you have to reinstall all the critical and security Windows updates, starting with SP1 if that is not included in your CD. Amongst other is the blaster worm hotfix. So when you went on line, the worm bit you (assuming that you did not have the firewall on).

53 Posts

January 6th, 2004 18:00

excellent info from all of you and thanks.expecting my new xps today with the 17" lcd,,trying to get this one up to par...always worked great,,just wanted to update..didn't want to give someone a problem machine.

2 Intern

 • 

2K Posts

January 6th, 2004 19:00

Before you go online, be sure you have the WindowsXP built-in fire wall enabled. The MSBlaster worm is still out there in the wild and an unprotected machine can be infected within 30 seconds of going online. The firewall will protect you until you can get the critical/security updates installed. The updates close the security hole.

2 Intern

 • 

2.2K Posts

January 6th, 2004 21:00

That Blaster was a real pain. Thinking for some reason     that the installed McAfee was activated, I went online only long enough to register my new 4600 back in August, during the same weekend that the virus was raising havoc. That was all it took.     What a hassle for a day or two to get things cleaned up...learned my lesson. Even if the pre-installed McAfee had been activated, it would not have been updated to detect Blaster, as far as I know. Was going to remove the McAfee and install Norton as soon as I had the computer all fired up

Not sure what would have happened if I had installed NIS 2004 and then went online to Symantec for all the live updates. I assume  that as long as your have NIS enabled and the Antivirus on auto-protect you are safe from new viruses   while downloading the updates... for the new definitions that cover the new virus.  Or not.....I have never been quite clear on this point.  Thanks for any input. 

2 Intern

 • 

4.4K Posts

January 6th, 2004 21:00

You are not protected from new viruses whilst downloading virus definition updates. Only after they have auto installed at the end of the download would the new definitions take effect. So after a clean install, including your AV, you would have outdated virus definition (corresponding to the ones on your installation disk), and unless you have the firewall switched on you will be vulnerable to blaster (and others) until after you have downloaded and installed the new virus definitions and/or installed the critical updates. 

2 Intern

 • 

2K Posts

January 7th, 2004 03:00

Besides, IFAIK, MSBlaster is not really a virus, but a worm that crawled in through a security hole in Windows. Even a perfectly up to date AV program wouldn't stop it. A firewall could keep it out, and a MS hotfix plugged the security hole.
No Events found!

Top