Vino's Event Viewer v01c run on Windows 7 in English
Report run at 21/06/2016 16:10:54

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/09/2015 20:11:53
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: 17/06/2016 16:07:07
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4545DEA0-2DFC-4906-A728-6D986BA399A9} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 17/06/2016 16:07:07
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4545DEA0-2DFC-4906-A728-6D986BA399A9} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 16/06/2016 06:02:23
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {DDCFD26B-FEED-44CD-B71D-79487D2E5E5A} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 16/06/2016 06:02:19
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the DPS service.

Log: 'System' Date/Time: 14/06/2016 08:44:15
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4545DEA0-2DFC-4906-A728-6D986BA399A9} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/06/2016 08:44:15
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4545DEA0-2DFC-4906-A728-6D986BA399A9} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 12/06/2016 21:14:22
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 12/06/2016 21:14:22
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 12/06/2016 21:14:22
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 12/06/2016 21:14:22
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 28/05/2016 06:35:44
Type: Error Category: 0
Event: 55 Source: Ntfs
A corruption was discovered in the file system structure on volume ??.  The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x150000000311c6.  The name of the file is "<unable to determine file name>". 

Log: 'System' Date/Time: 28/05/2016 06:35:00
Type: Error Category: 0
Event: 55 Source: Ntfs
A corruption was discovered in the file system structure on volume ??.  The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x100000001418c.  The name of the file is "\Windows\System32\config\SYSTEM.LOG1". 

Log: 'System' Date/Time: 28/05/2016 06:35:00
Type: Error Category: 0
Event: 55 Source: Ntfs
A corruption was discovered in the file system structure on volume ??.  The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x100000002d2b5.  The name of the file is "<unable to determine file name>". 

Log: 'System' Date/Time: 28/05/2016 06:34:59
Type: Error Category: 0
Event: 55 Source: Ntfs
A corruption was discovered in the file system structure on volume ??.  A corruption was found in a file system index structure.  The file reference number is 0x1000000000f4e.  The name of the file is "\Windows\System32".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION". 

Log: 'System' Date/Time: 28/05/2016 06:34:59
Type: Error Category: 0
Event: 55 Source: Ntfs
A corruption was discovered in the file system structure on volume ??.  The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x2000000018966.  The name of the file is "<unable to determine file name>". 

Log: 'System' Date/Time: 28/05/2016 06:34:59
Type: Error Category: 0
Event: 55 Source: Ntfs
A corruption was discovered in the file system structure on volume ??.  A corruption was found in a file system index structure.  The file reference number is 0x1000000000f4e.  The name of the file is "\Windows\System32".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION". 

Log: 'System' Date/Time: 25/05/2016 21:10:20
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Superfetch service terminated with the following error:  The service has not been started.

Log: 'System' Date/Time: 25/05/2016 21:10:17
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 25/05/2016 21:10:17
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 23/05/2016 19:19:18
Type: Error Category: 0
Event: 55 Source: Ntfs
A corruption was discovered in the file system structure on volume ??.  The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x150000000311c6.  The name of the file is "<unable to determine file name>". 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 20/06/2016 18:56:59
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_Kingston&Prod_DataTraveler_2.0&Rev_1.00#C860008861F9CE10BA0724DF&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Log: 'System' Date/Time: 19/06/2016 11:36:21
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: 18/06/2016 19:45:26
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 71 seconds since the last report.

Log: 'System' Date/Time: 18/06/2016 19:45:26
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 71 seconds since the last report.

Log: 'System' Date/Time: 18/06/2016 08:17:04
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_Kingston&Prod_DataTraveler_2.0&Rev_1.00#C860008861F9CE10BA0724DF&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Log: 'System' Date/Time: 17/06/2016 13:42:32
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_Kingston&Prod_DataTraveler_2.0&Rev_1.00#C860008861F9CE10BA0724DF&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Log: 'System' Date/Time: 16/06/2016 08:53:45
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_Kingston&Prod_DataTraveler_2.0&Rev_1.00#C8600088637DCE10BA0824E0&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Log: 'System' Date/Time: 14/06/2016 08:40:26
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name TOWER timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 12/06/2016 17:33:53
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name code.createjs.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 12/06/2016 13:58:15
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: 11/06/2016 20:25:58
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: 11/06/2016 15:14:58
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name cdn.adsafeprotected.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 11/06/2016 15:05:36
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name nexus.officeapps.live.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 11/06/2016 08:09:12
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name TOWER timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 09/06/2016 19:43:28
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name copy.loop.services.mozilla.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 09/06/2016 18:44:23
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name TOWER timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 07/06/2016 16:49:58
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name y.analytics.yahoo.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 07/06/2016 10:57:21
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 71 seconds since the last report.

Log: 'System' Date/Time: 07/06/2016 10:57:21
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 71 seconds since the last report.

Log: 'System' Date/Time: 06/06/2016 19:06:27
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.