New
#21
That's possible. I know I have had some trojans detected in my backup drives before. Sometimes it does slip through before definition updates allow the antivirus software to be aware of the malware/viruses.
That's possible. I know I have had some trojans detected in my backup drives before. Sometimes it does slip through before definition updates allow the antivirus software to be aware of the malware/viruses.
Yep, and Avira seems to suck at removing it, even the rescue cd did nothing. I need to find a better free antivirus.
Most on here use Microsoft Security Essentials and Malwarebytes. I found this to work well. An even better setup was provided by a friend of mine on the forums: Good and Free system security combination.
As to removing the malicious item you are trying to remove, there are a few nice offline scanners: Windows Defender Offline
Free Bootable AntiVirus Rescue CDs Download List
Thanks, I'll look into all that. I do currently run MBAM, Avira, and various little exe's like Kaspersky's TDSS killer, GMER, and a bunch of others.
Well, I'm still getting 116 errors and I only have a minimal install, pretty much just Cat drivers, everything Windows auto installed like chipset and such, and DirectX for a couple games.
I tried loading Runescape and got the error just a couple minutes into playing. It actually gave a blue screen this time, then proceeded to restart and crashed somewhere along the POST before my monitor even turned on and started looping until my mobos built in "bad start" kicked in after 3 loops, default setting, and finally started and told me. I don't think this is an OC error as it has done it before at stock speeds when I was trying to narrow things down. So, I'm now going to load up OCCT and run the psu test again and see if I can replicate the problem.
Do you have this problem with either graphics card installed? Have you tried the other graphics card?
Before this last wipe I was getting 116 with both cards out, so I think that eliminates those right?
Running onboard graphics, you mean? If you get a 116 error with onboard graphics, and you have a minimal installation, chances are it is hardware related and probably a bad motherboard. It could be a bad PSU, as well, but I find that less likely given the small amount of hardware installed.
Last edited by writhziden; 06 May 2012 at 18:21. Reason: PSU?
Not onboard, I was running the integrated HD3000 on my 2500k.
Ah, interesting... Was not aware of that feature. Hopefully that does not mean a bad 2500k CPU... Doing a little research online indicates the 0x116 due to the HD3000 may be resolved by getting the proper Intel graphics driver for that device.