The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Runtime Error 216? Microsoft says it's a Trojan?
TetraNitroCubane
Not Angry...Just VERY Disappointed...Registered User regular
Not Angry...Just VERY Disappointed...Registered User regular
Hi everyone, just a quick question about a weird error I received this evening. Every week I do a thorough system scan with NOD32, MalwareByte AntiMalware, and then Spybot S&D. I know Spybot is pretty useless, but I still use it for the immunizations.
This week I got through all the scans, right up to the very last one, without finding a thing. However, when I closed Spybot, I got the following error:
" The instruction at "0x074d40c2" referenced memory at "0x0777dec8". The memory could not be "read" "
Followed by:
" runtime error 216 at 074D40C2 "
Now, according to Microsoft, this error is caused by the SubSeven trojan. I can't find out much more than this, as being the cause, since just about everything on Google says it's SubSeven, too. I can't imagine having a trojan, since Nod32 is running, already scanned thoroughly, and have also done the same with MalwareBytes and Spybot. Then again, Spybot did update and install a patch, and I don't know if that might've been hijacked.
Does anyone have any advice for finding out if I actually do have this trojan? Obviously Nod32, MalwareBytes, and Spybot can't see it if I am, and I don't want to install a second A/V program on top of an existing one... Is there anything I can do to see if the virus is there otherwise? Telltale signs and the sort?
Alternatively, does anyone have any experience with this "runtime error 216"? Is it really only caused by a virus, or is it possibly something else? Thanks.
This week I got through all the scans, right up to the very last one, without finding a thing. However, when I closed Spybot, I got the following error:
" The instruction at "0x074d40c2" referenced memory at "0x0777dec8". The memory could not be "read" "
Followed by:
" runtime error 216 at 074D40C2 "
Now, according to Microsoft, this error is caused by the SubSeven trojan. I can't find out much more than this, as being the cause, since just about everything on Google says it's SubSeven, too. I can't imagine having a trojan, since Nod32 is running, already scanned thoroughly, and have also done the same with MalwareBytes and Spybot. Then again, Spybot did update and install a patch, and I don't know if that might've been hijacked.
Does anyone have any advice for finding out if I actually do have this trojan? Obviously Nod32, MalwareBytes, and Spybot can't see it if I am, and I don't want to install a second A/V program on top of an existing one... Is there anything I can do to see if the virus is there otherwise? Telltale signs and the sort?
Alternatively, does anyone have any experience with this "runtime error 216"? Is it really only caused by a virus, or is it possibly something else? Thanks.
TetraNitroCubane on
0
Posts
CUZ THERE'S SOMETHING IN THE MIDDLE AND IT'S GIVING ME A RASH
Apparently there are new versions defeating updated scanning tools all the time. Wikipedia claims so, at least. Can you recommend a trusted site that's serving such a tool? The other issue is that most google results just say 'Install our antimalware software!', and I'm not sure what more I should be running beyond Nod, MBAM, and Spybot.
Also, I'm not even sure if I do have an infection or not. I did another MBAM scan, this time in safemode, and it didn't come up with anything. I'm begging to wonder if it was just an odd Spybot issue (seems reproducable in Spybot, but the error doesn't occur anywhere else). There aren't any popups or browser hijacks, or otherwise. Process Explorer doesn't seem to show any other odd processes running beyond what I'm used to seeing, and TCP/IPview isn't showing any open connections... But I realize this is hardly definitive proof - Keyloggers can remain tucked away without being verified, I know. I'm just a bit wary of going nuts and breaking my system in an attempt to solve a problem that's not there, while still being paranoid as hell about this "runtime error 216".
Uhm. Backup, slow format, re-install windows?
I know it's not what you want to hear, but it beats anything but a BIOS level rootkit...
CUZ THERE'S SOMETHING IN THE MIDDLE AND IT'S GIVING ME A RASH
Shit. That seems a bit overkill, but I guess it must be the only way? So Runtime Error 216 is certainly an indication of a virus/trojan?
Oh well, I guess.
I started using IE again recently instead of Mozilla Firefox.
Spybot never gave me any problems until I move to IE. I was aksed by IE to enable Spybot in its add-ons, which I did.
Since then, despite putting the seetings back to default under IE, I get the "Instructions at..." and runtime error at the END of the automatice scan.
The scan runs properly, I remove/fix any problems found and it's only on closing Spybot that I get this problem.
If IE isn't running or I do a manual scan, this problem doesn't occur.
Are you using IE?