Certain processes in Windows are specially protected by additional signature enforcements. \Device\HarddiskVolume3\Program Files\Emsisoft Anti-Malware\a2hooks64.dll The invalid hashes could indicate a potential disk device error.įile Name: \Device\HarddiskVolume3\Program Files\Emsisoft Anti-Malware\a2hooks64.dll The file could be improperly signed without page hashes or corrupt due to unauthorized modification. Source: Microsoft-Windows-Security-AuditingĬode Integrity determined that the page hashes of an image file are not valid. My boots have been noticeably slower with multiple desktop refreshes and now I suspect this as the reason. I just noticed the same thing in my event log. I will appreciate any insightful input very much.
I have not analyzed the dates and times at this point.Īn attempt at an explanation concerning these Code Integrity Logs will go a long way towards my moving on from these questions unless problems arise over the next few days. I have noticed that from the Code Integrity Logs that the A2hooks64.dll problem comes and goes and could very well be linked to when a2hooks64.dll is updated, as it is not always updated in all new build releases.
Is it a timing issue when the system is under heavy use? Does it have something to do with alternating betweem 3 user profiles or :ĭoes it have something to do with the latest Build 6513 installing a new Epp.sys driver or a new A2hooks64.dll?
Why does A2hooks64.dll specifically have problems with Code Integrity Checks? I am sure that the file is properly signed as I have checked.
I am concerned that I may start encountering problems again related to A2hooks64.dll or epp.sys and I will let you know promply. It has only been 1 whole day since I updated to build 6513 (done on 070316) and everything went smoothly but :
(Basically programs that rely heavily on Net Framework 4.5.2.īut, now since my update to build 6513 the log entry:Ĭode Integrity is unable to verify the image integrity of the fileĪ2hooks64.dll because the set of per-page image hashes could not be found on the system has reappeared since the EAM build 6513 update. I also noticed that all of these problems stopped happening after I made the above mentioned repairs and re-installs. Per crashdumps and MS Reliability App compatibility Reports, I believe most of my occasional app stopped working were either due to Framework Garbage Collection or a2hooks64.dll hanging up under heavy video browsing sometimes leading to a epp.sys bsod.
I also noticed in the Code Integrity Log (after re-installing EAM after clean uninstall using Emsiclean Removal) that the Code Integrity log entries no longer appeared and I was very satisfied plus my system was running for many days at a time without any problems such as app stopped working or BSOS's or Framework garbage collection timing issues. I re-installed EAM (the prior build to current one) plus emet 5.2 and have had no problems for around 10 days (no need to reboot) concerning any Net Framework garbage collection issues or crash dumps or apps stopped working issues. I ran it on all 3 user profiles to be sure all user profiles were successful. So about 4 weeks ago I did a clean uninstall of EAM and epp.sys driver and the Emet 5.2 program and then did a Net Framework Repair Tool repair with success. Also, per older complete memory dumps(1 month or older) the epp.sys driver was blamed by WhoCrashed Program. I have seen these entries sporadically (3 or 4 times a month) since 12-08-15.