VEW Log continued 3/3
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 08/01/2013 6:35:29 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: 06/01/2013 7:50: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: 06/01/2013 7:21: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: 04/01/2013 9:56:00 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/12/2012 6:40:28 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/12/2012 6:32: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: 29/12/2012 5:54:10 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: 27/12/2012 7:18: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: 26/12/2012 5:43:21 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: 22/12/2012 2:00:41 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/12/2012 8:53:15 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: 18/12/2012 6:01:23 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: 18/12/2012 2:35:03 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/12/2012 11:20: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: 15/12/2012 10:52: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: 28/09/2012 8:00:22 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: 11/01/2013 3:12:30 AM
Type: Error Category: 0
Event: 8003 Source: bowser
The master browser has received a server announcement from the computer BUCK-PC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{BA7FB304-0598-44D2-BA04-BB77413308DF}. The master browser is stopping or an election is being forced.
Log: 'System' Date/Time: 11/01/2013 1:01:36 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 12 service to connect.
Log: 'System' Date/Time: 11/01/2013 12:59:31 AM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: is3srv
Log: 'System' Date/Time: 11/01/2013 12:59:16 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The NTRU TSS v1.2.1.34 TCS service depends on the TPM Base Services service which failed to start because of the following error: The operation completed successfully.
Log: 'System' Date/Time: 11/01/2013 12:03:04 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 12 service to connect.
Log: 'System' Date/Time: 11/01/2013 12:00:59 AM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: is3srv
Log: 'System' Date/Time: 11/01/2013 12:00:46 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The NTRU TSS v1.2.1.34 TCS service depends on the TPM Base Services service which failed to start because of the following error: The operation completed successfully.
Log: 'System' Date/Time: 10/01/2013 11:59:16 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {51FA2736-5DEE-11D4-98E8-006008BF430C} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 10/01/2013 8:47:49 AM
Type: Error Category: 0
Event: 8032 Source: BROWSER
The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{BA7FB304-0598-44D2-BA04-BB77413308DF}. The backup browser is stopping.
Log: 'System' Date/Time: 10/01/2013 8:47:29 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 12 service to connect.
Log: 'System' Date/Time: 10/01/2013 8:45:26 AM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: is3srv
Log: 'System' Date/Time: 10/01/2013 8:45:12 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The NTRU TSS v1.2.1.34 TCS service depends on the TPM Base Services service which failed to start because of the following error: The operation completed successfully.
Log: 'System' Date/Time: 10/01/2013 8:42:59 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {51FA2736-5DEE-11D4-98E8-006008BF430C} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 10/01/2013 8:02:43 AM
Type: Error Category: 0
Event: 8032 Source: BROWSER
The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{BA7FB304-0598-44D2-BA04-BB77413308DF}. The backup browser is stopping.
Log: 'System' Date/Time: 09/01/2013 6:22:12 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 12 service to connect.
Log: 'System' Date/Time: 09/01/2013 6:20:10 PM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: is3srv
Log: 'System' Date/Time: 09/01/2013 6:20:02 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The NTRU TSS v1.2.1.34 TCS service depends on the TPM Base Services service which failed to start because of the following error: The operation completed successfully.
Log: 'System' Date/Time: 08/01/2013 7:18:43 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 12 service to connect.
Log: 'System' Date/Time: 08/01/2013 7:17:31 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4EB61BAC-A3B6-4760-9581-655041EF4D69} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 08/01/2013 7:16:39 PM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: is3srv
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/01/2013 5:50:13 PM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 22 seconds since the last report.
Log: 'System' Date/Time: 11/01/2013 5:50:13 PM
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 22 seconds since the last report.
Log: 'System' Date/Time: 11/01/2013 5:50:12 PM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 22 seconds since the last report.
Log: 'System' Date/Time: 11/01/2013 5:50:12 PM
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 22 seconds since the last report.
Log: 'System' Date/Time: 11/01/2013 5:09:34 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name shasta-clt.symantec.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 11/01/2013 4:55:19 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name spoc-pool-gtm.norton.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 11/01/2013 4:55:18 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name client.akamai.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 11/01/2013 4:55:13 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.Belkin timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 11/01/2013 4:55:08 PM
Type: Warning Category: 0
Event: 27 Source: e1cexpress
Intel(R) 82579LM Gigabit Network Connection Network link is disconnected.
Log: 'System' Date/Time: 11/01/2013 3:11:56 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name BUCK-PC.belkin timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 11/01/2013 3:11:17 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name BUCK-PC.belkin timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 11/01/2013 2:05:53 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name dns.msftncsi.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 11/01/2013 2:02:11 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name postnewsweekmedia.112.2o7.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 11/01/2013 1:34:47 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll
Log: 'System' Date/Time: 11/01/2013 1:34:24 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name BOTANICALBLOOMS.belkin timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 11/01/2013 1:06:53 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name
www.earthlink.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 11/01/2013 12:59:17 AM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
Log: 'System' Date/Time: 11/01/2013 12:59:07 AM
Type: Warning Category: 0
Event: 27 Source: e1cexpress
Intel(R) 82579LM Gigabit Network Connection Network link is disconnected.
Log: 'System' Date/Time: 11/01/2013 12:59:05 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device USB\VID_0A5C&PID_5801&MI_01\7&1eb0f4e8&0&0001.
Log: 'System' Date/Time: 11/01/2013 12:58:18 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Thanks Jacee.