Memory leak

[Hagla007]

I was testing the Nod32 RC out on a heavily infected machine. The HIPS was messed up. It was constantly popping up. During the scan Eset used almost 100% of the CPU. In addition, it couldn't get rid of a Win32/Patched.GC trojan.

http://imageshack.us/photo/my-images/268/esetcpu.jpg/

[Galaxykiss]

scan in safe mode please

[agoretsky]

Hello,

Did you try scanning from an ESET SysRescue disc? If so, did that make any difference?

Regards,

Aryeh Goretsky

[Marcos]

The title of the thread is "Memory leak" but I don't see any such indication / evidence in your post.

[Hagla007]

Since this happened in a virtual machine, I don't really care so much about it. I won't scan with a SysRescue disk.

Marcos, maybe the title of the thread was wrong. However, the CPU-usage is extremely high, and it almost makes the computer freeze. I don't know if it was "fighting" with another process to get high CPU, but if you look at the picture, there is a process called "ssdapi5.exe". It's a malware which, along side with Eset, trying to "use the most CPU". It was either one of them who used 90+% CPU.

I just want to say that Nod32 did a good job by detecting malware. Over 3000 pieces of malware, or tracks, was found. Good job! And after a full in-depth scan, it got rid of the ssdapi5.exe, but the Win32\Patched.GC is still there popping up all the time.

[Marcos]

Originally Posted by Hagla007

And after a full in-depth scan, it got rid of the ssdapi5.exe, but the Win32\Patched.GC is still there popping up all the time.

Patched files are usually uncleanable / irrecoverable and need to be replaced with a clean copy of the files.

[Hagla007]

I submitted the file anyways.