Help!
I deleted the trojan because I was unable to move it to chest (Access Denied). My computer is still running slow and CPU usage is high (fan is running, loud), and disk space is low (140GB) even though I dont have files that do not take up total gig space (should only be around 60GB used. I already ran Full system scan, Malware Bytes, Spyware Blaster, RunScanner, and Dr. WebCureIt. What do I do?
To avoid using multiple post with copy and paste you have to attach the log`s
Lower left corner: Additional Options > Attach ( OTL.Txt and Extras.Txt. and Malwarebytes scan log)
No, I just ran it without updating. I am currently running MalwareBytes again (I just updated to the current version). I also included the file in my initial post above.
If the original detection was by avast, then you should have scheduled a boot-time scan as that would have got round the access denied issue as it gets in before windows has fully started.
I’d wait and see what an expert has to say about the OTL log. It looks decidedly rootkit-y to me, but I don’t know.
When I see numbers like that in the alternate data stream, and names like “tempimage.exe” that definitely raises suspicions.
Most likely, the result you got in the quote box above is because avast uses gmer as it’s rootkit detector inside the avast program. Avast had already scanned for rootkits and a separate gmer scan was not needed.
Please wait for Essexboy to interpret your logs before doing anything else.
Essexboy is a certified malware expert.
[*]Then click the Run Fix button at the top
[*]Let the program run unhindered, reboot the PC when it is done
[*]Open OTL again and click the Quick Scan button. Post the log it produces in your next reply.
Im experiencing unusually high CPU Usage (around 50% idle, up to 100% in use)
Slower computer performance
Fan is constantly on (except when asleep or hibernation)
Disk Space (C: Primary Drive)is almost full. It fluctuates by GB every time I look at the disk space. Low disk space warnings also appear and say less than 6MB left on the drive.
I did a chkdsk on D (Recovery) and C (Primary) and found no errors.
Attached are the OTL logs, per your instructions. Thank you very much for your help, much appreciated!