BSOD 0xD1 in eamonm.sys, Windows 7 x64

Today my Windows 7 x64 crashed with BSOD for the first time (I think) in over a year. Here's some details:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP 0x000000D1
eamonm.sys FFFFF88002442B57

I have memory.dmp and minidump file and can send it to someone from ESET.

Windows has all patches installed. ESS was working fine for a long time.

ESS Smart Security, English version, 4.2.64.12:

Virus signature database: 5752 (20110101)
Update module: 1031 (20091029)
Antivirus and antispyware scanner module: 1293 (20101110)
Advanced heuristics module: 1115 (20101116)
Archive support module: 1123 (2010110
Cleaner module: 1050 (20101207)
Anti-Stealth support module: 1023 (20101125)
Personal firewall module: 1061 (20100607)
Antispam module: 1015 (20100524)
SysInspector module: 1217 (20100907)
Self-defense support module : 1018 (20100812)
Real-time file system protection module: 1004 (20100727)

This happened while I was away from computer and I have no idea how to reproduce. However, I hope you can use memory dump to narrow down the place where an operation was made under incorrect IRQL level.

Feel free to ask more questions.

 

Hello,
you can PM me a link to the dump. I'd strongly recommend installing the latest version 4.2.67 which might address this issue. Another reason for the BSOD might be malware or another probably outdated 3rd party driver.

 

Hello,

The first thing ESET Support is going to get you to do is upgrade to the latest version of ESET Smart Security to see if that fixes the problem. You can download and install v4.2.67.10 from the ESET Download Center. I recently had eamonm.sys STOP errors when restarting my Vista machine after installing Windows updates, and upgrading to the latest build available at the time fixed the problem.

Happy New Year!

Mark

 

There's no mentioning of crashes in the changelog between my version and the current version. I will definitely upgrade the software. However, given >1yr error-free operation, I'm not expecting another BSOD anytime soon, even without upgrade : )

My hope is that the data I'm uploading to ESET FTP server will help locating the offending call that ran under wrong IRQL. Please, update the thread when/if you're able to locate the root cause.