Spybot 1.6.2 update and Runtime Error 216

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.

This week I got through all the scans, right up to the very last one. The last one was Spybot, and durring the update process before the scan, version 1.6.2 was installed. The scan then went off without finding a thing. However, when I closed Spybot, after it had concluded the scan, 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 (link here). 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.

Has anyone ever seen this kind of an error with Spybot before? I'm not sure if it's a trojan or just a problem with Spybot's new version, and I'm not sure of what steps to take next. Obviously Nod32, MalwareBytes, and Spybot can't see it if I am infected (even did a safe-mode rescan), 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.

i also recived this error,i did post 4 days ago but got no reply,perhaps its time to ask again.

i certaily dont want to go asking for help if i am not infected and this is not a virus.
it also statred with the new updates,imo its not a virus but seems to be affecting ceratin machine and not others.

still i might be wrong and i would like to know

perhaps this could be awasered?

try looking for this;

C:\WINDOWS\system32\bingoo.exe

it was on my system not sure if thats the reason but might be.
(its not now but i need to do more looking to find anything else that might be causeing this)

Quote:

---

Originally Posted by kinos

try looking for this;

C:\WINDOWS\system32\bingoo.exe

it was on my system not sure if thats the reason but might be.
(its not now but i need to do more looking to find anything else that might be causeing this)

---

I could not find that file on my system anywhere. Additionally, updated MBAM scans have yeilded no traces of Sub7. Given that Sub7 is roughly ten years old, I would certainly hope it could be found. I'm beginning to think more and more that Microsoft might not be correct, and this might not be a virus.

I am also having this problem after updating Spybot tonight. I hope some answers come soon.

I have the same problem. I have version 1.6.2.46. The address that can't be read will vary. Otherwise my errors are identical to the original poster's errors.

I find the crash only happens if I terminate Spybot after it completes a scan. If I stop the scan and terminate, it doesn't crash.

As far as I know, this is always the case when I'm running from my admin account. I tried it from my non-admin account using "runas", and it didn't crash.


P.S. It seems silly that I can't search for Runtime error 216. The search engine will ignore the 216. Maybe it thinks if it narrows down the search too much, it would make things too easy for me? :)

P.P.S. Maybe it's just a coincidence but I also use NOD32.

I disabled NOD32 antivirus and ran some scans. It didn't crash. I re-enabled the antivirus and it still didn't crash. Apparently that fixed my problem, at least temporarily.

just for info;i am not useing nod32.

its about time someone addressed this,it been a week since i first reported this.
even if only to let us know there working on it or somthing.

I had similar error messages after the 29 July SBot update. They haven't reappeared after a reboot, but I noticed something odd:

After the update downloaded, SBot closed by itself, an old style DOS screen came up momentarily running too quickly to make out what was happening, then SBot reopened.

This happened on both my computers. XP Home SP3.

MBAM, Superantispyware, NIS 2009, the Microsoft Malicious Software Removal Tool and SBot all showed the computers as being clean.

I've never seen this behavior from a SBot update before. Weird or expected?

Quote:

---

Originally Posted by NotGeordie

I had similar error messages after the 29 July SBot update. They haven't reappeared after a reboot, but I noticed something odd:

After the update downloaded, SBot closed by itself, an old style DOS screen came up momentarily running too quickly to make out what was happening, then SBot reopened.

This happened on both my computers. XP Home SP3.

MBAM, Superantispyware, NIS 2009, the Microsoft Malicious Software Removal Tool and SBot all showed the computers as being clean.

I've never seen this behavior from a SBot update before. Weird or expected?

---

i belive thats the cmd sreen;expected,it happens occasionally,dont belive ive seen it in a yr or two,thats nothing to worry about.