Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 01/11/2014 22:18:43
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 03/09/2013 11:47:19
Type: Critical Category: 0
Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (SUPERAntiSpyware, from vendor SUPERAntiSpyware.com) was hard-blocked and raised the following: SUPERAntiSpyware is incompatible with this version of Windows. For more information, contact SUPERAntiSpyware.com.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 01/11/2014 17:53:21
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: PCDiag.exe, version: 4.0.0.3, time stamp: 0x4a76b371 Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb10c6 Exception code: 0xe0434f4d Fault offset: 0x0000812f Faulting process id: 0x1204 Faulting application start time: 0x01cff5fb730933f5 Faulting application path: C:\Program Files\Toshiba\PCDiag\PCDiag.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: f758ddd6-61ef-11e4-b7db-00266c302f38
Log: 'Application' Date/Time: 01/11/2014 17:53:12
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: NDSTray.exe, version: 7.4.1.29, time stamp: 0x4a5ad27f Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea91c Exception code: 0xc0150010 Fault offset: 0x00083fd3 Faulting process id: 0xf90 Faulting application start time: 0x01cff5ed85ad53f9 Faulting application path: C:\Program Files\TOSHIBA\ConfigFree\NDSTray.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: f20d26e8-61ef-11e4-b7db-00266c302f38
Log: 'Application' Date/Time: 01/11/2014 17:51:01
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\dbgeng.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 Windows Problem Reporting because of this error. Program: Windows Problem Reporting File: C:\Windows\System32\dbgeng.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: 01/11/2014 17:51:01
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WerFault.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc2d9 Faulting module name: dbgeng.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b7bb Exception code: 0xc0000006 Fault offset: 0x00204312 Faulting process id: 0x1588 Faulting application start time: 0x01cff5fbdf0c7cba Faulting application path: C:\Windows\system32\WerFault.exe Faulting module path: C:\Windows\system32\dbgeng.dll Report Id: a405d8c7-61ef-11e4-b7db-00266c302f38
Log: 'Application' Date/Time: 01/11/2014 17:50:20
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\Prefetch\AgAppLaunch.db 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\Prefetch\AgAppLaunch.db 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: 01/11/2014 17:50:20
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: svchost.exe_SysMain, version: 6.1.7600.16385, time stamp: 0x4a5bc100 Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeaf722 Exception code: 0xc0000006 Fault offset: 0x00009b60 Faulting process id: 0x3d4 Faulting application start time: 0x01cff5ed6cf32dca Faulting application path: C:\Windows\System32\svchost.exe Faulting module path: C:\Windows\system32\msvcrt.dll Report Id: 8b96398d-61ef-11e4-b7db-00266c302f38
Log: 'Application' Date/Time: 01/11/2014 17:48:08
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\mfc80.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 ConfigFree Switch Manager Process because of this error. Program: ConfigFree Switch Manager Process File: C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\mfc80.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: 01/11/2014 17:48:08
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\mfc80.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 ConfigFree Task Tray Menu because of this error. Program: ConfigFree Task Tray Menu File: C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\mfc80.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: 01/11/2014 17:47:14
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: NDSTray.exe, version: 7.4.1.29, time stamp: 0x4a5ad27f Faulting module name: MFC80.DLL, version: 8.0.50727.6195, time stamp: 0x4dcdeca2 Exception code: 0xc0000006 Fault offset: 0x000242ce Faulting process id: 0xf90 Faulting application start time: 0x01cff5ed85ad53f9 Faulting application path: C:\Program Files\TOSHIBA\ConfigFree\NDSTray.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL Report Id: 1cc4ee7b-61ef-11e4-b7db-00266c302f38
Log: 'Application' Date/Time: 01/11/2014 17:47:14
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: CFSwMgr.exe, version: 7.0.1.9, time stamp: 0x4a6edff2 Faulting module name: MFC80.DLL, version: 8.0.50727.6195, time stamp: 0x4dcdeca2 Exception code: 0xc0000006 Fault offset: 0x00032ad2 Faulting process id: 0xfc0 Faulting application start time: 0x01cff5ed85f13bb9 Faulting application path: C:\Program Files\TOSHIBA\ConfigFree\CFSwMgr.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL Report Id: 1cc74fdb-61ef-11e4-b7db-00266c302f38
Log: 'Application' Date/Time: 01/11/2014 17:43:21
Type: Error Category: 0
Event: 11704 Source: MsiInstaller
Product: TOSHIBA HDD/SSD Alert -- Error 1704.An installation for PreReq is currently suspended. You must undo the changes made by that installation to continue. Do you want to undo those changes?
Log: 'Application' Date/Time: 01/11/2014 17:42:48
Type: Error Category: 0
Event: 8194 Source: VSS
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process.
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {964e6d17-8e08-44d4-af30-2cd91e8bd66a}
Log: 'Application' Date/Time: 01/11/2014 17:20:07
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "c:\Program Files\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.
Log: 'Application' Date/Time: 01/11/2014 13:54:37
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{44A722B3-8DD8-4886-A867-617A8F24E40F}\mpengine.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:\ProgramData\Microsoft\Windows Defender\Definition Updates\{44A722B3-8DD8-4886-A867-617A8F24E40F}\mpengine.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: 01/11/2014 13:54:37
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: svchost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc100 Faulting module name: mpengine.dll, version: 1.1.11104.0, time stamp: 0x543d815e Exception code: 0xc0000006 Fault offset: 0x003f0ac0 Faulting process id: 0xaa0 Faulting application start time: 0x01cff5d97a38b1e4 Faulting application path: C:\Windows\System32\svchost.exe Faulting module path: C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{44A722B3-8DD8-4886-A867-617A8F24E40F}\mpengine.dll Report Id: 9dc1ae34-61ce-11e4-8797-0026b667c678
Log: 'Application' Date/Time: 01/11/2014 13:53:08
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: 01/11/2014 13:53:08
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: svchost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc100 Faulting module name: sysmain.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba10 Exception code: 0xc0000006 Fault offset: 0x00087b94 Faulting process id: 0x3c0 Faulting application start time: 0x01cff5d96b2fec1f Faulting application path: C:\Windows\System32\svchost.exe Faulting module path: c:\windows\system32\sysmain.dll Report Id: 689dcc9b-61ce-11e4-8797-0026b667c678
Log: 'Application' Date/Time: 01/11/2014 13:52:14
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\IPSECSVC.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\IPSECSVC.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: 01/11/2014 13:52:14
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: svchost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc100 Faulting module name: ipsecsvc.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b865 Exception code: 0xc0000006 Fault offset: 0x00031d30 Faulting process id: 0xcb4 Faulting application start time: 0x01cff5d97d4bf0e6 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: c:\windows\system32\ipsecsvc.dll Report Id: 48930107-61ce-11e4-8797-0026b667c678
Log: 'Application' Date/Time: 01/11/2014 13:50:23
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\eapphost.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\eapphost.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 - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 01/11/2014 22:18:45
Type: Information Category: 0
Event: 903 Source: Microsoft-Windows-Security-SPP
The Software Protection service has stopped.
Log: 'Application' Date/Time: 01/11/2014 22:15:07
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket 3031133169, type 5 Event Name: WindowsUpdateFailure Response: Not available Cab Id: 0 Problem signature: P1: 7.6.7600.256 P2: 80072efd P3: 00000000-0000-0000-0000-000000000000 P4: Scan P5: 101 P6: Unmanaged P7: P8: P9: P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_837afdc942feb2e11f432e5bf43e434282f8bfb8_1125d420 Analysis symbol: Rechecking for solution: 0 Report Id: 871373e9-6214-11e4-9914-00266c302f38 Report Status: 0
Log: 'Application' Date/Time: 01/11/2014 22:15:04
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: WindowsUpdateFailure Response: Not available Cab Id: 0 Problem signature: P1: 7.6.7600.256 P2: 80072efd P3: 00000000-0000-0000-0000-000000000000 P4: Scan P5: 101 P6: Unmanaged P7: P8: P9: P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_837afdc942feb2e11f432e5bf43e434282f8bfb8_1111c754 Analysis symbol: Rechecking for solution: 0 Report Id: 871373e9-6214-11e4-9914-00266c302f38 Report Status: 4
Log: 'Application' Date/Time: 01/11/2014 22:15:04
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: WindowsUpdateFailure Response: Not available Cab Id: 0 Problem signature: P1: 7.6.7600.256 P2: 80072efd P3: 00000000-0000-0000-0000-000000000000 P4: Scan P5: 101 P6: Unmanaged P7: P8: P9: P10: Attached files: These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: 871373e9-6214-11e4-9914-00266c302f38 Report Status: 0
Log: 'Application' Date/Time: 01/11/2014 22:13:45
Type: Information Category: 0
Event: 902 Source: Microsoft-Windows-Security-SPP
The Software Protection service has started. 6.1.7601.17514
Log: 'Application' Date/Time: 01/11/2014 22:13:45
Type: Information Category: 0
Event: 1003 Source: Microsoft-Windows-Security-SPP
The Software Protection service has completed licensing status check. Application Id=55c92734-d682-4d71-983e-d6ec3f16059f Licensing Status=
1: 01f5fc37-a99e-45c5-b65e-d762f3518ead, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
2: 2e7d060d-4714-40f2-9896-1e4f15b612ad, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
3: 3b965dfc-31d9-4903-886f-873a0382776c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
4: 586bc076-c93d-429a-afe5-a69fbc644e88, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
5: 5e017a8a-f3f9-4167-b1bd-ba3e236a4d8f, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
6: 5e35dc43-389b-47c5-b889-2088b06738cb, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
7: 6a7d5d8a-92af-4e6a-af4b-8fddaec800e5, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
8: 9ab82e0c-ffc9-4107-baa1-c65a8bd3ccc3, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
9: 9f83d90f-a151-4665-ae69-30b3f63ec659, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
10: a63275f4-530c-48a7-b0d3-4f00d688d151, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
11: b8a4bb91-69b1-460d-93f8-40e0670af04a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
12: d2c04e90-c3dd-4260-b0f3-f845f5d27d64, 1, 1 [(0 [0x00000000, 1, 0], [(?)(?)( 1 0x00000000 0 0 msft:rm/algorithm/bios/4.0 0x00000000 0)(?)(?)(?)])(1 )(2 )]
13: e68b141f-4dfa-4387-b3b7-e65c4889216e, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
14: ee4e1629-bcdc-4b42-a68f-b92e135f78d7, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
15: 4a8149bb-7d61-49f4-8822-82c7bf88d64b, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
16: afd5f68f-b70f-4000-a21d-28dbc8be8b07, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
Log: 'Application' Date/Time: 01/11/2014 22:13:44
Type: Information Category: 0
Event: 1066 Source: Microsoft-Windows-Security-SPP
Initialization status for service objects. C:\Windows\system32\sppwinob.dll, msft:spp/windowsfunctionality/agent/7.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/phone/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/pkey/2005, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/TaskScheduler/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/licenserenewal/1.0, 0x00000000, 0x00000000
Log: 'Application' Date/Time: 01/11/2014 22:13:42
Type: Information Category: 0
Event: 1 Source: SecurityCenter
The Windows Security Center Service has started.
Log: 'Application' Date/Time: 01/11/2014 22:13:42
Type: Information Category: 0
Event: 900 Source: Microsoft-Windows-Security-SPP
The Software Protection service is starting.
Log: 'Application' Date/Time: 01/11/2014 22:13:40
Type: Information Category: 0
Event: 1076 Source: ASP.NET 4.0.30319.0
State server starts listening with 6 listeners
Log: 'Application' Date/Time: 01/11/2014 22:11:50
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket 649591368, type 5 Event Name: ServiceHang Response: Not available Cab Id: 0 Problem signature: P1: WdiServiceHost P2: wdi.dll P3: 6.1.7600.16385 P4: 20 P5: 2 P6: P7: P8: P9: P10: Attached files: C:\Windows\Temp\WERADCB.tmp.WERInternalMetadata.xml C:\Windows\Temp\WERADDC.tmp.hdmp C:\Windows\Temp\WERB665.tmp.mdmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_WdiServiceHost_9dd9ae16a6e249d236b8827ddc731f247677bdd9_0382d26b Analysis symbol: Rechecking for solution: 0 Report Id: 0da383fe-6214-11e4-9914-00266c302f38 Report Status: 0
Log: 'Application' Date/Time: 01/11/2014 22:11:45
Type: Information Category: 1
Event: 1003 Source: Microsoft-Windows-Search
The Windows Search Service started.
Log: 'Application' Date/Time: 01/11/2014 22:11:44
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: ServiceHang Response: Not available Cab Id: 0 Problem signature: P1: WdiServiceHost P2: wdi.dll P3: 6.1.7600.16385 P4: 20 P5: 2 P6: P7: P8: P9: P10: Attached files: C:\Windows\Temp\WERADCB.tmp.WERInternalMetadata.xml C:\Windows\Temp\WERADDC.tmp.hdmp C:\Windows\Temp\WERB665.tmp.mdmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_WdiServiceHost_9dd9ae16a6e249d236b8827ddc731f247677bdd9_cab_0faab940 Analysis symbol: Rechecking for solution: 0 Report Id: 0da383fe-6214-11e4-9914-00266c302f38 Report Status: 4
Log: 'Application' Date/Time: 01/11/2014 22:11:43
Type: Information Category: 3
Event: 302 Source: ESENT
Windows (3368) Windows: The database engine has successfully completed recovery steps.
Log: 'Application' Date/Time: 01/11/2014 22:11:43
Type: Information Category: 3
Event: 301 Source: ESENT
Windows (3368) Windows: The database engine has begun replaying logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log.
Log: 'Application' Date/Time: 01/11/2014 22:11:43
Type: Information Category: 3
Event: 300 Source: ESENT
Windows (3368) Windows: The database engine is initiating recovery steps.
Log: 'Application' Date/Time: 01/11/2014 22:11:42
Type: Information Category: 1
Event: 102 Source: ESENT
Windows (3368) Windows: The database engine (6.01.7601.0000) started a new instance (0).
Log: 'Application' Date/Time: 01/11/2014 22:11:40
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: ServiceHang Response: Not available Cab Id: 0 Problem signature: P1: WdiServiceHost P2: wdi.dll P3: 6.1.7600.16385 P4: 20 P5: 2 P6: P7: P8: P9: P10: Attached files: These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: 0da383fe-6214-11e4-9914-00266c302f38 Report Status: 0
Log: 'Application' Date/Time: 01/11/2014 22:10:22
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: toshibareminder.exe P2: 8.0.4.0 P3: 4a7190e1 P4: System.Xml P5: 2.0.0.0 P6: 51e9fc46 P7: 283c P8: 123 P9: System.InvalidOperationException P10: Attached files: These files may be available here: C:\Users\Ray\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_toshibareminder._3ee96f35a526f8cc19173bbedfb3126a923a397_0ec97ba4 Analysis symbol: Rechecking for solution: 0 Report Id: df09a1ff-6213-11e4-9914-0026b667c678 Report Status: 6
Log: 'Application' Date/Time: 01/11/2014 22:10:18
Type: Information Category: 0
Event: 0 Source: TemproMonitoringService
Service started successfully.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 01/11/2014 17:58:35
Type: Warning Category: 3
Event: 4879 Source: Microsoft-Windows-MSDTC Client 2
MSDTC encountered an error (HR=0x80000171) while attempting to establish a secure connection with system RAY-TOSH.
Log: 'Application' Date/Time: 30/10/2014 16:24:54
Type: Warning Category: 0
Event: 6005 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (EndShell).
Log: 'Application' Date/Time: 30/10/2014 11:29:29
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-473944389-2725691915-1153018630-1000_Classes:
Process 1824 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000_CLASSES
Log: 'Application' Date/Time: 30/10/2014 11:29:28
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-473944389-2725691915-1153018630-1000:
Process 1824 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Log: 'Application' Date/Time: 30/10/2014 11:24:36
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Index Corruption}.
Log: 'Application' Date/Time: 30/10/2014 10:49:48
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-473944389-2725691915-1153018630-1000:
Process 3176 (\Device\HarddiskVolume2\Windows\System32\msiexec.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Log: 'Application' Date/Time: 29/10/2014 22:21:47
Type: Warning Category: 18
Event: 4627 Source: Microsoft-Windows-EventSystem
The COM+ Event System timed out attempting to fire the DisplayUnlock method on event class {D5978630-5B9F-11D1-8DD2-00AA004ABD5E} for publisher and subscriber . The subscriber failed to respond within 180 seconds. The display name of the subscription is "Explorer". The HRESULT was 800705b4.
Log: 'Application' Date/Time: 29/10/2014 22:21:36
Type: Warning Category: 18
Event: 4627 Source: Microsoft-Windows-EventSystem
The COM+ Event System timed out attempting to fire the DisplayLock method on event class {D5978630-5B9F-11D1-8DD2-00AA004ABD5E} for publisher and subscriber . The subscriber failed to respond within 180 seconds. The display name of the subscription is "Explorer". The HRESULT was 800705b4.
Log: 'Application' Date/Time: 29/10/2014 18:31:36
Type: Warning Category: 3
Event: 4879 Source: Microsoft-Windows-MSDTC Client 2
MSDTC encountered an error (HR=0x80000171) while attempting to establish a secure connection with system RAY-TOSH.
Log: 'Application' Date/Time: 29/10/2014 15:02:25
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-473944389-2725691915-1153018630-1000_Classes:
Process 1872 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000_CLASSES
Log: 'Application' Date/Time: 29/10/2014 15:02:23
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 17 user registry handles leaked from \Registry\User\S-1-5-21-473944389-2725691915-1153018630-1000:
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 1872 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\Root
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\Windows\CurrentVersion\Explorer
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\SmartCardRoot
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\Disallowed
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\Windows NT\CurrentVersion
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\TrustedPeople
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Policies\Microsoft\SystemCertificates
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\My
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\trust
Process 532 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\CA
Log: 'Application' Date/Time: 20/10/2014 15:39:14
Type: Warning Category: 7
Event: 508 Source: ESENT
wuaueng.dll (1008) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 0 (0x0000000000000000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Log: 'Application' Date/Time: 05/10/2014 12:39:59
Type: Warning Category: 0
Event: 6001 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <Sens> failed a notification event.
Log: 'Application' Date/Time: 01/10/2014 15:16:11
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 2 user registry handles leaked from \Registry\User\S-1-5-21-473944389-2725691915-1153018630-1000_Classes:
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000_CLASSES
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000_CLASSES
Log: 'Application' Date/Time: 01/10/2014 15:16:10
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 16 user registry handles leaked from \Registry\User\S-1-5-21-473944389-2725691915-1153018630-1000:
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\Root
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\Windows\CurrentVersion\Explorer
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\SmartCardRoot
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\Disallowed
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\Windows NT\CurrentVersion
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\TrustedPeople
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Policies\Microsoft\SystemCertificates
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\My
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\trust
Process 1872 (\Device\HarddiskVolume2\Program Files\ESET\ESET Smart Security\egui.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\SystemCertificates\CA
Log: 'Application' Date/Time: 01/10/2014 12:50:35
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 6 user registry handles leaked from \Registry\User\S-1-5-21-473944389-2725691915-1153018630-1000:
Process 988 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software
Process 988 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\Internet Explorer\Main
Process 988 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Policies
Process 988 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Process 988 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Process 988 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-473944389-2725691915-1153018630-1000\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings
Log: 'Application' Date/Time: 29/08/2014 19:48:09
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files\Apple Software Update\SoftwareUpdate.exe' (pid 10116) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 29/08/2014 19:48:09
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\System32\dllhost.exe' (pid 7088) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 29/08/2014 19:48:07
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files\Apple Software Update\SoftwareUpdate.exe' (pid 10116) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 29/08/2014 19:48:07
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\System32\dllhost.exe' (pid 7088) cannot be restarted - Application SID does not match Conductor SID..
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 01/11/2014 22:09:04
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/11/2014 13:40:26
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/10/2014 10:26:11
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/10/2014 09:46:14
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: 30/10/2014 23:18:45
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: 30/10/2014 16:58:53
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 30/10/2014 16:26:42
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: 30/10/2014 12:45:25
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: 30/10/2014 11:48:31
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/10/2014 16:48:58
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/10/2014 16:33:59
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/10/2014 15:10:20
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/10/2014 15:01:55
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device WPD FileSystem Volume Driver (location (unknown)) 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: 29/10/2014 15:01:55
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: 29/10/2014 09:16:39
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/10/2014 12:10:49
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/10/2014 11:08:50
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: 25/10/2014 16:55:28
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: 25/10/2014 14:01:52
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: 23/10/2014 08:57:37
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: 01/11/2014 22:11:40
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: tcpipBM
Log: 'System' Date/Time: 01/11/2014 22:11:40
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Diagnostic Service Host service hung on starting.
Log: 'System' Date/Time: 01/11/2014 22:11:41
Type: Error Category: 0
Event: 14332 Source: Microsoft-Windows-WMPNSS-Service
Service 'WMPNetworkSvc' did not start correctly because CoCreateInstance(CLSID_UPnPDeviceFinder) encountered error '0x80004005'. Verify that the UPnPHost service is running and that the UPnPHost component of Windows is installed properly.
Log: 'System' Date/Time: 01/11/2014 22:09:44
Type: Error Category: 0
Event: 7003 Source: Service Control Manager
The Net.Tcp Listener Adapter service depends the following service: was. This service might not be installed.
Log: 'System' Date/Time: 01/11/2014 22:09:44
Type: Error Category: 0
Event: 7003 Source: Service Control Manager
The Net.Pipe Listener Adapter service depends the following service: was. This service might not be installed.
Log: 'System' Date/Time: 01/11/2014 22:09:44
Type: Error Category: 0
Event: 7003 Source: Service Control Manager
The Net.Msmq Listener Adapter service depends the following service: msmq. This service might not be installed.
Log: 'System' Date/Time: 01/11/2014 22:09:19
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 18:22:09 on ?01/?11/?2014 was unexpected.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:36
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:31
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
Log: 'System' Date/Time: 01/11/2014 18:07:31
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 01/11/2014 22:18:45
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Software Protection service entered the stopped state.
Log: 'System' Date/Time: 01/11/2014 22:16:43
Type: Information Category: 0
Event: 206 Source: Microsoft-Windows-Application-Experience
The Program Compatibility Assistant service successfully performed phase two initialization.
Log: 'System' Date/Time: 01/11/2014 22:16:35
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Application Experience service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:14:50
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Multimedia Class Scheduler service entered the stopped state.
Log: 'System' Date/Time: 01/11/2014 22:13:45
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Update service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:13:42
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Security Center service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:13:42
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Software Protection service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:13:41
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The TOSHIBA Modem region select service service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:13:41
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Portable Device Enumerator Service service entered the stopped state.
Log: 'System' Date/Time: 01/11/2014 22:13:41
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The ConfigFree Service service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:13:41
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Microsoft .NET Framework NGEN v4.0.30319_X86 service entered the stopped state.
Log: 'System' Date/Time: 01/11/2014 22:13:41
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Microsoft .NET Framework NGEN v4.0.30319_X86 service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:13:41
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The ConfigFree WiMAX Service service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:13:40
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The ASP.NET State Service service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:11:54
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Program Compatibility Assistant Service service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:11:54
Type: Information Category: 0
Event: 201 Source: Microsoft-Windows-Application-Experience
The Program Compatibility Assistant service started successfully.
Log: 'System' Date/Time: 01/11/2014 22:11:45
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Search service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:11:43
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Diagnostic Service Host service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:11:41
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The IPsec Policy Agent service entered the running state.
Log: 'System' Date/Time: 01/11/2014 22:11:41
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Portable Device Enumerator Service service entered the running state.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 01/11/2014 22:09:09
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 01/11/2014 17:53:46
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name watson.microsoft.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 01/11/2014 16:22:22
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 01/11/2014 16:03:43
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 01/11/2014 16:03:42
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\usbccgp failed to load for the device USB\VID_04F2&PID_B070\SN0001.
Log: 'System' Date/Time: 01/11/2014 16:03:42
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\mouhid failed to load for the device HID\VID_3938&PID_1031&Col01\6&39eb0813&0&0000.
Log: 'System' Date/Time: 01/11/2014 13:40:32
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 01/11/2014 13:23:38
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 01/11/2014 13:07:22
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 01/11/2014 12:49:23
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 01/11/2014 11:40:10
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 01/11/2014 11:00:39
Type: Warning Category: 2
Event: 57 Source: Ntfs
The system failed to flush data to the transaction log. Corruption may occur.
Log: 'System' Date/Time: 01/11/2014 10:54:27
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 01/11/2014 10:14:06
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 01/11/2014 09:29:50
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 31/10/2014 23:24:07
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 31/10/2014 23:06:45
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 31/10/2014 20:27:13
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 31/10/2014 19:28:28
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.
Log: 'System' Date/Time: 31/10/2014 18:48:20
Type: Warning Category: 0
Event: 1 Source: RTL8167
Realtek PCIe FE Family Controller is disconnected from network.