I was told to post this from the malware/viruses forums. My computer hangs and freezes very frequently. I can still move my mouse but cannot click on all applications and windows. Here is the log they wanted me to post.
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 21/01/2013 5:34:40 AM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 21/01/2013 5:55:49 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Users\Brad\Downloads\SoftonicDownloader_for_hi jackthis.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows. common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6 975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.window s.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa39 6087175ac9ac.manifest.
Log: 'Application' Date/Time: 16/01/2013 9:08:01 PM
Type: Error Category: 0
Event: 4103 Source: Microsoft-Windows-Winlogon
Windows license activation failed. Error 0x00000000.
Log: 'Application' Date/Time: 16/01/2013 9:08:01 PM
Type: Error Category: 0
Event: 8198 Source: Microsoft-Windows-Security-SPP
License Activation (slui.exe) failed with the following error code: 0x800401F9
Log: 'Application' Date/Time: 15/01/2013 8:21:34 PM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\Windows\System32\systemcpl.dll". Dependent Assembly Microsoft.Windows.Common-Controls,language="*",processorArchitecture="*",pu blicKeyToken="436865772d574741",type="win32",versi on="6.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
Log: 'Application' Date/Time: 15/01/2013 8:19:06 PM
Type: Error Category: 0
Event: 4103 Source: Microsoft-Windows-Winlogon
Windows license activation failed. Error 0x00000000.
Log: 'Application' Date/Time: 15/01/2013 8:19:06 PM
Type: Error Category: 0
Event: 8198 Source: Microsoft-Windows-Security-SPP
License Activation (slui.exe) failed with the following error code: 0x800401F9
Log: 'Application' Date/Time: 15/01/2013 7:49:57 AM
Type: Error Category: 0
Event: 4103 Source: Microsoft-Windows-Winlogon
Windows license activation failed. Error 0x00000000.
Log: 'Application' Date/Time: 15/01/2013 7:49:57 AM
Type: Error Category: 0
Event: 8198 Source: Microsoft-Windows-Security-SPP
License Activation (slui.exe) failed with the following error code: 0x800401F9
Log: 'Application' Date/Time: 15/01/2013 7:49:43 AM
Type: Error Category: 0
Event: 8211 Source: System Restore
The scheduled restore point could not be created. Additional information: (0x81000101).
Log: 'Application' Date/Time: 15/01/2013 7:49:43 AM
Type: Error Category: 0
Event: 8193 Source: System Restore
Failed to create restore point (Process = C:\Windows\system32\rundll32.exe /d srrstr.dll,ExecuteScheduledSPPCreation; Description = Scheduled Checkpoint; Error = 0x81000101).
Log: 'Application' Date/Time: 15/01/2013 7:47:45 AM
Type: Error Category: 0
Event: 12344 Source: VSS
Volume Shadow Copy Error: An error 0x00000000c000014d was encountered while Registry Writer was preparing the registry for a shadow copy. Check the Application and System event logs for any related errors.
Operation:
OnFreeze event
Freeze Event
Context:
Execution Context: Registry Writer
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {a811937e-d816-4cd3-a3e6-27ff86428abc}
Log: 'Application' Date/Time: 15/01/2013 7:46:00 AM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\taskeng.exe for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Task Scheduler Engine because of this error. Program: Task Scheduler Engine File: C:\Windows\System32\taskeng.exe The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C0000185 Disk type: 3
Log: 'Application' Date/Time: 15/01/2013 7:46:00 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: taskeng.exe, version: 6.1.7601.17514, time stamp: 0x4ce79d2c Faulting module name: taskeng.exe, version: 6.1.7601.17514, time stamp: 0x4ce79d2c Exception code: 0xc0000006 Fault offset: 0x000000000002a910 Faulting process id: 0x838 Faulting application start time: 0x01cdf2f439bc0ebd Faulting application path: C:\Windows\system32\taskeng.exe Faulting module path: C:\Windows\system32\taskeng.exe Report Id: 9a7dc187-5ee7-11e2-b1c9-00268314a5a8
Log: 'Application' Date/Time: 15/01/2013 7:45:21 AM
Type: Error Category: 0
Event: 12289 Source: VSS
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{7117087c-78d6-11e0-a68d-806e6f6e6963} - 0000000000000144,0x0053c008,000000000018AFB0,0,000 000000018E350,4096,[0]). hr = 0x8007045d, The request could not be performed because of an I/O device error. .
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider
Log: 'Application' Date/Time: 15/01/2013 7:00:16 AM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\mssrch.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Microsoft Windows Search Indexer because of this error. Program: Microsoft Windows Search Indexer File: C:\Windows\System32\mssrch.dll The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C0000185 Disk type: 3
Log: 'Application' Date/Time: 15/01/2013 7:00:16 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.7601.17610, time stamp: 0x4dc0d019 Faulting module name: MSSRCH.DLL, version: 7.0.7601.17610, time stamp: 0x4dc0e0c8 Exception code: 0xc0000006 Fault offset: 0x000000000011ef80 Faulting process id: 0xbb8 Faulting application start time: 0x01cdf2ed5c7cd617 Faulting application path: C:\Windows\system32\SearchIndexer.exe Faulting module path: C:\Windows\system32\MSSRCH.DLL Report Id: 37064f46-5ee1-11e2-b1c9-00268314a5a8
Log: 'Application' Date/Time: 15/01/2013 6:53:26 AM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\win32spl.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Spooler SubSystem App because of this error. Program: Spooler SubSystem App File: C:\Windows\System32\win32spl.dll The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C0000185 Disk type: 3
Log: 'Application' Date/Time: 15/01/2013 6:53:26 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: spoolsv.exe, version: 6.1.7601.17777, time stamp: 0x4f35fc1d Faulting module name: win32spl.dll, version: 6.1.7601.17777, time stamp: 0x4f360beb Exception code: 0xc0000006 Fault offset: 0x0000000000030514 Faulting process id: 0x63c Faulting application start time: 0x01cdf2ec5bfe2f31 Faulting application path: C:\Windows\System32\spoolsv.exe Faulting module path: C:\Windows\System32\win32spl.dll Report Id: 424873ba-5ee0-11e2-b1c9-00268314a5a8
Log: 'Application' Date/Time: 15/01/2013 6:53:18 AM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\sysmain.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error. Program: Host Process for Windows Services File: C:\Windows\System32\sysmain.dll The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C0000185 Disk type: 3
Log: 'Application' Date/Time: 15/01/2013 6:53:18 AM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\esent.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error. Program: Host Process for Windows Services File: C:\Windows\System32\esent.dll The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C0000185 Disk type: 3
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 21/01/2013 6:46:05 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 21/01/2013 1:45:35 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 8:45:08 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 3:44:41 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 10:46:58 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 10:44:14 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 5:43:45 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 12:43:18 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 19/01/2013 7:42:51 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 19/01/2013 2:42:24 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 19/01/2013 1:13:27 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 19/01/2013 9:41:56 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 19/01/2013 4:41:20 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 18/01/2013 11:40:53 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 18/01/2013 6:40:25 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 18/01/2013 1:39:55 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 18/01/2013 8:39:14 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 18/01/2013 3:38:39 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 17/01/2013 10:38:02 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 17/01/2013 5:37:27 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 16/01/2013 10:03:48 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/01/2013 11:46: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: 15/01/2013 6:47:56 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: 14/01/2013 10:04:31 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: 14/01/2013 9:21:17 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: 14/01/2013 5:56:12 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: 14/01/2013 5:53:04 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: 14/01/2013 5:48: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: 14/01/2013 2:01:15 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: 12/01/2013 9:00:00 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/01/2013 1:05:47 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/01/2013 7:01:04 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/01/2013 5:37:39 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: 07/01/2013 7:59:14 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: 07/01/2013 6:05:28 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: 07/01/2013 3:16:19 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/01/2013 8:45: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: 02/01/2013 5:50: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: 01/01/2013 9:57:39 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: 28/12/2012 11:15:47 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: 20/01/2013 6:03:28 AM
Type: Error Category: 0
Event: 14 Source: volsnap
The shadow copies of volume C: were aborted because of an IO failure on volume C:.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 21/01/2013 8:15:09 AM
Type: Warning Category: 2
Event: 16 Source: Microsoft-Windows-WindowsUpdateClient
Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
Log: 'System' Date/Time: 19/01/2013 8:15:08 AM
Type: Warning Category: 2
Event: 16 Source: Microsoft-Windows-WindowsUpdateClient
Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
Log: 'System' Date/Time: 18/01/2013 2:52:24 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.gateway.2wire.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 17/01/2013 10:37:46 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.gateway.2wire.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 17/01/2013 5:37:11 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.gateway.2wire.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 17/01/2013 8:15:06 AM
Type: Warning Category: 2
Event: 16 Source: Microsoft-Windows-WindowsUpdateClient
Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
Log: 'System' Date/Time: 16/01/2013 10:18:48 AM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-Kernel-Tm
The TransactionManager (TmId={33D5D438-5F09-11E2-A0CA-806E6F6E6963}, LogPath=\SystemRoot\System32\Config\TxR\{33d5d436-5f09-11e2-a0ca-806e6f6e6963}.TM) has failed to advance its log tail, due to the transaction (UOW={33D5D4EB-5F09-11E2-A0CA-00268314A5A8}, Description='') being unresolved for some time. The transaction must be forced to resolve in order for the TransactionManager to continue to provide transactional services. Forcing the incorrect outcome may cause data corruption in any subordinate ResourceManagers or Transactionmanagers.
Log: 'System' Date/Time: 16/01/2013 10:04:08 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: 16/01/2013 10:03:55 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\BtFilter failed to load for the device USB\VID_0B05&PID_179C\6&df2ee03&0&7.
Log: 'System' Date/Time: 15/01/2013 7:28:11 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.gateway.2wire.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 15/01/2013 7:28:06 PM
Type: Warning Category: 0
Event: 27 Source: e1cexpress
Intel(R) 82579V Gigabit Network Connection Network link is disconnected.
Log: 'System' Date/Time: 15/01/2013 7:27:17 PM
Type: Warning Category: 0
Event: 27 Source: e1cexpress
Intel(R) 82579V Gigabit Network Connection Network link is disconnected.
Log: 'System' Date/Time: 15/01/2013 11:46:54 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: 15/01/2013 8:15:06 AM
Type: Warning Category: 2
Event: 16 Source: Microsoft-Windows-WindowsUpdateClient
Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
Log: 'System' Date/Time: 15/01/2013 6:48:21 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: 15/01/2013 1:50:14 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: 14/01/2013 10:04:49 PM
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: 14/01/2013 9:21:36 PM
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: 14/01/2013 5:56:31 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: 14/01/2013 5:53:23 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.
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 21/01/2013 5:34:40 AM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 21/01/2013 5:55:49 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Users\Brad\Downloads\SoftonicDownloader_for_hi jackthis.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows. common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6 975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.window s.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa39 6087175ac9ac.manifest.
Log: 'Application' Date/Time: 16/01/2013 9:08:01 PM
Type: Error Category: 0
Event: 4103 Source: Microsoft-Windows-Winlogon
Windows license activation failed. Error 0x00000000.
Log: 'Application' Date/Time: 16/01/2013 9:08:01 PM
Type: Error Category: 0
Event: 8198 Source: Microsoft-Windows-Security-SPP
License Activation (slui.exe) failed with the following error code: 0x800401F9
Log: 'Application' Date/Time: 15/01/2013 8:21:34 PM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\Windows\System32\systemcpl.dll". Dependent Assembly Microsoft.Windows.Common-Controls,language="*",processorArchitecture="*",pu blicKeyToken="436865772d574741",type="win32",versi on="6.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
Log: 'Application' Date/Time: 15/01/2013 8:19:06 PM
Type: Error Category: 0
Event: 4103 Source: Microsoft-Windows-Winlogon
Windows license activation failed. Error 0x00000000.
Log: 'Application' Date/Time: 15/01/2013 8:19:06 PM
Type: Error Category: 0
Event: 8198 Source: Microsoft-Windows-Security-SPP
License Activation (slui.exe) failed with the following error code: 0x800401F9
Log: 'Application' Date/Time: 15/01/2013 7:49:57 AM
Type: Error Category: 0
Event: 4103 Source: Microsoft-Windows-Winlogon
Windows license activation failed. Error 0x00000000.
Log: 'Application' Date/Time: 15/01/2013 7:49:57 AM
Type: Error Category: 0
Event: 8198 Source: Microsoft-Windows-Security-SPP
License Activation (slui.exe) failed with the following error code: 0x800401F9
Log: 'Application' Date/Time: 15/01/2013 7:49:43 AM
Type: Error Category: 0
Event: 8211 Source: System Restore
The scheduled restore point could not be created. Additional information: (0x81000101).
Log: 'Application' Date/Time: 15/01/2013 7:49:43 AM
Type: Error Category: 0
Event: 8193 Source: System Restore
Failed to create restore point (Process = C:\Windows\system32\rundll32.exe /d srrstr.dll,ExecuteScheduledSPPCreation; Description = Scheduled Checkpoint; Error = 0x81000101).
Log: 'Application' Date/Time: 15/01/2013 7:47:45 AM
Type: Error Category: 0
Event: 12344 Source: VSS
Volume Shadow Copy Error: An error 0x00000000c000014d was encountered while Registry Writer was preparing the registry for a shadow copy. Check the Application and System event logs for any related errors.
Operation:
OnFreeze event
Freeze Event
Context:
Execution Context: Registry Writer
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {a811937e-d816-4cd3-a3e6-27ff86428abc}
Log: 'Application' Date/Time: 15/01/2013 7:46:00 AM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\taskeng.exe for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Task Scheduler Engine because of this error. Program: Task Scheduler Engine File: C:\Windows\System32\taskeng.exe The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C0000185 Disk type: 3
Log: 'Application' Date/Time: 15/01/2013 7:46:00 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: taskeng.exe, version: 6.1.7601.17514, time stamp: 0x4ce79d2c Faulting module name: taskeng.exe, version: 6.1.7601.17514, time stamp: 0x4ce79d2c Exception code: 0xc0000006 Fault offset: 0x000000000002a910 Faulting process id: 0x838 Faulting application start time: 0x01cdf2f439bc0ebd Faulting application path: C:\Windows\system32\taskeng.exe Faulting module path: C:\Windows\system32\taskeng.exe Report Id: 9a7dc187-5ee7-11e2-b1c9-00268314a5a8
Log: 'Application' Date/Time: 15/01/2013 7:45:21 AM
Type: Error Category: 0
Event: 12289 Source: VSS
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{7117087c-78d6-11e0-a68d-806e6f6e6963} - 0000000000000144,0x0053c008,000000000018AFB0,0,000 000000018E350,4096,[0]). hr = 0x8007045d, The request could not be performed because of an I/O device error. .
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider
Log: 'Application' Date/Time: 15/01/2013 7:00:16 AM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\mssrch.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Microsoft Windows Search Indexer because of this error. Program: Microsoft Windows Search Indexer File: C:\Windows\System32\mssrch.dll The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C0000185 Disk type: 3
Log: 'Application' Date/Time: 15/01/2013 7:00:16 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.7601.17610, time stamp: 0x4dc0d019 Faulting module name: MSSRCH.DLL, version: 7.0.7601.17610, time stamp: 0x4dc0e0c8 Exception code: 0xc0000006 Fault offset: 0x000000000011ef80 Faulting process id: 0xbb8 Faulting application start time: 0x01cdf2ed5c7cd617 Faulting application path: C:\Windows\system32\SearchIndexer.exe Faulting module path: C:\Windows\system32\MSSRCH.DLL Report Id: 37064f46-5ee1-11e2-b1c9-00268314a5a8
Log: 'Application' Date/Time: 15/01/2013 6:53:26 AM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\win32spl.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Spooler SubSystem App because of this error. Program: Spooler SubSystem App File: C:\Windows\System32\win32spl.dll The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C0000185 Disk type: 3
Log: 'Application' Date/Time: 15/01/2013 6:53:26 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: spoolsv.exe, version: 6.1.7601.17777, time stamp: 0x4f35fc1d Faulting module name: win32spl.dll, version: 6.1.7601.17777, time stamp: 0x4f360beb Exception code: 0xc0000006 Fault offset: 0x0000000000030514 Faulting process id: 0x63c Faulting application start time: 0x01cdf2ec5bfe2f31 Faulting application path: C:\Windows\System32\spoolsv.exe Faulting module path: C:\Windows\System32\win32spl.dll Report Id: 424873ba-5ee0-11e2-b1c9-00268314a5a8
Log: 'Application' Date/Time: 15/01/2013 6:53:18 AM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\sysmain.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error. Program: Host Process for Windows Services File: C:\Windows\System32\sysmain.dll The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C0000185 Disk type: 3
Log: 'Application' Date/Time: 15/01/2013 6:53:18 AM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\esent.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error. Program: Host Process for Windows Services File: C:\Windows\System32\esent.dll The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C0000185 Disk type: 3
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 21/01/2013 6:46:05 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 21/01/2013 1:45:35 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 8:45:08 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 3:44:41 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 10:46:58 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 10:44:14 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 5:43:45 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 20/01/2013 12:43:18 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 19/01/2013 7:42:51 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 19/01/2013 2:42:24 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 19/01/2013 1:13:27 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 19/01/2013 9:41:56 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 19/01/2013 4:41:20 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 18/01/2013 11:40:53 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 18/01/2013 6:40:25 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 18/01/2013 1:39:55 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 18/01/2013 8:39:14 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 18/01/2013 3:38:39 AM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 17/01/2013 10:38:02 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
Log: 'Application' Date/Time: 17/01/2013 5:37:27 PM
Type: Warning Category: 0
Event: 1015 Source: Microsoft-Windows-Security-SPP
Detailed HRESULT. Returned hr=0xC004F01F, Original hr=0x80049F2F
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 16/01/2013 10:03:48 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/01/2013 11:46: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: 15/01/2013 6:47:56 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: 14/01/2013 10:04:31 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: 14/01/2013 9:21:17 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: 14/01/2013 5:56:12 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: 14/01/2013 5:53:04 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: 14/01/2013 5:48: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: 14/01/2013 2:01:15 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: 12/01/2013 9:00:00 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/01/2013 1:05:47 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/01/2013 7:01:04 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/01/2013 5:37:39 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: 07/01/2013 7:59:14 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: 07/01/2013 6:05:28 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: 07/01/2013 3:16:19 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/01/2013 8:45: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: 02/01/2013 5:50: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: 01/01/2013 9:57:39 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: 28/12/2012 11:15:47 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: 20/01/2013 6:03:28 AM
Type: Error Category: 0
Event: 14 Source: volsnap
The shadow copies of volume C: were aborted because of an IO failure on volume C:.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 20/01/2013 6:03:10 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 21/01/2013 8:15:09 AM
Type: Warning Category: 2
Event: 16 Source: Microsoft-Windows-WindowsUpdateClient
Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
Log: 'System' Date/Time: 19/01/2013 8:15:08 AM
Type: Warning Category: 2
Event: 16 Source: Microsoft-Windows-WindowsUpdateClient
Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
Log: 'System' Date/Time: 18/01/2013 2:52:24 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.gateway.2wire.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 17/01/2013 10:37:46 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.gateway.2wire.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 17/01/2013 5:37:11 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.gateway.2wire.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 17/01/2013 8:15:06 AM
Type: Warning Category: 2
Event: 16 Source: Microsoft-Windows-WindowsUpdateClient
Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
Log: 'System' Date/Time: 16/01/2013 10:18:48 AM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-Kernel-Tm
The TransactionManager (TmId={33D5D438-5F09-11E2-A0CA-806E6F6E6963}, LogPath=\SystemRoot\System32\Config\TxR\{33d5d436-5f09-11e2-a0ca-806e6f6e6963}.TM) has failed to advance its log tail, due to the transaction (UOW={33D5D4EB-5F09-11E2-A0CA-00268314A5A8}, Description='') being unresolved for some time. The transaction must be forced to resolve in order for the TransactionManager to continue to provide transactional services. Forcing the incorrect outcome may cause data corruption in any subordinate ResourceManagers or Transactionmanagers.
Log: 'System' Date/Time: 16/01/2013 10:04:08 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: 16/01/2013 10:03:55 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\BtFilter failed to load for the device USB\VID_0B05&PID_179C\6&df2ee03&0&7.
Log: 'System' Date/Time: 15/01/2013 7:28:11 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.gateway.2wire.net timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 15/01/2013 7:28:06 PM
Type: Warning Category: 0
Event: 27 Source: e1cexpress
Intel(R) 82579V Gigabit Network Connection Network link is disconnected.
Log: 'System' Date/Time: 15/01/2013 7:27:17 PM
Type: Warning Category: 0
Event: 27 Source: e1cexpress
Intel(R) 82579V Gigabit Network Connection Network link is disconnected.
Log: 'System' Date/Time: 15/01/2013 11:46:54 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: 15/01/2013 8:15:06 AM
Type: Warning Category: 2
Event: 16 Source: Microsoft-Windows-WindowsUpdateClient
Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
Log: 'System' Date/Time: 15/01/2013 6:48:21 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: 15/01/2013 1:50:14 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: 14/01/2013 10:04:49 PM
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: 14/01/2013 9:21:36 PM
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: 14/01/2013 5:56:31 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: 14/01/2013 5:53:23 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.
