Nod32 blue screen

Discussion in 'NOD32 version 2 Forum' started by Biscuit, May 11, 2009.

Thread Status:
Not open for further replies.
  1. Biscuit

    Biscuit Registered Member

    Joined:
    May 26, 2006
    Posts:
    978
    Location:
    Isle of Man
    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?
     
  2. ASpace

    ASpace Guest

    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 :thumb:
     
  3. xMarkx

    xMarkx Registered Member

    Joined:
    Dec 1, 2008
    Posts:
    447
    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.
     
  4. Biscuit

    Biscuit Registered Member

    Joined:
    May 26, 2006
    Posts:
    978
    Location:
    Isle of Man
    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.
     
Thread Status:
Not open for further replies.