Vino's Event Viewer v01c run on Windows 2008 in English Report run at 21/11/2011 9:17:20 PM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 20/11/2011 2:09:32 PM Type: Error Category: 3 Event: 7042 Source: Microsoft-Windows-Search The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt. Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) Log: 'Application' Date/Time: 20/11/2011 2:09:25 PM Type: Error Category: 3 Event: 7010 Source: Microsoft-Windows-Search The index cannot be initialized. Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) Log: 'Application' Date/Time: 20/11/2011 2:09:25 PM Type: Error Category: 3 Event: 3058 Source: Microsoft-Windows-Search The application cannot be initialized. Context: Windows Application Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) Log: 'Application' Date/Time: 20/11/2011 2:09:25 PM Type: Error Category: 3 Event: 3028 Source: Microsoft-Windows-Search The gatherer object cannot be initialized. Context: Windows Application, SystemIndex Catalog Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) Log: 'Application' Date/Time: 20/11/2011 2:09:20 PM Type: Error Category: 3 Event: 3029 Source: Microsoft-Windows-Search The plug-in in cannot be initialized. Context: Windows Application, SystemIndex Catalog Details: Element not found. (HRESULT : 0x80070490) (0x80070490) Log: 'Application' Date/Time: 20/11/2011 2:04:36 PM Type: Error Category: 3 Event: 3029 Source: Microsoft-Windows-Search The plug-in in cannot be initialized. Context: Windows Application, SystemIndex Catalog Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) Log: 'Application' Date/Time: 20/11/2011 2:04:36 PM Type: Error Category: 1 Event: 9002 Source: Microsoft-Windows-Search The Windows Search Service cannot load the property store information. Context: Windows Application, SystemIndex Catalog Details: The content index server cannot update or access its database because insufficient system resources are available. Increase the system resource usage setting for the search service. If the problem persists, stop and restart the search service. (HRESULT : 0x80041185) (0x80041185) Log: 'Application' Date/Time: 20/11/2011 2:04:36 PM Type: Error Category: 3 Event: 7040 Source: Microsoft-Windows-Search The search service has detected corrupted data files in the index {id=1100}. The service will attempt to automatically correct this problem by rebuilding the index. Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) Log: 'Application' Date/Time: 20/11/2011 2:04:36 PM Type: Error Category: 3 Event: 9000 Source: Microsoft-Windows-Search The event description cannot be found. Log: 'Application' Date/Time: 20/11/2011 2:04:17 PM Type: Error Category: 3 Event: 454 Source: ESENT Windows (4316) Windows: Database recovery/restore failed with unexpected error -1014. Log: 'Application' Date/Time: 20/11/2011 1:57:40 PM Type: Error Category: 3 Event: 419 Source: ESENT Windows (4316) Windows: Unable to read page 4715 of database C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb. Error -1014. Log: 'Application' Date/Time: 19/11/2011 9:58:31 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 19/11/2011 9:58:07 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 19/11/2011 7:31:28 AM Type: Error Category: 100 Event: 1000 Source: Application Error Faulting application name: steam.exe, version: 1.0.1065.11, time stamp: 0x4d9b89de Faulting module name: Steam.dll_unloaded, version: 0.0.0.0, time stamp: 0x4e8cc0ab Exception code: 0xc0000005 Fault offset: 0x301f838b Faulting process id: 0xd8c Faulting application start time: 0x01cca683104f6349 Faulting application path: C:\Program Files (x86)\Steam\steam.exe Faulting module path: Steam.dll Report Id: 7db7d69f-1280-11e1-839f-1c6f6594698f Log: 'Application' Date/Time: 19/11/2011 3:54:21 AM Type: Error Category: 101 Event: 1002 Source: Application Hang The program MRUSetup.exe version 4.1.0.1610 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: f7c Start Time: 01cca669277b3a1c Termination Time: 0 Application Path: M:\marvell_raid_tool_s3_mb\MRU 4.1.0.1610\MRUSetup.exe Report Id: Log: 'Application' Date/Time: 19/11/2011 3:43:28 AM Type: Error Category: 0 Event: 8193 Source: System Restore Failed to create restore point (Process = C:\Windows\system32\DrvInst.exe "4" "0" "C:\Users\Mike\AppData\Local\Temp\{07c101a3-8df1-2ddf-7e11-8040c5355f12}\mv91cons.inf" "9" "62424a8e3" "00000000000005A0" "WinSta0\Default" "0000000000000568" "208" "c:\program files (x86)\marvell\raid\magniconsole"; Description = Device Driver Package Install: Marvell Semiconductor Inc. System devices; Error = 0x81000101). Log: 'Application' Date/Time: 18/11/2011 8:35:59 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 18/11/2011 8:35:38 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 17/11/2011 8:15:33 AM Type: Error Category: 0 Event: 8193 Source: System Restore Failed to create restore point (Process = C:\Windows\system32\svchost.exe -k netsvcs; Description = Windows Update; Error = 0x81000101). Log: 'Application' Date/Time: 17/11/2011 8:08:48 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: 17/11/2011 8:08:48 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: 16/11/2011 6:26:14 PM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 16/11/2011 6:25:53 PM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 16/11/2011 10:59:34 AM Type: Error Category: 0 Event: 512 Source: Microsoft-Windows-CAPI2 The Cryptographic Services service failed to initialize the VSS backup "System Writer" object. Details: Could not query the status of the EventSystem service. System Error: A system shutdown is in progress. . Log: 'Application' Date/Time: 15/11/2011 8:39:10 PM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 15/11/2011 8:00:19 PM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 14/11/2011 5:51:56 PM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 14/11/2011 5:51:33 PM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 13/11/2011 10:26:11 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 13/11/2011 10:25:49 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 13/11/2011 2:23:18 AM Type: Error Category: 101 Event: 1002 Source: Application Hang The program cfp.exe version 5.5.64714.1382 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 5a4 Start Time: 01cca0902bd95e02 Termination Time: 0 Application Path: C:\Program Files\COMODO\COMODO Internet Security\cfp.exe Report Id: 6e25a789-0d9d-11e1-a7b0-1c6f6594698f Log: 'Application' Date/Time: 12/11/2011 7:13:21 PM Type: Error Category: 0 Event: 8193 Source: System Restore Failed to create restore point (Process = C:\Windows\system32\svchost.exe -k netsvcs; Description = Windows Update; Error = 0x81000101). Log: 'Application' Date/Time: 12/11/2011 8:28:39 AM Type: Error Category: 0 Event: 8193 Source: System Restore Failed to create restore point (Process = C:\Windows\servicing\TrustedInstaller.exe; Description = Windows Modules Installer; Error = 0x81000101). Log: 'Application' Date/Time: 12/11/2011 8:13:39 AM Type: Error Category: 0 Event: 8193 Source: System Restore Failed to create restore point (Process = C:\Windows\system32\svchost.exe -k netsvcs; Description = Windows Update; Error = 0x81000101). Log: 'Application' Date/Time: 11/11/2011 7:22:33 PM Type: Error Category: 3 Event: 3100 Source: Microsoft-Windows-Search Unable to initialize the filter host process. Terminating. Details: This operation returned because the timeout period expired. (HRESULT : 0x800705b4) (0x800705b4) Log: 'Application' Date/Time: 11/11/2011 8:32:11 AM Type: Error Category: 0 Event: 8193 Source: System Restore Failed to create restore point (Process = C:\Windows\servicing\TrustedInstaller.exe; Description = Windows Modules Installer; Error = 0x81000101). Log: 'Application' Date/Time: 11/11/2011 8:13:42 AM Type: Error Category: 0 Event: 8193 Source: System Restore Failed to create restore point (Process = C:\Windows\system32\svchost.exe -k netsvcs; Description = Windows Update; Error = 0x81000101). Log: 'Application' Date/Time: 10/11/2011 7:20:52 PM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 10/11/2011 6:00:23 PM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 10/11/2011 9:08:05 AM Type: Error Category: 0 Event: 8193 Source: System Restore Failed to create restore point (Process = C:\Windows\system32\svchost.exe -k netsvcs; Description = Windows Update; Error = 0x81000101). Log: 'Application' Date/Time: 10/11/2011 2:44:52 AM Type: Error Category: 0 Event: 512 Source: Microsoft-Windows-CAPI2 The Cryptographic Services service failed to initialize the VSS backup "System Writer" object. Details: Could not query the status of the EventSystem service. System Error: A system shutdown is in progress. . Log: 'Application' Date/Time: 10/11/2011 12:48:52 AM Type: Error Category: 101 Event: 1002 Source: Application Hang The program firefox.exe version 1.9.2.4280 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: cdc Start Time: 01cc9f36c8e4ae20 Termination Time: 0 Application Path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe Report Id: bc846109-0b33-11e1-9655-1c6f6594698f Log: 'Application' Date/Time: 09/11/2011 9:02:34 PM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 09/11/2011 7:09:42 PM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 08/11/2011 12:34:08 PM Type: Error Category: 0 Event: 8193 Source: System Restore Failed to create restore point (Process = C:\Windows\system32\svchost.exe -k netsvcs; Description = Windows Update; Error = 0x81000101). Log: 'Application' Date/Time: 07/11/2011 3:38:26 PM Type: Error Category: 0 Event: 4100 Source: Windows Backup Backup did not complete successfully because a shadow copy could not be created. Free up disk space on the drive that you are backing up by deleting unnecessary files and then try again. Log: 'Application' Date/Time: 29/10/2011 4:31:41 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 29/10/2011 4:31:21 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 29/10/2011 3:18:18 AM Type: Error Category: 100 Event: 1000 Source: Application Error Faulting application name: DAOrigins.exe, version: 1.4.12393.0, time stamp: 0x4c093389 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000008 Faulting process id: 0x169c Faulting application start time: 0x01cc95d8b981cfe0 Faulting application path: C:\Program Files (x86)\Electronic Arts\Dragon Age Origins\bin_ship\DAOrigins.exe Faulting module path: unknown Report Id: a588fc09-01dc-11e1-b049-1c6f6594698f Log: 'Application' Date/Time: 28/10/2011 4:30:28 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 28/10/2011 4:30:25 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 27/10/2011 4:31:34 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 27/10/2011 4:31:14 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 26/10/2011 4:31:51 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 26/10/2011 4:31:30 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 25/10/2011 4:31:54 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 25/10/2011 4:31:32 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 24/10/2011 4:32:06 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 24/10/2011 4:31:33 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 23/10/2011 11:28:12 PM Type: Error Category: 0 Event: 517 Source: Microsoft-Windows-Backup The backup operation that started at '?2011?-?10?-?23T23:01:01.900567200Z' has failed with following error code '2155348129' (A Volume Shadow Copy Service operation failed. Please check "VSS" and "SPP" application event logs for more information.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved. Log: 'Application' Date/Time: 23/10/2011 5:48:56 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 23/10/2011 5:48:35 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 22/10/2011 5:41:45 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 22/10/2011 5:41:25 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 21/10/2011 4:31:49 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 21/10/2011 4:31:29 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 20/10/2011 4:31:47 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 20/10/2011 4:31:27 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 19/10/2011 4:31:44 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 19/10/2011 4:31:24 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 18/10/2011 4:31:42 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 18/10/2011 4:31:23 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 17/10/2011 4:31:52 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 17/10/2011 4:31:31 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 16/10/2011 4:44:58 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 16/10/2011 4:44:38 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 15/10/2011 4:31:47 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 15/10/2011 4:31:27 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 14/10/2011 4:31:59 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 14/10/2011 4:31:39 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 13/10/2011 4:31:43 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 13/10/2011 4:31:20 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 12/10/2011 4:31:33 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 12/10/2011 4:31:14 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 11/10/2011 4:31:53 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 11/10/2011 4:31:32 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 10/10/2011 5:30:49 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 10/10/2011 5:30:28 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 09/10/2011 4:31:52 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 09/10/2011 4:31:31 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 08/10/2011 4:40:55 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 08/10/2011 4:40:31 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 07/10/2011 4:31:50 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 07/10/2011 4:31:29 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 06/10/2011 4:31:54 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 06/10/2011 4:31:32 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 05/10/2011 7:15:54 PM Type: Error Category: 100 Event: 1000 Source: Application Error Faulting application name: DAOrigins.exe, version: 1.4.12393.0, time stamp: 0x4c093389 Faulting module name: DAOrigins.exe, version: 1.4.12393.0, time stamp: 0x4c093389 Exception code: 0xc0000005 Fault offset: 0x001531d5 Faulting process id: 0x1c40 Faulting application start time: 0x01cc83866b31aa34 Faulting application path: C:\Program Files (x86)\Electronic Arts\Dragon Age Origins\bin_ship\DAOrigins.exe Faulting module path: C:\Program Files (x86)\Electronic Arts\Dragon Age Origins\bin_ship\DAOrigins.exe Report Id: 7182e7f0-ef86-11e0-807e-1c6f6594698f Log: 'Application' Date/Time: 05/10/2011 4:31:41 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 05/10/2011 4:31:22 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 04/10/2011 4:31:43 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 04/10/2011 4:31:24 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 03/10/2011 11:55:39 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 03/10/2011 11:55:19 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 02/10/2011 4:31:44 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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: 02/10/2011 4:31:25 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 01/10/2011 5:41:31 AM Type: Error Category: 0 Event: 63 Source: SideBySide Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\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/10/2011 5:41:11 AM Type: Error Category: 0 Event: 72 Source: SideBySide Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. Log: 'Application' Date/Time: 01/10/2011 3:40:10 AM Type: Error Category: 100 Event: 1000 Source: Application Error Faulting application name: DAOrigins.exe, version: 1.4.12393.0, time stamp: 0x4c093389 Faulting module name: DAOrigins.exe, version: 1.4.12393.0, time stamp: 0x4c093389 Exception code: 0xc0000005 Fault offset: 0x0019977e Faulting process id: 0x16f8 Faulting application start time: 0x01cc7fd54cab5947 Faulting application path: C:\Program Files (x86)\Electronic Arts\Dragon Age Origins\bin_ship\DAOrigins.exe Faulting module path: C:\Program Files (x86)\Electronic Arts\Dragon Age Origins\bin_ship\DAOrigins.exe Report Id: 0fa99ebb-ebdf-11e0-807e-1c6f6594698f ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 20/11/2011 10:16:31 PM 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 - 5 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 748 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 748 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 748 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 748 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 748 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Log: 'Application' Date/Time: 20/11/2011 5:15:15 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (4756) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (63 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: 20/11/2011 5:15:13 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4756) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 80740352 (0x0000000004d00000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 28 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 289 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 5:10:25 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (4756) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (111 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: 20/11/2011 5:10:24 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4756) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 19824640 (0x00000000012e8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (104 seconds) to be serviced by the OS. In addition, 24 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 42 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 5:09:41 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4756) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 76087296 (0x0000000004890000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (67 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 374 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 5:03:27 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4756) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 73105408 (0x00000000045b8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (65 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 517 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 4:54:49 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4756) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 72744960 (0x0000000004560000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 23 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 813 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 4:41:15 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4756) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 30441472 (0x0000000001d08000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 1298 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 4:19:37 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (4756) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 6651904 (0x0000000000658000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 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: 20/11/2011 4:19:34 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (4756) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (67 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: 20/11/2011 3:46:56 PM Type: Warning Category: 7 Event: 509 Source: ESENT wuaueng.dll (1080) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 65732608 (0x0000000003eb0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (128 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 981 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 3:32:31 PM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1080) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (94 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 633 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 3:30:35 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1080) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 1966080 (0x00000000001e0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (126 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: 20/11/2011 3:21:57 PM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1080) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 32768 (0x0000000000008000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (100 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 100 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 3:20:17 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1080) 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 (236 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: 20/11/2011 3:15:28 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1080) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 980480 (0x00000000000ef600) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (159 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: 20/11/2011 3:11:42 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1080) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 980992 (0x00000000000ef800) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (122 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: 20/11/2011 3:07:49 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1080) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 980992 (0x00000000000ef800) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (89 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: 20/11/2011 2:51:57 PM 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: 20/11/2011 1:57:57 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (4316) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 18710528 (0x00000000011d8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (93 seconds) to be serviced by the OS. In addition, 141 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 96 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 1:56:20 PM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (4316) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7766016 (0x0000000000768000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (235 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: 20/11/2011 4:07:06 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 20/11/2011 4:06:56 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 20/11/2011 4:03:28 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 20/11/2011 4:03:12 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 99 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 20/11/2011 4:02:33 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 20/11/2011 1:30:13 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (65 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 27848 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 1:30:13 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 112525312 (0x0000000006b50000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 4 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 851 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 1:16:16 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (79 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: 20/11/2011 1:16:02 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 71303168 (0x0000000004400000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. In addition, 15 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 115 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 1:14:07 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 31293440 (0x0000000001dd8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 1826 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 20/11/2011 12:43:40 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 79462400 (0x0000000004bc8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (69 seconds) to be serviced by the OS. In addition, 16 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 2704 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 11:58:41 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (72 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: 19/11/2011 11:58:36 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 112459776 (0x0000000006b40000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 996 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 11:42:00 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 158793728 (0x0000000009770000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 12 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 11719 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 11:19:51 PM Type: Warning Category: 3 Event: 10023 Source: Microsoft-Windows-Search The protocol host process 4964 did not respond and is being forcibly terminated {filter host process 3356}. Log: 'Application' Date/Time: 19/11/2011 8:26:40 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 112394240 (0x0000000006b30000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 160 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 8:24:00 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47349760 (0x0000000002d28000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 15 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 281 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 8:19:19 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 15695872 (0x0000000000ef8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (124 seconds) to be serviced by the OS. In addition, 26 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 76 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 8:18:03 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 19529728 (0x00000000012a0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (98 seconds) to be serviced by the OS. In addition, 22 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 34 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 8:17:28 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 112656384 (0x0000000006b70000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (64 seconds) to be serviced by the OS. In addition, 42 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 209 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 8:16:14 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (61 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: 19/11/2011 8:14:08 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (69 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: 19/11/2011 8:13:59 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 151552000 (0x0000000009088000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 7224 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 6:13:34 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (1716) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 21626880 (0x00000000014a0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (64 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 88 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 6:12:05 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (1716) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 20021248 (0x0000000001318000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (67 seconds) to be serviced by the OS. In addition, 6 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 67 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 6:10:58 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (1716) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7569408 (0x0000000000738000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (107 seconds) to be serviced by the OS. In addition, 7 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 107 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 6:09:38 PM Type: Warning Category: 7 Event: 509 Source: ESENT wuaueng.dll (1116) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 83361792 (0x0000000004f80000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (95 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 646 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 6:09:10 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (1716) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7077888 (0x00000000006c0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (72 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 74 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 6:07:56 PM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (1716) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 22216704 (0x0000000001530000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (84 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: 19/11/2011 6:03:16 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 646656 (0x000000000009de00) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (67 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: 19/11/2011 5:58:51 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1116) 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 (79 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: 19/11/2011 5:58:30 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 101711872 (0x0000000006100000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. In addition, 26 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 235 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 5:55:36 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 647168 (0x000000000009e000) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (60 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: 19/11/2011 5:54:35 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (1716) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 29949952 (0x0000000001c90000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (305 seconds) to be serviced by the OS. In addition, 69 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 610 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 5:46:14 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (1716) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (75 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: 19/11/2011 5:44:24 PM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (1716) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7766016 (0x0000000000768000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (122 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: 19/11/2011 5:41:34 PM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 1597 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 19/11/2011 5:15:57 PM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 19/11/2011 3:40:16 PM 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 - 5 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 756 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 756 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 756 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 756 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 756 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Log: 'Application' Date/Time: 19/11/2011 12:29:14 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (69 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: 19/11/2011 12:29:10 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 15990784 (0x0000000000f40000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (63 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 586 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 12:19:29 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (79 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: 19/11/2011 12:19:24 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 71401472 (0x0000000004418000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 22 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 889 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 12:04:34 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 54198272 (0x00000000033b0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (95 seconds) to be serviced by the OS. In addition, 38 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 34 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 12:04:00 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23920640 (0x00000000016d0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (63 seconds) to be serviced by the OS. In addition, 2 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 770 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 11:51:09 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 108331008 (0x0000000006750000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (69 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 208 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 11:47:40 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 104366080 (0x0000000006388000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (92 seconds) to be serviced by the OS. In addition, 36 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 37 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 11:47:35 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 4096 (0x0000000000001000) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (71 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: 19/11/2011 11:47:03 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 41025536 (0x0000000002720000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 12754 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 8:14:29 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 104333312 (0x0000000006380000) 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: 19/11/2011 8:14:29 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 4096 (0x0000000000001000) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (61 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: 19/11/2011 7:50:39 AM Type: Warning Category: 3 Event: 10023 Source: Microsoft-Windows-Search The protocol host process 3688 did not respond and is being forcibly terminated {filter host process 4692}. Log: 'Application' Date/Time: 19/11/2011 7:43:37 AM Type: Warning Category: 3 Event: 10023 Source: Microsoft-Windows-Search The protocol host process 276 did not respond and is being forcibly terminated {filter host process 2100}. Log: 'Application' Date/Time: 19/11/2011 7:12:25 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1088) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 111 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:10:34 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1088) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (131 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 149 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:10:20 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 104333312 (0x0000000006380000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (110 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 42 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:09:37 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 72253440 (0x00000000044e8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (67 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 92 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:08:17 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 4608 (0x0000000000001200) for 9216 (0x00002400) bytes succeeded, but took an abnormally long time (149 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 149 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:08:05 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1088) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 4096 (0x0000000000001000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (335 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: 19/11/2011 7:08:05 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 5996544 (0x00000000005b8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (347 seconds) to be serviced by the OS. In addition, 16 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 62 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:07:02 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 92831744 (0x0000000005888000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (285 seconds) to be serviced by the OS. In addition, 16 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 67 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:05:55 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 80347136 (0x0000000004ca0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (218 seconds) to be serviced by the OS. In addition, 18 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 69 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:05:48 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 4096 (0x0000000000001000) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (211 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: 19/11/2011 7:04:45 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 53673984 (0x0000000003330000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (148 seconds) to be serviced by the OS. In addition, 16 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 51 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:03:54 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 37191680 (0x0000000002378000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (97 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 35 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:03:19 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23691264 (0x0000000001698000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. In addition, 116 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 584 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 19/11/2011 7:00:44 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3476) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 4608 (0x0000000000001200) for 512 (0x00000200) 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: 19/11/2011 6:53:46 AM Type: Warning Category: 7 Event: 507 Source: ESENT wuaueng.dll (1088) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 65536 (0x0000000000010000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (130 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: 19/11/2011 6:53:34 AM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (3476) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 5963776 (0x00000000005b0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (901 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: 19/11/2011 6:46:39 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1088) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 701440 (0x00000000000ab400) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (94 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: 19/11/2011 6:18:25 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 93 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 19/11/2011 6:17:52 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 18/11/2011 7:52:48 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1116) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\tmp.edb" at offset 524288 (0x0000000000080000) for 0 (0x00000000) bytes succeeded, but took an abnormally long time (74 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: 18/11/2011 1:54:23 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23822336 (0x00000000016b8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 346 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 1:48:37 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 42729472 (0x00000000028c0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (110 seconds) to be serviced by the OS. In addition, 19 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 61 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 1:47:35 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 70483968 (0x0000000004338000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (100 seconds) to be serviced by the OS. In addition, 6 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 38 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 1:46:56 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 54296576 (0x00000000033c8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 1920 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 1:15:20 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1116) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 569344 (0x000000000008b000) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (123 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: 18/11/2011 1:15:01 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (178 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: 18/11/2011 1:14:56 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 85327872 (0x0000000005160000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (152 seconds) to be serviced by the OS. In addition, 16 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 72 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 1:13:43 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 16515072 (0x0000000000fc0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (100 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 65 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 1:12:49 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1116) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 4096 (0x0000000000001000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (61 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: 18/11/2011 1:12:38 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23855104 (0x00000000016c0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 352 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 1:06:46 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 85229568 (0x0000000005148000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (71 seconds) to be serviced by the OS. In addition, 7 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 106 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 1:04:59 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 16646144 (0x0000000000fe0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (63 seconds) to be serviced by the OS. In addition, 2 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 702 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:53:16 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 16777216 (0x0000000001000000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (91 seconds) to be serviced by the OS. In addition, 22 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 66 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:52:48 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (115 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: 18/11/2011 12:52:09 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47415296 (0x0000000002d38000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (121 seconds) to be serviced by the OS. In addition, 20 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 67 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:51:02 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 84836352 (0x00000000050e8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (84 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 558 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:41:44 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 17072128 (0x0000000001048000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (330 seconds) to be serviced by the OS. In addition, 4 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 72 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:41:09 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (376 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: 18/11/2011 12:40:32 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 0 (0x0000000000000000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (328 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 66 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:39:25 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23855104 (0x00000000016c0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (272 seconds) to be serviced by the OS. In addition, 9 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 62 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:38:23 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 19169280 (0x0000000001248000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (217 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 75 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:37:08 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47415296 (0x0000000002d38000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (160 seconds) to be serviced by the OS. In addition, 15 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 56 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:36:11 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23691264 (0x0000000001698000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (106 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 52 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:35:19 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47349760 (0x0000000002d28000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (65 seconds) to be serviced by the OS. In addition, 4 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 458 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:27:40 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 87588864 (0x0000000005388000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (308 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 60 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:27:17 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (365 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: 18/11/2011 12:26:40 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 17432576 (0x00000000010a0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (347 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 85 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:25:14 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47742976 (0x0000000002d88000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (261 seconds) to be serviced by the OS. In addition, 11 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 63 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:24:11 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 84312064 (0x0000000005068000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (266 seconds) to be serviced by the OS. In addition, 9 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 68 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:23:02 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23527424 (0x0000000001670000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (211 seconds) to be serviced by the OS. In addition, 16 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 61 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:22:01 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47480832 (0x0000000002d48000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (160 seconds) to be serviced by the OS. In addition, 11 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 54 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:21:06 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23691264 (0x0000000001698000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (106 seconds) to be serviced by the OS. In addition, 2 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 36 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:20:30 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 18972672 (0x0000000001218000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (69 seconds) to be serviced by the OS. In addition, 106 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 947 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 12:18:25 PM Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search The content source cannot be accessed. Context: Application, SystemIndex Catalog Details: The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add. (HRESULT : 0x80040d0d) (0x80040d0d) Log: 'Application' Date/Time: 18/11/2011 12:04:42 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3312) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7045120 (0x00000000006b8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (1205 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 1205 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 11:44:36 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3312) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 6520832 (0x0000000000638000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (98 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 98 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 11:42:58 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3312) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 6029312 (0x00000000005c0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 61 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 11:41:57 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3312) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 5537792 (0x0000000000548000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (93 seconds) to be serviced by the OS. In addition, 4 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 100 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 11:40:16 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3312) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 22216704 (0x0000000001530000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (75 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 87 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 18/11/2011 11:38:49 AM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (3312) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 131072 (0x0000000000020000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (97 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: 18/11/2011 11:29:18 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 0 (0x0000000000000000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (91 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: 18/11/2011 11:26:40 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3312) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 216064 (0x0000000000034c00) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (233 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: 18/11/2011 11:19:40 AM Type: Warning Category: 0 Event: 4105 Source: Microsoft-Windows-Winlogon Windows is in Notification period. Log: 'Application' Date/Time: 18/11/2011 11:19:40 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 2608 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 18/11/2011 10:37:12 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 18/11/2011 4:41:59 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 943 second(s) to handle the notification event (CreateSession). Log: 'Application' Date/Time: 18/11/2011 4:27:15 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (CreateSession). Log: 'Application' Date/Time: 18/11/2011 4:26:00 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 82 second(s) to handle the notification event (CreateSession). Log: 'Application' Date/Time: 18/11/2011 4:25:38 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (CreateSession). Log: 'Application' Date/Time: 18/11/2011 2:04:29 AM 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 - 5 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 800 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 800 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 800 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 800 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 800 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Log: 'Application' Date/Time: 17/11/2011 5:50:57 PM Type: Warning Category: 7 Event: 507 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 56557568 (0x00000000035f0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (77 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: 17/11/2011 12:51:14 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 0 (0x0000000000000000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (123 seconds) to be serviced by the OS. In addition, 9 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 334 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:51:12 PM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 8060928 (0x00000000007b0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (165 seconds) to be serviced by the OS. In addition, 21 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 59 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:50:12 PM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 64094208 (0x0000000003d20000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (106 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 37 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:49:35 PM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 8257536 (0x00000000007e0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (69 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 69 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:48:26 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 8814592 (0x0000000000868000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (69 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: 17/11/2011 12:45:39 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47448064 (0x0000000002d40000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 15 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 834 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:31:45 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7766016 (0x0000000000768000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (68 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 1301 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:31:43 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 872960 (0x00000000000d5200) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (75 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: 17/11/2011 12:31:34 PM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 950272 (0x00000000000e8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (70 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 1303 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:10:03 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23691264 (0x0000000001698000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (127 seconds) to be serviced by the OS. In addition, 14 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 65 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:09:51 PM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 1703936 (0x00000000001a0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (157 seconds) to be serviced by the OS. In addition, 23 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 741 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:09:33 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (252 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: 17/11/2011 12:08:57 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 30441472 (0x0000000001d08000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (217 seconds) to be serviced by the OS. In addition, 13 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 66 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:07:51 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 54296576 (0x00000000033c8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (234 seconds) to be serviced by the OS. In addition, 15 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 77 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:06:33 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 37191680 (0x0000000002378000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (157 seconds) to be serviced by the OS. In addition, 11 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 62 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:05:31 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96829440 (0x0000000005c58000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (100 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 36 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 12:04:55 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 62521344 (0x0000000003ba0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (64 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 1181 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:57:29 AM Type: Warning Category: 7 Event: 509 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 83886080 (0x0000000005000000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (122 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 134 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:55:14 AM Type: Warning Category: 7 Event: 509 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 21856256 (0x00000000014d8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (75 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 348 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:49:26 AM Type: Warning Category: 7 Event: 509 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 78020608 (0x0000000004a68000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (70 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 76 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:48:10 AM Type: Warning Category: 7 Event: 509 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 61636608 (0x0000000003ac8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 4 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 68 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:47:01 AM Type: Warning Category: 7 Event: 509 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 60948480 (0x0000000003a20000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (74 seconds) to be serviced by the OS. In addition, 76 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 165 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:45:13 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 104267776 (0x0000000006370000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (371 seconds) to be serviced by the OS. In addition, 14 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 68 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:45:05 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (155 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 155 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:44:15 AM Type: Warning Category: 7 Event: 509 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 63012864 (0x0000000003c18000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (244 seconds) to be serviced by the OS. In addition, 4 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 256 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:44:05 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47349760 (0x0000000002d28000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (345 seconds) to be serviced by the OS. In addition, 12 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 62 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:43:02 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 8617984 (0x0000000000838000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (283 seconds) to be serviced by the OS. In addition, 19 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 71 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:42:29 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (253 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: 17/11/2011 11:41:50 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 92602368 (0x0000000005850000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (214 seconds) to be serviced by the OS. In addition, 18 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 61 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:40:49 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 21987328 (0x00000000014f8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (153 seconds) to be serviced by the OS. In addition, 9 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 55 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:39:58 AM Type: Warning Category: 7 Event: 507 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 58851328 (0x0000000003820000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (80 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: 17/11/2011 11:39:53 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 91848704 (0x0000000005798000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (97 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 36 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 11:39:16 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 70418432 (0x0000000004328000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 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: 17/11/2011 11:27:28 AM Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search The content source cannot be accessed. Context: Application, SystemIndex Catalog Details: The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add. (HRESULT : 0x80040d0d) (0x80040d0d) Log: 'Application' Date/Time: 17/11/2011 11:08:02 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (4120) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 828928 (0x00000000000ca600) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (63 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: 17/11/2011 9:19:57 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (67 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 124 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 9:17:52 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1028) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (91 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 263 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 9:14:16 AM Type: Warning Category: 7 Event: 510 Source: ESENT Catalog Database (864) Catalog Database: A request to write to the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 138 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 17/11/2011 9:13:28 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1028) 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: 17/11/2011 9:11:58 AM Type: Warning Category: 7 Event: 508 Source: ESENT Catalog Database (864) Catalog Database: A request to write to the file "C:\Windows\system32\CatRoot2\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}\catdb" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (73 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: 17/11/2011 2:43:18 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 81 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 17/11/2011 2:42:57 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 17/11/2011 2:41:57 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 315 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 17/11/2011 2:37:41 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 16/11/2011 1:35:15 PM Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search The content source cannot be accessed. Context: Application, SystemIndex Catalog Details: The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add. (HRESULT : 0x80040d0d) (0x80040d0d) Log: 'Application' Date/Time: 16/11/2011 1:06:05 PM Type: Warning Category: 3 Event: 10024 Source: Microsoft-Windows-Search The filter host process 3956 did not respond and is being forcibly terminated. Log: 'Application' Date/Time: 16/11/2011 12:52:15 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (1932) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 21594112 (0x0000000001498000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (76 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 76 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 16/11/2011 12:50:58 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (1932) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 21069824 (0x0000000001418000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (86 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 86 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 16/11/2011 12:49:32 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (1932) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 20545536 (0x0000000001398000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (76 seconds) to be serviced by the OS. In addition, 6 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 76 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 16/11/2011 12:48:16 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (1932) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 20021248 (0x0000000001318000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (81 seconds) to be serviced by the OS. In addition, 6 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 81 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 16/11/2011 12:46:55 PM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (1932) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7602176 (0x0000000000740000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (81 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: 16/11/2011 11:42:21 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 16/11/2011 11:41:43 AM Type: Warning Category: 0 Event: 6003 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a critical notification event. Log: 'Application' Date/Time: 16/11/2011 10:58:55 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 16/11/2011 10:58:50 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 16/11/2011 10:46:12 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 16/11/2011 4:41:49 AM Type: Warning Category: 0 Event: 6003 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a critical notification event. Log: 'Application' Date/Time: 16/11/2011 3:33:01 AM Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search The content source cannot be accessed. Context: Application, SystemIndex Catalog Details: The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add. (HRESULT : 0x80040d0d) (0x80040d0d) Log: 'Application' Date/Time: 16/11/2011 3:09:44 AM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (2316) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7077888 (0x00000000006c0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (78 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: 16/11/2011 2:23:50 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 16/11/2011 2:23:04 AM Type: Warning Category: 0 Event: 6003 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a critical notification event. Log: 'Application' Date/Time: 16/11/2011 1:10:09 AM 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-1888492754-3244777765-1062032002-1001_Classes: Process 1756 (\Device\HarddiskVolume2\Program Files\SUPERAntiSpyware\SASCORE64.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001_CLASSES Log: 'Application' Date/Time: 16/11/2011 1:10:09 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 149 second(s) to handle the notification event (Logoff). Log: 'Application' Date/Time: 16/11/2011 1:08:40 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logoff). Log: 'Application' Date/Time: 16/11/2011 1:07:46 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1100) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 60358656 (0x0000000003990000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (282 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: 16/11/2011 1:07:45 AM 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 - 7 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 1236 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 1756 (\Device\HarddiskVolume2\Program Files\SUPERAntiSpyware\SASCORE64.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 692 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 692 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 692 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 692 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 692 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Log: 'Application' Date/Time: 15/11/2011 1:57:48 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3904) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) 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: 15/11/2011 1:54:45 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3904) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (77 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: 15/11/2011 1:54:37 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3904) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 31260672 (0x0000000001dd0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 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: 15/11/2011 1:38:16 PM Type: Warning Category: 3 Event: 10023 Source: Microsoft-Windows-Search The protocol host process 2984 did not respond and is being forcibly terminated {filter host process 3920}. Log: 'Application' Date/Time: 15/11/2011 1:22:19 PM Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search The content source cannot be accessed. Context: Application, SystemIndex Catalog Details: The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add. (HRESULT : 0x80040d0d) (0x80040d0d) Log: 'Application' Date/Time: 15/11/2011 1:17:24 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3904) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 58720256 (0x0000000003800000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 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: 15/11/2011 11:52:54 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 1199 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 15/11/2011 11:33:54 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 15/11/2011 12:53:10 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 70 second(s) to handle the notification event (Logoff). Log: 'Application' Date/Time: 15/11/2011 12:52:59 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logoff). Log: 'Application' Date/Time: 15/11/2011 12:51:59 AM 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-1888492754-3244777765-1062032002-1001: Process 1220 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Log: 'Application' Date/Time: 14/11/2011 12:07:46 PM Type: Warning Category: 7 Event: 507 Source: ESENT Catalog Database (1004) Catalog Database: A request to read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 11423744 (0x0000000000ae5000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (67 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: 14/11/2011 11:59:55 AM Type: Warning Category: 7 Event: 508 Source: ESENT Catalog Database (1004) Catalog Database: A request to write to the file "C:\Windows\system32\CatRoot2\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}\catdb" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (72 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: 13/11/2011 6:41:22 PM Type: Warning Category: 7 Event: 507 Source: ESENT wuaueng.dll (840) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 45285376 (0x0000000002b30000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 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: 13/11/2011 4:09:57 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2992) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 1179648 (0x0000000000120000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 24 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 73 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 13/11/2011 4:08:44 PM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (2992) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 17596416 (0x00000000010c8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (125 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: 13/11/2011 2:06:03 PM 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-1888492754-3244777765-1062032002-1001_Classes: Process 860 (\Device\HarddiskVolume2\Program Files (x86)\Google\Update\GoogleUpdate.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001_CLASSES Log: 'Application' Date/Time: 13/11/2011 2:06:03 PM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 94 second(s) to handle the notification event (Logoff). Log: 'Application' Date/Time: 13/11/2011 2:05:29 PM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logoff). Log: 'Application' Date/Time: 13/11/2011 2:04:29 PM 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 - 5 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 768 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 768 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 768 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 768 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 768 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Log: 'Application' Date/Time: 13/11/2011 6:08:06 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (992) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 4096 (0x0000000000001000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (64 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: 13/11/2011 6:07:51 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (704) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 82968576 (0x0000000004f20000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 3540 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 13/11/2011 5:23:37 AM Type: Warning Category: 3 Event: 10024 Source: Microsoft-Windows-Search The filter host process 3172 did not respond and is being forcibly terminated. Log: 'Application' Date/Time: 13/11/2011 5:08:39 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (704) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 21102592 (0x0000000001420000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 2 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 164 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 13/11/2011 5:05:54 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (704) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7569408 (0x0000000000738000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (73 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 73 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 13/11/2011 5:04:40 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (704) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7045120 (0x00000000006b8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (91 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 91 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 13/11/2011 5:03:08 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (704) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 6520832 (0x0000000000638000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 2 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 61 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 13/11/2011 5:02:07 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (704) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 5996544 (0x00000000005b8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (68 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 68 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 13/11/2011 5:00:58 AM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (704) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 5537792 (0x0000000000548000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 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: 13/11/2011 4:52:13 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (704) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96698368 (0x0000000005c38000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (99 seconds) to be serviced by the OS. In addition, 37 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 35 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 13/11/2011 4:51:38 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (704) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 53706752 (0x0000000003338000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (63 seconds) to be serviced by the OS. In addition, 40 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 118 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 13/11/2011 4:49:39 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (704) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 17596416 (0x00000000010c8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (261 seconds) to be serviced by the OS. In addition, 52 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 336 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 13/11/2011 4:44:03 AM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (704) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 15073280 (0x0000000000e60000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (176 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: 13/11/2011 4:19:50 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 597 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 13/11/2011 4:11:02 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 13/11/2011 2:37:26 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 134 second(s) to handle the notification event (Logoff). Log: 'Application' Date/Time: 13/11/2011 2:36:12 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logoff). Log: 'Application' Date/Time: 13/11/2011 2:35:49 AM 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 - 5 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 764 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 764 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 764 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 764 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 764 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Log: 'Application' Date/Time: 12/11/2011 7:12:27 PM Type: Warning Category: 7 Event: 508 Source: ESENT Catalog Database (444) Catalog Database: A request to write to the file "C:\Windows\system32\CatRoot2\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}\catdb" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (99 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: 11/11/2011 8:29:26 PM Type: Warning Category: 3 Event: 10023 Source: Microsoft-Windows-Search The protocol host process 3180 did not respond and is being forcibly terminated {filter host process 3820}. Log: 'Application' Date/Time: 11/11/2011 8:21:56 PM Type: Warning Category: 3 Event: 10023 Source: Microsoft-Windows-Search The protocol host process 3008 did not respond and is being forcibly terminated {filter host process 4588}. Log: 'Application' Date/Time: 11/11/2011 8:14:49 PM Type: Warning Category: 3 Event: 10023 Source: Microsoft-Windows-Search The protocol host process 4864 did not respond and is being forcibly terminated {filter host process 4972}. Log: 'Application' Date/Time: 11/11/2011 7:52:36 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 41025536 (0x0000000002720000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 4 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 250 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:48:25 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 17006592 (0x0000000001038000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (91 seconds) to be serviced by the OS. In addition, 34 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 35 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:47:50 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 79036416 (0x0000000004b60000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 325 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:42:24 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 98861056 (0x0000000005e48000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 63 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:41:20 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (176 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: 11/11/2011 7:41:20 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 83034112 (0x0000000004f30000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (222 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 69 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:40:11 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 92766208 (0x0000000005878000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (152 seconds) to be serviced by the OS. In addition, 39 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 56 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:39:14 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96731136 (0x0000000005c40000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (99 seconds) to be serviced by the OS. In addition, 22 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 36 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:38:38 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23527424 (0x0000000001670000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. In addition, 9 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 311 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:33:26 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 17039360 (0x0000000001040000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (106 seconds) to be serviced by the OS. In addition, 11 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 63 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:32:23 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 84606976 (0x00000000050b0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (64 seconds) to be serviced by the OS. In addition, 12 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 271 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:27:53 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (77 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: 11/11/2011 7:27:51 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47284224 (0x0000000002d18000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (65 seconds) to be serviced by the OS. In addition, 61 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 863 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:22:20 PM Type: Warning Category: 3 Event: 10024 Source: Microsoft-Windows-Search The filter host process 4892 did not respond and is being forcibly terminated. Log: 'Application' Date/Time: 11/11/2011 7:19:45 PM Type: Warning Category: 3 Event: 10024 Source: Microsoft-Windows-Search The filter host process 4848 did not respond and is being forcibly terminated. Log: 'Application' Date/Time: 11/11/2011 7:13:39 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (73 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: 11/11/2011 7:13:28 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47611904 (0x0000000002d68000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. In addition, 63 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 5284 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 7:00:50 PM Type: Warning Category: 7 Event: 507 Source: ESENT wuaueng.dll (1032) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 42598400 (0x00000000028a0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (84 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: 11/11/2011 5:56:19 PM Type: Warning Category: 3 Event: 10024 Source: Microsoft-Windows-Search The filter host process 2348 did not respond and is being forcibly terminated. Log: 'Application' Date/Time: 11/11/2011 5:45:23 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3000) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 20021248 (0x0000000001318000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (126 seconds) to be serviced by the OS. In addition, 4 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 126 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 5:43:16 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3000) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7569408 (0x0000000000738000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (93 seconds) to be serviced by the OS. In addition, 6 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 93 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 5:41:43 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3000) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7045120 (0x00000000006b8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (103 seconds) to be serviced by the OS. In addition, 2 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 103 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 5:40:00 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3000) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 6520832 (0x0000000000638000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (75 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 75 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 5:38:44 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3000) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 6029312 (0x00000000005c0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (66 seconds) to be serviced by the OS. In addition, 27 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 66 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 5:37:37 PM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3000) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 393216 (0x0000000000060000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (207 seconds) to be serviced by the OS. In addition, 7 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 95 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 5:36:02 PM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (3000) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 131072 (0x0000000000020000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (162 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: 11/11/2011 5:28:34 PM Type: Warning Category: 7 Event: 507 Source: ESENT wuaueng.dll (1032) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 131072 (0x0000000000020000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (113 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: 11/11/2011 5:26:16 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 0 (0x0000000000000000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 725 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 5:22:17 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1032) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (145 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: 11/11/2011 5:22:03 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 92831744 (0x0000000005888000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (96 seconds) to be serviced by the OS. In addition, 17 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 32 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 5:21:31 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 70615040 (0x0000000004358000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (64 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: 11/11/2011 5:17:38 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1032) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 1304576 (0x000000000013e800) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (72 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: 11/11/2011 5:14:11 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 0 (0x0000000000000000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 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: 11/11/2011 5:09:38 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3000) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 907264 (0x00000000000dd800) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (101 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: 11/11/2011 3:52:35 PM Type: Warning Category: 0 Event: 6003 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a critical notification event. Log: 'Application' Date/Time: 11/11/2011 2:32:12 PM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 11/11/2011 11:43:32 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 69 second(s) to handle the notification event (Logoff). Log: 'Application' Date/Time: 11/11/2011 11:43:23 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logoff). Log: 'Application' Date/Time: 11/11/2011 11:42:23 AM 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 - 5 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 760 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 760 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 760 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 760 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 760 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Log: 'Application' Date/Time: 11/11/2011 8:27:05 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1108) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 1205760 (0x0000000000126600) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (79 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: 11/11/2011 8:26:50 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1108) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 98107392 (0x0000000005d90000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (65 seconds) to be serviced by the OS. In addition, 206 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 65 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 8:25:45 AM Type: Warning Category: 7 Event: 507 Source: ESENT wuaueng.dll (1108) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 56557568 (0x00000000035f0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (236 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: 11/11/2011 3:41:33 AM Type: Warning Category: 7 Event: 507 Source: ESENT wuaueng.dll (1108) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 74809344 (0x0000000004758000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 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: 11/11/2011 3:09:15 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2508) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 4784128 (0x0000000000490000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (95 seconds) to be serviced by the OS. In addition, 20 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 21 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 11/11/2011 3:08:54 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (2508) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 85426176 (0x0000000005178000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (63 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: 11/11/2011 12:27:34 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 296 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 11/11/2011 12:23:38 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 10/11/2011 10:57:59 PM 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-1888492754-3244777765-1062032002-1001_Classes: Process 1888 (\Device\HarddiskVolume2\Program Files\SUPERAntiSpyware\SASCORE64.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001_CLASSES Log: 'Application' Date/Time: 10/11/2011 10:57:59 PM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 107 second(s) to handle the notification event (Logoff). Log: 'Application' Date/Time: 10/11/2011 10:57:12 PM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logoff). Log: 'Application' Date/Time: 10/11/2011 10:56:12 PM 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 - 41 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 772 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 772 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 1888 (\Device\HarddiskVolume2\Program Files\SUPERAntiSpyware\SASCORE64.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{F4E57C4B-2036-45F0-A9AB-443BCFE33D9F}\Count Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\TrustedPeople Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 772 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows NT\CurrentVersion Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Root Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\Shell\Bags\3\Desktop Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\CurrentVersion\Explorer Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\CurrentVersion\Explorer Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{CEBFF5CD-ACE2-4F4F-9178-9926F41749EA}\Count Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\trust Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Internet Explorer\Main\WindowsSearch Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 772 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies\Microsoft\SystemCertificates Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Process 772 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\SmartCardRoot Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\CurrentVersion\HomeGroup\Printers Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Internet Explorer\Suggested Sites Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\Shell\Bags\24\Shell\{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7} Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\Shell\Bags\24\Shell\{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7} Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\Shell\Bags\290\Shell\{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7} Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\CurrentVersion\Internet Settings Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\CurrentVersion\Internet Settings Process 1312 (\Device\HarddiskVolume2\Windows\explorer.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\Windows\Shell Log: 'Application' Date/Time: 10/11/2011 11:23:58 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 97222656 (0x0000000005cb8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (91 seconds) to be serviced by the OS. In addition, 27 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 31 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 11:23:27 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 17203200 (0x0000000001068000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 23 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 3110 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 11:04:04 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (75 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 10441 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 10:31:37 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96927744 (0x0000000005c70000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 1634 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 10:31:19 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1048) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 886784 (0x00000000000d8800) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (186 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 9596 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 10:30:39 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1048) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 73072640 (0x00000000045b0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (154 seconds) to be serviced by the OS. In addition, 7 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 54 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 10:29:45 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1048) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 47906816 (0x0000000002db0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (100 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 38 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 10:29:07 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1048) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 32145408 (0x0000000001ea8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. In addition, 26 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 7972 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 10:04:22 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 62128128 (0x0000000003b40000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (124 seconds) to be serviced by the OS. In addition, 19 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 71 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 10:03:10 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 19169280 (0x0000000001248000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (123 seconds) to be serviced by the OS. In addition, 20 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 45 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 10:02:25 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 70418432 (0x0000000004328000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (77 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 5955 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 10:00:58 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 4096 (0x0000000000001000) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (60 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: 10/11/2011 9:02:05 AM Type: Warning Category: 3 Event: 10024 Source: Microsoft-Windows-Search The filter host process 3792 did not respond and is being forcibly terminated. Log: 'Application' Date/Time: 10/11/2011 8:23:09 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (2752) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 22183936 (0x0000000001528000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (75 seconds) to be serviced by the OS. In addition, 6 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 94 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 8:21:35 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (2752) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 21594112 (0x0000000001498000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (145 seconds) to be serviced by the OS. In addition, 4 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 145 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 8:19:09 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (2752) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 21102592 (0x0000000001420000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (79 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 124 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 8:17:05 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (2752) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7045120 (0x00000000006b8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (69 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 69 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 8:16:14 AM Type: Warning Category: 7 Event: 507 Source: ESENT wuaueng.dll (1048) SUS20ClientDataStore: A request to read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 72941568 (0x0000000004590000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (96 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: 10/11/2011 8:15:55 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (2752) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 6553600 (0x0000000000640000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (76 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 79 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 8:14:36 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (2752) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 22216704 (0x0000000001530000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (125 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 148 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 8:12:07 AM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (2752) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 131072 (0x0000000000020000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (71 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: 10/11/2011 8:10:02 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 0 (0x0000000000000000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (64 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: 10/11/2011 7:59:42 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 4096 (0x0000000000001000) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (297 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: 10/11/2011 7:59:09 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96894976 (0x0000000005c68000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (264 seconds) to be serviced by the OS. In addition, 14 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 65 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 7:58:03 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 79200256 (0x0000000004b88000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (199 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 75 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 7:56:48 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 70221824 (0x00000000042f8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (124 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 50 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 7:55:58 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 53936128 (0x0000000003370000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (73 seconds) to be serviced by the OS. In addition, 52 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 242 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 7:51:55 AM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (2752) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 15073280 (0x0000000000e60000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (547 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: 10/11/2011 7:51:23 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1048) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 823808 (0x00000000000c9200) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (160 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: 10/11/2011 7:38:20 AM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (2752) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log" at offset 4608 (0x0000000000001200) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (90 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: 10/11/2011 2:44:34 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 10/11/2011 2:43:33 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 10/11/2011 2:29:13 AM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 10/11/2011 2:28:04 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 270 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 10/11/2011 2:24:34 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 10/11/2011 12:37:21 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (852) 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. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 11509 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 10/11/2011 12:14:27 AM Type: Warning Category: 7 Event: 508 Source: ESENT Catalog Database (1396) Catalog Database: A request to write to the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (60 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: 10/11/2011 12:11:37 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (852) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 815104 (0x00000000000c7000) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (81 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: 09/11/2011 10:30:48 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96600064 (0x0000000005c20000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 25 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 352 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 10:30:33 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (78 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: 09/11/2011 10:24:55 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 71532544 (0x0000000004438000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 23 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 199 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 10:21:36 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47742976 (0x0000000002d88000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (63 seconds) to be serviced by the OS. In addition, 21 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 213 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 10:18:28 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (94 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: 09/11/2011 10:18:03 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96829440 (0x0000000005c58000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 24 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 167 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 10:15:51 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (104 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: 09/11/2011 10:15:15 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23527424 (0x0000000001670000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (65 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 587 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 10:05:27 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 85327872 (0x0000000005160000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (100 seconds) to be serviced by the OS. In addition, 20 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 70 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 10:04:16 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96665600 (0x0000000005c30000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (93 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 31 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 10:03:47 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (63 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: 09/11/2011 10:03:45 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 31358976 (0x0000000001de8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. In addition, 6 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 235 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:59:50 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 31293440 (0x0000000001dd8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (64 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 286 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:55:14 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (77 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: 09/11/2011 9:55:03 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 17137664 (0x0000000001058000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (66 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 322 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:49:41 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 84475904 (0x0000000005090000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (109 seconds) to be serviced by the OS. In addition, 19 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 66 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:49:06 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (120 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: 09/11/2011 9:48:34 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 84344832 (0x0000000005070000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (102 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 42 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:47:51 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96534528 (0x0000000005c10000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (64 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 313 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:42:38 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 83034112 (0x0000000004f30000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (229 seconds) to be serviced by the OS. In addition, 12 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 63 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:42:14 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (220 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: 09/11/2011 9:41:35 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47316992 (0x0000000002d20000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (187 seconds) to be serviced by the OS. In addition, 16 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 61 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:40:33 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47644672 (0x0000000002d70000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (139 seconds) to be serviced by the OS. In addition, 14 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 60 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:39:33 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 17694720 (0x00000000010e0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (97 seconds) to be serviced by the OS. In addition, 11 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 38 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:38:54 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 4882432 (0x00000000004a8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (64 seconds) to be serviced by the OS. In addition, 2 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 174 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:36:08 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 4096 (0x0000000000001000) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (204 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 204 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:35:59 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 98861056 (0x0000000005e48000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (542 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 77 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:34:42 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 5242880 (0x0000000000500000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (465 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 69 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:33:33 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 53575680 (0x0000000003318000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (416 seconds) to be serviced by the OS. In addition, 12 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 61 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:32:44 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (482 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: 09/11/2011 9:32:31 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 31260672 (0x0000000001dd0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (475 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 64 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:31:27 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 30375936 (0x0000000001cf8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (424 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 67 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:30:19 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 83558400 (0x0000000004fb0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (358 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 66 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:29:13 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 70483968 (0x0000000004338000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (316 seconds) to be serviced by the OS. In addition, 7 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 64 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:28:08 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47710208 (0x0000000002d80000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (252 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 62 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:27:06 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 36962304 (0x0000000002340000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (190 seconds) to be serviced by the OS. In addition, 12 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 66 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:26:00 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 4784128 (0x0000000000490000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (277 seconds) to be serviced by the OS. In addition, 11 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 67 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:25:32 PM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (852) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 4096 (0x0000000000001000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (252 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 551 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:24:52 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96862208 (0x0000000005c60000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (214 seconds) to be serviced by the OS. In addition, 9 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 61 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:23:51 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 92635136 (0x0000000005858000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (153 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 53 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:22:57 PM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 83460096 (0x0000000004f98000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (99 seconds) to be serviced by the OS. In addition, 14 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 38 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 9:22:18 PM Type: Warning Category: 7 Event: 508 Source: ESENT Windows (3144) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 22020096 (0x0000000001500000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 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: 09/11/2011 9:16:21 PM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (852) 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 (60 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 47932 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 8:37:02 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (852) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 45481984 (0x0000000002b60000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (152 seconds) to be serviced by the OS. In addition, 26 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 51 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 8:36:11 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (852) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 7438336 (0x0000000000718000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (101 seconds) to be serviced by the OS. In addition, 11 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 35 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 09/11/2011 8:35:35 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (852) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 6684672 (0x0000000000660000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (66 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: 09/11/2011 7:57:28 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (852) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) 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: 09/11/2011 7:54:13 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (852) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 1966080 (0x00000000001e0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (146 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: 09/11/2011 7:50:15 AM Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search The content source cannot be accessed. Context: Application, SystemIndex Catalog Details: The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add. (HRESULT : 0x80040d0d) (0x80040d0d) Log: 'Application' Date/Time: 09/11/2011 4:09:29 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 672 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 09/11/2011 3:59:17 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 08/11/2011 8:42:27 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1008) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 752128 (0x00000000000b7a00) for 34816 (0x00008800) bytes succeeded, but took an abnormally long time (65 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 382 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 8:42:20 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1008) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 4063232 (0x00000000003e0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 274 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 8:37:45 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1008) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 56262656 (0x00000000035a8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (97 seconds) to be serviced by the OS. In addition, 22 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 37 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 8:37:08 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1008) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 4587520 (0x0000000000460000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. In addition, 16 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 91 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 8:36:05 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1008) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 440320 (0x000000000006b800) for 4608 (0x00001200) bytes succeeded, but took an abnormally long time (86 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: 08/11/2011 8:35:36 AM 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 102039552 (0x0000000006150000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 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: 08/11/2011 7:58:15 AM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (1008) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 360960 (0x0000000000058200) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (72 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 2445 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 7:58:01 AM 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 83165184 (0x0000000004f50000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 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: 08/11/2011 7:27:55 AM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (3568) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 20578304 (0x00000000013a0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (70 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: 08/11/2011 7:17:30 AM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (1008) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 62464 (0x000000000000f400) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (282 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: 08/11/2011 7:16:44 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3568) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 96927744 (0x0000000005c70000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (483 seconds) to be serviced by the OS. In addition, 15 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 66 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 7:15:38 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3568) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 91357184 (0x0000000005720000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (417 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 62 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 7:14:35 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3568) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 78872576 (0x0000000004b38000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (354 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 61 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 7:13:33 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3568) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 62390272 (0x0000000003b80000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (292 seconds) to be serviced by the OS. In addition, 10 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 62 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 7:12:30 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3568) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47677440 (0x0000000002d78000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (229 seconds) to be serviced by the OS. In addition, 11 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 69 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 7:11:21 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3568) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 47284224 (0x0000000002d18000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (160 seconds) to be serviced by the OS. In addition, 8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 56 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 7:10:24 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3568) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 31326208 (0x0000000001de0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (103 seconds) to be serviced by the OS. In addition, 5 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 37 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 7:09:47 AM Type: Warning Category: 7 Event: 510 Source: ESENT Windows (3568) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23724032 (0x00000000016a0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (66 seconds) to be serviced by the OS. In addition, 3 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 84 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 7:08:23 AM Type: Warning Category: 7 Event: 509 Source: ESENT Windows (3568) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 23724032 (0x00000000016a0000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (68 seconds) to be serviced by the OS. In addition, 37 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 111 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 08/11/2011 7:06:31 AM Type: Warning Category: 7 Event: 507 Source: ESENT Windows (3568) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 7766016 (0x0000000000768000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (211 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: 08/11/2011 2:42:39 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 378 second(s) to handle the notification event (Logon). Log: 'Application' Date/Time: 08/11/2011 2:37:24 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logon). Log: 'Application' Date/Time: 08/11/2011 1:22:10 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (Logoff). Log: 'Application' Date/Time: 07/11/2011 10:59:59 PM Type: Warning Category: 7 Event: 510 Source: ESENT wuaueng.dll (2912) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 95059968 (0x0000000005aa8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (102 seconds) to be serviced by the OS. In addition, 4 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 34 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 07/11/2011 10:59:24 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (2912) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 45252608 (0x0000000002b28000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (68 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: 07/11/2011 5:46:46 PM Type: Warning Category: 7 Event: 508 Source: ESENT wuaueng.dll (2912) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 77627392 (0x0000000004a08000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (61 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: 07/11/2011 3:35:15 PM Type: Warning Category: 7 Event: 508 Source: ESENT Catalog Database (568) Catalog Database: A request to write to the file "C:\Windows\system32\CatRoot2\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}\catdb" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (68 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: 07/11/2011 12:29:23 PM Type: Warning Category: 0 Event: 6001 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber failed a notification event. Log: 'Application' Date/Time: 07/11/2011 12:20:14 PM Type: Warning Category: 0 Event: 6001 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber failed a notification event. Log: 'Application' Date/Time: 07/11/2011 12:20:14 PM Type: Warning Category: 0 Event: 6000 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a notification event. Log: 'Application' Date/Time: 07/11/2011 12:17:31 PM Type: Warning Category: 0 Event: 6003 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber was unavailable to handle a critical notification event. Log: 'Application' Date/Time: 30/10/2011 2:31:39 AM 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-1888492754-3244777765-1062032002-1001_Classes: Process 1688 (\Device\HarddiskVolume2\Program Files\SUPERAntiSpyware\SASCORE64.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001_CLASSES\Interface Log: 'Application' Date/Time: 30/10/2011 2:31:39 AM 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 - 5 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 760 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 760 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 760 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 760 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 760 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Log: 'Application' Date/Time: 23/10/2011 11:27:22 PM 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-1888492754-3244777765-1062032002-1001_Classes: Process 1928 (\Device\HarddiskVolume2\Program Files\SUPERAntiSpyware\SASCORE64.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001_CLASSES\Interface Log: 'Application' Date/Time: 23/10/2011 11:27:20 PM 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 - 15 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\TrustedPeople Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Root Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\trust Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies\Microsoft\SystemCertificates Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies\Microsoft\SystemCertificates Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies\Microsoft\SystemCertificates Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies\Microsoft\SystemCertificates Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Process 2368 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\SmartCardRoot Log: 'Application' Date/Time: 21/10/2011 10:40:14 AM Type: Warning Category: 0 Event: 10010 Source: Microsoft-Windows-RestartManager Application 'C:\Program Files (x86)\iTunes\iTunesHelper.exe' (pid 4176) cannot be restarted - Application SID does not match Conductor SID.. Log: 'Application' Date/Time: 13/10/2011 10:05:32 PM 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 - 4 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001_Classes: Process 1968 (\Device\HarddiskVolume2\Program Files\SUPERAntiSpyware\SASCORE64.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001_CLASSES\Interface Process 1968 (\Device\HarddiskVolume2\Program Files\SUPERAntiSpyware\SASCORE64.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001_CLASSES\Interface Process 1968 (\Device\HarddiskVolume2\Program Files\SUPERAntiSpyware\SASCORE64.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001_CLASSES\Interface Process 1968 (\Device\HarddiskVolume2\Program Files\SUPERAntiSpyware\SASCORE64.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001_CLASSES\Interface Log: 'Application' Date/Time: 13/10/2011 10:05:30 PM 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 - 20 user registry handles leaked from \Registry\User\S-1-5-21-1888492754-3244777765-1062032002-1001: Process 764 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 764 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001 Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\TrustedPeople Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 764 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Disallowed Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\Root Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\trust Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 764 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\My Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies\Microsoft\SystemCertificates Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies\Microsoft\SystemCertificates Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies\Microsoft\SystemCertificates Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Policies\Microsoft\SystemCertificates Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Process 764 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\CA Process 2884 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1888492754-3244777765-1062032002-1001\Software\Microsoft\SystemCertificates\SmartCardRoot