Please help,

I have recently switched from nod version 1 to version 2 running under xp
home. I often disable amon if I install a new program or am gaming, to avoid
installation problems and to stop it using system resources. After I
re-enable amon everything is fine until I shutdown at the end of my session.
At this point (more often than not) my pc crashes. Upon reboot i get a
"system has recovered from serious error" message and am asked whether i
want to submit information to microsoft. If I submit the info I am taken to
the microsoft online crash analysis which tells me a device driver has
caused the problem but it cant tell me which one. I have painstakingly
rounded up all of the latest drivers for my hardware but still the problem
persists. However it only ever happens if i disable amon and then re-enable.
Has anyone else ever experienced this problem? I have nod v2 on other
machines and have tried to replicate the problem on them but it seems
rock-solid. It just seems to happen on my home pc. I have had my memory and
cpu tested and they are ok. Could it be an incompatibility with nforce 2
chipset. (The other machines i've tried it on were not nforce).

tia

matthew jones

In article <PVdnb.2227$(E-Mail Removed)>,
(E-Mail Removed) says...

> However it only ever happens if i disable amon and then re-enable.
> Has anyone else ever experienced this problem? I have nod v2 on other

I've never found in necessary to disable Amon for any purpose, not
installation of new software, not even for Windows hotfixes. No ill
effects whatever, and certainly not what you describe.

I'm using NOD32 Version 2.000.6 and XP Home here.

Cheers,

Roy

"Matthew Jones" <(E-Mail Removed)> wrote in
news:PVdnb.2227$(E-Mail Removed):

> Please help,
>
> I have recently switched from nod version 1 to version 2 running under
> xp home. I often disable amon if I install a new program or am gaming,
> to avoid installation problems and to stop it using system resources.
> After I re-enable amon everything is fine until I shutdown at the end
> of my session. At this point (more often than not) my pc crashes. Upon
> reboot i get a "system has recovered from serious error" message and
> am asked whether i want to submit information to microsoft. If I
> submit the info I am taken to the microsoft online crash analysis
> which tells me a device driver has caused the problem but it cant tell
> me which one. I have painstakingly rounded up all of the latest
> drivers for my hardware but still the problem persists. However it
> only ever happens if i disable amon and then re-enable. Has anyone
> else ever experienced this problem? I have nod v2 on other machines
> and have tried to replicate the problem on them but it seems
> rock-solid. It just seems to happen on my home pc. I have had my
> memory and cpu tested and they are ok. Could it be an incompatibility
> with nforce 2 chipset. (The other machines i've tried it on were not
> nforce).
>
> tia
>
> matthew jones
>
>

Same here I just switched to XP on one machine and installing software,
SP(s), Hot fixes, etc. etc. and AMON is running. I don't have any
problems in doing it.

Duane

"Matthew Jones" <(E-Mail Removed)> wrote in message
news:PVdnb.2227$(E-Mail Removed)...
> Please help,
>
> I have recently switched from nod version 1 to version 2 running under xp
> home. I often disable amon if I install a new program or am gaming, to
avoid
> installation problems and to stop it using system resources. After I
> re-enable amon everything is fine until I shutdown at the end of my
session.
> At this point (more often than not) my pc crashes. Upon reboot i get a
> "system has recovered from serious error" message and am asked whether i
> want to submit information to microsoft. If I submit the info I am taken
to
> the microsoft online crash analysis which tells me a device driver has
> caused the problem but it cant tell me which one. I have painstakingly
> rounded up all of the latest drivers for my hardware but still the problem
> persists. However it only ever happens if i disable amon and then
re-enable.

Call me stupid, but have you thought about *not* disabling Amon and see what
happens? Or, an even stupider question: have you contacted Eset support
about this?