Very Disappointed in NOD32 v3

And hopefully a last time. I'm another EAV fan who was trouble free until I installed v.3.0 in each new version that has come out. Like qdemn7 I've had nothing but BSODs since with all the crash dump analyses pointing to the easdrv.sys driver. I uninstalled 3.0 and went back to 2.7, which does not have that driver, and I'm trouble free again. Its not other software, its the easdrv.sys driver that's causing the problem and it needs fixing. EAV 2.7 is installed on two other machines owned by family members but I'm not upgrading them until the problem is sorted. Version 3.0 is much smarter and simpler but it has to work!

 

I haven't upgraded to 3.0 yet. It seems I made the right decision to wait just a little longer.

 

Due to Marcos help my problem has been solved. The problem is the easdrv.sys.

As Marcos stated:

Edit: Personal correspondence removed.
Marcos

I d/l the file, reinstalled v3, replaced the file and rebooted. No problems and the system has been running for over 4 hours. I did an indepth scan, and have been running the system at 100% using BIONC.

 

I'm sorry, but why is my personal ftp mentioned here? There's also a general rule that personal email may not be disclosed without a consent of the person it concers. As of now, I will not provide any links by PM to persons that I'm not familiar with.

 

Marcos, I have read your helpful contributions on the forums for some time and have appreciated them. But if there is an answer to a common problem can you not share it with all of us who are suffering from the problem? That, after all, is what qdemn7 was trying to do, even if he was going about it the wrong way.

 

I apologize profoudly, I was simply not thinking. I should have asked first, I was wrong.

 

Of course, if there is a solution to a known problem we announce it here. It does not justify posting here private correspondence and links to a private ftp. We kindly ask you all to accept this rule.
If there is a newer version of a specific dll/drive available for testing, I send it privately to the appropriate person or limited group of people who have reported the issue.

 

Thank you. I look forward to hearing the outcome.

 

There's no "staff" FTP accounts on this server to utilize to help end users? Thus not have to open up/advertise/worry about "personal" ones.