IMON crashing Internet Explorer

[OldNEWUser]

Well, I am shocked to see that IMON still crashes IE during attempts to stream media even with the new version of Nod32 (2.13 to 2.5). This has been going on for some time now via the complaints in this forum. Why is it that this issue can not be corrected after all this time? I'm ready to move on if for only this one issue, and there are a number of other problems with 2.5 to be mentioned. What is the deal?

[rumpstah]

Hi OldNEWUser:

For many (most) these types of issues are non-existent. Major causes are:

1. Vestiges of other programs including but not limited to:
Another antivirus
Firewall
Spyware monitors/removers
Adware removers

2. Registry "healers" improperly removing needed (mostly windows) entries.

3. Corrupt winsock entries.

Correctly removing programs from #1 can be daunting to say the least.

Running an sfc /scannow can help to repair missing entries/files in the OS.

Running winsockfix can assist with the streaming.

It can be any one or more of the above (and some not listed).

If you can provide more information regarding your current (or removed programs from above) setup, that would be helpful.

;)

[OldNEWUser]

Hi rumpstah,

I appreciate the reply and the effort in trying to resolve the issue. Let me take each statement you made one by one and reply to them..


Another antivirus - I only have Nod32 installed and running.
Firewall - Windows Firewall
Spyware monitors/removers - Using spywareblaster
Adware removers - No resident programs installed

2. Registry "healers" improperly removing needed (mostly windows) entries.
I do not use these.

3. Corrupt winsock entries. - ESET is BIG on this one. If I had a problem with my winsock entries I would be seeing issues elsewhere and otherwise.


Using other Antivirus programs does not exhibit the issue with streaming media, and Windows XP plainly identifies IMON as what crashed Internet Explorer. So, without sounding sarcastic, let me just say that with the two facts just mentioned, it does not take much to figure out where the problem lies.

This reminds me of all the times I used to have to deal with dialup tech support. "There is nothing wrong with my computer"... LOL

Thanks for trying, really, but I don't buy it.

Later dude

[Marcos]

Just out of curiosity, didn't you switch your streaming media player (wmp, winamp, etc.) to higher efficiency mode in the IMON setup?

[pc-support]

{QUOTE-> Hi rumpstah,
Windows XP plainly identifies IMON as what crashed Internet Explorer <-QUOTE}

Can you post the exact errors from the windows 2000/xp event logs? After all, without a lot more information from yourself how can we be expected to help you?

[OldNEWUser]

Thanks guys. I will get the crash log for you..

[OldNEWUser]

Here you go....

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 11/1/2005
Time: 2:19:20 AM
User: N/A
Computer:
Description:
Faulting application iexplore.exe, version 6.0.2900.2180, faulting module imon.dll, version 0.0.0.0, fault address 0x0001c30a.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 69 65 78 ure iex
0018: 70 6c 6f 72 65 2e 65 78 plore.ex
0020: 65 20 36 2e 30 2e 32 39 e 6.0.29
0028: 30 30 2e 32 31 38 30 20 00.2180
0030: 69 6e 20 69 6d 6f 6e 2e in imon.
0038: 64 6c 6c 20 30 2e 30 2e dll 0.0.
0040: 30 2e 30 20 61 74 20 6f 0.0 at o
0048: 66 66 73 65 74 20 30 30 ffset 00
0050: 30 31 63 33 30 61 0d 0a 01c30a..

[OldNEWUser]

Hi Marcos,

The answer to your question is no. I'm not sure of how to do it either.

[OldNEWUser]

To continue to prove that NOD32 and IMON is the cause of my problems, I tried yet another antivirus program to see how it would behave. This time I tried the latest from Kaspersky, and sure enough I had no crashes during anything, much less streaming media. I did not like Kaspersky as far as speed, compared to NOD32, however. It just seemed slightly sluggish. Guess I'm spoiled. I hope ESET can fix said issue, as I'm ready to give up the ghost and bite the slower speed bullet of another antivirus.

[Marcos]

OldNewUser, I could not send you a PM as you are not registered. Please drop an email to support[at]eset.com with a link to this thread and enclose the information on installed NOD32 as well (this can be found in the NOD32 Control Center - NOD32 System Tools - Information).

[OldNEWUser]

Done! Thanks! :)

[ZGeist]

Hi.

Just like to add, are you running IE7?

I have IE hangups running IE7 beta 1 with IMON. So you're not the only one.
I'm also running AdMuncer though.

I told IMON to ignore both of them. -- Problem Solved, I guess.

[OldNEWUser]

No IE 7 here. I have not heard anything from ESET either.

[CyberMew]

Sorry to bump this up but sometimes (rarely) i get that error too.

Faulting application iexplore.exe, version 6.0.2900.2180, faulting module imon.dll, version 2.51.26.0, fault address 0x0001ca63.

[Blackspear]

{QUOTE-> Sorry to bump this up but sometimes (rarely) i get that error too.

Faulting application iexplore.exe, version 6.0.2900.2180, faulting module imon.dll, version 2.51.26.0, fault address 0x0001ca63. <-QUOTE}I would suggest repairing Winsock, (http://www.wilderssecurity.com/showthread.php?p=462132#post462132) then repair IMON; see post number 40 HERE (http://www.wilderssecurity.com/showthread.php?p=266653#post266653)

Let us know how you go...

Cheers ;D