I was trying to fix my cousin's computer (she had Internet Security 2010 and various other problems). Some of the other problems included "DCOM Server Process Launcher service terminated unexpectedly" and "Generic Host Process for Win32 Services encountered a problem". The DCOM message always wanted to force a reboot.
In the process of doing scans, the computer shut down and supposedly did updates. I accidentally clicked for AVG to heal a file - C:\WINDOWS\SYSTEM32\6334.exe. - about 20-30 minutes before it shut down.
After that, I got a BSOD screen 0x0000007F (0x0000000D, 0x00000000, 0x00000000, 0x00000000). This would not let me do anything (including safe mode). I am not sure if the 6334 file caused the BSOD or if it was caused by viruses/malware still on the computer.
I posted this in the BSOD thread first and was advised to make that hard drive a slave and do a hard drive diagnosicts, then the 8 step virus/malware removal process. I have done all that, but not sure how to do a HJT log for the slave drive. Both drives are using Windows XP.
I have attached the required logs. I am more concerned with the E drive than C being stable enough to use again on its own, and hopefully without any lingering issues.
I would appreciate any help you can give me. Thank you.
In the process of doing scans, the computer shut down and supposedly did updates. I accidentally clicked for AVG to heal a file - C:\WINDOWS\SYSTEM32\6334.exe. - about 20-30 minutes before it shut down.
After that, I got a BSOD screen 0x0000007F (0x0000000D, 0x00000000, 0x00000000, 0x00000000). This would not let me do anything (including safe mode). I am not sure if the 6334 file caused the BSOD or if it was caused by viruses/malware still on the computer.
I posted this in the BSOD thread first and was advised to make that hard drive a slave and do a hard drive diagnosicts, then the 8 step virus/malware removal process. I have done all that, but not sure how to do a HJT log for the slave drive. Both drives are using Windows XP.
I have attached the required logs. I am more concerned with the E drive than C being stable enough to use again on its own, and hopefully without any lingering issues.
I would appreciate any help you can give me. Thank you.