|
|
#1
May 11th, 2009, 04:31 AM
|
|||
|
|||
Nod32 blue screen
Nod32 v2.7 blue screened this morning caused by amon.sys a reboot was fine. I'm not sure of the sig version as it updated immediately on the 2nd boot. Anyone else got this?
__________________
Windows 7 32bit Ultimate SP1 | MS ISA 2004 Firewall | Malwarebytes | Firefox with NoScript | Acronis True Image |
|
#2
May 11th, 2009, 06:46 AM
|
|||
|
|||
|
Re: Nod32 blue screen
2.70.39 is the latest English build . v2 is no longer developed and I doubt they'll fix it (they'll fix whatever in it) because of this fact .
I no longer use v2 on any of my own computers but haven't heard any complaint of clients re. something about NOD32 that has happened today or recently . Greetings  |
|
#3
May 12th, 2009, 07:29 PM
|
||||
|
||||
|
Re: Nod32 blue screen
Hello,
Is this the first time that ESET NOD32 Antivirus v2.x has given you a STOP message? If it becomes a reoccuring problem, try upgrading to either v3.0 or v4.0 of ESET NOD32 Antivirus and see if the same STOP message happens again. Version 3.0/4.0 has an improved GUI and enchanced capabilities for the detection of malware. Regards, Mark.
__________________
ESET NOD32 Antivirus v6 |
|
#4
May 16th, 2009, 02:19 PM
|
|||
|
|||
|
Re: Nod32 blue screen
I beleive it is the send blue screen I've had from Nod32 on my computer. I do not want to "upgrade" to v3 or v4 because firstly I have a server network & only v2.7 is "fully" supported & secondly because I have been seeing many other types of problems running both v3 & v4.
__________________
Windows 7 32bit Ultimate SP1 | MS ISA 2004 Firewall | Malwarebytes | Firefox with NoScript | Acronis True Image |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|
