Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: bertil on July 19, 2005, 08:36:06 AM
-
Good morning!
It sometimes takes rather long time to shutdown windows.
When XP SP2 shows the normal blue screen on exit
the time the message "loggin you of" shows is ok,
the time the message "saving your settings" shows in ok,
the time the message "windows is closing" shows is rather long (2-3 minutes)
When avast is disabled the shut down process is normal.
Is it possible to debug this situation?
Regards,
Bertil
-
And good morning to you too Bertil !
To solve this " problem" (and many others ;D ) it is advisable to download this tiny little program and tick the box that says "enable fast shutdown".
This way, windows won't wait for running processes to end but "kill" them gently and shut down, period.
It works well and has no negative side-effects.
The description and option to download can be found here :
http://www.snapfiles.com/get/xpantispy.html
Good luck,
Fast
-
If I want to shutdown my system real fast, I just use the power button on it
-
Hey Eddy, I guess your kidding huh ?
I did this once and at the next boot, it took 5 minutes for a harddisk-scan before windows booted, so I guess this is meant as a joke ?
Fast 8)
-
No I am not kidding. I really do it. No problems at all when doing so.
Only thing is that if you changed some settings they will not be safed, but that's all.
-
If I want to shutdown my system real fast, I just use the power button on it
Fast,
you can configure what should be done, when the power button is pressed. And indeed the shutdown seems to be really quick this way.
-
I'm stunned !
I really thought when shutting down this way, the most terrible things would happen, smoke coming out of the pc-case and so on ;D
So, how do you configure it in windows xp ?
And is there a gracious way to exit windows with the keyboard (like in SuSE ctrl+alt+backspace/alt+s) when the system hangs when exiting ?
Fast :)
-
So, how do you configure it in windows xp ?
Control Panel - Power Options - Advanced
Of course the system should be shut down before powering off. And this is the reason why ATX motherboards does not turn the power imediately off, but instead signal this to be handled by OS.
-
Thank you for the info. When I'm at the windows pc this afternoon I will have a look at it.
Bye :)
-
On my system Holding in the power button (not reset) for 5 seconds shuts down the system and generally there are no problems, like having to check the drives on the next boot. It is not something that I do regularly.
If people are deleting/clearing the page file on exit this can slow the exit considerably.
-
Hint: The time it takes to hold down the power button before the system shuts down can often be set in the bios.
-
And what if the systems "hangs"?
Is there a keyboard-combination (as described above in SuSE) to shut down the system immediately in a non-destructive manner ?
When I try ctrl+alt+del the same thing happens: on boot, windows complains it isn't shut-down gracefully and starts a disc-scan before booting the operating system.
Sorry this is getting off-topic
-
If the system really hangs, it won't respond to anything, not in Windows nor in *nix.
-
Getting back on topic, I also noticed my system takes longer to shut down since avast has been installed. Same thing on my friend's system where I installed avast. It is not always consistant though. Sometimes is does shutdown normally but many times it takes a while now. I wish this could be debugged. I don't want to install a third-party app to shutdown.
-
Such problems are almost impossible to debug (at least without the aid of the kernel debugger). This is because the system refuses to load any monitoring tools at this stage - it just sits there and waits for something - without the ability to determine for what it's waiting...
-
I get these Application warnings when this happens.
Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 7/15/2005
Time: 9:52:09 PM
User: NT AUTHORITY\SYSTEM
Computer: xxx
Description:
Windows saved user xxx\yyy registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
-
Good morning again!
Thank you very much for all feedback!
I have tried msconfig and disabled some services but it takes too much time to disable/enable services. From time to time the system shudown is normal and I can't trust that the disabled sevice was the cause.
I think it would be funny to find out the cause of this shutdown delay.
Microsoft has some KB articles about shut down problems (eg USB).
Is it possible to enable logging in Avast in this late stage?
I would like to try a debugger, please tell me more!
Regards
Bertil
-
I get these Application warnings when this happens.
Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 7/15/2005
Time: 9:52:09 PM
User: NT AUTHORITY\SYSTEM
Computer: xxx
Description:
Windows saved user xxx\yyy registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
I think the shutdown process is a three or more step process.
First a logoff process
Then a save settings process
I think the above happens while windows displays "saving your settings" during the shut down process?
Then a terminate process process
In my case windows hang during "windows is shuting down".
Regards
Bertil
-
Good evening!
Perhaps this is the wrong forum for this...
I now have a dump when XP is in the "slow shut down state" waiting for something.
I have also got the debuger running and have loaded the dump file into it.
Does anyone have a clue where to start looking?
Regards
Bertil
-
I get these Application warnings when this happens.
Windows saved user xxx\yyy registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
I don't understand ? Please explain.
-
This really isn't a problem, I occasionaly get this error a program is running in the background that has something still loaded in memory. For me I believe it is SnagIt when I have done an image capture, that is likely to be in memory untill saved to the HDD. I'm not sure if this is/should be cleared from memory when saved to disk.
1. it is only a warning and not a full blown error.
2. unless it happens every time, trying to find the culprit is more hassle than the warning in the event logs.
3. relax, don't worry, be happy ;D
-
Good morning!
I wonder if the dumpentry in the enclosed file is of any use?
Regards
Bertil
-
Might Avast be checking all modified and changed files before shutting down?
You could test this by temporarily disabling that function and seeing whether shutdown speeds up.
But, on my computer, when I hit start/shutdown/restart, the first thing that seems to happen is that Avast shuts down and puts the little red x on its icon. I believe it's my firewall (Sygate Pro), that actually slows the shut down process...but it is impossible to be sure.
Louise
-
Might Avast be checking all modified and changed files before shutting down?
Don't know.
The dump is taken when XP seems to do nothing but wait during a 3 minute period just before power off.
You could test this by temporarily disabling that function and seeing whether shutdown speeds up.
Yes, with ashServ.exe disabled everyting is fine.
I believe it's my firewall (Sygate Pro), that actually slows the shut down process...but it is impossible to be sure.
I have tried with a sygate disable but that does not help.
Regards
Bertil
-
Such problems are almost impossible to debug (at least without the aid of the kernel debugger). This is because the system refuses to load any monitoring tools at this stage - it just sits there and waits for something - without the ability to determine for what it's waiting...
Ok.
Do you think it's possible by inspecting the dump?
Regards
Bertil