Win32:Zhelatin-gen2 infecting AVG process?

I don’t know if this could be a false alarm, but after my weekly virus scan earlier today Avast claims to have a SEVERE threat found. I’ll write out what it says. File name: Process 568 [avgcsrva.exe], memory block 0x0000000007960000, block size 4194304 Severity: High Threat: Win32:Zhelatin-gen2 [Wrm]
This shows up twice, except the memory block and block sizes are different between the two.

This shows up on the results page, but I’m not able to click on them or able to take an action in any way except to close out of the window. I don’t get the option to move it to the chest or anything. This whole thing seems rather strange to me, and I just don’t understand what’s going on. avgcsra is the process that runs AVG Security, which I wouldn’t think would register as a virus (except out of jealousy maybe, heheh) so I don’t know what’s happening. Anyone who can shed some light on this would be awesome! Thanks a lot!

File name: Process 568 [avgcsrva.exe], memory block 0x0000000007960000, block size 4194304 Severity: High Threat: Win32:Zhelatin-gen2 [Wrm]
vgcsra is the process that runs AVG Security, which I wouldn't think would register as a virus

Why are you running memory scans?

There are many posts re these sort of reports/problems around in this forum. All of them have to do with running Avast! in a non-standard scan (not default) where running processes are scanned and give this sort of strange result. You cannot move, delete, or quarantine a running process, as it is running in memory, and not resident on the hard drive. All Avast! can do is report that this file is running in memory and flag it.

Solution is to run only default scans, not custom.

BTW, are you running both Avast! antivirus and AVG Security (avg antivirus included) at the same time? Running two resident active antivirus programs can cause conflict and give strange results at the same time. Run only one a/v. If you feel you must run two, one must not be resident or run in real-time. Otherwise, one a/v or the other will report this type of issue as an infection or malicious file.