Operating memory cannot be scanned

Hi Everyone,

I am currently running the latest commercial release of NOD32. On running a scan of the hard drive (have tried turning AH on and off) the following error appears:

Error occurred while scanning operating memory. Operating memory cannot be scanned (an error occurred while loading nod32m1.vxd file or during communication with the testing service).

If I restart the pc, the error disappears, but resurfaces in a few days. I've also uninstalled NOD, including deleting the Eset folder. NOD runs fine for a few days, then the error is back.

Has anyone run into this kind of error or am I the only lucky one? All help and suggestions appreciated.

Regards

Chiana

 

I'll let the Eset mods to handle this one....it would be better if you posted your PC specifications as well

 

Thanks Firecat,

Specs as follows: NOD32 Antivirus System information
Virus signature database version: 1.1085 (20050501)
Dated: Saturday, 30 April 2005
Virus signature database build: 5563
Information on other scanner support parts
Advanced heuristics module version: 1.013 (20050303)
Advanced heuristics module build: 1078
Internet filter version: 1.002 (2004070
Internet filter build: 1013
Archive support module version: 1.028 (20050411)
Archive support module build version: 1114

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.12.2
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.12.2
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.12.2

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 1024 MB
Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000 MHz)


Chiana

 

It's supposed to be fixed in beta 2.50

 

Look here

 

Doesnt seem there was a solution then....Not a sure-shot one anyway

 

Hi,

I'm unwilling to install the beta version as I've just reinstalled the OS and sw on this pc and since NOD32 v2.5 release is only a few days away, I'll sit quietly and wait.

Thanks for your replies.

Regards

Chiana

 

Not fixed in beta (at least I have it with the latest beta).

I'm getting it with the scan from the NOD32 manual scan (any profile) as well as the NOD32 Advanced shell extension activated scan.

Has anybody got a fix for this?

Should we file a bug report?

Regards,
Halcyon

PS I've used the search and looked at the other threads. I can't solve this issue with the input from other threads.

 

That would be good beta25@eset.sk

Cheers

 

Thanks!

Bug report sent.

I'll post here if I get a solution to this.

 

Doing one more uninstall / reboot / re-install / reboot cured this for me.

 

Thanks for letting us know Halcyon.

Cheers