Got better and then got busy with work, Christmas and then other stuff ... I'm back now though
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 31/12/2016 1:36:31 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 25/12/2016 8:20:44 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 20/12/2016 4:09:54 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 19/12/2016 4:43:23 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 18/12/2016 8:10:57 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 03/12/2016 12:44:19 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 01/12/2016 12:21:00 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 17/11/2016 5:02:14 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 04/11/2016 1:25:33 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 24/10/2016 4:47:52 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 20/10/2016 5:25:07 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 06/10/2016 12:09:45 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 02/10/2016 10:55:26 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 28/09/2016 12:49:33 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 20/09/2016 3:57:24 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 08/09/2016 2:41:30 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 19/08/2016 5:21:23 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 08/08/2016 5:55:29 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 30/06/2016 2:37:03 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 14/06/2016 5:22:22 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
Log: 'System' Date/Time: 18/04/2016 1:44:01 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 31/12/2016 12:26:21 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 31/12/2016 12:21:19 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 31/12/2016 12:20:49 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 27/12/2016 1:57:13 AM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 20.
Log: 'System' Date/Time: 25/12/2016 9:41:53 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 25/12/2016 9:41:23 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 25/12/2016 8:20:41 PM
Type: Error Category: 0
Event: 13 Source: Microsoft-Windows-HAL
The system watchdog timer was triggered.
Log: 'System' Date/Time: 25/12/2016 8:20:59 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 5:46:55 AM on ?12/?24/?2016 was unexpected.
Log: 'System' Date/Time: 23/12/2016 4:14:10 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 23/12/2016 3:23:26 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 23/12/2016 3:22:56 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 23/12/2016 3:17:50 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 23/12/2016 3:17:20 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 20/12/2016 11:09:10 PM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 20.
Log: 'System' Date/Time: 20/12/2016 7:06:22 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 20/12/2016 5:45:36 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 20/12/2016 5:45:06 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 20/12/2016 4:09:46 PM
Type: Error Category: 0
Event: 13 Source: Microsoft-Windows-HAL
The system watchdog timer was triggered.
Log: 'System' Date/Time: 20/12/2016 4:10:23 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 6:39:39 PM on ?12/?19/?2016 was unexpected.
Log: 'System' Date/Time: 19/12/2016 4:43:20 PM
Type: Error Category: 0
Event: 13 Source: Microsoft-Windows-HAL
The system watchdog timer was triggered.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 31/12/2016 6:26:30 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name g1.symcb.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 31/12/2016 5:28:07 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x7f8162c7 for Disk 3 (PDO name: \Device\00000085) was retried.
Log: 'System' Date/Time: 31/12/2016 5:20: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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20: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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20: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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20: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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20: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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20:21 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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20:21 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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20:21 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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20:21 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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20:21 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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20:17 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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20:11 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: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
Log: 'System' Date/Time: 31/12/2016 5:20:11 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: D:, DeviceName: \Device\HarddiskVolume10. (This device does not exist.)
Log: 'System' Date/Time: 31/12/2016 5:20:11 PM
Type: Warning Category: 0
Event: 51 Source: disk
An error was detected on device \Device\Harddisk1\DR5 during a paging operation.
Log: 'System' Date/Time: 31/12/2016 4:50:50 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: 31/12/2016 9:36:57 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: 31/12/2016 6:36:32 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.msftncsi.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 31/12/2016 5:01:57 AM
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 108859 seconds since the last report.