Backdoor.generic_c.akaf

Here's an update, for those wondering:

I followed the instructions contained in AVG's e-mail, and gave remote access to my computer to an AVG tech support representative. They downloaded some additional free AVG components to my computer (I'm not sure if they were necessary, but I suppose I can remove them). They also downloaded something called "PC Doctor for Windows" (again, I suppose I can remove it).

They performed a scan using AVG, and also using "Adware Removal Tool by TSA" (which wasn't on my computer to begin with, so I'm assuming they installed it; however, I cannot find it in my list of programs - perhaps it's the same thing as the "PC Doctor" software that I saw them install?). 

The scans detected the trojan horse backdoor.generic_c.akaf, and both scans indicated that the infected file was healed. However, the trojan horse was detected on subsequent scans.

The tech support representative then checked the Resident Shield log from the initial detection of the trojan horse. The Resident Shield log has a section named "Extended element information", and in this section it lists a process name of "c:\Program Files\Malwarebytes' Anti-Malware\mbam.exe". 

The representative then told me that there isn't actually a trojan horse virus on my computer. He said that AVG is continually detecting a trojan horse due to a conflict between it and Malwarebytes. Since Malwarebytes is trying to take access of my computer settings, he said, AVG detects it as a virus.

Which is all well and good, but I'm left wondering about a few things. Firstly, Malwarebytes isn't new to my computer. It and AVG had co-existed peacefully until today. So why all of a sudden did AVG begin to detect it as a virus? I hadn't even updated Malwarebytes since 2012.

Secondly, if the conflict with Malwarebytes was the cause of the "false trojan horse", why does AVG continue to detect it at C:\Program Files\Hewlett-Packard\HP Health Check\ActiveCheck\vista2\systemAgeDetect.jse? Why wouldn't it detect it in a Malwarebytes file?

Thirdly, after my session with the tech support representative ended, I uninstalled Malwarebytes and ran another AVG scan. It is still detecting and "healing" the infected file. If the cause of the problem was a conflict with Malwarebytes and Malwarebytes is no longer on my computer, why is AVG still detecting the trojan horse?

So ultimately, AVG assured me that there isn't actually a trojan horse on my computer, but I am left somewhat suspicious of that determination.