Vino's Event Viewer v01c run on Windows 2008 in English Report run at 20/08/2011 11:58:51 AM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 20/08/2011 8:48:15 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 8:48:15 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 8:48:10 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 8:48:10 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 8:48:10 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 8:42:40 AM Type: Error Category: 0 Event: 4103 Source: Microsoft-Windows-Winlogon Windows license activation failed. Error 0x80070005. Log: 'Application' Date/Time: 20/08/2011 8:26:35 AM Type: Error Category: 0 Event: 20227 Source: RasClient CoId={B0870727-FE16-460F-80B7-4B7235A53982}: The user Dio-PC\Dio dialed a connection named Broadband Connection which has failed. The error code returned on failure is 718. Log: 'Application' Date/Time: 20/08/2011 4:21:34 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 4:21:34 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 4:20:52 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 4:20:52 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 3:11:26 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 3:11:26 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 2:37:34 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . Log: 'Application' Date/Time: 20/08/2011 2:37:34 AM Type: Error Category: 0 Event: 4107 Source: Microsoft-Windows-CAPI2 Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 20/08/2011 8:42:24 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/08/2011 1:25:51 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: 18/08/2011 6:01:23 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: 17/08/2011 9:03:08 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/08/2011 12:05:02 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: 15/08/2011 3:52:27 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: 14/08/2011 9:45:20 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/08/2011 1:42:13 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/08/2011 1:38:22 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/08/2011 1:33:18 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/08/2011 1:28:52 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/08/2011 1:17:34 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/08/2011 1:13:25 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/08/2011 10:49:26 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: 14/08/2011 10:38:51 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. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 20/08/2011 8:45:18 AM Type: Error Category: 0 Event: 4311 Source: NetBT Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000010000C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. Log: 'System' Date/Time: 20/08/2011 8:43:32 AM Type: Error Category: 0 Event: 34001 Source: Microsoft-Windows-SharedAccess_NAT The ICS_IPV6 failed to configure IPv6 stack. Log: 'System' Date/Time: 20/08/2011 8:43:32 AM Type: Error Category: 0 Event: 34001 Source: Microsoft-Windows-SharedAccess_NAT The ICS_IPV6 failed to configure IPv6 stack. Log: 'System' Date/Time: 20/08/2011 8:43:23 AM Type: Error Category: 0 Event: 7026 Source: Service Control Manager The following boot-start or system-start driver(s) failed to load: ATITool Log: 'System' Date/Time: 20/08/2011 8:43:18 AM Type: Error Category: 0 Event: 7009 Source: Service Control Manager A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 9 service to connect. Log: 'System' Date/Time: 20/08/2011 8:42:38 AM Type: Error Category: 0 Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x00000008, 0x801e9000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082011-21060-01. Log: 'System' Date/Time: 20/08/2011 8:42:35 AM Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 11:40:51 AM on ?8/?20/?2011 was unexpected. Log: 'System' Date/Time: 20/08/2011 8:27:07 AM Type: Error Category: 0 Event: 4311 Source: NetBT Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000010000C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. Log: 'System' Date/Time: 20/08/2011 8:27:07 AM Type: Error Category: 0 Event: 31004 Source: Microsoft-Windows-SharedAccess_NAT The DNS proxy agent was unable to allocate 0 bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error. Log: 'System' Date/Time: 20/08/2011 4:55:49 AM Type: Error Category: 0 Event: 34001 Source: Microsoft-Windows-SharedAccess_NAT The ICS_IPV6 failed to configure IPv6 stack. Log: 'System' Date/Time: 20/08/2011 2:47:17 AM Type: Error Category: 0 Event: 31004 Source: Microsoft-Windows-SharedAccess_NAT The DNS proxy agent was unable to allocate 0 bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error. Log: 'System' Date/Time: 19/08/2011 9:31:52 PM Type: Error Category: 0 Event: 31004 Source: Microsoft-Windows-SharedAccess_NAT The DNS proxy agent was unable to allocate 0 bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error. Log: 'System' Date/Time: 19/08/2011 9:00:40 PM Type: Error Category: 0 Event: 31004 Source: Microsoft-Windows-SharedAccess_NAT The DNS proxy agent was unable to allocate 0 bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error. Log: 'System' Date/Time: 19/08/2011 8:32:31 PM Type: Error Category: 0 Event: 4311 Source: NetBT Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000010000C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. Log: 'System' Date/Time: 19/08/2011 8:28:43 PM Type: Error Category: 0 Event: 4311 Source: NetBT Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000010000C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name.