Hi Jacee
I thought you had solved my problem with by ‘start/stopping Bits’
The laptop was ok for 20 – 30 starts – then it happened again
Reset spoolsv – then ok for 20+ starts – then it happened again
Reset spoolsv – then ok for 14 starts – then it happened again
Reset spoolsv – then ok for 5 starts – then it happened again
Reset spoolsv – then ok for 4 starts – then it happened again
Now the ‘corruption’ happens every time – running the bits start/stop does not work (the warning is not there in VEW)
This has happened in a similar way before in that a change/fix has been made which works for a period but the problem creeps back over time with the reapplication of the fix not now working!
I have copied the latest VEW log, it may help:
0000000000000000000000000000000000000000000000000
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 23/09/2011 13:07:53
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 23/09/2011 11:47:38
Type: Information Category: 0
Event: 903 Source: Microsoft-Windows-Security-SPP
The Software Protection service has stopped.
Log: 'Application' Date/Time: 23/09/2011 11:44:42
Type: Information Category: 0
Event: 1000 Source: Microsoft-Windows-LoadPerf
Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data in the data section contains the new index values assigned to this service.
Log: 'Application' Date/Time: 23/09/2011 11:44:42
Type: Information Category: 0
Event: 1001 Source: Microsoft-Windows-LoadPerf
Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
Log: 'Application' Date/Time: 23/09/2011 11:42:38
Type: Information Category: 0
Event: 902 Source: Microsoft-Windows-Security-SPP
The Software Protection service has started. 6.1.7601.17514
Log: 'Application' Date/Time: 23/09/2011 11:42:38
Type: Information Category: 0
Event: 1003 Source: Microsoft-Windows-Security-SPP
The Software Protection service has completed licensing status check. Application Id=55c92734-d682-4d71-983e-d6ec3f16059f Licensing Status=
1: 01f5fc37-a99e-45c5-b65e-d762f3518ead, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
2: 2e7d060d-4714-40f2-9896-1e4f15b612ad, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
3: 3b965dfc-31d9-4903-886f-873a0382776c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
4: 586bc076-c93d-429a-afe5-a69fbc644e88, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
5: 5e017a8a-f3f9-4167-b1bd-ba3e236a4d8f, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
6: 5e35dc43-389b-47c5-b889-2088b06738cb, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
7: 6a7d5d8a-92af-4e6a-af4b-8fddaec800e5, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
8: 9ab82e0c-ffc9-4107-baa1-c65a8bd3ccc3, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
9: 9f83d90f-a151-4665-ae69-30b3f63ec659, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
10: a63275f4-530c-48a7-b0d3-4f00d688d151, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
11: b8a4bb91-69b1-460d-93f8-40e0670af04a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
12: d2c04e90-c3dd-4260-b0f3-f845f5d27d64, 1, 1 [(0 [0x00000000, 1, 0], [(?)(?)( 1 0x00000000 0 0 msft:rm/algorithm/bios/4.0 0x00000000 0)(?)(?)(?)])(1 )(2 )]
13: e68b141f-4dfa-4387-b3b7-e65c4889216e, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
14: ee4e1629-bcdc-4b42-a68f-b92e135f78d7, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
15: 4a8149bb-7d61-49f4-8822-82c7bf88d64b, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
16: afd5f68f-b70f-4000-a21d-28dbc8be8b07, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
Log: 'Application' Date/Time: 23/09/2011 11:42:37
Type: Information Category: 0
Event: 1066 Source: Microsoft-Windows-Security-SPP
Initialization status for service objects. C:\Windows\system32\sppwinob.dll, msft:spp/windowsfunctionality/agent/7.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/phone/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/pkey/2005, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/TaskScheduler/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/licenserenewal/1.0, 0x00000000, 0x00000000
Log: 'Application' Date/Time: 23/09/2011 11:42:35
Type: Information Category: 0
Event: 1 Source: SecurityCenter
The Windows Security Center Service has started.
Log: 'Application' Date/Time: 23/09/2011 11:42:34
Type: Information Category: 0
Event: 900 Source: Microsoft-Windows-Security-SPP
The Software Protection service is starting.
Log: 'Application' Date/Time: 23/09/2011 11:40:42
Type: Information Category: 1
Event: 1003 Source: Microsoft-Windows-Search
The Windows Search Service started.
Log: 'Application' Date/Time: 23/09/2011 11:40:41
Type: Information Category: 3
Event: 302 Source: ESENT
Windows (2304) Windows: The database engine has successfully completed recovery steps.
Log: 'Application' Date/Time: 23/09/2011 11:40:39
Type: Information Category: 3
Event: 301 Source: ESENT
Windows (2304) Windows: The database engine has begun replaying logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log.
Log: 'Application' Date/Time: 23/09/2011 11:40:39
Type: Information Category: 3
Event: 300 Source: ESENT
Windows (2304) Windows: The database engine is initiating recovery steps.
Log: 'Application' Date/Time: 23/09/2011 11:40:39
Type: Information Category: 1
Event: 102 Source: ESENT
Windows (2304) Windows: The database engine (6.01.7601.0000) started a new instance (0).
Log: 'Application' Date/Time: 23/09/2011 11:40:35
Type: Information Category: 0
Event: 5617 Source: Microsoft-Windows-WMI
Windows Management Instrumentation Service subsystems initialized successfully
Log: 'Application' Date/Time: 23/09/2011 11:40:32
Type: Information Category: 0
Event: 5615 Source: Microsoft-Windows-WMI
Windows Management Instrumentation Service started sucessfully
Log: 'Application' Date/Time: 23/09/2011 11:40:32
Type: Information Category: 0
Event: 35 Source: NIS
The 'NIS' service has started.
Log: 'Application' Date/Time: 23/09/2011 11:40:32
Type: Information Category: 0
Event: 34 Source: NIS
The 'NIS' service is starting.
Log: 'Application' Date/Time: 23/09/2011 11:40:29
Type: Information Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.
Log: 'Application' Date/Time: 23/09/2011 11:40:29
Type: Information Category: 0
Event: 4101 Source: Microsoft-Windows-Winlogon
Windows license validated.
Log: 'Application' Date/Time: 23/09/2011 11:40:26
Type: Information Category: 0
Event: 1531 Source: Microsoft-Windows-User Profiles Service
The User Profile Service has started successfully.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 23/09/2011 09:31:55
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-2742660404-3765029268-2200134315-500:
Process 820 (\Device\HarddiskVolume3\Windows\System32\winlogon.exe) has opened key \REGISTRY\USER\S-1-5-21-2742660404-3765029268-2200134315-500
Log: 'Application' Date/Time: 16/09/2011 14:38:04
Type: Warning Category: 7
Event: 508 Source: ESENT
wuaueng.dll (948) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 519680 (0x000000000007ee00) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (22693 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Log: 'Application' Date/Time: 13/09/2011 16:27:25
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Application Requested}.
Log: 'Application' Date/Time: 13/09/2011 16:24:31
Type: Warning Category: 0
Event: 6004 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <TrustedInstaller> failed a critical notification event.
Log: 'Application' Date/Time: 05/09/2011 23:02:50
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Application Requested}.
Log: 'Application' Date/Time: 05/09/2011 20:38:46
Type: Warning Category: 0
Event: 6004 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <TrustedInstaller> failed a critical notification event.
Log: 'Application' Date/Time: 04/09/2011 13:22:36
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
The content source <C:\ProgramData\Microsoft\Windows\Start Menu\> cannot be accessed.
Context: Application, SystemIndex Catalog
Details:
The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add. (HRESULT : 0x80040d0d) (0x80040d0d)
Log: 'Application' Date/Time: 04/09/2011 12:28:17
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-2742660404-3765029268-2200134315-1000:
Process 472 (\Device\HarddiskVolume3\Windows\System32\winlogon.exe) has opened key \REGISTRY\USER\S-1-5-21-2742660404-3765029268-2200134315-1000
Log: 'Application' Date/Time: 04/09/2011 12:20:01
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 04/09/2011 12:14:50
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 23/09/2011 12:07:34
Type: Information Category: 0
Event: 206 Source: Microsoft-Windows-Application-Experience
The Program Compatibility Assistant service successfully performed phase two initialization.
Log: 'System' Date/Time: 23/09/2011 12:07:30
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Application Information service entered the running state.
Log: 'System' Date/Time: 23/09/2011 12:07:06
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Multimedia Class Scheduler service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:58:34
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The WinHTTP Web Proxy Auto-Discovery Service service entered the stopped state.
Log: 'System' Date/Time: 23/09/2011 11:50:35
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Application Experience service entered the stopped state.
Log: 'System' Date/Time: 23/09/2011 11:47:38
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Software Protection service entered the stopped state.
Log: 'System' Date/Time: 23/09/2011 11:45:37
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Multimedia Class Scheduler service entered the stopped state.
Log: 'System' Date/Time: 23/09/2011 11:42:39
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Update service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:42:34
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Security Center service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:42:34
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Software Protection service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:42:33
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Font Cache Service service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:40:43
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The HomeGroup Provider service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:40:43
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Function Discovery Provider Host service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:40:43
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Media Player Network Sharing Service service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:40:42
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Search service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:40:42
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Computer Browser service entered the stopped state.
Log: 'System' Date/Time: 23/09/2011 11:40:42
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The IPsec Policy Agent service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:40:43
Type: Information Category: 0
Event: 14204 Source: Microsoft-Windows-WMPNSS-Service
Service 'WMPNetworkSvc' started.
Log: 'System' Date/Time: 23/09/2011 11:40:42
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Network Connections service entered the running state.
Log: 'System' Date/Time: 23/09/2011 11:40:41
Type: Information Category: 7005
Event: 20003 Source: Microsoft-Windows-UserPnp
Driver Management has concluded the process to add Service tunnel for Device Instance ID ROOT\*ISATAP\0000 with the following status: 0.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 23/09/2011 11:40:24
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.
Log: 'System' Date/Time: 23/09/2011 11:37:36
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 23/09/2011 10:56:03
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name liveupdate.symantecliveupdate.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 23/09/2011 10:56:01
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name dns.msftncsi.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 23/09/2011 10:15:20
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.
Log: 'System' Date/Time: 23/09/2011 10:14:32
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 23/09/2011 10:07:08
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.
Log: 'System' Date/Time: 23/09/2011 10:06:19
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 23/09/2011 09:46:10
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.
Log: 'System' Date/Time: 23/09/2011 09:45:26
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 23/09/2011 09:39:28
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.
Log: 'System' Date/Time: 23/09/2011 09:38:06
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 23/09/2011 09:33:02
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.
Log: 'System' Date/Time: 23/09/2011 09:31:59
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 23/09/2011 09:06:11
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.
Log: 'System' Date/Time: 23/09/2011 09:05:11
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 23/09/2011 08:44:07
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.
Log: 'System' Date/Time: 22/09/2011 22:57:54
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 22/09/2011 22:56:58
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.
Log: 'System' Date/Time: 22/09/2011 19:42:07
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
0000000000000000000000000000000000000000000000000000000000
Once again I am really grateful for your help.