I am sure everyone has has seen these errors at Windows shut down .....
"The instruction at "0x........" referenced memory at "0x........". The memory could not be "read"
Firstly, I would like to thank delphinium for the link he provided to download Microsoft UPHCleanup.
This link has solved the on going but occasional problem I have when Norton upgrades one of its components, such as recently when it upgraded the toolbar to work with Firefox 6.0.
All userenv error messages in MS Event Viewer have now stopped on computer shut down.
To quote from Microsoft ......
"The User Profile Hive Cleanup service helps to ensure user sessions are completely terminated when a user logs off. System processes and applications occasionally maintain connections to registry keys in the user profile after a user logs off. In those cases the user session is prevented from completely ending."
I thought that I had seen the last of these message but last night at Windows shut down up popped .........
"dwwin.exe - DLL initialization failed"
To stop this I have now removed the Dr Watson "Aedebug" key in the Registry.
HKLM \ Software \ Microsoft \ Windows NT \ CurrentVersion \ AeDebug
The only remaining error message in Event Viewer Security Center is .......
"The Windows Security Center Service was unable to establish event queries with WMI to monitor third party AntiVirus and Firewall"
For one reason or another I understand that Windows will not always recognise third party Virus Protection so to stop this error message appearing in Event Viewer I have changed the entry in the Windows Security Center so that Virus Protection is not monitored.
Windows now reports ......
"You've told us that you're using antivirus software that you will monitor yourself. Windows will not monitor your virus protection status or send you messages if it is turned off or out of date"
Norton doesn’t report any errors so everthing must be working correctly.
For years now I have had a problem with Windows Time not being set correctly at next logon whenever a change has been made to the registry. The clock reverts back to the year / day when Windows was installed (2005). After years of research and even installing the KB951531 Hotfix for W32Time.dll the issue was never completely resolved. As a remedial measure I installed Sync-It to synchronize the time correctly and that works fine
It has occurred to me that these shut down errors could affect the time settings in the registry, so hopefully UPHCleanup will solve this issue as well. Only time will tell as they say!
I hope this report will help other users having similar problems.