Can you give me some information about shut down

Epokhe · 25 Dec 2011

You know windows 7 shutdown screen, first "logging off" and after "shutting down". Due to a problem which I don't exactly know how it first started, shut down time of my laptop slowed from 20-25 seconds(i think) to 1-2 minutes. But "logging off" text disappears in 1-2 seconds and then "shutting down" part lasts very long. Problem is in this part, I know it but in shutting down part, what happens? Are tasks, services, all of them closed in this stage? Is there a program that can show me the order of closing programs in shutting down part? ~~And I want to add one thing more, if I don't log in my windows 7 account, only turn off the computer and turn on then, it shuts down very easily.~~This part is NOT true from now on... Some advice, please? And sorry for my english if I've made a mistake.

scrooge · 25 Dec 2011

see if this help you.
Shut Down -Speed Up

scrooge

Epokhe · 25 Dec 2011

I know this trick, but it doesn't properly closes programs. I want to find out what my problem stem from; if some programs conflict, I want to know what they are.

Epokhe · 26 Dec 2011

At least say that there is no way to see the shut down stage in details.

I want to know only if I can do or not.

Ztruker · 26 Dec 2011

I cannot find any mention of a way to record/trace/monitor the shutdown process.

When did this start happening? Did you add or remove any programs around that time? How does it behave if you boot to Safe Mode with Networking then do a shutdown?

If better then something is running that is causing the slow shutdown.

Is the shutdown slow if you boot the computer, wait a minute or two then shutdown without starting any other programs? If yes then something is starting at boot time that is causing the problem.

Advanced startup options - XP
Advanced startup options - Vista
Advanced startup options - Windows 7

Use msconfig to determine what is causing the problem

These are good tutorials on using msconfig in XP, Vista or Windows 7:
How to use msconfig in Windows XP
How to use msconfig in Windows Vista
How to use msconfig in Windows 7

Click on Start then Run, type msconfig and press Enter.
Click on the Startup tab, record what is currently starting then click the Disable All button.
Reboot and see if it runs better.
If yes then use msconfig to enable several items at a time till you find the culprit.

If no, start msconfig and click on the Services tab.
Check the Hide All Microsoft Services box, record what is currently starting then click the Disable All button.
Again, do a regular boot, see if it runs normal.
If yes then use msconfig to enable services till you find the culprit.

Once you've found the culprit, uninstall it or find out how to eliminate it from your system. Simply disabling it in msconfig is a temporary fix at best.
Enable everything else you disabled.

Another way to debug this is to start killing processes in Task Manager a few at a time and trying shutdown, until you find the one that is causing the slowdown. This will take some time but it should work. Stick with non Microsoft process initially.

Epokhe · 27 Dec 2011

Heheh, the times aren't as I hoped

.
Using computer 5-10 minutes and shut down-2 minutes 45 seconds
Safe Mode with Networking-2 minutes 34 seconds(improvement

)
Only turn on the computer and then without logging on shut down-(you see right)3 minutes 5 seconds

It started after I used dr. web live cd.
http://www.freedrweb.com/livecd/?lng=en
I might have used the cd or written the image wrong but I remember that it wasn't working in graphics mode, and after I tried to scan with non-graphic interface, it stopped the middle of the scan and you know, long error mesages... I couldn't turn off the computer by pushing the key or couldn't type anything, so with 5 sec push I turned it off. I remember doing this shut down several times with this cd, because it caused problems more than one. Anyway, maybe it is because of the scan, or many 5 sec push shut downs over and over. I have ubuntu 11.10 also, ~~now I will open Ubuntu and shut down then, and tell you if it is like Windows or not.~~ Ubuntu is shutting down in 18 seconds :). At least, we now know that it is not about machine, it is about windows 7.

**cluberti** · 27 Dec 2011

There is indeed a way to monitor the shutdown process. You can take a shutdown trace:
Gathering a Startup, Shutdown, Sleep, Hibernate, or Reboot Trace

Ztruker · 28 Dec 2011

Thank you, that is excellent. I'll have to give it a try soon.

Might be nice to have a now, shutdown good trace to compare against a then, shutdown slow trace.

Epokhe · 28 Dec 2011

I had a shutdown trace, at last. I say "at last", because I couldn't install the SDK first, it didn't give a proper error text. I tried the registry solution which is on an internet site, it didn't work. Then I opened its log, saw the problem in it, there was a conflict between SDK and vcredist_x(64 or 86, one of which had been installed) package. SDK can't be installed if microsoft visual c++ redistributable x64 or x86 is already installed, or I can't find a way to do.

Ztruker said:

Thank you, that is excellent. I'll have to give it a try soon.

If you have those packages installed, first uninstall them not to have a problem like me.

cluberti said:

There is indeed a way to monitor the shutdown process. You can take a shutdown trace:
Gathering a Startup, Shutdown, Sleep, Hibernate, or Reboot Trace

And yes, thanks to you, I took the trace, opened the .etl file. It showed some graphs. Because up-downloading the .etl file will take long time, I took pictures of the graphs:
http://img685.imageshack.us/img685/373/ithinkididit.png
I think there are some weird things in the graph:
1. WSearch Stop, as you see, lasts about 80 seconds.
2. nvUpdatusService Stop, lasts 6 seconds. It is not much weird, I only want to know whether I can stop this service completely to reduce the time because it is only an update service.
3. The most weird one, or I didn't think on it enough. My computer didn't shut down in 86 seconds. I looked the chronometer, it shutted down in 2 minutes 40 seconds

. However, in the graph is shown 86 seconds. And I can't go right in the program. Maybe it is the limit of the program and if I can fix this WSearch thing, I can see the rest of the graph

.
I must sleep now, and I will try to completely close the service "windows search" tomorrow. If you have any other idea, please tell me.

And Ztruker, we have this proverb(in your sign) in our country too, but a little different.
Our proverb is "It is not shameful not to know, it is so not to learn." I think both come from the same thought but they are evolutionized by the cultural differences. Actually I liked the african one more

.

**cluberti** · 28 Dec 2011

Indeed, wsearch taking that long to stop is interesting. What would be more interesting would be if you looked at the summary details of the Disk I/O graph, because it shows (where the all blue lines start) an insanely high number of disk writes - blue - versus reads - red. Taking a look at the summary graph (right click the disk I/O graph and select summary to open that detail) and seeing which process, and to which file(s) all of the write I/O and time goes, would probably give you a hint as to what's happening.