Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 27/06/2011 10:36:55 AM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 27/06/2011 1:35:06 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: nmsrvc.exe, version: 11.0.8268.0, time stamp: 0x48dac758 Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7ab86 Exception code: 0xc0000005 Fault offset: 0x00038db9 Faulting process id: 0xa40 Faulting application start time: 0x01cc344723e08525 Faulting application path: C:\Program Files (x86)\Common Files\Pure Networks Shared\Platform\nmsrvc.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 44c02d93-a0c2-11e0-91ae-0025645fa9e5
Log: 'Application' Date/Time: 25/06/2011 6:21:54 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: nmsrvc.exe, version: 11.0.8268.0, time stamp: 0x48dac758 Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7ab86 Exception code: 0xc0000005 Fault offset: 0x00038db9 Faulting process id: 0xa28 Faulting application start time: 0x01cc32a7dce30004 Faulting application path: C:\Program Files (x86)\Common Files\Pure Networks Shared\Platform\nmsrvc.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 6b382846-9ef3-11e0-a93a-0025645fa9e5
Log: 'Application' Date/Time: 24/06/2011 12:11:27 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: nmsrvc.exe, version: 11.0.8268.0, time stamp: 0x48dac758 Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7ab86 Exception code: 0xc0000005 Fault offset: 0x00038db9 Faulting process id: 0x9bc Faulting application start time: 0x01cc321eb7eb3e5d Faulting application path: C:\Program Files (x86)\Common Files\Pure Networks Shared\Platform\nmsrvc.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 15b396f2-9e5b-11e0-8b72-0025645fa9e5
Log: 'Application' Date/Time: 23/06/2011 10:26:07 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program Skype.exe version 5.3.0.116 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 1bbc Start Time: 01cc31591722ef4f Termination Time: 78 Application Path: C:\Program Files (x86)\Skype\Phone\Skype.exe Report Id:
Log: 'Application' Date/Time: 22/06/2011 5:13:45 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: nmsrvc.exe, version: 11.0.8268.0, time stamp: 0x48dac758 Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7ab86 Exception code: 0xc0000005 Fault offset: 0x00038db9 Faulting process id: 0x9e0 Faulting application start time: 0x01cc30ea4d9aae3d Faulting application path: C:\Program Files (x86)\Common Files\Pure Networks Shared\Platform\nmsrvc.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: fbbe06ac-9cf2-11e0-925a-0025645fa9e5
Log: 'Application' Date/Time: 21/06/2011 6:01:46 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: nmsrvc.exe, version: 11.0.8268.0, time stamp: 0x48dac758 Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7ab86 Exception code: 0xc0000005 Fault offset: 0x00038db9 Faulting process id: 0x7f0 Faulting application start time: 0x01cc3016f6955385 Faulting application path: C:\Program Files (x86)\Common Files\Pure Networks Shared\Platform\nmsrvc.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 86c8dee3-9c30-11e0-9e2c-0025645fa9e5
Log: 'Application' Date/Time: 21/06/2011 1:28:49 PM
Type: Error Category: 0
Event: 0 Source: Swapdrive Backup
Swapdrive Backup: Web Service Error: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Net.TlsStream.CallProcessAuthentication(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.WriteHeaders(Boolean async) --- End of inner exception stack trace --- at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Swapdrive.Shared.com.backup.uswsvcdell.Service.GetInfo(GetInfoRequest req) at Swapdrive.Shared.ActivationWsvcs.GetInfo()
Log: 'Application' Date/Time: 21/06/2011 1:27:47 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: YahooAUService.exe, version: 1.0.0.53, time stamp: 0x49174c52 Faulting module name: YahooAUService.exe, version: 1.0.0.53, time stamp: 0x49174c52 Exception code: 0xc0000005 Fault offset: 0x00011d01 Faulting process id: 0xb94 Faulting application start time: 0x01cc3016f564a362 Faulting application path: C:\Program Files (x86)\Yahoo!\SoftwareUpdate\YahooAUService.exe Faulting module path: C:\Program Files (x86)\Yahoo!\SoftwareUpdate\YahooAUService.exe Report Id: 408f1aef-9c0a-11e0-9e2c-0025645fa9e5
Log: 'Application' Date/Time: 19/06/2011 6:25:00 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\program files (x86)\spybot - search & destroy\DelZip179.dll".Error in manifest or policy file "c:\program files (x86)\spybot - search & destroy\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.
Log: 'Application' Date/Time: 19/06/2011 6:22:07 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "c:\Windows\SysWOW64\coziscreensaver.scr".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_420fe3fa2b8113bd.manifest.
Log: 'Application' Date/Time: 19/06/2011 6:16:16 AM
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "c:\program files (x86)\microsoft\search enhancement pack\search helper\sepsearchhelperie.dll".Error in manifest or policy file "c:\program files (x86)\microsoft\search enhancement pack\search helper\sepsearchhelperie.dll" on line 2. Invalid Xml syntax.
Log: 'Application' Date/Time: 19/06/2011 6:09:50 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_420fe3fa2b8113bd.manifest.
Log: 'Application' Date/Time: 19/06/2011 2:10:13 AM
Type: Error Category: 0
Event: 11606 Source: MsiInstaller
Product: Microsoft Visual C++ 2005 Redistributable -- Error 1606.Could not access network location %APPDATA%\.
Log: 'Application' Date/Time: 19/06/2011 2:10:13 AM
Type: Error Category: 0
Event: 11606 Source: MsiInstaller
Product: Microsoft Visual C++ 2005 Redistributable -- Error 1606.Could not access network location %APPDATA%\.
Log: 'Application' Date/Time: 18/06/2011 4:30:56 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program Skype.exe version 5.3.0.116 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 2780 Start Time: 01cc2d7058d57838 Termination Time: 200 Application Path: C:\Program Files (x86)\Skype\Phone\Skype.exe Report Id:
Log: 'Application' Date/Time: 18/06/2011 4:29:18 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program VisualBoyAdvance.exe version 1.8.0.603 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 23b8 Start Time: 01cc2d0436eff4b8 Termination Time: 48 Application Path: C:\Users\Adam Kohn\Desktop\GBA\VisualBoyAdvance.exe Report Id: 8158486e-9963-11e0-a1f4-0025645fa9e5
Log: 'Application' Date/Time: 17/06/2011 3:49:45 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
mDNSCoreReceiveResponse: Reseting to Probing: 16 Akatsuki.local. AAAA FE80:0000:0000:0000:38C2:D5A7:F255:F7E2
Log: 'Application' Date/Time: 17/06/2011 3:49:45 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
mDNSCoreReceiveResponse: Received from 172.24.58.35:5353 4 Akatsuki.local. Addr 192.168.1.100
Log: 'Application' Date/Time: 17/06/2011 3:49:45 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
mDNSCoreReceiveResponse: Reseting to Probing: 4 Akatsuki.local. Addr 172.24.58.35
Log: 'Application' Date/Time: 17/06/2011 3:49:45 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
mDNSCoreReceiveResponse: Received from 172.24.58.35:5353 4 Akatsuki.local. Addr 192.168.1.100
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 27/06/2011 11:19:52 AM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 26/06/2011 9:23:10 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 26/06/2011 4:51:25 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 26/06/2011 5:19:19 AM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 25/06/2011 9:19:20 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 25/06/2011 12:25:50 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 25/06/2011 4:25:49 AM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 24/06/2011 7:50:07 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 24/06/2011 7:46:58 PM
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 - 15 user registry handles leaked from \Registry\User\S-1-5-21-1101292609-3000308259-264279-1001:
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Microsoft\SystemCertificates\TrustedPeople
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Microsoft\SystemCertificates\Disallowed
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Microsoft\SystemCertificates\trust
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Microsoft\SystemCertificates\SmartCardRoot
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Policies\Microsoft\SystemCertificates
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Policies\Microsoft\SystemCertificates
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Policies\Microsoft\SystemCertificates
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Policies\Microsoft\SystemCertificates
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Microsoft\SystemCertificates\My
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Microsoft\SystemCertificates\CA
Process 1756 (\Device\HarddiskVolume3\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1101292609-3000308259-264279-1001\Software\Microsoft\SystemCertificates\Root
Log: 'Application' Date/Time: 24/06/2011 3:29:33 AM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 23/06/2011 8:57:37 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 23/06/2011 12:57:36 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 23/06/2011 4:57:34 AM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 22/06/2011 9:00:03 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 22/06/2011 2:41:05 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 22/06/2011 12:46:26 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 21/06/2011 9:27:27 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 21/06/2011 1:29:09 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 21/06/2011 12:33:49 PM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
Log: 'Application' Date/Time: 21/06/2011 3:26:16 AM
Type: Warning Category: 0
Event: 64 Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Certificate for local system with Thumbprint fc e2 31 fb 4d a4 09 19 ef c4 5a d0 09 90 03 3a fa 85 c5 6b is about to expire or already expired.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 22/06/2011 8:57:04 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 22/06/2011 2:39:39 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 21/06/2011 1:26:58 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 19/06/2011 7:59:11 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 19/06/2011 6:47:11 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 19/06/2011 8:59:36 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 19/06/2011 5:13:11 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 16/06/2011 6:18:35 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 16/06/2011 4:18:57 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 15/06/2011 5:13:49 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 14/06/2011 7:48:19 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 14/06/2011 6:27:16 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 13/06/2011 8:49:42 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 11/06/2011 3:58:15 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 10/06/2011 2:54:09 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 10/06/2011 2:12:24 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 10/06/2011 2:53:46 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 03/06/2011 10:54:06 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 02/06/2011 9:54:16 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 01/06/2011 6:58:44 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/06/2011 1:35:12 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Pure Networks Platform Service service terminated unexpectedly. It has done this 1 time(s).
Log: 'System' Date/Time: 25/06/2011 6:22:01 AM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Pure Networks Platform Service service terminated unexpectedly. It has done this 1 time(s).
Log: 'System' Date/Time: 24/06/2011 8:24:45 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The VideoAcceleratorService service terminated unexpectedly. It has done this 1 time(s).
Log: 'System' Date/Time: 24/06/2011 5:56:37 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR2.
Log: 'System' Date/Time: 24/06/2011 5:56:36 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR2.
Log: 'System' Date/Time: 24/06/2011 5:56:35 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR2.
Log: 'System' Date/Time: 24/06/2011 12:11:49 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Pure Networks Platform Service service terminated unexpectedly. It has done this 1 time(s).
Log: 'System' Date/Time: 24/06/2011 3:39:46 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070643: Windows 7 Service Pack 1 for x64-based Systems (KB976932).
Log: 'System' Date/Time: 24/06/2011 3:35:16 AM
Type: Error Category: 0
Event: 8 Source: Microsoft-Windows-Service Pack Installer
Service Pack installation failed with error code 0x80070026.
Log: 'System' Date/Time: 23/06/2011 3:13:22 PM
Type: Error Category: 0
Event: 8003 Source: bowser
The master browser has received a server announcement from the computer COURTNEY-PC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{50E2F7FD-E811-40CE-9A14-3AAF91289C5B}. The master browser is stopping or an election is being forced.
Log: 'System' Date/Time: 23/06/2011 3:02:13 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.
Log: 'System' Date/Time: 23/06/2011 3:02:12 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.
Log: 'System' Date/Time: 23/06/2011 3:02:11 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.
Log: 'System' Date/Time: 23/06/2011 3:52:01 AM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The VideoAcceleratorService service terminated unexpectedly. It has done this 1 time(s).
Log: 'System' Date/Time: 22/06/2011 8:58:20 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The SBSD Security Center Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 22/06/2011 8:58:20 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the SBSD Security Center Service service to connect.
Log: 'System' Date/Time: 22/06/2011 8:57:16 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 4:55:24 PM on ?6/?22/?2011 was unexpected.
Log: 'System' Date/Time: 22/06/2011 5:15:00 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.
Log: 'System' Date/Time: 22/06/2011 5:14:59 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.
Log: 'System' Date/Time: 22/06/2011 5:14:58 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/06/2011 11:19:45 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.hsd1.ma.comcast.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/06/2011 11:19:39 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 2 seconds since the last report.
Log: 'System' Date/Time: 27/06/2011 11:19:39 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 2 seconds since the last report.
Log: 'System' Date/Time: 27/06/2011 3:47:27 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.hsd1.ma.comcast.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/06/2011 1:17:21 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.hsd1.ma.comcast.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/06/2011 12:38:17 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.hsd1.ma.comcast.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 26/06/2011 6:22:46 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 26/06/2011 4:51:15 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.hsd1.ma.comcast.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 26/06/2011 1:06:29 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.hsd1.ma.comcast.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 26/06/2011 5:09:54 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 6 seconds since the last report.
Log: 'System' Date/Time: 26/06/2011 5:09:54 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 6 seconds since the last report.
Log: 'System' Date/Time: 25/06/2011 9:19:11 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.hsd1.ma.comcast.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 25/06/2011 5:09:54 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 4 seconds since the last report.
Log: 'System' Date/Time: 25/06/2011 5:09:54 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 4 seconds since the last report.
Log: 'System' Date/Time: 24/06/2011 8:24:46 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.hsd1.ma.comcast.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 24/06/2011 8:09:39 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name
www.marketwatch.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 24/06/2011 7:48:13 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 24/06/2011 7:19:23 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name
www.history.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 24/06/2011 5:50:18 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.hsd1.ma.comcast.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 24/06/2011 1:38:54 PM
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.
