Vino's Event Viewer v01c run on Windows 7 in English Report run at 15/06/2018 3:57:55 PM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 15/06/2018 4:16: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: 31/05/2018 6:15: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: 27/05/2018 3:30:30 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: 15/06/2018 9:48:27 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 9:48:21 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 4:18:55 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscDataProtection and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 4:16:37 PM Type: Error Category: 1 Event: 10 Source: Microsoft-Windows-EnhancedStorage-EhStorTcgDrv A TCG Command has returned an error. Desc: AuthenticateSession Param1: 0x1 Param2: 0x60000001C Param3: 0x900000006 Param4: 0x0 Status: 0x12 Log: 'System' Date/Time: 15/06/2018 4:16:42 PM Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 9:54:42 AM on ?6/?15/?2018 was unexpected. Log: 'System' Date/Time: 15/06/2018 2:41:38 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 2:41:38 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 2:41:38 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 2:31:24 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 2:28:38 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 2:28:38 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 2:28:38 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 2:28:38 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 2:28:38 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 2:28:38 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 1:09:26 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscBrokerManager and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 1:09:26 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscDataProtection and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 15/06/2018 1:07:32 PM Type: Error Category: 0 Event: 7000 Source: Service Control Manager The Origin Web Helper 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: 15/06/2018 1:07:32 PM Type: Error Category: 0 Event: 7009 Source: Service Control Manager A timeout was reached (30000 milliseconds) while waiting for the Origin Web Helper Service service to connect. Log: 'System' Date/Time: 15/06/2018 1:07:10 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user LivingRoomPC\Cooper SID (S-1-5-21-2496469957-2484257577-3520296607-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 15/06/2018 12:39:58 AM Type: Warning Category: 0 Event: 10400 Source: Microsoft-Windows-NDIS The network interface "Realtek PCIe GBE Family Controller" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver detected that its hardware has stopped responding to commands. This network interface has reset 1 time(s) since it was last initialized. Log: 'System' Date/Time: 15/06/2018 12:39:55 AM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name r4---sn-qxo7rn7e.googlevideo.com timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/06/2018 7:53:19 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name us.patch.battle.net timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/06/2018 7:52:51 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name v10.events.data.microsoft.com timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/06/2018 7:51:35 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name us.patch.battle.net timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/06/2018 7:50:30 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name us.actual.battle.net timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/06/2018 7:49:58 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/06/2018 7:48:54 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name us.actual.battle.net timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/06/2018 7:48:16 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/06/2018 7:48:11 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name 0.client-channel.google.com timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 12/06/2018 10:41:03 AM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name maxineapi.razersynapse.com timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 10/06/2018 9:23:51 AM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name login.live.com timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 07/06/2018 12:00:11 AM 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: 04/06/2018 9:27:24 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name client.wns.windows.com timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 04/06/2018 9:26:05 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: 04/06/2018 9:25:55 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name iir.blizzard.com timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 04/06/2018 9:24:55 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name us.actual.battle.net timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 04/06/2018 9:24:25 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: 04/06/2018 9:23:19 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name heartbeat.dm.origin.com timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 04/06/2018 9:22:43 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.