XP takes forever to shut down - Tilted Forum Project Discussion Community

F-18_Driver · 04-13-2005, 11:10 PM

This isn't life or death, but it's annoying.

I have a fair amount of programs running in Windows XP, but the machine has pretty decent horsepower and a gig of memory.

If I start up and shut down within a few minutes, everything seems to be okay. However, after the computer has been on for awhile, when I hit "start" and "shut down" I am privileged to stare at an hourglass for about a minute before I'm presented with the opportunity to hit "turn off."

At first I thought it was a non-responsive background program, but I never get a message saying so, and if I cancel the first shutdown, and try again, it takes just as long.

Anyone have any ideas, or suggestions on how to get to the bottom of it?

Thanks.

superiorrain · 04-14-2005, 12:40 AM

This is a tweeking program i use http://www.softpedia.com/get/Tweak/S...H-TuneXP.shtml
It certainly cut my shut down and start up time. Might be worth a look.

feelgood · 04-14-2005, 03:50 AM

Before you shutdown, go to the Taskmanager and take at look at which process is taking up alot of CPU and memory.

F-18_Driver · 04-16-2005, 05:19 PM

Thanks for the suggestions. (Got bogged down with taxes--sorry to take so long.)

Svchost took up the most memory, but when I checked CPU usage, 97% was in use by "system idle."

I have a feeling that's the problem, but it would be nice if someone who actually knows what they're doing (meaning, someone other than myself) offered some advice.

Thanks again.

phukraut · 04-16-2005, 05:29 PM

System idle means the cpu cycles are not being used. My advice: manually close down everything nonessential (through TaskManager), then try again. That ought to tell you if a rogue program is the problem. You can also try to manually shut down as many services as you can---maybe you will hunt down one that isn't working right. You can access this list by going to Run (Win+R) and type in services.msc and press enter.

vinaur · 04-17-2005, 06:50 AM

If you messed with windows configurations (Using TuneUp Utilities for instance) you might have checked the option to delete the paging file on shutdown. This could cause a rather prolonged shutdown.

F-18_Driver · 05-02-2005, 12:08 PM

Finally figured it out. However, I learned a few things en route-tried Tune XP and a program someone somewhere suggested called Currprocess.

However, the problem was somehow related to a KVM switch I have. Once I finally farted around with that a little bit, the problem went away.

Thanks for the suggestions. Like I said, I learned from them.

skaven · 05-02-2005, 07:50 PM

I know you've already fixed your problem, but I used to have the same problem due to mapped network drives. For some reason Windows would just sit there and hang trying to unmount network drives. As I recall...I ceased having this problem when I set up a Linux/Samba file server.

...And then I ditched Windows on my desktop too and switched to NFS ;-)

04-13-2005, 11:10 PM	#1 (permalink)
F-18_Driver Loser Location: Check your six.	XP takes forever to shut down This isn't life or death, but it's annoying. I have a fair amount of programs running in Windows XP, but the machine has pretty decent horsepower and a gig of memory. If I start up and shut down within a few minutes, everything seems to be okay. However, after the computer has been on for awhile, when I hit "start" and "shut down" I am privileged to stare at an hourglass for about a minute before I'm presented with the opportunity to hit "turn off." At first I thought it was a non-responsive background program, but I never get a message saying so, and if I cancel the first shutdown, and try again, it takes just as long. Anyone have any ideas, or suggestions on how to get to the bottom of it? Thanks.

04-14-2005, 12:40 AM	#2 (permalink)
superiorrain Psycho Location: London	This is a tweeking program i use http://www.softpedia.com/get/Tweak/S...H-TuneXP.shtml It certainly cut my shut down and start up time. Might be worth a look. __________________ "The only way to discover the limits of the possible is to go beyond them into the impossible." - Arthur C. Clarke

04-14-2005, 03:50 AM	#3 (permalink)
feelgood Free Mars! Location: I dunno, there's white people around me saying "eh" all the time	Before you shutdown, go to the Taskmanager and take at look at which process is taking up alot of CPU and memory. __________________ Looking out the window, that's an act of war. Staring at my shoes, that's an act of war. Committing an act of war? Oh you better believe that's an act of war

04-17-2005, 06:50 AM	#6 (permalink)
vinaur Insane	If you messed with windows configurations (Using TuneUp Utilities for instance) you might have checked the option to delete the paging file on shutdown. This could cause a rather prolonged shutdown. __________________ If you multiply that by infinity and take it to the depths of forever, you will, perhaps, get just a glimpse of what I am talking about. --Meet Joe Black--

04-16-2005, 05:19 PM	#4 (permalink)
F-18_Driver Loser Location: Check your six.	Thanks for the suggestions. (Got bogged down with taxes--sorry to take so long.) Svchost took up the most memory, but when I checked CPU usage, 97% was in use by "system idle." I have a feeling that's the problem, but it would be nice if someone who actually knows what they're doing (meaning, someone other than myself) offered some advice. Thanks again.

04-16-2005, 05:29 PM	#5 (permalink)
phukraut Addict	System idle means the cpu cycles are not being used. My advice: manually close down everything nonessential (through TaskManager), then try again. That ought to tell you if a rogue program is the problem. You can also try to manually shut down as many services as you can---maybe you will hunt down one that isn't working right. You can access this list by going to Run (Win+R) and type in services.msc and press enter.

05-02-2005, 12:08 PM	#7 (permalink)
F-18_Driver Loser Location: Check your six.	Finally figured it out. However, I learned a few things en route-tried Tune XP and a program someone somewhere suggested called Currprocess. However, the problem was somehow related to a KVM switch I have. Once I finally farted around with that a little bit, the problem went away. Thanks for the suggestions. Like I said, I learned from them.

05-02-2005, 07:50 PM	#8 (permalink)
skaven Insane Location: Austin, TX	I know you've already fixed your problem, but I used to have the same problem due to mapped network drives. For some reason Windows would just sit there and hang trying to unmount network drives. As I recall...I ceased having this problem when I set up a Linux/Samba file server. ...And then I ditched Windows on my desktop too and switched to NFS ;-)