Search the Community

After installing the November 2014 update rollup for Windows (hxxp://support2.microsoft.com/kb/3000850/en-us) Windows starts to BSOD on boot. Removing ESET Smart Security 8 or the November 2014 rollup fixes the issue. I have tried reinstalling Windows 8.1 and installed all updates. The computer works fine until I install Smart Security 8. Everything is works until the first reboot and then the BSOD on boot starts again. Removing either Smart Security 8 or the November 2014 rollup will fix the issue. My system: Lenovo Thinkpad W520 set to UEFI only Windows 8.1 x64 (with all updates) and bitlocker on all disks Smart Security 8.0.304.0

Hello everyone, This will be a long post but I will add a TL;DR version at the bottom. We've got 1048 PC's that we've recently bought ESET Endpoint Security licenses for, we're upgrading from Symantec Endpoint Protection. So after we installed about 400 machines, we realized the machines were getting really slow, hanging, getting bluescreens, and the HDD light is constantly burning / processes running very high. I immediately contact our local South African Eset helpdesk, and they told me to install the new version EES 5.0.2228.1 up from 5.0.2225.0. The remote upgrade didn't work, so I had to start all over again (we don't have an Active Directory, so we install it manually). This made things even worse, PC's with the 5.0.2228.1 version were worse off than before. We already established it wasn't a driver issue. Windows updates were done, all AV updates were done, nothing helps. We took a machine and formatted it completely and just loaded ESET and it still gives intermittent bluescreens. It's not every machine that does that, only about 50 so far. But that's 50 angry people who can't work... I've captured memory.dmp files, even though sometimes they don't leave any memory.dmp files behind, I run DumpConfigurator.hta and simulate a BSOD and then collect the memory.dmp file. I've submitted it to ESET HQ, but they haven't responded yet. The only way I can get the machines to function normally again, is to uninstall ESET. When the processes runs high, and the hard drive light is constantly on, I disable ESET's real-time protection and firewall, and the whole machine goes back to idle. The BSOD error and STOP code I get looks like the follow: Kernel_Data_Inpage_Error Stop: 0x0000007A (0xX0418680, 0xC000000E, 0x232F6860, 0x830D0160) Please, I really don't know what to do anymore. TL;DR We've installed ESET on 400+ machines and getting freezing, hanging blue screen of deaths as a result. Only thing that solves it is removing ESET. See BSOD message above. Any help would be appreciated!

I have a problem installing Eset Endpoint Security Version 5.0.2122.10. The install begins, but then the whole computer crashes and the bluescreen appears. The system is a Lenovo Thinkpad T440 Windows 7. We have no problem installing Eset Endpoint Security on computers from other vendors. I have searched in earlier threads regarding this issue and found some fixes. But nothing have worked for me. The most popular fix is to disable ESET device control integration but this is disabled as default in this new install package version from Eset. I am very grateful for any help with this issue.

I have two computers running: Windows 7 x64 SP1 and ESET NOD32 Anti-Virus 7.0.302.26 This morning (about 13 hours ago), one system BSOD: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffffa80087d6ca2, 0x0000000000000000, 0xfffff880029c8f29, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030314-25989-01. After doing some research on this type of error (hxxp://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx), I have decided (for the moment) this is probably a "one-time" event -- as this is the first BSOD on this system that I can recall in at least several years, and the error has not reoccurred in over 12 hours. (The error occurred while using Skype, if that makes any difference ... and I used Skype frequently afterwards without issue.) But ... here's the issue which I don't know if it is related to the above. On both systems, the modules are the same (as of 10:30 p.m. Eastern/U.S.) ... Virus signature database: 9496 (20140303) Rapid Response module: 3767 (20140303) Update module: 1047 (20131023) Antivirus and antispyware scanner module: 1421 (20140219) Advanced heuristics module: 1147 (20140114) Archive support module: 1191 (20140210) Cleaner module: 1084 (20140224) Anti-Stealth support module: 1057 (20131125) ESET SysInspector module: 1240 (20131202) Real-time file system protection module: 1006 (20110921) Translation support module: 1145 (20131121) HIPS support module: 1115 (20140206) Internet protection module: 1108 (20140224) Database module: 1054 (20140218) ... except on the system that BSODed ... the HIPS support module is now 1119 (20140227) On both systems NOD32 is set for "regular updates," not "pre-release updates" Can anyone confirm whether 1115 or 1119 is the current HIPS module? Did one of my computer's inadvertently pull down a pre-release module or has one computer not updated to the latest HIPS module? In either case, how can I resolve the issue? Thanks for any insights!

Hi, I'm having a problem launching tf2/l4d2/payday2 or any other source based game. i cant launch them without turning off ALL of my security features. Which is weird, because it used to work just fine. When i launch the game with all of my security features turned on it will launch the process but it becomes bugged and cannot be killed with nothing but a reboot (tried several other options besides windows task manager). i've tried to disable the security features for 10 minutes, launching the game, only to get a blue screen after 10 minutes 5 out of 5 times. So my question is: Is there any way i can whitelist the tf2/l4d2/pd2 proces so it will bypass smart security? i know this will create a hole in my protection but turning smart security aff completely makes an even bigger hole than just the tf2 proces.

I'm using ESS 7.0.302.26 and OpenVPN 2.3.2 When I start OpenVPN and connect to a server (TAP up), sometimes will trigger BSOD which says IRQL NOT LESS OR EQUAL, uncheck Epfw NDIS LightWeight Filter in wireless network properties can solve this issue, so I think it is a conflict, but uncheck filter seems not safe, so maybe ESET can solve this problem? I can provide minidump file if you want and I can promise this issue happens since ESS v5. Thanks~

hi i did notice the sometime peerblock the last version and smart security 6 generate bsod that's happen occasionally is there a fix? thanks