This problem has plagued for us the past couple of years (about June 2008). Randomly, through out the company, we get a random STOP 8E BSOD on computers at bootup. User logs in and bang: STOP 8E in NTOSKNRL.EXE. Very rarely, this comes up as a STOP 8E in EAMON.SYS. If you reboot, the PC/laptop will boot without any problems. We are running Windows XP SP3 across the board and have had this issue across ESET 3.0 and now 4.0. It happens on new computers, old computers, ones running standard image and others the stock OEM Dell image. Eventually, the problem goes away and then comes back. It always comes in batches: multiple computers will BSOD with the same error message. Why do I think ESET is the problem? Well, I looked in our ticketing system and right around the time we deployed ESET in replacement of Symantec in May 2008, all these BSOD tickets started appearing 2 weeks later. I even got this error on a brand new Optiplex 755 computer. I formatted the drive, put Windows 2003 server R2 on it and after a few logins, up comes STOP 8E in NTOSKRNL.EXE. I took a guy that was really a bad case: about 3 BSODs a week with 8E, took off ESET and put on Microsoft Security Essentials. For the past 2 months, he has not BSODed once. The kicker of course is that when you look at the mini dumps, the problem child is NTOSKRNL and generally not EAMON. However, this can't be a NTOSKRNL problem or Microsoft would get like a million complaints a day. Any one have any ideas? I haven't approached ESET tech support, because I fear they are just going to blame my hardware or Windows setup. I would really like to just dump ESET completely and go with Forefront just to see if this BSOD problem goes away.