NOD32 and Win2000 SP4

  • Thread starter Thread starter Mark Jurik
  • Start date Start date
M

Mark Jurik

I recently bought NOD32 v1 and installed it with default settings. It
installed OK and my computer rebooted. However, within 2 minutes of
getting the desktop displayed, I get the blue screen of death saying
the NTKERNEL had a unhandled exception error. The system would then
reboot and crash again, ad infinitum. To stop this, I ran the O/S in
safe mode, uninstalled NOD32 and all is well once again. Anybody else
have this problem?

SYSTEM SPECS:

Tyan dual-proc MB, running Win2000, SP4, with all the latest security
upgrades from MS, as of 20-OCT-03. Also using IE6, SP1, with all the
latest security upgrades, and ZoneAlarm Pro (latest version).

- Mark
 
(e-mail address removed) (Mark Jurik) wrote in
I recently bought NOD32 v1 and installed it with default settings. It
installed OK and my computer rebooted. However, within 2 minutes of
getting the desktop displayed, I get the blue screen of death saying
the NTKERNEL had a unhandled exception error. The system would then
reboot and crash again, ad infinitum. To stop this, I ran the O/S in
safe mode, uninstalled NOD32 and all is well once again. Anybody else
have this problem?

SYSTEM SPECS:

Tyan dual-proc MB, running Win2000, SP4, with all the latest security
upgrades from MS, as of 20-OCT-03. Also using IE6, SP1, with all the
latest security upgrades, and ZoneAlarm Pro (latest version).

- Mark
Click to expand...

I am runnning NOD32 v 2.6 (latest) with Win 2k SP4 and all the fixings with
no problems.

Duane :)
 
SYSTEM SPECS:

Tyan dual-proc MB, running Win2000, SP4, with all the latest security
upgrades from MS, as of 20-OCT-03. Also using IE6, SP1, with all the
latest security upgrades, and ZoneAlarm Pro (latest version).
Click to expand...

Try uninstalling ZoneAlarm, not simply disabling it, and then try NOD32
again.

ZoneAlarm seems to cause all too many 'funnies' and there are other,
some would say better - certainly less intrusive on the system -
firewalls. Free too.

Cheers,

Roy
 
Have several computers on work network with Win 2K SP4 and latest Nod32 with
no problems.

Let us know what the cure is eventually. Perhaps a over top OS refresh
repair reinstall.
 
Have several computers on work network with Win 2K SP4 and latest Nod32 with
no problems.

Let us know what the cure is eventually. Perhaps a over top OS refresh
repair reinstall.
Click to expand...

If a product I wanted to use required me to do this I would just stop using he
product.
 
More test results with NOD32 crashing Win2000 ...

My system has a TYAN dual-proc board, running Win2000, SP4.

When I install NOD32 setting both AMON and IMON disabled, the O/S
boots up OK. I then open NOD32 from the system tray, and load IMON
into memory and enable it. It seems to scan files and all is OK.

BUT ... when I change the setting so that IMON is loaded up
automatically during boot, and then reboot, then during the bootup
procedure, just as the desktop appears, the O/S crashes with an
"EXCEPTION_NOT_HANDLED_ERROR"

I reboot into safe mode and run NOD32 from the desktop icon (in safe
mode it does not appear in the system tray). This dialog box does not
allow me to disable IMON. I have no choice but to uninstall NOD32.
When I do, the problem goes away.

ANALYSIS - there appears to be a timing issue, whereby IMON's
activation is too early and is interfering with the normal boot
process. Perhaps this problem occurs only with dual-processor boards.
What's needed is a feature whereby the user can request having IMON
loaded and enabled X seconds after the boot process has completed.

Comments?

- Mark
 
(e-mail address removed) (Mark Jurik) wrote in
More test results with NOD32 crashing Win2000 ...

My system has a TYAN dual-proc board, running Win2000, SP4.

When I install NOD32 setting both AMON and IMON disabled, the O/S
boots up OK. I then open NOD32 from the system tray, and load IMON
into memory and enable it. It seems to scan files and all is OK.

BUT ... when I change the setting so that IMON is loaded up
automatically during boot, and then reboot, then during the bootup
procedure, just as the desktop appears, the O/S crashes with an
"EXCEPTION_NOT_HANDLED_ERROR"

I reboot into safe mode and run NOD32 from the desktop icon (in safe
mode it does not appear in the system tray). This dialog box does not
allow me to disable IMON. I have no choice but to uninstall NOD32.
When I do, the problem goes away.

ANALYSIS - there appears to be a timing issue, whereby IMON's
activation is too early and is interfering with the normal boot
process. Perhaps this problem occurs only with dual-processor boards.
What's needed is a feature whereby the user can request having IMON
loaded and enabled X seconds after the boot process has completed.

Comments?

- Mark
Click to expand...

I think you should contact NOD32 Tech Support. Maybe, there is a work
around you're not aware of at this time. I would think that NOD32 is
running on a dule processor machine somewhere.

There is also the Eset or NOD32 forum.

Duane :)
 
Back
Top