Very Disappointed in NOD32 v3

[qdemn7]

I've been using NOD32 for over 5 years, always been extremely pleased, any infections were caught right away. Never had any problems with permanent infections requiring clean install of Windows. The only problem I've encountered in the past is false positives generated when running Trojan Hunter automatic scanning while NOD32 is running.

Just upgraded to v3 yesterday, and had nothing but problems. Constant BSODs with the easdrv.sys as the culprit. Uninstalled NOD32 reinstalled it 3 times, still not working.

Contacted support and they told me that I can't run Trojan Hunter, and Spybot Tea Timer while running v3. so I turned them off in msconfig. The last time the system ran OK for about 4 hours before the BSOD started again. Started up BOINC and that was it.

Still running Spywareblaster, don't know if that's the problem or what. I really don't want to have to uninstall it, but I will if I have to. So right now I have no anti-virus on my system. Still working with support, sent them a LookinmyPC report as they requested.

Anyone have any ideas?

[rolarocka]

Turning them off in msconfig is not the same as uninstalling. I would really try uninstalling them.

[proactivelover]

welcome to eset support forum
tell about your OS
what version you trying to install(v3.0.650 letest)

[qdemn7]

Thank you for the quick replies. System is XP Pro w/all updates. Very latest version, downloaded just yesterday 04/03. Do you want a list of all installed software?

[Marcos]

The best would be to create a full memory dump when a BSOD occurs. If you have a fast-speed Internet connection, I can grant you access to our ftp so that we could get the dump and analyse it.

[qdemn7]

-{ Quote: "The best would be to create a full memory dump when a BSOD occurs. If you have a fast-speed Internet connection, I can grant you access to our ftp so that we could get the dump and analyse it." }-I can do that. I'll have to reinstall NOD32. Thank for the help. What info do you need from me to grant me access?

[Marcos]

I'll PM you details. Note that the size of a full memory dump will be as large as the amount of installed RAM, but zipping it will diminisher it a bit.

[qdemn7]

Acknowledged. PM replied.

[qdemn7]

File uploaded. I re-installed NOD32, tried a few things, and the system seemed OK. Rebooted the system and got an immediate BSOD.

[gvWSF]

Usually BSOD issues are retaled to hardware. I wouldn't blame v3 for that.

[piranha]

anybody can explain what is BSOD ?

qdemn7

Downgrade to v2.7, i did and many other did. One day the v3 will be as perfect as v2.7 is still now

[The_Duality]

BSOD is a "blue screen of death" - the characteristically blue error screen seen when an error is serious enough to cause the system to halt :)

[stratoc]

third attempt with v3, still get much more ram and cpu use than v2.7 it was'nt allowed by my firewall (on silent oops) after 4 days i noticed it had never updated, as shown in the log and yet all was green and giving full protection aparrently? back with 2.7 again..

[qdemn7]

-{ Quote: "anybody can explain what is BSOD ?

qdemn7

Downgrade to v2.7, i did and many other did. One day the v3 will be as perfect as v2.7 is still now" }-Well it's only be two days, if support and the forums here can't help, I will have to downgrade.

[piranha]

-{ Quote: "BSOD is a "blue screen of death" - the characteristically blue error screen seen when an error is serious enough to cause the system to halt :)" }-


Ho boy !!!! BSOD...... remember me W98 !!!

Hardware problem ? If all is ok befor he installed NOD32 V3 and right after he got BSOD.... hum..... :doubt:

[the mul]

Well all I can say is I gave version 650 a go of eset antivirus last night, I uninstalled and cleaned out the old version 2.7 with reg cleaners and deleted all files and folders, then I installed latest version 650 of eset antivirus and set it up using all of blackspears settings, things went ok for about 15 minutes, then bsod and I rebooted my system and all seemed to go ok, as it was getting late I went to my bed and when I checked my system in the morning about 5 hours later after install of version 650 I had lost my wireless connection it just would not connect, :'( I have never seen this in all of my 2 years using wireless until I installed v3 of eset and not had a bsod for many many months either, my other system connected to my router without any issues and it has version 2.7 installed on it, so I have uninstalled v3 650 and I have installed 2.7 of nod32 once again and set it up using blackspears settings and everything is back to normal .;D
I will give v3 a go maybe in the future if things improve but I am like many others staying with version 2.7 for now which runs like a dream.:thumb:

THE MUL

[CBiggerstaff]

I've been having intermittent BSODs for about 3 weeks now myself. I enabled Verifier about an hour ago and it has identified easdrv.sys as the culprit. I just relized I'm running v3.0.642.0 even though I have updates on - guess maybe they just update signatures and not program - dunno. So I have downloaded v650 and am going to give that a try, but now you have me concerned that will not help either. I suppose it's worth a shot.
I too have been a loyal user of NOD32 for some years and recommend it to my clients. This is concerning. Wonder if they lost some good developers or what - seems they are having issues with v3 across the board with their new variation offerings. I hope they can manage to come up with new reliable software in the future. I'm surprised they haven't managed it yet, I waited sometime to upgrade thinking they had finally got it good.

[qdemn7]

I'm beginning to think the developers tried to do much with one app. They seem to be making a mistake many other vendors have made, making their program become bloated memory hogs.

One reason I went to NOD32 was the recommendation of it's small footprint and lack of impact on the system. With v3, that seems to be falling by the wayside.

[qdemn7]

Update:

Well the easdrv.sys is definitely in conflict with something, I just don't know what. I uninstalled Spybot, Spywareblaster and Trojan Hunter. Did a CClean and a Registry Mechanic clean. Installed v3, and rebooted the system. Instant BSOD. I couldn't even boot into Safe Mode to do system restore. I had to use a backup drive as a boot drive, then go into the main drive C partition and delete all Eset files. The problem is that the easdrv.sys resides in the drivers folder and not the Eset folder. Once I did that I booted back into my primary drive and the system is now running fine. I'm not running ANY anti-virus, trojan or spyware apps, so I'm puzzled just what this driver is conflicting with.

[e36]

-{ Quote: "Update:

Did a CClean and a Registry Mechanic clean. " }-

Automatic registry cleaning is very risky. My guess is, this is the cause of your problem.

[piranha]

-{ Quote: "Automatic registry cleaning is very risky. My guess is, this is the cause of your problem." }-


:shifty: I did it regularly too with CCleaner and RegCleaner with probleme here

[qdemn7]

-{ Quote: "Automatic registry cleaning is very risky. My guess is, this is the cause of your problem." }-

I have to disagree, I've been using both for over a year now, with no problems before. The only BSOD, I've seen before this have been related to overclocking. Ther system isn't o/c now.

[Joliet Jake]

Someone mentioned Spywareblaster. I have this and NOD V3, no problems.

[qdemn7]

-{ Quote: "Someone mentioned Spywareblaster. I have this and NOD V3, no problems." }-It's not Spywareblaster. I unistalled that and the BSOD still occurs.

[The Hammer]

-{ Quote: " no problems before. " }-There's always a first time. :isay:

[Ants]

-{ Quote: "There's always a first time. :isay:" }-
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!

[The Hammer]

-{ Quote: "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. ;)

[qdemn7]

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.

[Marcos]

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.

[Ants]

-{ Quote: "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 concerns. 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.

[qdemn7]

-{ Quote: "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." }-I apologize profoudly, I was simply not thinking. I should have asked first, I was wrong.

[Marcos]

-{ Quote: "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." }-

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.

[Ants]

-{ Quote: "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.

[YeOldeStonecat]

-{ Quote: "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." }-

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. ;)