Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 31/07/2016 2:54:25 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 31/07/2016 6:28:53 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 31/07/2016 2:38:24 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 29/07/2016 12:34:43 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 31/07/2016 6:53:38 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x800736cc: Update for Windows 7 for x64-based Systems (KB2732487).
Log: 'System' Date/Time: 31/07/2016 6:33:57 PM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 6:29:53 PM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 6:29:25 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 3:10:16 AM on ?7/?31/?2016 was unexpected.
Log: 'System' Date/Time: 31/07/2016 5:19:50 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80246007: Security Update for Windows 7 for x64-based Systems (KB3109094).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80246007: Security Update for Windows 7 for x64-based Systems (KB3078601).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80246007: Security Update for Windows 7 for x64-based Systems (KB3156016).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80246007: Security Update for Windows 7 for x64-based Systems (KB3110329).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80246007: Security Update for Windows 7 for x64-based Systems (KB3035132).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024200d: Security Update for Windows 7 for x64-based Systems (KB3156019).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024200d: Security Update for Windows 7 for x64-based Systems (KB3035126).
Log: 'System' Date/Time: 31/07/2016 3:02:01 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80242016: Update for Internet Explorer 8 Compatibility View List for Windows 7 for x64-based Systems (KB2598845).
Log: 'System' Date/Time: 31/07/2016 2:59:54 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {752073A1-23F2-4396-85F0-8FDB879ED0ED} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 31/07/2016 2:59:37 AM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The event description cannot be found.
Log: 'System' Date/Time: 31/07/2016 2:55:02 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 2:52:14 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 2:51:44 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 2:49:17 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 2:44:45 AM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The NVIDIA Stereoscopic 3D Driver Service service terminated unexpectedly. It has done this 1 time(s).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 31/07/2016 6:31:29 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 31/07/2016 5:43:20 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ajax.cloudflare.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 31/07/2016 3:46:29 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 31/07/2016 2:52:26 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 31/07/2016 2:44:46 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 31/07/2016 1:50:28 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310916608 bytes, svchost.exe (316) consumed 501866496 bytes, and chrome.exe (2656) consumed 236052480 bytes.
Log: 'System' Date/Time: 31/07/2016 1:45:29 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310752768 bytes, svchost.exe (316) consumed 501927936 bytes, and chrome.exe (2656) consumed 236052480 bytes.
Log: 'System' Date/Time: 31/07/2016 1:40:29 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310752768 bytes, svchost.exe (316) consumed 501923840 bytes, and chrome.exe (2656) consumed 234688512 bytes.
Log: 'System' Date/Time: 31/07/2016 1:35:29 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 501919744 bytes, and chrome.exe (2656) consumed 231784448 bytes.
Log: 'System' Date/Time: 31/07/2016 1:30:32 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 501862400 bytes, and chrome.exe (2656) consumed 231972864 bytes.
Log: 'System' Date/Time: 31/07/2016 1:25:29 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 502022144 bytes, and chrome.exe (2656) consumed 226627584 bytes.
Log: 'System' Date/Time: 31/07/2016 1:20:32 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 501964800 bytes, and chrome.exe (2656) consumed 225427456 bytes.
Log: 'System' Date/Time: 31/07/2016 1:15:27 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 502083584 bytes, and chrome.exe (2656) consumed 224743424 bytes.
Log: 'System' Date/Time: 31/07/2016 1:10:27 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 501903360 bytes, and chrome.exe (2656) consumed 219430912 bytes.
Log: 'System' Date/Time: 31/07/2016 1:05:26 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 501841920 bytes, and chrome.exe (2656) consumed 216850432 bytes.
Log: 'System' Date/Time: 31/07/2016 1:00:26 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 502046720 bytes, and chrome.exe (2656) consumed 215801856 bytes.
Log: 'System' Date/Time: 31/07/2016 12:55:27 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9183145984 bytes, svchost.exe (316) consumed 502050816 bytes, and chrome.exe (2656) consumed 213975040 bytes.
Log: 'System' Date/Time: 30/07/2016 8:12:20 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name nist1.nyc.certifiedtime.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 29/07/2016 7:36:26 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 29/07/2016 3:42:52 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
This is the file generated by the Event Viewer Tool with the "Application" box checked:
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 31/07/2016 2:57: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: 31/07/2016 6:40:07 PM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 31/07/2016 6:40:07 PM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
Log: 'Application' Date/Time: 31/07/2016 5:31:21 AM
Type: Error Category: 0
Event: 1014 Source: Microsoft-Windows-Security-SPP
Acquisition of End User License failed. hr=0xC004C008 Sku Id=da22eadd-46dc-4056-a287-f5041c852470
Log: 'Application' Date/Time: 31/07/2016 5:31:21 AM
Type: Error Category: 0
Event: 8200 Source: Microsoft-Windows-Security-SPP
License acquisition failure details. hr=0xC004C008
Log: 'Application' Date/Time: 31/07/2016 5:26:16 AM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 31/07/2016 5:26:16 AM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
Log: 'Application' Date/Time: 31/07/2016 3:02:09 AM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 31/07/2016 3:02:09 AM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
Log: 'Application' Date/Time: 31/07/2016 2:44:40 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: RtlService.exe, version: 700.1006.416.2010, time stamp: 0x4bc81b90 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x745c7454 Faulting process id: 0x6ac Faulting application start time: 0x01d1ead4c3e01a6f Faulting application path: C:\Program Files (x86)\CNet\Wireless LAN Driver and Utility\RtlService.exe Faulting module path: unknown Report Id: b9ed1b69-56c8-11e6-a366-00e04d70621e
Log: 'Application' Date/Time: 31/07/2016 2:44:35 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: NvNetworkService.exe, version: 1.0.3.10, time stamp: 0x531e899e Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x745c7454 Faulting process id: 0x618 Faulting application start time: 0x01d1ead4c06cfbea Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NetService\NvNetworkService.exe Faulting module path: unknown Report Id: b6ec3ef0-56c8-11e6-a366-00e04d70621e
Log: 'Application' Date/Time: 31/07/2016 2:44:32 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: nvSCPAPISvr.exe, version: 7.17.13.4052, time stamp: 0x53b44454 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x745c7454 Faulting process id: 0x2e8 Faulting application start time: 0x01d1ead4aa2cbefa Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPISvr.exe Faulting module path: unknown Report Id: b4f39b36-56c8-11e6-a366-00e04d70621e
Log: 'Application' Date/Time: 31/07/2016 2:43:58 AM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 31/07/2016 2:43:58 AM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
Log: 'Application' Date/Time: 31/07/2016 1:46:11 AM
Type: Error Category: 0
Event: 9020 Source: Desktop Window Manager
The Desktop Window Manager has encountered a fatal error (0x80070008)
Log: 'Application' Date/Time: 30/07/2016 9:33:04 PM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service Windows Workflow Foundation 4.0.0.0 (Windows Workflow Foundation 4.0.0.0) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 30/07/2016 9:33:04 PM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
Log: 'Application' Date/Time: 30/07/2016 9:33:04 PM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service Windows Workflow Foundation 4.0.0.0 (Windows Workflow Foundation 4.0.0.0) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 30/07/2016 9:33:04 PM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
Log: 'Application' Date/Time: 30/07/2016 9:32:41 PM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service MSDTC Bridge 4.0.0.0 (MSDTC Bridge 4.0.0.0) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 30/07/2016 9:32:41 PM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 31/07/2016 6:31:24 PM
Type: Warning Category: 0
Event: 6004 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <TrustedInstaller> failed a critical notification event.
Log: 'Application' Date/Time: 31/07/2016 5:21:37 AM
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: Application Requested}.
Log: 'Application' Date/Time: 31/07/2016 2:52:14 AM
Type: Warning Category: 0
Event: 6004 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <TrustedInstaller> failed a critical notification event.
Log: 'Application' Date/Time: 31/07/2016 2:52:14 AM
Type: Warning Category: 0
Event: 6006 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <TrustedInstaller> took 153 second(s) to handle the notification event (CreateSession).
Log: 'Application' Date/Time: 31/07/2016 2:50:40 AM
Type: Warning Category: 0
Event: 6005 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <TrustedInstaller> is taking long time to handle the notification event (CreateSession).
Log: 'Application' Date/Time: 31/07/2016 2:44:26 AM
Type: Warning Category: 0
Event: 6004 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <TrustedInstaller> failed a critical notification event.
Log: 'Application' Date/Time: 31/07/2016 2:43:08 AM
Type: Warning Category: 0
Event: 6006 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <TrustedInstaller> took 112 second(s) to handle the notification event (CreateSession).
Log: 'Application' Date/Time: 31/07/2016 2:42:16 AM
Type: Warning Category: 0
Event: 6005 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <TrustedInstaller> is taking long time to handle the notification event (CreateSession).
Log: 'Application' Date/Time: 31/07/2016 12:53:13 AM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files (x86)\Google\Chrome\Application\chrome.exe' (pid 2452) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 31/07/2016 12:53:12 AM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files\Microsoft Security Client\msseces.exe' (pid 2944) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 31/07/2016 12:53:12 AM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\explorer.exe' (pid 2404) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 31/07/2016 12:53:12 AM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files (x86)\Skype\Phone\Skype.exe' (pid 2952) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 30/07/2016 9:32:31 PM
Type: Warning Category: 1
Event: 1020 Source: ASP.NET 4.0.30319.0
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /i.
Log: 'Application' Date/Time: 30/07/2016 9:32:28 PM
Type: Warning Category: 1
Event: 1020 Source: ASP.NET 4.0.30319.0
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /i.
Log: 'Application' Date/Time: 30/07/2016 9:31:28 PM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files (x86)\Skype\Phone\Skype.exe' (pid 2952) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 30/07/2016 9:31:02 PM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files (x86)\Skype\Phone\Skype.exe' (pid 2952) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 30/07/2016 9:21:57 PM
Type: Warning Category: 1
Event: 1020 Source: ASP.NET 4.0.30319.0
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /i.
Log: 'Application' Date/Time: 30/07/2016 9:21:53 PM
Type: Warning Category: 1
Event: 1020 Source: ASP.NET 4.0.30319.0
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /i.
Log: 'Application' Date/Time: 30/07/2016 9:09:49 PM
Type: Warning Category: 1
Event: 1020 Source: ASP.NET 4.0.30319.0
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /i.
Log: 'Application' Date/Time: 30/07/2016 9:09:45 PM
Type: Warning Category: 1
Event: 1020 Source: ASP.NET 4.0.30319.0
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /i.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 31/07/2016 6:28:53 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 31/07/2016 2:38:24 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 29/07/2016 12:34:43 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 31/07/2016 6:53:38 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x800736cc: Update for Windows 7 for x64-based Systems (KB2732487).
Log: 'System' Date/Time: 31/07/2016 6:33:57 PM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 6:29:53 PM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 6:29:25 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 3:10:16 AM on ?7/?31/?2016 was unexpected.
Log: 'System' Date/Time: 31/07/2016 5:19:50 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80246007: Security Update for Windows 7 for x64-based Systems (KB3109094).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80246007: Security Update for Windows 7 for x64-based Systems (KB3078601).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80246007: Security Update for Windows 7 for x64-based Systems (KB3156016).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80246007: Security Update for Windows 7 for x64-based Systems (KB3110329).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80246007: Security Update for Windows 7 for x64-based Systems (KB3035132).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024200d: Security Update for Windows 7 for x64-based Systems (KB3156019).
Log: 'System' Date/Time: 31/07/2016 3:42:53 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024200d: Security Update for Windows 7 for x64-based Systems (KB3035126).
Log: 'System' Date/Time: 31/07/2016 3:02:01 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80242016: Update for Internet Explorer 8 Compatibility View List for Windows 7 for x64-based Systems (KB2598845).
Log: 'System' Date/Time: 31/07/2016 2:59:54 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {752073A1-23F2-4396-85F0-8FDB879ED0ED} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 31/07/2016 2:59:37 AM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The event description cannot be found.
Log: 'System' Date/Time: 31/07/2016 2:55:02 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 2:52:14 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 2:51:44 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 2:49:17 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start. Module Path: C:\Windows\system32\Rtlihvs.dll Error Code: 126
Log: 'System' Date/Time: 31/07/2016 2:44:45 AM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The NVIDIA Stereoscopic 3D Driver Service service terminated unexpectedly. It has done this 1 time(s).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 31/07/2016 6:31:29 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 31/07/2016 5:43:20 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ajax.cloudflare.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 31/07/2016 3:46:29 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 31/07/2016 2:52:26 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 31/07/2016 2:44:46 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 31/07/2016 1:50:28 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310916608 bytes, svchost.exe (316) consumed 501866496 bytes, and chrome.exe (2656) consumed 236052480 bytes.
Log: 'System' Date/Time: 31/07/2016 1:45:29 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310752768 bytes, svchost.exe (316) consumed 501927936 bytes, and chrome.exe (2656) consumed 236052480 bytes.
Log: 'System' Date/Time: 31/07/2016 1:40:29 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310752768 bytes, svchost.exe (316) consumed 501923840 bytes, and chrome.exe (2656) consumed 234688512 bytes.
Log: 'System' Date/Time: 31/07/2016 1:35:29 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 501919744 bytes, and chrome.exe (2656) consumed 231784448 bytes.
Log: 'System' Date/Time: 31/07/2016 1:30:32 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 501862400 bytes, and chrome.exe (2656) consumed 231972864 bytes.
Log: 'System' Date/Time: 31/07/2016 1:25:29 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 502022144 bytes, and chrome.exe (2656) consumed 226627584 bytes.
Log: 'System' Date/Time: 31/07/2016 1:20:32 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 501964800 bytes, and chrome.exe (2656) consumed 225427456 bytes.
Log: 'System' Date/Time: 31/07/2016 1:15:27 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 502083584 bytes, and chrome.exe (2656) consumed 224743424 bytes.
Log: 'System' Date/Time: 31/07/2016 1:10:27 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 501903360 bytes, and chrome.exe (2656) consumed 219430912 bytes.
Log: 'System' Date/Time: 31/07/2016 1:05:26 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 501841920 bytes, and chrome.exe (2656) consumed 216850432 bytes.
Log: 'System' Date/Time: 31/07/2016 1:00:26 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9310838784 bytes, svchost.exe (316) consumed 502046720 bytes, and chrome.exe (2656) consumed 215801856 bytes.
Log: 'System' Date/Time: 31/07/2016 12:55:27 AM
Type: Warning Category: 3
Event: 2004 Source: Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TrustedInstaller.exe (296) consumed 9183145984 bytes, svchost.exe (316) consumed 502050816 bytes, and chrome.exe (2656) consumed 213975040 bytes.
Log: 'System' Date/Time: 30/07/2016 8:12:20 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name nist1.nyc.certifiedtime.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 29/07/2016 7:36:26 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 29/07/2016 3:42:52 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
I forgot to mention that the CPU is damaged (it overheated because there was no thermal paste on it when it was installed). I had to underclock it for it to function properly. However, it worked fine before while damaged & underclocked. Could the CPU be causing the problem? I apologize for forgetting to mention this detail.