BSOD issues Possibly related to Nod32

I have been having some issues with some windows 7 machines crashing. The only link I have been able to find between the 4 computers (all running windows 7 professional) is they all had downloaded and installed Windows update :
Definition Update for Windows Defender - KB915597 (Definition 1.123.978.0)
And after the system is restarted, or signed onto, it will either BSOD on start up, or the user will be able to sign on for a short period of time, then it will BSOD and continuously restart and crash.
We have run into a similar issue before but on Windows Server 2008 R2, and we determined the issue was ESET nod32. After Removal, the servers worked fine and quit unexpectedly crashing. The same seems to be True in this case with the windows 7 machines. We have removed nod32 from the machines that were experiencing these issues, and the issue seems to be resolved.
I'm trying to look at the memory.dmp files but and having no luck opening them in windbg because it says i'm not using the correct symbols (which I downloaded and have listed in windbg symbol file path area). I was wondering If someone could possibly help me out with these and help shed some light on what the exact issue(s) is/are on these PC's and if they are all related or if each are having their own problems.
I am attaching a copy of the Memory.DMP file from one of the computer's (file extentions changed to .txt) for anyone that may be able to help.

Thank you for your time
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

smckeown777Connect With a Mentor Commented:
Might be the only option

Do u have enterprise support?
Might be an option to send them the same u sent here
They may be more able to help

But to get ur machines back on their feet uninstall and reinstall
Maybe its me but I can't see your memory dump file?
Can you attach the minidump files? They are smaller in size, usually located in C:\Windows\Minidump...

sobrsuAuthor Commented:
Oh.. looks like it didn't make it because the file was to large.. I found three files. in the mini dump folder

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

sobrsuAuthor Commented:
and here are 2 more from another computer that experienced the same problem just this morning.
smckeown777Connect With a Mentor Commented:
Based on the minidumps these BSOD's are also relating to ESET, the faulting file is listed as 'eamonm.sys' which is a file associated with ESET antivirus

Is ESET up to date with latest version?
willcompConnect With a Mentor Commented:
The faulting module on both PCs is eamonm.sys which is the NOD32 driver. Copies of the crash dump analyses are attached.
@smckeown777 -- didn't mean to steal your thunder. At least we agree.
Not a problem sir, all here to help!
sobrsuAuthor Commented:
Wow Thanks for the quick responses. This is the list of Installed components for nod32 :

Virus signature database: 7024 (20120403)
Update module: 1040 (20120313)
Antivirus and antispyware scanner module: 1349 (20120329)
Advanced heuristics module: 1121 (20111208)
Archive support module: 1143 (20120320)
Cleaner module: 1054 (20120323)
Anti-Stealth support module: 1026 (20110628)
ESET SysInspector module: 1216 (20100517)
Self-defense support module: 1018 (20100812)
Real-time file system protection module: 1006 (20110921)

And the Version we are running is : Version

To the Best of my knowledge this is the latest (For enterprise). I know personal is at version 5, but it hasn't been released for business use which allows for a Remote Administration and Update server and all that.
Any Advice on how to proceed? Maybe just re installing NOD32?
Also u mentioned windows defender update
Possibly it and nod are in conflict?
Can u disable it maybe an see if it helps?
sobrsuAuthor Commented:
Well, on the system's that were experiencing this issue NOD32 was uninstalled. I reinstalled on one of the computer's last night, and spoke to the user this morning (who's been working on it for about 2 hours now) who said it was working fine. I found this help article on ESET's website 
And it looks like the windows defender updates have caused problems in the past. I had another issue with them after trying to recreate this problem on a test machine. I installed NOD32, before anything else on a brand new Laptop running windows 7 pro x86. After I ran all windows updates and nothing happened, I opened NOD32 and there are no menu items available and a message shows saying error communicating with kernel. Just thought I'd post that to document ESET issues here.
But any way, thank you smckeown777 and willcomp. You helped me out greatly.
Good info to know, glad u got sorted...
I'm glad I'm not the only one that has been experiencing these freezes and crashes.  I have had 3 users at work in the past week all reported the same issues as the original poster.  All PC's effected are running Windows 7 Profession 64-bit and all have ESET NOD32.  My breakdown of the error reports pointed to ESET being a factor.  I temporarily resolved this on the first user to report the issue by completely removing ESET.  They have been 100% stable since the removal of ESET.  I still have to reinstall on that users's PC and see if the issue reappears.

Thanks for the info everyone posted here.  I'm troubleshooting 2 more PC's with this issue as I type this...
All Courses

From novice to tech pro — start learning today.