Vino's Event Viewer v01c run on Windows 2008 in English Report run at 21/11/2011 8:59:24 PM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 19/11/2011 4:30:33 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/2011 1:28:30 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: 16/11/2011 4:10:06 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: 15/11/2011 11:32:01 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: 11/11/2011 3:19: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: 10/11/2011 1:10:38 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: 09/11/2011 3:08:43 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/11/2011 1:45: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: 21/10/2011 10:43:03 AM Type: Critical Category: 64 Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode The device Apple iPod (location Port_#0003.Hub_#0008) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. Log: 'System' Date/Time: 21/10/2011 10:43:03 AM Type: Critical Category: 64 Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. Log: 'System' Date/Time: 31/08/2011 10:02:10 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: 31/08/2011 9:36:55 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: 11/08/2011 3:57: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: 08/08/2011 7:49:17 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: 06/07/2011 3:16:08 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: 15/04/2011 12:06:54 AM Type: Critical Category: 64 Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode The device MTP USB Device (location Port_#0003.Hub_#0008) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. Log: 'System' Date/Time: 15/04/2011 12:06:54 AM Type: Critical Category: 64 Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. Log: 'System' Date/Time: 10/04/2011 8:33:49 PM Type: Critical Category: 64 Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode The device MTP USB Device (location Port_#0003.Hub_#0008) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. Log: 'System' Date/Time: 10/04/2011 8:33:49 PM Type: Critical Category: 64 Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. Log: 'System' Date/Time: 02/04/2011 1:51:01 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. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 21/11/2011 7:37:06 PM Type: Error Category: 0 Event: 10010 Source: Microsoft-Windows-DistributedCOM The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Log: 'System' Date/Time: 21/11/2011 12:10:48 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: 21/11/2011 12:05:51 PM Type: Error Category: 0 Event: 10010 Source: Microsoft-Windows-DistributedCOM The server {752073A1-23F2-4396-85F0-8FDB879ED0ED} did not register with DCOM within the required timeout. Log: 'System' Date/Time: 21/11/2011 11:53:42 AM Type: Error Category: 0 Event: 7001 Source: Service Control Manager The Peer Networking Grouping service depends on the Peer Name Resolution Protocol service which failed to start because of the following error: After starting, the service hung in a start-pending state. Log: 'System' Date/Time: 21/11/2011 11:49:42 AM Type: Error Category: 0 Event: 7022 Source: Service Control Manager The Peer Name Resolution Protocol service hung on starting. Log: 'System' Date/Time: 21/11/2011 11:48:22 AM Type: Error Category: 0 Event: 7001 Source: Service Control Manager The Peer Networking Grouping service depends on the Peer Name Resolution Protocol service which failed to start because of the following error: After starting, the service hung in a start-pending state. Log: 'System' Date/Time: 21/11/2011 11:47:39 AM Type: Error Category: 0 Event: 7022 Source: Service Control Manager The Peer Name Resolution Protocol service hung on starting. Log: 'System' Date/Time: 21/11/2011 11:46:19 AM Type: Error Category: 0 Event: 7000 Source: Service Control Manager The Steam Client 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: 21/11/2011 11:46:19 AM Type: Error Category: 0 Event: 7009 Source: Service Control Manager A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. Log: 'System' Date/Time: 21/11/2011 11:45:45 AM Type: Error Category: 0 Event: 7001 Source: Service Control Manager The Peer Networking Grouping service depends on the Peer Name Resolution Protocol service which failed to start because of the following error: After starting, the service hung in a start-pending state. Log: 'System' Date/Time: 21/11/2011 11:45:32 AM Type: Error Category: 0 Event: 7022 Source: Service Control Manager The Peer Name Resolution Protocol service hung on starting. Log: 'System' Date/Time: 21/11/2011 6:15:49 AM Type: Error Category: 0 Event: 2001 Source: Microsoft Antimalware Microsoft Antimalware has encountered an error trying to update signatures. New Signature Version: Previous Signature Version: 1.115.2192.0 Update Source: Microsoft Update Server Update Stage: Download Source Path: http://www.microsoft.com Signature Type: AntiVirus Update Type: Full User: NT AUTHORITY\SYSTEM Current Engine Version: Previous Engine Version: 1.1.7801.0 Error code: 0xc80003f6 Error description: One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful. Log: 'System' Date/Time: 21/11/2011 6:15:49 AM Type: Error Category: 0 Event: 2001 Source: Microsoft Antimalware Microsoft Antimalware has encountered an error trying to update signatures. New Signature Version: Previous Signature Version: 1.115.2192.0 Update Source: Microsoft Update Server Update Stage: Install Source Path: http://www.microsoft.com Signature Type: AntiVirus Update Type: Full User: NT AUTHORITY\SYSTEM Current Engine Version: Previous Engine Version: 1.1.7801.0 Error code: 0xc80003f6 Error description: One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful. Log: 'System' Date/Time: 21/11/2011 6:15:45 AM Type: Error Category: 0 Event: 2001 Source: Microsoft Antimalware Microsoft Antimalware has encountered an error trying to update signatures. New Signature Version: Previous Signature Version: 1.115.2192.0 Update Source: Microsoft Update Server Update Stage: Install Source Path: http://www.microsoft.com Signature Type: AntiVirus Update Type: Full User: NT AUTHORITY\SYSTEM Current Engine Version: Previous Engine Version: 1.1.7801.0 Error code: 0xc80003f6 Error description: One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful. Log: 'System' Date/Time: 21/11/2011 5:46:20 AM Type: Error Category: 0 Event: 7000 Source: Service Control Manager The Windows Search 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: 21/11/2011 5:46:20 AM Type: Error Category: 0 Event: 7009 Source: Service Control Manager A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect. Log: 'System' Date/Time: 21/11/2011 5:44:46 AM Type: Error Category: 0 Event: 7000 Source: Service Control Manager The NVIDIA Update Service Daemon 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: 21/11/2011 5:44:10 AM Type: Error Category: 0 Event: 7009 Source: Service Control Manager A timeout was reached (30000 milliseconds) while waiting for the NVIDIA Update Service Daemon service to connect. Log: 'System' Date/Time: 21/11/2011 5:41:15 AM Type: Error Category: 0 Event: 7000 Source: Service Control Manager The Intuit Update 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: 21/11/2011 5:41:15 AM Type: Error Category: 0 Event: 7009 Source: Service Control Manager A timeout was reached (30000 milliseconds) while waiting for the Intuit Update Service service to connect. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 21/11/2011 4:58:25 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: 20/11/2011 2:51:26 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:47:55 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:47:55 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:47:55 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:47:55 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:47:55 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:47:55 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:47:55 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:47:55 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:11:19 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:04:37 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 2:04:37 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 1:56:23 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 1:56:23 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 1:56:23 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 1:56:23 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 1:56:23 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 1:56:23 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem. Log: 'System' Date/Time: 20/11/2011 1:56:23 PM Type: Warning Category: 0 Event: 2012 Source: srv While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem.