I had though my problem had been answered in another thread, only to find that his problem was a conflict with another AV program.
I have been experiencing shutdown problems - WinXP Pro SP1a fully updated. The duration of my shutdown has increased since I installed Avast 4 Home and on one occasion I thought it had hung completely so I manually shutdown (5 seconds on the power button).
I have checked my Event Viewer Logs and found a warning in the Application Log (copy below), although it doesn’t state which program, This Warning has cropped up regularly on shutdown since I installed Avast 4 Home.
Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 07/05/2004
Time: 15:15
User: NT AUTHORITY\SYSTEM
Computer: ******
Description:
Windows saved user *****\***** 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 have also noticed that Avast doesn’t shutdown/exit when you right click on the Avast Icon and select ‘Stop On-Access Protection and Exit.’ All that happens is the On-Access providers (2 running) are stopped but the program dosen’t EXIT.
The Avast Icon remains in the system tray but changes to one with a no entry/stop sign on top of it. On checking Task Manager I still have 4 avast processes running, ashmaisv.exe, ashdisp.exe, ashserv.exe and aswupdsv.exe.
This would appear to me to be the reason why the warning message is being generated because Avast is still runing.
ashmaisv.exe: this is the Mail provider Service
ashdisp.exe: this is the icon in your system tray
ashserv.exe: avast service
aswupdsv.exe: avast update service
I think that when you stop the providers and exit you only disable the protection. You do not ‘stop’ the services… :-\
Hi Technical,
Further to my initial question (1.) and your reply, using Task Manager I ended the tasks (exe programs you mentioned) and rebooted.
Thats right you guessed it I still got the same error in the Event Viewer Log, so there is something else going on, even though I never had this warning prior to Avast 4 Home.
Something is hanging onto registry and I will have to investigate further.
I have this too, on one machine only. Same error and the system for me, never fully shuts down. I have to use the power or reset switch. Other systems with the same updates/software installed along with avast don’t have the problem.
However, I’m not sure that it’s avast that is the real thing doing it. I think it’s a combination of USB and avast. If I uninstall avast, the problem goes away. If I uninstall USB, the problem goes away. There is something with the two of them on some systems that is a problem.
I think the problem on that machine started about the same time as the USB update for XP came out, but can’t remember exactly, and it’s rare that I reboot that system at all. I do remember that at one time even with avast installed, the system shutdown and rebooted without any problems.
So, if you do find out what it is, I’d like to know too.
No further news to report, even manually ending tasks (4) for Avast and every other non essential task, I still get the message.
If anyone knows of a registry sniffer program (and who to use one), I can try and track down what program is holding onto registry when the user logs off on shutdown.
I have tried the RegMon.exe program and that lists real time access to the registry (literally thousands of entries), being updated by the millisecond. So I have been unable to identify the program at fault. As you mention it could be a combination, but what?
1. I have been experiencing shutdown problems - WinXP Pro SP1a fully updated.
Startup items:
Avast 4.1 Home - Outpost 1.0.242 - Nvida Display Driver 6.14.10.4523 - Systray (win xp pro). As you can see I run a tight ship, nothing that doesn’t physically have to run at startup gets loaded.
Regular use but not startup and closed prior to exit:
Avant Browser 9.02 (updated) - OE6 fully updated.
I read this youst the other day in Lockergnome reguarding Slow shutdown and the following was mentioned reguarding Nvida Display and other things.
Some users report a minute or longer for shutdown to visibly start. Generally, this is a consequence of software that is running when shutdown is attempted. It usually has something to do with particular hardware. If you experience this problem, be sure to close all running programs before attempting shutdown and see if this solves your problem. If so, then you can determine, by trial and error, which program or programs are involved.
One specific solution for this problem is to stop the Nvidia Driver Helper service in the Services applet. You can locate the Services applet in the Administrative Tools folder in the Control Panel. You can also get this by launching SERVICES.MSC from a Run box.
An alternative solution in Windows XP Professional is to clear the pagefile at system shutdown. To clear these options, use the Group Policy Editor. The same setting also forces the hibernation file to be wiped at shutdown. These processes take long enough that users may think that shutdown has hung. Since someone actually has to have set this policy, the problem will be pretty rare, but is worth mentioning. To change the setting type GPEDIT.MSC from the Run box and click OK. You will need to browse through the following items to locate the Security Options: Computer Configuration, Windows Settings, Security Settings, Local Policies and Security Options. In the right pane, find Shutdown: Clear virtual memory pagefile.
@BoB3160 - Thanks, I also get LockerGnome and read the article, I had already shutdown NV Helper and tried the clear pagefile on shutdown (and would you believe it), it took longer.
Having restored the GPEDIT.MSC setting back to what it was shutdown is much more acceptable.
@whocares - FW fully upto date and no reported conflicts with Avast, indeed, many report it very stable with Avast.
I have hijack this and there is nothing untoward there - only 37 lines total whilst posting this. I used to use StartMan.exe PCForest (and that only reported 5 programs running at startup). I have been using starter.exe lately and that reported 6 at startup, one of those ctfmon.exe (part of SP1a aparently but is only for Office XP [which I don’t have], so that has been disabled so back to just 5. I will have a look at ASviewer though.
My system is very tightly clamped down, nothing runs that doesn’t have to run and then only for the time required; this is why I noticed the Event Viewer log warning messages after installing Avast.
I know this is going to sound weird, but it has fixed a few computers I have worked on around the area with shhut down problems. Turn off Fast writes, for Nvidia Driver set, and also in your bios.
Your right, it does sound weird ;D. I never had a shutdown problem pre avast, so no changes relating to fast writes? My shutdown problem now only relates to the warning messages in Event Viewer Log (applications) in my first post of this thread. Every time I shutdown some thing is hanging on to registry.
My point was, that Nvidia drivers have caused hang ups on shut downs .
Fastwrites have been contributed to it, along with bios updates not in current, AGP out of date, INF drivers out of sync, MOBO drivers per manufactuer not current etc.
Yes, a HP Deskjet 1220c with latest, XP/HP Printer Driver, it is connected by USB and is usually switched of.
Checked Printers and Faxes and printer shows current status offline (correct) and Driver shows Unidrv Printer Driver Version 5.1.2600.1106 Microsoft Corp Filename HPW5122.GPD
I do take your point, I am aware of some problems with Nvidia drivers There are two on the windows update site, one which is older than the one I am using. The newer one, some time ago I tried to windows update/install it, but it failed twice and I rolled back to my previous good driver.
There are prople that also don’t recommend updating your video driver if all is well and up until I installed avast no driver problems.
Fastwrites have been contributed to it, along with bios updates not in current, AGP out of date, INF drivers out of sync, MOBO drivers per manufactuer not current etc.
My system (home build) is less than 18 months old everything compatible to start with. My card is Nvidia 440MX 64 Mb AGP4 and for non games use is fine - Motherboard Gigabyte GA-7VAX AGP8 FSB 333Mhz
Please don’t get me wrong I am not saying you are wrong, simply that there have been no hardware changes, my system had no prior problems, so I find it hard to see how it can suddenly go wrong after a software installation.
If you are having problems with nVidia drivers (or suspect that you do), go to the nVidia site to download the most up to date drivers for the card you have. They have a basically easy to use system for selecting the correct card and drivers.
