Multiple "kzhztufvoy.exe*32" Google Chrome running & causing high CPU.
1. Ran a virus/malware check and came back with nothing
2. Uninstalled Chrome with same results
3. Looked for "kzhztufvoy.exe*32" in system 32 directory but no file found.
Any ideas?
Last edited by sdstarnes; 01 Jan 2015 at 14:32.
Wow that is bizarre. Various search engines come up with nothing or only this thread. That is unusual...
Virus, I would suggest you run Adwcleaner and clean anything found, If something running shows the (*32) entry I have always found to be a virus.
Adwcleaner: don't worry it's safe.
AdwCleaner Download
I ran into that same thing a few weeks ago. None of my anti-malware programs could detect it (although SuperAntiSpyware was able to find all the adware the accursed little beast was frantically installing on my machine) and I also found nothing when I searched the "interwebz". It apparently lodges its sorry little self (I would be more descriptive but Mama told me not to use those words) in the system reserved partition and reinstalls its sorry little self in a legitimate program every time I rebooted. The only way I was able to get rid of the misbegotten little piece of...ah...work for keeps was to restore from an earlier image.
If you don't have images you can restore from, you might try doing a System Restore back to before when the little...pest first showed up. If your AV is capable of it, you might be able to do a boot scan to see if that can find it (I didn't bother because it takes a really long time with my AV).
HitmanPro [free for 30 days], Malwarebytes Anti-Malware [free or pay-for versions] might detect and root out such things.
That's why I have several anti-viri and anti-malware run several scheduled scans during the week, 'cause no one program ever catches everything everytime everywhere. Thanks for the update :)
Nothing found it. I'm running Avast Free, MBAM PRO, SuperAntiSpyware (SAS; it did find and clean up the huge amount of adware the miserable bugger installed), and Spybot S&D. Avast might have found it with a boot scan but it takes a really long time for that to run so I just wimped out and restored from an earlier image.
Quote