Vino's Event Viewer v01c run on Windows 7 in English Report run at 28/03/2015 16:49:07 Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 27/03/2015 21:43:51 Type: Error Category: 101 Event: 1002 Source: Application Hang The program IEXPLORE.EXE version 11.0.9600.17416 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: d38 Start Time: 01d0681f5e0af3f4 Termination Time: 100 Application Path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE Report Id: 5ab18f19-d4ca-11e4-8285-28e347e6e14b Faulting package full name: Faulting package-relative application ID: Log: 'Application' Date/Time: 26/03/2015 15:26:17 Type: Error Category: 0 Event: 8194 Source: VSS Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process. Operation: Gathering Writer Data Context: Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Name: System Writer Writer Instance ID: {4f249a43-8066-492b-b400-3960b02f6f53} Log: 'Application' Date/Time: 26/03/2015 15:23:45 Type: Error Category: 101 Event: 1002 Source: Application Hang The program NOTEPAD.EXE version 6.3.9600.17415 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: a5c Start Time: 01d067d8ce9b5acb Termination Time: 15 Application Path: C:\Windows\system32\NOTEPAD.EXE Report Id: 15b67133-d3cc-11e4-8282-28e347e6e14b Faulting package full name: Faulting package-relative application ID: Log: 'Application' Date/Time: 26/03/2015 15:23:17 Type: Error Category: 101 Event: 1002 Source: Application Hang The program NOTEPAD.EXE version 6.3.9600.17415 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: a68 Start Time: 01d067d8b333749f Termination Time: 15 Application Path: C:\Windows\system32\NOTEPAD.EXE Report Id: 043bc1ee-d3cc-11e4-8282-28e347e6e14b Faulting package full name: Faulting package-relative application ID: Log: 'Application' Date/Time: 21/03/2015 21:04:51 Type: Error Category: 3 Event: 7010 Source: Microsoft-Windows-Search The index cannot be initialised. Details: The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06) Log: 'Application' Date/Time: 21/03/2015 21:04:51 Type: Error Category: 3 Event: 3058 Source: Microsoft-Windows-Search The application cannot be initialised. Context: Windows Application Details: The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06) Log: 'Application' Date/Time: 21/03/2015 21:04:51 Type: Error Category: 3 Event: 3028 Source: Microsoft-Windows-Search The gatherer object cannot be initialised. Context: Windows Application, SystemIndex Catalogue Details: The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06) Log: 'Application' Date/Time: 21/03/2015 21:04:51 Type: Error Category: 3 Event: 3029 Source: Microsoft-Windows-Search The plug-in in cannot be initialised. Context: Windows Application, SystemIndex Catalogue Details: The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06) Log: 'Application' Date/Time: 21/03/2015 21:04:49 Type: Error Category: 3 Event: 3057 Source: Microsoft-Windows-Search The plug-in manager cannot be initialised. Context: Windows Application Details: (HRESULT : 0x8e5e0210) (0x8e5e0210) Log: 'Application' Date/Time: 21/03/2015 21:04:49 Type: Error Category: 1 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 catalogue is corrupt. 0xc0041801 (0xc0041801) Log: 'Application' Date/Time: 21/03/2015 21:04:48 Type: Error Category: 1 Event: 7040 Source: Microsoft-Windows-Search The search service has detected corrupted data files in the index {id=4810 - enduser\mssearch2\search\ytrip\common\util\jetutil.cpp (167)}. The service will attempt to automatically correct this problem by rebuilding the index. Details: 0x8e5e0210 (0x8e5e0210) Log: 'Application' Date/Time: 21/03/2015 21:04:48 Type: Error Category: 3 Event: 455 Source: ESENT SearchIndexer (3092) Windows: Error -1811 (0xfffff8ed) occurred while opening logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb000DD.log. Log: 'Application' Date/Time: 20/03/2015 20:12:55 Type: Error Category: 101 Event: 1002 Source: Application Hang The program IEXPLORE.EXE version 11.0.9600.17416 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: de0 Start Time: 01d061b3c693f4a7 Termination Time: 202 Application Path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE Report Id: 7ddb39f8-cf3d-11e4-827e-28e347e6e14b Faulting package full name: Faulting package-relative application ID: Log: 'Application' Date/Time: 13/03/2015 16:40:58 Type: Error Category: 0 Event: 4 Source: Microsoft-Windows-WMI Error 0x8004401e encountered when trying to load MOF C:\WINDOWS\SYSTEM32\WBEM\SV-SE\RDPCORE.MFL while recovering .MOF file marked with autorecover. Log: 'Application' Date/Time: 13/03/2015 16:40:58 Type: Error Category: 0 Event: 4 Source: Microsoft-Windows-WMI Error 0x8004401e encountered when trying to load MOF C:\WINDOWS\SYSTEM32\WBEM\SV-SE\MSFEEDS.MFL while recovering .MOF file marked with autorecover. Log: 'Application' Date/Time: 13/03/2015 16:40:58 Type: Error Category: 0 Event: 4 Source: Microsoft-Windows-WMI Error 0x8004401e encountered when trying to load MOF C:\WINDOWS\SYSTEM32\WBEM\SV-SE\WUDFX02000.MFL while recovering .MOF file marked with autorecover. Log: 'Application' Date/Time: 13/03/2015 16:40:58 Type: Error Category: 0 Event: 4 Source: Microsoft-Windows-WMI Error 0x8004401e encountered when trying to load MOF C:\WINDOWS\SYSTEM32\WBEM\SV-SE\DSCCORECONFPROV.MFL while recovering .MOF file marked with autorecover. Log: 'Application' Date/Time: 13/03/2015 16:40:58 Type: Error Category: 0 Event: 4 Source: Microsoft-Windows-WMI Error 0x8004401e encountered when trying to load MOF C:\WINDOWS\SYSTEM32\WBEM\SV-SE\MDMSETTINGSPROV.MFL while recovering .MOF file marked with autorecover. Log: 'Application' Date/Time: 13/03/2015 16:40:58 Type: Error Category: 0 Event: 4 Source: Microsoft-Windows-WMI Error 0x8004401e encountered when trying to load MOF C:\WINDOWS\SYSTEM32\WBEM\SV-SE\SR.MFL while recovering .MOF file marked with autorecover. Log: 'Application' Date/Time: 13/03/2015 16:40:58 Type: Error Category: 0 Event: 4 Source: Microsoft-Windows-WMI Error 0x8004401e encountered when trying to load MOF C:\WINDOWS\SYSTEM32\WBEM\SV-SE\SMBWMIV2.MFL while recovering .MOF file marked with autorecover. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 28/03/2015 04:24:15 Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search Crawl could not be completed on content source . Context: Application, SystemIndex Catalogue Details: The parameter is incorrect. (HRESULT : 0x80070057) (0x80070057) Log: 'Application' Date/Time: 26/03/2015 23:17:11 Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search Crawl could not be completed on content source . Context: Application, SystemIndex Catalogue Details: The parameter is incorrect. (HRESULT : 0x80070057) (0x80070057) Log: 'Application' Date/Time: 26/03/2015 17:00:39 Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, InvProv, has been registered in the Windows Management Instrumentation namespace Root\cimv2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 26/03/2015 17:00:39 Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, InvProv, has been registered in the Windows Management Instrumentation namespace Root\cimv2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 25/03/2015 21:39:13 Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search Crawl could not be completed on content source . Context: Application, SystemIndex Catalogue Details: The parameter is incorrect. (HRESULT : 0x80070057) (0x80070057) Log: 'Application' Date/Time: 23/03/2015 21:53:31 Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search Crawl could not be completed on content source . Context: Application, SystemIndex Catalogue Details: The parameter is incorrect. (HRESULT : 0x80070057) (0x80070057) Log: 'Application' Date/Time: 22/03/2015 18:39:13 Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search Crawl could not be completed on content source . Context: Windows Application, SystemIndex Catalogue Details: The parameter is incorrect. (HRESULT : 0x80070057) (0x80070057) Log: 'Application' Date/Time: 21/03/2015 22:07:26 Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search Crawl could not be completed on content source . Context: Windows Application, SystemIndex Catalogue Details: The parameter is incorrect. (HRESULT : 0x80070057) (0x80070057) Log: 'Application' Date/Time: 21/03/2015 21:06:02 Type: Warning Category: 3 Event: 3036 Source: Microsoft-Windows-Search Crawl could not be completed on content source . Context: Windows Application, SystemIndex Catalogue Details: The parameter is incorrect. (HRESULT : 0x80070057) (0x80070057) Log: 'Application' Date/Time: 21/03/2015 21:05:21 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: 17/03/2015 19:27:48 Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, DSCCoreProviders, has been registered in the Windows Management Instrumentation namespace root\Microsoft\Windows\DesiredStateConfiguration to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 17/03/2015 19:27:48 Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, DSCCoreProviders, has been registered in the Windows Management Instrumentation namespace root\Microsoft\Windows\DesiredStateConfiguration to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 17/03/2015 19:27:48 Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, DSCCoreProviders, has been registered in the Windows Management Instrumentation namespace root\Microsoft\Windows\DesiredStateConfiguration to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 17/03/2015 19:27:47 Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, dsccore, has been registered in the Windows Management Instrumentation namespace root\Microsoft\Windows\DesiredStateConfiguration to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 17/03/2015 19:27:47 Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, dsccore, has been registered in the Windows Management Instrumentation namespace root\Microsoft\Windows\DesiredStateConfiguration to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 14/03/2015 10:06:08 Type: Warning Category: 0 Event: 10010 Source: Microsoft-Windows-RestartManager Application 'C:\Windows\System32\RuntimeBroker.exe' (pid 5916) cannot be restarted - Application SID does not match Conductor SID.. Log: 'Application' Date/Time: 14/03/2015 10:06:08 Type: Warning Category: 0 Event: 10010 Source: Microsoft-Windows-RestartManager Application 'C:\Program Files\Internet Explorer\iexplore.exe' (pid 1988) cannot be restarted - Application SID does not match Conductor SID.. Log: 'Application' Date/Time: 14/03/2015 10:06:08 Type: Warning Category: 0 Event: 10010 Source: Microsoft-Windows-RestartManager Application 'C:\Windows\explorer.exe' (pid 2968) cannot be restarted - Application SID does not match Conductor SID.. Log: 'Application' Date/Time: 14/03/2015 10:05:20 Type: Warning Category: 0 Event: 10010 Source: Microsoft-Windows-RestartManager Application 'C:\Program Files\Internet Explorer\iexplore.exe' (pid 1988) cannot be restarted - Application SID does not match Conductor SID.. Log: 'Application' Date/Time: 14/03/2015 10:05:20 Type: Warning Category: 0 Event: 10010 Source: Microsoft-Windows-RestartManager Application 'C:\Program Files (x86)\Toshiba TEMPRO\Toshiba.Tempro.UI.CommonNotifier.exe' (pid 3600) cannot be restarted - Application SID does not match Conductor SID.. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 26/03/2015 15:47:28 Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 21/03/2015 21:03:59 Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 18/03/2015 19:41:36 Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 13/03/2015 16:21:30 Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 20/02/2015 15:46:53 Type: Critical Category: 64 Event: 10115 Source: Microsoft-Windows-DriverFrameworks-UserMode The device Amanda Williams (GT-I9 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. Log: 'System' Date/Time: 20/02/2015 15:46:53 Type: Critical Category: 64 Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. Log: 'System' Date/Time: 20/02/2015 15:45:53 Type: Critical Category: 64 Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode The device Amanda Williams (GT-I9 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. Log: 'System' Date/Time: 20/02/2015 15:45:53 Type: Critical Category: 64 Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. Log: 'System' Date/Time: 22/08/2014 18:17:34 Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 20/08/2014 22:20:26 Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 28/03/2015 12:17:43 Type: Error Category: 0 Event: 10010 Source: Microsoft-Windows-DistributedCOM The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout. Log: 'System' Date/Time: 28/03/2015 12:17:13 Type: Error Category: 0 Event: 10010 Source: Microsoft-Windows-DistributedCOM The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout. Log: 'System' Date/Time: 27/03/2015 20:52:41 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 20:52:41 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 20:52:40 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 20:52:09 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 20:52:09 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 20:52:08 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 19:14:46 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 252. Log: 'System' Date/Time: 27/03/2015 19:14:46 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 252. Log: 'System' Date/Time: 27/03/2015 19:12:54 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 19:12:54 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 19:12:54 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 19:11:13 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 252. Log: 'System' Date/Time: 27/03/2015 19:11:13 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 252. Log: 'System' Date/Time: 27/03/2015 19:11:12 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 252. Log: 'System' Date/Time: 27/03/2015 19:11:12 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 252. Log: 'System' Date/Time: 27/03/2015 19:05:21 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 19:05:20 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. Log: 'System' Date/Time: 27/03/2015 19:05:20 Type: Error Category: 0 Event: 36888 Source: Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 28/03/2015 16:29:24 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 28/03/2015 15:49:42 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 28/03/2015 13:59:14 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 28/03/2015 10:09:08 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 28/03/2015 04:24:10 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 27/03/2015 19:12:39 Type: Warning Category: 0 Event: 4230 Source: Tcpip TCP/IP has chosen to restrict the congestion window for several connections due to a network condition. This could be related to a problem in the TCP global or supplemental configuration and will cause degraded throughput. Log: 'System' Date/Time: 27/03/2015 18:43:02 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 27/03/2015 18:29:27 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 27/03/2015 09:05:05 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 27/03/2015 06:45:02 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 26/03/2015 23:17:04 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 26/03/2015 19:09:46 Type: Warning Category: 0 Event: 4230 Source: Tcpip TCP/IP has chosen to restrict the congestion window for several connections due to a network condition. This could be related to a problem in the TCP global or supplemental configuration and will cause degraded throughput. Log: 'System' Date/Time: 26/03/2015 18:32:19 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 26/03/2015 17:07:44 Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name pq-direct.revsci.net timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 26/03/2015 17:01:08 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 26/03/2015 16:48:01 Type: Warning Category: 0 Event: 4230 Source: Tcpip TCP/IP has chosen to restrict the congestion window for several connections due to a network condition. This could be related to a problem in the TCP global or supplemental configuration and will cause degraded throughput. Log: 'System' Date/Time: 26/03/2015 16:46:48 Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name tracking.m6r.eu timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 26/03/2015 15:47:29 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 26/03/2015 15:28:14 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset. Log: 'System' Date/Time: 26/03/2015 15:11:50 Type: Warning Category: 0 Event: 1 Source: TXEIx64 The Intel(R) Trusted Execution Engine Interface is being reset.