I find it very peculiar that the results from VEW show date time stamps that are "into the future" from when it was actually run. Some of the dates are showing as 2/2/2015 and it's nowhere near to midnight here.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Log: 'System' Date/Time: 02/02/2015 12:18:38 AMType: Error Category: 0Event: 10016 Source: Microsoft-Windows-DistributedCOMThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.Log: 'System' Date/Time: 02/02/2015 12:18:33 AMType: Error Category: 0Event: 10016 Source: Microsoft-Windows-DistributedCOMThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 02/02/2015 12:17:52 AMType: Error Category: 0Event: 7034 Source: Service Control ManagerThe Realtek DHCP Service service terminated unexpectedly. It has done this 1 time(s).
Log: 'System' Date/Time: 02/02/2015 12:17:37 AMType: Error Category: 0Event: 4 Source: Microsoft-Windows-Time-ServiceThe time provider 'VMICTimeProvider' failed to start due to the following error: The specified module could not be found. (0x8007007E)
Are you running a virtual machine or Hyper-V ?
Log: 'System' Date/Time: 02/02/2015 12:17:23 AMType: Error Category: 0Event: 7006 Source: Service Control ManagerThe ScRegSetValueExW call failed for FailureActions with the following error: Access is denied.
Log: 'System' Date/Time: 02/02/2015 12:16:58 AMType: Error Category: 0Event: 7000 Source: Service Control ManagerThe Garmin Core Update Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Probably because you have part of it turned off with msconfig.
Log: 'System' Date/Time: 02/02/2015 12:16:58 AMType: Error Category: 0Event: 7009 Source: Service Control ManagerA timeout was reached (30000 milliseconds) while waiting for the Garmin Core Update Service service to connect.
Log: 'System' Date/Time: 02/02/2015 12:17:58 AMType: Warning Category: 212Event: 219 Source: Microsoft-Windows-Kernel-PnPThe driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&1&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_MULTIPLE&PROD_CARD_READER&REV_1.00#058F63666433&0#.
Log: 'System' Date/Time: 02/02/2015 12:16:53 AMType: Warning Category: 0Event: 11 Source: Microsoft-Windows-WininitCustom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
Without a FRST or OTL log I can't say what is doing this. Probably Panda.
We can look:
Copy the next 3 lines;
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows" /v AppInit_DLLs > \junk.txt
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows" /v AppInit_DLLs >> \|junk.txt
notepad \junk.txt
Start, All Programs, Accessories then right click on Command Prompt and Run As Admin. Right click and Paste or Edit then paste and the copied lines should appear. Hit Enter if notepad does not pop up. Copy and paste the text from notepad into a reply.
Log: 'Application' Date/Time: 01/02/2015 9:51:17 PMType: Error Category: 0Event: 1 Source: ChromeThe event description cannot be found.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'Application' Log - Warning Type~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Log: 'Application' Date/Time: 01/02/2015 11:05:04 PMType: Warning Category: 0Event: 1530 Source: Microsoft-Windows-User Profiles ServiceWindows 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-3700817450-263443993-1340972289-1001_Classes:Process 5952 (\Device\HarddiskVolume2\Program Files (x86)\Google\Update\GoogleUpdate.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001_CLASSESLog: 'Application' Date/Time: 01/02/2015 11:05:02 PMType: Warning Category: 0Event: 1530 Source: Microsoft-Windows-User Profiles ServiceWindows 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 - 31 user registry handles leaked from \Registry\User\S-1-5-21-3700817450-263443993-1340972289-1001:Process 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001Process 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001Process 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001Process 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001Process 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001Process 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001Process 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001Process 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001Process 1360 (\Device\HarddiskVolume2\Windows\SysWOW64\Fast Boot\FastBootAgent.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001Process 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\SmartCardRootProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\SmartCardRootProcess 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\trustProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\trustProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\MyProcess 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\MyProcess 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\TrustedPeopleProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\TrustedPeopleProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\CAProcess 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\CAProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Policies\Microsoft\SystemCertificatesProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Policies\Microsoft\SystemCertificatesProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Policies\Microsoft\SystemCertificatesProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Policies\Microsoft\SystemCertificatesProcess 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Policies\Microsoft\SystemCertificatesProcess 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Policies\Microsoft\SystemCertificatesProcess 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Policies\Microsoft\SystemCertificatesProcess 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Policies\Microsoft\SystemCertificatesProcess 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\RootProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\RootProcess 372 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\DisallowedProcess 2336 (\Device\HarddiskVolume2\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-3700817450-263443993-1340972289-1001\Software\Microsoft\SystemCertificates\Disallowed
Most of these are from WIndows Live. Some From Fastboot which comes from Asus. Perhaps there is a newer version for Fastboot and Windows Live? These will slow down shutdown quite a bit.
Log: 'Application' Date/Time: 01/02/2015 10:44:18 PMType: Warning Category: 3Event: 3036 Source: Microsoft-Windows-SearchThe content source <iehistory://{S-1-5-18}/> cannot be accessed.Context: Application, SystemIndex CatalogDetails:(HRESULT : 0x80004005) (0x80004005)Log: 'Application' Date/Time: 01/02/2015 10:44:14 PMType: Warning Category: 3Event: 3036 Source: Microsoft-Windows-SearchThe content source <iehistory://{S-1-5-21-3700817450-263443993-1340972289-1003}/> cannot be accessed.Context: Application, SystemIndex CatalogDetails:(HRESULT : 0x80004005) (0x80004005)Log: 'Application' Date/Time: 01/02/2015 10:26:00 PMType: Warning Category: 3Event: 3036 Source: Microsoft-Windows-SearchThe content source <ONEINDEX14://{S-1-5-21-3700817450-263443993-1340972289-1001}/> cannot be accessed.Context: Application, SystemIndex CatalogDetails:(HRESULT : 0x80004005) (0x80004005)
b. Double click on the Indexing Options.
c. Click on the Advanced button.
d. Click on on Restore Defaults.
I will run the memory test only if necessary after all of this is reviewed. I have no indications of issues with memory that I am familiar with.