Sys freezes on Outlook if Imon is on at startup

HI,

I have nod32 2nd version. (I have winxp.)

Just started happening where if I turn IMON on then start Outlook the system freezes. I have to boot, then start Outlook first, and then Imon.

This is a brand new problem, and wondering if anyone else has this problem and how to fix it.

(I have not downloaded sp2.)

Thanks, Taperino

 

Try and run the winsockfix utility found here: WinSock XP Fix

Drop us a note if it fixes your issue.

 

hi, are u using a D-Link modem?

the driver software for some D-Link modems is having compatability problems with windows xp SP1 & SP2, that causes the computer to freeze applications when a connection is made with the net. outlook may be connecting to check your e-mail.

the problems have only recently become apparent, i think with the latest updates from microsoft. there is an error with the L2TP/IPSec services.
you can check from event viewer, look for errors,details.

or mabey this has nothing 2 do with your problem...

 

Dear Rumpstah,

I ran that fix, and while running it the system beeped internally. Should it have done that?

I then turned on IMON and the sys didn't crash, but I haven't rebooted again as I am afraid the sys won't come up. It didn't come up this morning but did on reboot.

I'll have to boot a few more times before seeing if fix worked.

Before this problem started I got a message from outlook that flew by so fast I couldn't read it.

I don't know what to do if computer breaks, I have no money to get it fixed.

I'll let you know if it continues to work.

Thanks, taperino.

 

Have you tried disabling ZoneAlarm to see if that makes a difference? Just tossing out ideas.

 

The internal beeping happens at the beginning and end of the Winsock XP Fix running. This is normal.

If your system had a bad tcp/ip stack, it may have taken a long time for it to come back up.

Please keep us informed.

Thank you.

 

The following is a manuel way to fix Winsock:


To resolve this issue, delete the corrupted registry keys, and then reinstall the TCP/IP protocol.


Step 1: Delete the corrupted registry keys

1. Click Start, and then click Run.

2. In the Open box, type regedit, and then click OK.

3. In Registry Editor, locate the following keys, right-click each key, and then click Delete:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

4. When you are prompted to confirm the deletion, click Yes.

Note: Restart the computer after you delete the Winsock keys.

Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.


Step 2: Install TCP/IP

1. Right-click the network connection, and then click Properties.

2. Click Install.

3. Click Protocol, and then click Add.

4. Click Have Disk.

5. Type C:\Windows\inf, and then click OK.

6. On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.

7. Restart the computer.


Hope this helps…

Let us know how you go…

Cheers

 

Hi again,

The winsock xp fix worked!!!!!! Thanks for telling me about the system beep also.

Is there any way I can prevent this problem in the future? What does winsock fix? The registry? I'm very illiterate at these things.

Thank you so much for the fix.

Sincerely,

Taperino

 

Glad to see that it did! You are welcome regarding the system beep(s).

As far as prevention, there is not an easy answer as these keys become corrupt due to programs and or processes that may be shutdown prematurely.

Registry keys are what it fixes. See Blackspear's post #7 above regarding which keys.