Vino's Event Viewer v01c run on Windows 7 in English Report run at 13/09/2017 12:58:51 PM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 09/09/2017 9:04:27 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: 05/09/2017 12:46:31 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: 26/08/2017 9:47:37 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/08/2017 5:11: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: 31/05/2017 3:37: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: 30/05/2017 1:57: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: 22/03/2017 8:04:59 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: 05/12/2016 11:18:45 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: 05/12/2016 7:25:02 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: 04/10/2016 1:10:09 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: 12/09/2017 11:34:14 PM Type: Error Category: 0 Event: 4307 Source: NetBT Initialization failed because the transport refused to open initial addresses. Log: 'System' Date/Time: 12/09/2017 11:34:14 PM Type: Error Category: 0 Event: 4307 Source: NetBT Initialization failed because the transport refused to open initial addresses. Log: 'System' Date/Time: 12/09/2017 11:34:14 PM Type: Error Category: 0 Event: 4307 Source: NetBT Initialization failed because the transport refused to open initial addresses. Log: 'System' Date/Time: 12/09/2017 8:31:31 PM Type: Error Category: 0 Event: 7032 Source: Service Control Manager The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the DNS Client service, but this action failed with the following error: An instance of the service is already running. Log: 'System' Date/Time: 12/09/2017 8:30:31 PM Type: Error Category: 0 Event: 7032 Source: Service Control Manager The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Cryptographic Services service, but this action failed with the following error: An instance of the service is already running. Log: 'System' Date/Time: 12/09/2017 8:29:31 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The Network Location Awareness service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service. Log: 'System' Date/Time: 12/09/2017 8:29:31 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The Workstation service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Log: 'System' Date/Time: 12/09/2017 8:29:31 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The DNS Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. Log: 'System' Date/Time: 12/09/2017 8:29:31 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The Cryptographic Services service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Log: 'System' Date/Time: 11/09/2017 11:40:00 PM Type: Error Category: 0 Event: 10010 Source: Microsoft-Windows-DistributedCOM The server {DABF28BE-F6B4-4E40-8F40-C4FB26F3116C} did not register with DCOM within the required timeout. Log: 'System' Date/Time: 11/09/2017 11:37:56 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The User Data Access_77d1d service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. Log: 'System' Date/Time: 11/09/2017 11:37:56 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The User Data Storage_77d1d service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. Log: 'System' Date/Time: 11/09/2017 11:37:56 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The Contact Data_77d1d service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. Log: 'System' Date/Time: 11/09/2017 11:37:56 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The Sync Host_77d1d service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. Log: 'System' Date/Time: 11/09/2017 7:33:24 PM Type: Error Category: 1 Event: 20 Source: Microsoft-Windows-WindowsUpdateClient Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703. Log: 'System' Date/Time: 11/09/2017 5:46:40 PM Type: Error Category: 0 Event: 10010 Source: Microsoft-Windows-DistributedCOM The server {DABF28BE-F6B4-4E40-8F40-C4FB26F3116C} did not register with DCOM within the required timeout. Log: 'System' Date/Time: 11/09/2017 5:43:12 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The User Data Access_60df7 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. Log: 'System' Date/Time: 11/09/2017 5:43:12 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The User Data Storage_60df7 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. Log: 'System' Date/Time: 11/09/2017 5:43:12 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The Contact Data_60df7 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. Log: 'System' Date/Time: 11/09/2017 5:43:12 PM Type: Error Category: 0 Event: 7031 Source: Service Control Manager The Sync Host_60df7 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 13/09/2017 4:48:17 PM Type: Warning Category: 0 Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig WLAN Extensibility Module has stopped. Module Path: C:\WINDOWS\System32\IWMSSvc.dll Log: 'System' Date/Time: 13/09/2017 2:26:25 PM Type: Warning Category: 0 Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig WLAN Extensibility Module has stopped. Module Path: C:\WINDOWS\System32\IWMSSvc.dll Log: 'System' Date/Time: 13/09/2017 12:08:32 AM Type: Warning Category: 0 Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig WLAN Extensibility Module has stopped. Module Path: C:\WINDOWS\System32\IWMSSvc.dll Log: 'System' Date/Time: 12/09/2017 11:34:19 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name abnvueikxrnon timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 11:30:54 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name wpad timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 9:19:12 PM Type: Warning Category: 0 Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig WLAN Extensibility Module has stopped. Module Path: C:\WINDOWS\System32\IWMSSvc.dll Log: 'System' Date/Time: 12/09/2017 8:32:03 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name wpad timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:31:54 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name zrowukydemkcu timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:31:37 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name wpad timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:31:32 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name wpad timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:31:29 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name isatap timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:31:25 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name vdnaunfxg timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:31:13 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name wpad timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:30:59 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name isatap timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:30:46 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name isatap.caltech.edu timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:30:41 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name wpad timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:28:41 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name isatap.caltech.edu timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:28:40 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name isatap timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:28:28 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name wpad timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/09/2017 8:28:21 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name d29x207vrinatv.cloudfront.net timed out after none of the configured DNS servers responded.