Vino's Event Viewer v01c run on Windows 7 in English
Report run at 25/01/2018 4:22:25 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 24/01/2018 7:16: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.

Log: 'System' Date/Time: 15/01/2018 1:10: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: 30/12/2017 11:33: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: 28/12/2017 7:37:41 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/12/2017 8:37: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: 02/12/2017 9:37:46 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: 23/11/2017 4:10:35 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/11/2017 3:25:50 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/11/2017 8:27:43 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: 07/11/2017 7:01:01 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: 04/11/2017 8:05: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: 02/11/2017 3:01: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: 27/10/2017 5:37: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: 24/10/2017 11: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: 21/10/2017 6:14:54 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/10/2017 5:20: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: 17/10/2017 6:06:53 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: 12/10/2017 1:48:35 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: 08/10/2017 11:57: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: 03/10/2017 10:30:21 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: 25/01/2018 10:07:02 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server Microsoft.Windows.CloudExperienceHost_10.0.15063.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 25/01/2018 8:25:35 PM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AVP18.0.0 service.

Log: 'System' Date/Time: 24/01/2018 9:57:08 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.

Log: 'System' Date/Time: 24/01/2018 9:33:09 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 24/01/2018 9:09:42 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 24/01/2018 8:33:44 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The MBAMWebProtection service failed to start due to the following error:  Access is denied.

Log: 'System' Date/Time: 24/01/2018 8:29:45 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server Microsoft.Windows.CloudExperienceHost_10.0.15063.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 24/01/2018 7:24:30 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Downloaded Maps Manager 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: 24/01/2018 7:24:30 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Downloaded Maps Manager service to connect.

Log: 'System' Date/Time: 24/01/2018 7:23:33 PM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Delivery Optimization service hung on starting.

Log: 'System' Date/Time: 24/01/2018 7:18:34 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Net.Msmq Listener Adapter 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: 24/01/2018 7:18:33 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the NetMsmqActivator service to connect.

Log: 'System' Date/Time: 24/01/2018 7:18:17 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Net.Pipe Listener Adapter 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: 24/01/2018 7:18:17 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the NetPipeActivator service to connect.

Log: 'System' Date/Time: 24/01/2018 7:17:58 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Seagate MobileBackup Service service to connect.

Log: 'System' Date/Time: 24/01/2018 7:17:57 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The mmsminisrv 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: 24/01/2018 7:17:57 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the mmsminisrv service to connect.

Log: 'System' Date/Time: 24/01/2018 7:17:57 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: 24/01/2018 7:17:57 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: 24/01/2018 7:17:57 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The ByteFenceService service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 25/01/2018 9:16:25 PM
Type: Warning Category: 0
Event: 50 Source: NTFS
{Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Log: 'System' Date/Time: 25/01/2018 9:16:22 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume16. (A device which does not exist was specified.)

Log: 'System' Date/Time: 25/01/2018 9:16:18 PM
Type: Warning Category: 0
Event: 153 Source: Disk
The IO operation at logical block address 0x5bcb30 for Disk 6 (PDO name: \Device\0000008d) was retried.

Log: 'System' Date/Time: 25/01/2018 8:25:05 PM
Type: Warning Category: 0
Event: 129 Source: UASPStor
Reset to device, \Device\RaidPort0, was issued.

Log: 'System' Date/Time: 25/01/2018 8:09:51 PM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 25/01/2018 8:09:42 PM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 24/01/2018 11:36:43 PM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 24/01/2018 7:17:56 PM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 24/01/2018 7:17:07 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic-&Prod_SD#MMC&Rev_1.00#7&1c4905a4&0&058F63646476&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Log: 'System' Date/Time: 24/01/2018 7:17:07 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic-&Prod_Compact_Flash&Rev_1.01#7&1c4905a4&0&058F63646476&1#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Log: 'System' Date/Time: 24/01/2018 7:17:07 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic-&Prod_SM#xD-Picture&Rev_1.02#7&1c4905a4&0&058F63646476&2#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Log: 'System' Date/Time: 24/01/2018 7:17:07 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic-&Prod_MS#MS-Pro&Rev_1.03#7&1c4905a4&0&058F63646476&3#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Log: 'System' Date/Time: 24/01/2018 7:16:58 PM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 24/01/2018 7:09:43 PM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 24/01/2018 7:09:23 PM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 24/01/2018 7:09:12 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\klhk failed to load for the device ROOT\SYSTEM\0001.

Log: 'System' Date/Time: 24/01/2018 1:12:57 AM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 23/01/2018 1:11:54 AM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 22/01/2018 5:03:27 AM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 21/01/2018 9:52:35 PM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.