DisplayLink Forum - View Single Post

iecuk · 07-24-2013, 01:17 AM

I have been having the same problem for the last week and reached the same conclusion as you this evening. I had been tearing my hair out today after losing count of the number of crashes. I have changed memory modules, drives, worked through recent Windows updates etc and then started looking at what I use that is "out of the ordinary" given the lack of reports online. That was when I remembered having similar issues when ESET first introduced HIPS in Version 5 (change log here: http://www.eset.co.uk/Download/ChangeLog/EAVB).

Now, if what you have said is stable (DisplayLink 6.1.3 with ESET 5.0.2126) then it has got to be more than a coincidence that the version of DisplayLink was the last version released before ESET introduced HIPS (DisplayLink releases: http://www.displaylink.com/support/downloads.php).

I noticed that ESET picks up the three active DisplayLink executables as unknown and only discovered them within the last week (guessing due to the revised version number), and as such they do not have a "green light". I tried to create some sort of HIPS rule to account for this, but really don't understand it. Instead, I have now disabled HIPS and HIPS Self Defence again (as I did when the first introduced it).

Now to see if the problem goes away and stays away.

I will post back tomorrow and let you know if the system is stable.

HTH,

iecuk

07-24-2013, 01:17 AM	#8
iecuk Junior Member Join Date: Jul 2013 Posts: 2	I have been having the same problem for the last week and reached the same conclusion as you this evening. I had been tearing my hair out today after losing count of the number of crashes. I have changed memory modules, drives, worked through recent Windows updates etc and then started looking at what I use that is "out of the ordinary" given the lack of reports online. That was when I remembered having similar issues when ESET first introduced HIPS in Version 5 (change log here: http://www.eset.co.uk/Download/ChangeLog/EAVB). Now, if what you have said is stable (DisplayLink 6.1.3 with ESET 5.0.2126) then it has got to be more than a coincidence that the version of DisplayLink was the last version released before ESET introduced HIPS (DisplayLink releases: http://www.displaylink.com/support/downloads.php). I noticed that ESET picks up the three active DisplayLink executables as unknown and only discovered them within the last week (guessing due to the revised version number), and as such they do not have a "green light". I tried to create some sort of HIPS rule to account for this, but really don't understand it. Instead, I have now disabled HIPS and HIPS Self Defence again (as I did when the first introduced it). Now to see if the problem goes away and stays away. I will post back tomorrow and let you know if the system is stable. HTH, iecuk