Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Forced system shutdown

May 30, 2005 4:24PM PDT

I have a number processes listed as running. And like usual its hard to tell which processes belong to which program. As far as I know in XP pro, only two of those processes are critical, the rest should be able to be shut down and yet windows still run. But apparently shutting down one or more of these processes causes a pop up that shuts down your computer in 60 seconds.

The first time it happened was when I was in display properties and the box went buggy, I tried to close it and a pop up told me that it was no longer responding, would I like to close it. I said yes and the 60 second close down box came up.

Second time it happened was when i was trying to follow the suggested instructions for a different issue, he wanted me to rename some folders. When i tried it told me I couldn't because a file in it was in use. I started shutting down processes to allow a renaming.

Just recently I started shutting down processes just to see which one triggered it and managed to get a screen shot before the 60 seconds was up (it was real close though, fumbling with ms paint and save paths)

I got a number of processes all called svchost.exe running. What triggered it was shutting down one of those svchosts (not any one of them, the first 4 or 5 or so shut down fine without triggering it)

The message is:
This system is shutting down. Please save all work in progress and log off. Any unsaved changes will be lost. This shutdown was initiated by NT AUTHORITY\SYSTEM

Time before shutdown: (starts out at 60 seconds and counts down)

Message
Windows must now restart because the Remote Procedure Call (RCP) service terminated unexpectedly.

I have a screen shot if anyone wants to see it and can tell me of a way to attach images to cnet posts or another way for me to send it to you.

Discussion is locked

- Collapse -
(NT) (NT) BTW I have done a online virus scan and a ad aware scan
May 30, 2005 4:41PM PDT
- Collapse -
Google is your friend
May 30, 2005 10:47PM PDT

If you want to know what processes do what, type the name into Google and see what comes up. Rinse and repeat until you're out of processes you can't identify.

- Collapse -
solution
May 30, 2005 10:58PM PDT

well, first adjust ur date in ur system to few days later, this will increase the system shutdown time.

next, get microsoft antispyware beta, its free and best of all. i'm not sure which one triggered it but it happened to me once and i solved it this way.
i hope this would help

- Collapse -
Adjust the date?
May 31, 2005 12:40AM PDT
- Collapse -
Back to the main issue.
Jun 4, 2005 7:04PM PDT

Identifing processes running is only a small portion of this issue. The main issue is this forced shut down. I've tried a host of antispyware programs and both avg and microprose online virus scans. They haven't found anything that getting ride of fixed.[the issue that is]

Does someone know something about this problem?